I currently am developing a TypeScript shared library. The library needs to be imported in sections to minimize the imported bundle size, so I broke it up into packages with a monorepo with Lerna. Things are going great. Each package has its own dist folder and each of those are published to the GitHub artifact store for consumption by other applications. The expectation was that I'd unit test the library and any updates would be published as new versions to this store.
But a new requirement is shaking things up. Normally if I'd like to develop a library in tandem with the application that's consuming it, I'd provide a local URL to the package.json. But for a mono repo, this doesn't work. The URL points to a different file structure than what is expected.
This is leading to all kinds of headaches. The host applications are dockerized, so it's leaning to over-complicated solutions like Rsyncing over the files, setting up custom volumes and build locations, or literally copy pasting the library's source into the host app for momentary use.
I feel like I'm reinventing the wheel here. What do other folks do for developing a mono repo library through other applications? My preference would be to just test the library well and then iterate as new requirements arise, but that's not an option anymore.
TypeScript is used for the build step.
Lerna helps with having each different piece of the library be in a different
Each package has its own package.json, in which: