[BUG] next command clashes with next from Next.js library

[etagwerker]

Expected Behavior

next command should not clash with another library's command.

Actual Behavior

After running these steps:

npm install -g next
next start

I'd like it to use the next.js command.

Possible Fix

Rename the next_rails command to be next_rails so that it doesn't clash with Next.js's next command.

To Reproduce

1. gem install next_rails
2. npm install -g next
3. git clone a next project
4. next start

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