You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As @amb26 and others are urging us to move more towards using monorepos in our work, we need for fluid-publish to understand our conventions and assist us in publishing releases to npm.
It would need to be able to publish the outermost package as well as any sub-packages that are intended for separate reuse.
The text was updated successfully, but these errors were encountered:
We've had some conversations with @colinbdclark in the meantime about the extra requirements on fluid-publish. It seems that an important extra one is synthesizing internal module references into the package.json of the nested projects based on some declarative information. It's already been long enough that I can't completely recall the reasoning behind this - we should start to have meetings on this topic early as the New Year starts.
As @amb26 and others are urging us to move more towards using monorepos in our work, we need for fluid-publish to understand our conventions and assist us in publishing releases to npm.
It would need to be able to publish the outermost package as well as any sub-packages that are intended for separate reuse.
The text was updated successfully, but these errors were encountered: