Open etagwerker opened 7 months ago
next command should not clash with another library's command.
next
After running these steps:
npm install -g next next start
I'd like it to use the next.js command.
Rename the next_rails command to be next_rails so that it doesn't clash with Next.js's next command.
next_rails
See something like this:
rbenv: next: command not found The `next' command exists in these Ruby versions: 2.7.2 3.0.4 3.1.3 3.2.2
Then you can check which next command is getting used:
which next /Users/etagwerker/.rbenv/shims/next
I will abide by the code of conduct
Expected Behavior
next
command should not clash with another library's command.Actual Behavior
After running these steps:
I'd like it to use the next.js command.
Possible Fix
Rename the
next_rails
command to benext_rails
so that it doesn't clash with Next.js'snext
command.To Reproduce
See something like this:
Then you can check which
next
command is getting used:I will abide by the code of conduct