Skip to content
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

[BUG] next --init doesn't output anything to stdout even though it works #119

Open
etagwerker opened this issue Aug 2, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@etagwerker
Copy link
Member

Hi there! 👋🏼

Expected Behavior

Running next --init I'd expect it to output _something to the console. For example:

Created symlink Gemfile.next from Gemfile

And/or:

Copied Gemfile.lock -> Gemfile.next.lock

Actual Behavior

After calling next --init I only see a blank line:

➜  foo git:(upgrade-rails-7-1) ✗ next --init

Possible Fix

More verbose output?

To Reproduce

  1. Add next_rails to your Gemfile (v1.3.0)
  2. bundle
  3. Call command: next --init
  4. You should see the empty output there

Additional Information

I'm working on a migration project using these versions:

  • Current dev environment: Apple M3 Max (ARM)
  • Rails 7.0 to 7.1
  • Ruby 3.2.3

Thanks!

I will abide by the code of conduct

@etagwerker etagwerker added the bug Something isn't working label Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant