Replies: 1 comment
-
I think, nx should not ignore the projects in .gitignore. There are use cases when a developer wants to have a local playground project within the monorepo without the risk of accidentally committing it. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I just wasted four hours trying to work this out, because yet again. something critical was glossed over.
Suggestions
.gitignore
behaviour should be very obviously mentioned in all the migration tutorials.nxignore
page needs to say more than.nxignore
is the same format as.gitignore
... probably even have an equivilant page called.gitignore
1. Ran through the getting started:
nx nx@latest init
✅@nx/js
installs. so i add that.@nx/next
✅yarn nx g @nx/next:app web
✅src
directory.2. try to work out what's broken
project.json
,nx.json
over to the first monorepo... maybenx init
is broken andnpx create-nx-workspace@latest
is not. I dont know and i'm not going to spend the rest of my weekend examining source code of nx.dev to work that out.3. Start reading nx docs website in detail
project.json
? did i miss something? no. everything looks normalproject ignored
orproject not found
. there's one or two, but in the end not able to help my scenario.4. start trying random things
.gitignore
. think, maybe this is something? nah surely not..gitignore
has this much importance on the dep graph.Beta Was this translation helpful? Give feedback.
All reactions