After a quick discussion in Gitter, I was asked to create an issue with my workflow to see if there is a bit configuration that would fit me well :)
Basically what I was/am hoping bit will be, is a way to have source-code only packages.
Essentially the same thing as git submodules but the benefits of a) not having to authenticate - I am only interested in private packages b) not having to create a repository for every micropackage I have.
It's perfect because I have multiple clients and I reuse a lot of stuff so putting into packages was a great idea.
I was very close to achieving this using the saveDependenciesAsComponents option but I ran into an issue when I had App -> lib1 -> lib2. This still requires bit link to run before the build which doesn't make sense given that bit import will establish file: equivalencies in package.json
The other problem I have is that I am using an Azure App Service and it doesn't like symlinks. It's probably the same deal with this: yarnpkg/yarn#6621
After a quick discussion in Gitter, I was asked to create an issue with my workflow to see if there is a bit configuration that would fit me well :)
Basically what I was/am hoping bit will be, is a way to have source-code only packages.
Essentially the same thing as git submodules but the benefits of a) not having to authenticate - I am only interested in private packages b) not having to create a repository for every micropackage I have.
It's perfect because I have multiple clients and I reuse a lot of stuff so putting into packages was a great idea.
I was very close to achieving this using the
saveDependenciesAsComponentsoption but I ran into an issue when I hadApp -> lib1 -> lib2. This still requiresbit linkto run before the build which doesn't make sense given thatbit importwill establishfile:equivalencies inpackage.jsonThe other problem I have is that I am using an Azure App Service and it doesn't like symlinks. It's probably the same deal with this: yarnpkg/yarn#6621