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
App generator fails with webpacker error #37453
Comments
@JorgeDDW is right, I reproduced the issue |
As a temporary solution you can create and fill webpacker.yml manually and run |
But @JorgeDDW is trying to |
As you say.. |
So, I tried and get something weird
I am on Ubuntu 19.04 and using Ruby 2.5.5p157. |
Yes, it must be running after project creation
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
rails/webpacker#2301 is a proposed fix for this issue. |
Small info from a rails newcomer: on Friday 8th 2019 the default PS: I use the standard rails command, not edge, just the default rails command of 6.0.1 (current stable). |
Webpacker 4.1.0 was released two hours ago, which is why this error now happens even without the @gouravtiwari 👋 |
Thanks for raising the issue, it seems to have worked when I tested locally after release but I can reproduce now. Will look into it. |
@eugenebolshakov @ytbryan Could you please check this pr? rails/webpacker#2366 |
I can confirm that using that branch resolves the issue:
👍 |
Released 4.2.0 |
Thanks for the quick fix @gauravtiwari ❤️ Closing as both |
This same webpacker errors occurs under Rails 6.0.2.1 and webpacker 4.2.2 with a brand new rails command stacktrace$ bin/rails The most common rails commands are: generate Generate new code (short-cut alias: "g") console Start the Rails console (short-cut alias: "c") server Start the Rails server (short-cut alias: "s") test Run tests except system tests (short-cut alias: "t") test:system Run system tests dbconsole Start a console for the database specified in config/database.yml (short-cut alias: "db") To be fair, I'm experimenting with a weird setup in which I'm using the macOS system Ruby (hence |
Steps to reproduce
Expected behavior
using:
rails new project --edge --database=postgresql --skip=turbolinks --skipt-test
Actual behavior
System configuration
Rails version:
6.0
Ruby version:
2.6.5
The text was updated successfully, but these errors were encountered: