Investigate possibilities to move TurboRepo config to app repository

[ricardovdheijden]

When adding dependencies to our SURF specific app we need to update the package-lock in the orchestrator-ui-library repository.

Trying to solve:

• The need to expose the dependencies of our internal project to the open source repository by updating the package-lock.json
• Make it easier for contributors to work on their own app and contribute to our orchestrator-ui-library repository

Open questions (also mentioned in the Powerpoint):

• Is it possible to use the example-orchestrator-ui without the need to clone packages for a "consumer" who is using the component-library to work on the app? The usecase of a consumer is in contrast with a "contributor" who need to work on both the app and component-library at the same time.
• Related to previous question: is it possible to pin to a specific version of the orchestrator-ui in the package-lock.json? This is needed to build the app in a pipeline for a release. We need to be able to build the app using a specific version of the component-library

Attachment for a visual representation of the current setup and the suggested new setup. See slide-notes for some textual context:
Monorepo-v2.pptx

---

• First try to set the package-lock to local
  • see https://chatgpt.com/share/6759b244-86ec-800c-a54c-c4524c8d070a

[ricardovdheijden]

The quick fix mentioned in the chatGpt suggestion is not working, it suggests to disable parts of the npm workspace. However TurboRepo is building on top of the functionalities of npm workspace. Therefore the initial suggested setup might be the way to go in case we want to provide better support for contributors.