-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package scopes other than project name? #87
Comments
The scope can be set separately here: Having different scopes for different libraries is a reasonable use case. So at some point we will probably implement it. |
Hello @vsavkin
So the first two points are decisions made on the feasibility, but for the last point, semantic-release, I am still evaluating the way (not the if). So what I want to suggest ist perhaps that you document in a few words, sentences or paragraphes which differences from your monorepo approach to the one built with lerna. |
For default Nx projects: We aren't considering using lerna within the workspace, only to connect the workspace to other projects, similar to how you would use "yarn workspaces" (https://blog.nrwl.io/dev-workflow-using-git-submodules-and-yarn-workspaces-14fd06c07964). For your project: |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Currently it seems nrwl/nx takes an opinionated approach to monorepos which isn't yet as flexible as nor compatible to Lerna monorepo structure. E.g. all libraries in a workspace inherit the package scope from the workspace/project name which works for company policies like always use a project scope for libraries. Lets pretend two other reasonable scenarios/policies:
Can these policies be met with nrwl/nx workspaces? For example is there a means/plans to read a default package scope from a config file in a users $HOME (would help to meet 1.) or to allow defining scopes on library generation (would help to meet both)? I couldn't see a
package.json
or proper folder structure being generated for libs so I assume the second is not possible as of today (ng generate lib @foo/mylib
didn't work 😢 ).Note: I'd be satisfied with an answer and leave it open to the maintainers or community whether to handle the issue as a question or feature request.
Thank you.
The text was updated successfully, but these errors were encountered: