Description
UPDATE
The current setup is Yarn 3.6.3 which does not use the PnP, which means, we're still using node_modules. After several tries, there seems to be issues with multiple same packages in the same monorepo, and yarn doesn't seem to be respecting this behavior.
The alternative is create the isolated apps and treat them as such, and don't let them build with the monorepo.
Updating this issue to keep track.
Issue:
Before I made the changes, I was able to add the internal packages as a dependencies, but I ran into an issue when I packaged and published a package with workspace in the version.
The packages are now pinned to the latest version but it does not help in this development, because it is easier test via hoisting, rather than pinning a version and publishing a version to test the changes.
Opening a ticket to track this behavior.
Contributor Guides and Resources
- 🛠 Meshery Build & Release Strategy
- 📚 Instructions for contributing to documentation
- 🎨 Wireframes and designs for Layer5 site in Figma (open invite)
- 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack