-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
webpacker is installed... ./bin/webpack: not found #379
Comments
Perhaps you need to run |
@btc i just tried your suggestion but unfortunately it didn't work. i get the same error. this line https://github.com/rails/webpacker/blob/master/lib/tasks/webpacker/compile.rake#L11 |
What's your rails version? Are you using rails 5? I think it's because you are lacking the binstub And what's your webpacker's version? |
@ytbryan you are right. i have a bin folder on my local machine but not on the remote server. my webpacker version is 1.2, my rails version is 5.0.2 (i am blocked from upgrading to 5.1.0 by a dependency) |
i ran ok, so the problem seems to be that the auto-generated .gitignore file from rails 4.x has the bin folder in the .gitignore file. i'm going to play around with not .gitignoring the bin folder and see if that resolves the issue |
the issue was caused by the bin folder not being present, and updating the .gitignore file and redeploying fixed it. |
What's the solution for getting the webpack binstubs? in a rails 5.0.2 app? same as OP can't upgrade to 5.1 yet. |
@raldred Did you run |
Doh. '~> 2.0'. I guess I assumed |
@raldred , same problem, I am assumed webpacker:install:react would auto generate all config files |
I also experienced this issue while trying to add webpacker to an existing rails app. Trying to run |
* webpack or webpack-dev-server not found Add to troubleshooting of readme to prevent such issues #379 (comment), #506 * Update README.md * Update README.md * Include solution for error occurring in heroku * Update README.md Since it is known that node buildpacks is not necessary Read: #522 (comment) * Update README.md * Update README.md Include instruction while upgrading from rails 4 to 5. * Minor update * Use ./bin/rails * Add as comment
Running rails 4.2. I also had to |
* webpack or webpack-dev-server not found Add to troubleshooting of readme to prevent such issues rails/webpacker#379 (comment), rails/webpacker#506 * Update README.md * Update README.md * Include solution for error occurring in heroku * Update README.md Since it is known that node buildpacks is not necessary Read: rails/webpacker#522 (comment) * Update README.md * Update README.md Include instruction while upgrading from rails 4 to 5. * Minor update * Use ./bin/rails * Add as comment
I had this problem ( |
Follow pattern at rails/webpacker#379 (comment) to attempt to fix webpack.
I also has the same problem, and I reinstall
many time >"< |
I also having the issues. |
Install webpack manually on your server:
cd /var/www/your_project/releases/your_release_timestamp
yarn
|
* webpack or webpack-dev-server not found Add to troubleshooting of readme to prevent such issues rails/webpacker#379 (comment), rails/webpacker#506 * Update README.md * Update README.md * Include solution for error occurring in heroku * Update README.md Since it is known that node buildpacks is not necessary Read: rails/webpacker#522 (comment) * Update README.md * Update README.md Include instruction while upgrading from rails 4 to 5. * Minor update * Use ./bin/rails * Add as comment
* webpack or webpack-dev-server not found Add to troubleshooting of readme to prevent such issues rails/webpacker#379 (comment), rails/webpacker#506 * Update README.md * Update README.md * Include solution for error occurring in heroku * Update README.md Since it is known that node buildpacks is not necessary Read: rails/webpacker#522 (comment) * Update README.md * Update README.md Include instruction while upgrading from rails 4 to 5. * Minor update * Use ./bin/rails * Add as comment
I'm not sure how to interpret this error that I get when trying to precompile assets on the server.
The text was updated successfully, but these errors were encountered: