fb318005f2
For the new TS setup, we currently use nested glob patterns: `apps/**`, `libs/**`, and `packages/**`. Nested paths can result into too many projects being matched. For example, if `libs/mylib/src/__fixtures__/package.json` is there for testing, it will be matched as a project and likely result in an error. Other tools like turborepo also caution against this: https://turbo.build/repo/docs/crafting-your-repository/structuring-a-repository#declaring-directories-for-packages If users want to, they could change to nested `**` paths, but we should not use it by default. Note: For CNW, we only use `apps/*` by default since that is where the project lives. When users do `nx g lib packages/foo` then `packages/*` will be added automatically. <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> Use nested `**` paths. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> Don't use nested `**` paths. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
{{links}}
> npx create-nx-workspace
Nx is a build system, optimized for monorepos, with plugins for popular frameworks and tools and advanced CI capabilities including caching and distribution.
What is It?
It's a command to create a new Nx workspace.
{{content}}