Command "webpack-dev-server" not found. #506

luispcosta · 2017-06-15T16:40:55Z

I'm trying to create a new project with webpacker in rails and I constantly get the error

yarn run v0.24.6
error Command "webpack-dev-server" not found.

When trying to launch the dev server.

Run down of the commands:

rails new testapp--webpack
./bin/rails webpacker:install:vue
./bin/webpack-dev-server
yarn run v0.24.6
error Command "webpack-dev-server" not found.

System configuration

Rails: 5.1.1
Ruby: 2.4.1p111
Node: v6.10.2
Yarn: v0.24.6
OS: Ubuntu 16.10

I'm also running this on a Vagrant machine with the version 1.9.3

I tried doing:

$ sudo npm install -g webpack-dev-server
$ npm install (from the rails project folder)
$ yarn
$  ./bin/yarn install

Nothing seems to work. Any help?

Thanks!

The text was updated successfully, but these errors were encountered:

gauravtiwari · 2017-06-15T17:59:52Z

@luispcosta Is webpacker installed i.e. config/webpack exists and all node_modules are bundled? Check node_modules folder please.

luispcosta · 2017-06-17T15:21:30Z

You're right. config/webpack doesn't exist. node_modules exists, and it contains webpack-dev-middleware and webpack-dev-server amongst other stuff.

What do I have to do to have config/webpack ?

Edit: Actually I do have the config/webpack folder.

ytbryan · 2017-06-18T09:29:16Z

@luispcosta you should do rails:webpacker:install

Because rails new testapp--webpack there is a missing space

Therefore, rails:webpacker:install not called. Therefore you don't have a config/webpack.

gauravtiwari · 2017-06-18T10:43:43Z

Thanks @ytbryan. @luispcosta as suggested could you please re-run bundle exec rails webpacker:install and see if ./bin/webpack-dev-server works for you?

gauravtiwari · 2017-06-18T10:45:07Z

Also could you please check your node_modules/.bin folder? See if you can run ./node_modules/.bin/webpack-dev-server manually (this won't work but just to check)

* 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

gauravtiwari · 2017-06-22T08:03:12Z

@luispcosta Does the above suggestions work?

luispcosta · 2017-06-22T08:09:04Z

Hey @gauravtiwari . Sorry for the late response, but no, it didn't work :\ I had the config/webpack folder all along, that wasn't the issue. I don't know if it is any problem related with yarn or node, but everything seems to be installed correctly. I even tried it from a new fresh rails project but it didn't work either. Not sure what's going on

ytbryan · 2017-06-22T08:12:44Z

@luispcosta can you push that fresh rails project on github ? and share with us?

luispcosta · 2017-06-22T08:15:04Z

@ytbryan Sure, I can do it, but I can only do it later today. I'll ping here when I do it

gauravtiwari · 2017-06-22T08:25:40Z

@luispcosta Seems like something to do with node or yarn. Are you able to manually run those executables? - ./node_modules/.bin/webpack-dev-server or yarn run webpack-dev-server

gauravtiwari · 2017-06-30T21:34:14Z

@luispcosta Were you able to get this to work?

ghost · 2017-07-25T01:33:38Z

I know this issue was closed, but I had the same problem.

In my case, the commands to configure wepacker didn't add the webpack-dev-server on the package.json, should it do it 🤔 ? I've solved it installing manually by yarn: yarn add webpack-dev-server.

gauravtiwari · 2017-07-25T07:31:34Z

@frenangomes Yes if you have run bundle exec rails webpacker:install it should add that automatically for you. Perhaps the command exited prematurely due to an underlying error with node or yarn version. Could you check that please, trying running this command again - bundle exec rails webpacker:install?

ghost · 2017-07-25T13:51:31Z

@gauravtiwari I had executed webpacker:install but it didn't add webpack-dev-server automatically. Testing it on another project it works very well, so I think it's a specific problem with my project, already I have updated Rails from 4.2 to 5.1.

I think the solution is this PR that was mentioned here. I didn't see it, my bad 😞 . I'll try it later.

tarr11 · 2017-08-16T17:51:04Z

I had this same problem (randomly - on a project that had been working fine for months) - I think it had something to do with npm messing up my node_modules.

Running bundle exec rails webpacker:install and clicking n to every suggestion worked fine for me.

hovancik · 2017-08-21T07:52:40Z

I have the same issue on docker. When I am on linux machine, everything works. On macOS, it does not. From my docker-compose.ym

command: bundle exec bin/webpack-dev-server

webpacker_1  | yarn run v0.27.5
webpacker_1  | error Command "webpack-dev-server" not found.
webpacker_1  | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

ruby '2.4.1'
gem 'rails', '~> 5.1.3'

I created new app with

docker-compose build
docker-compose run web rails new . --force --database=postgresql --webpack=vue --skip-coffee --skip-turbolinks --skip-action-cable
docker-compose build

gauravtiwari · 2017-08-21T08:12:37Z

@hovancik Could you please remove node_modules folder and do yarn install?

gauravtiwari · 2017-08-21T08:14:31Z

Also you may want to use latest master where we have removed yarn run but for that you would need to reinstall webpacker. bundle exec rails webpacker:install after bundle update webpacker

Note: Also re-update webpacker.yml if you have changed the defaults after upgrade :)

hovancik · 2017-08-21T08:29:52Z

Thanks, works now with new yarn install.

* 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

HarikrishnaDS · 2018-03-11T11:15:36Z

I have installed yarn, foreman and also added it in Gemfile.
I create a Procfile as
rails: bundle exec rails server
webpack: bin/webpack-dev-server

When I run foreman start its showing error. I have been trying from 4 days couldn't find any solution to help me to fix this. Please help me!!!!!!!!!!!!!

C:\Sites\shine>foreman start
C:/RailsInstaller/Ruby2.3.3/lib/ruby/gems/2.3.0/gems/foreman-0.84.0/lib/foreman/process.rb:54:in spawn': Exec format error - bin/webpack-dev-server (Errno::ENOEXEC) from C:/RailsInstaller/Ruby2.3.3/lib/ruby/gems/2.3.0/gems/foreman-0.84.0/lib/foreman/process.rb:54:in block in run'
from C:/RailsInstaller/Ruby2.3.3/lib/ruby/gems/2.3.0/gems/foreman-0.84.0/lib/foreman/process.rb:53:in chdir' from C:/RailsInstaller/Ruby2.3.3/lib/ruby/gems/2.3.0/gems/foreman-0.84.0/lib/foreman/process.rb:53:in run'
from C:/RailsInstaller/Ruby2.3.3/lib/ruby/gems/2.3.0/gems/foreman-0.84.0/lib/foreman/engine.rb:366:in block (2 levels) in spawn_processes' from C:/RailsInstaller/Ruby2.3.3/lib/ruby/gems/2.3.0/gems/foreman-0.84.0/lib/foreman/engine.rb:363:in upto'
from C:/RailsInstaller/Ruby2.3.3/lib/ruby/gems/2.3.0/gems/foreman-0.84.0/lib/foreman/engine.rb:363:in block in spawn_processes' from C:/RailsInstaller/Ruby2.3.3/lib/ruby/gems/2.3.0/gems/foreman-0.84.0/lib/foreman/engine.rb:362:in each'
from C:/RailsInstaller/Ruby2.3.3/lib/ruby/gems/2.3.0/gems/foreman-0.84.0/lib/foreman/engine.rb:362:in spawn_processes' from C:/RailsInstaller/Ruby2.3.3/lib/ruby/gems/2.3.0/gems/foreman-0.84.0/lib/foreman/engine.rb:57:in start'
from C:/RailsInstaller/Ruby2.3.3/lib/ruby/gems/2.3.0/gems/foreman-0.84.0/lib/foreman/cli.rb:42:in start' from C:/RailsInstaller/Ruby2.3.3/lib/ruby/gems/2.3.0/gems/thor-0.19.4/lib/thor/command.rb:27:in run'
from C:/RailsInstaller/Ruby2.3.3/lib/ruby/gems/2.3.0/gems/thor-0.19.4/lib/thor/invocation.rb:126:in invoke_command' from C:/RailsInstaller/Ruby2.3.3/lib/ruby/gems/2.3.0/gems/thor-0.19.4/lib/thor.rb:369:in dispatch'
from C:/RailsInstaller/Ruby2.3.3/lib/ruby/gems/2.3.0/gems/thor-0.19.4/lib/thor/base.rb:444:in start' from C:/RailsInstaller/Ruby2.3.3/lib/ruby/gems/2.3.0/gems/foreman-0.84.0/bin/foreman:7:in <top (required)>'
from C:/RailsInstaller/Ruby2.3.3/bin/foreman:23:in load' from C:/RailsInstaller/Ruby2.3.3/bin/foreman:23:in

'

gauravtiwari · 2018-03-11T11:55:27Z

Have you installed webpacker after adding to your Gemfile?

bundle exec rails webpacker:install

HarikrishnaDS · 2018-03-11T12:27:36Z

@gauravtiwari Yes I had executed the same command and when I run foreman start still getting the same error.
I even executed bundle install command too.

My gemfile looks like

Attached image after executing bundle exec rails webpacker:install

gauravtiwari · 2018-03-11T18:01:16Z

What happens if you run bundle exec rails webpacker:binstubs?

HarikrishnaDS · 2018-03-11T18:14:21Z

@gauravtiwari I executed the command you sent the result is attached below

gauravtiwari · 2018-03-11T18:36:48Z

Ahh right so it's there. Could you please run it like so: ruby ./bin/webpack-dev-server from Procfile?

HarikrishnaDS · 2018-03-11T18:43:18Z

@gauravtiwari It's throwing some error as;

gauravtiwari · 2018-03-11T18:44:19Z

Ahh right so it seems you got the latest dev server installed which is only works with 4.0. Please could you do: yarn add [email protected] and then run the command.

HarikrishnaDS · 2018-03-11T18:50:02Z

I executed yarn add [email protected] it installs few packages. Then I executed ruby ./bin/webpack-dev-server it runs successfully.

Then I run foreman start still its showing same error.

gauravtiwari · 2018-03-11T19:54:41Z

What error are you getting with foreman start ? Have you changed foreman command to use ruby ./bin/webpack-dev-server?

HarikrishnaDS · 2018-03-11T20:00:03Z

@gauravtiwari I changed my Procfile as

Then when I run foreman start it shows error as

gauravtiwari · 2018-03-11T20:17:40Z

Looks like there is some syntax error in Gemfile on line 13.

HarikrishnaDS · 2018-03-11T20:23:46Z

@gauravtiwari At line 13 there was gem 'devise'. I removed it and run foreman start now its showing

But localhost:5000 not working in browser

gauravtiwari · 2018-03-11T20:34:13Z

What happens if you run bundle exec rails s? - looks like since you removed devise, there might be configuration still present in config/initializers. It was actually some syntax issue probably the quote was wrong in the Gemfile, so fix that instead of removing devise.

HarikrishnaDS · 2018-03-11T20:41:21Z

@gauravtiwari bundle exec rails s is working fine after removing gem 'devise'. I can open localhost:3000 in browser successfully.

But when I add gem 'devise' in Gem file, if i run bundle exec rails s it's showing errors as

gauravtiwari · 2018-03-11T20:54:21Z

Not sure what's wrong there. Can you manually type gem 'devise' into your Gemfile? (make sure quotes are correct)

HarikrishnaDS · 2018-03-11T21:00:18Z

@gauravtiwari I changed its position i.e., after gem 'rails' and run bundle install. Now bundle exec rails s is working fine.
But when i run foreman start its not showing any http port i.e. localhost:5000. It's showing as I send a screenshot earlier as

abineetds · 2018-04-03T23:49:48Z

Facing the same issue. Any solution to this?

gauravtiwari · 2018-04-04T08:04:51Z

Could you please make an example repo?

abineetds · 2018-04-04T21:44:54Z

https://bitbucket.org/abineetds/qiggleonrails
I can run the rails server but am having the same issue when trying to run foreman to run webpack-dev-server simultaneously.
I'm running on a 64-bit Windows 10 machine.

juantoniomac · 2018-04-09T23:01:16Z

@abineetds could you find a solution for your issue? I have exactly the same issue in Windows 10 machine too

abineetds · 2018-04-10T19:12:34Z

Sadly no. Just not using hot reloading at the moment. Slow, but works.

gauravtiwari · 2018-04-10T19:50:40Z

@abineetds Are you able to run webpack dev server without foreman?

ruby ./bin/webpack-dev-server

abineetds · 2018-04-10T20:00:28Z

Yes it does run, but on navigating to localhost:3035, I get what looks like a routing error. no GET for /.
I got past the ENOEXEC error in foreman, by using this.
webpacker: ruby ./bin/webpack-dev-server

Now what I see is this:

13:00:07 web.1       | started with pid 9772
13:00:07 webpacker.1 | started with pid 20120
13:00:10 webpacker.1 | exited with code 0
13:00:10 system      | sending SIGKILL to all processes
13:00:10 system      | sending SIGKILL to web.1 at pid 9772
13:00:10 web.1       | exited with code 0

gauravtiwari · 2018-04-10T20:16:19Z

You don't need to go to localhost:3035 if dev server is running fine. Try navigating to rails s url:

Run following in separate terminal windows (without foreman):

bundle exec rails s
ruby ./bin/webpack-dev-server

Navigate to localhost:3000 or whatever rails s URL is.

The home views should load javascript/packs if you have included javascript_pack_tag to it.

gauravtiwari · 2018-04-10T20:18:05Z

Have you tried invoker or https://github.com/ddollar/forego on windows?

abineetds · 2018-04-10T20:41:02Z

Hey @gauravtiwari,

That actually worked. I'm just running rails s in one Powershell window and ruby ./bin/webpack-dev-server in another.

Thanks a ton! I'll try out your other recommendations too.

@juantoniomac This might work for you.

kingpalethe · 2018-04-11T05:52:29Z

Interestingly, this issue was closed but recently sprang to life, and I am having a similar problem (really more of "syndrome") which I have reported in this issue: #1419

christiangenco · 2018-09-10T17:51:53Z

I was missing a package.json file, which wasn't getting initialized when I ran rails webpacker:install.

Running yarn init, then rails webpacker:install added these dependencies:

  "dependencies": {
    "@rails/webpacker": "3.5"
  },
  "devDependencies": {
    "webpack-dev-server": "2.11.2"
  }

and then bin/webpack-dev-server worked.

diegocharles · 2019-01-20T16:06:38Z

I was missing a package.json file, which wasn't getting initialized when I ran rails webpacker:install.

Running yarn init, then rails webpacker:install added these dependencies:
  "dependencies": {
    "@rails/webpacker": "3.5"
  },
  "devDependencies": {
    "webpack-dev-server": "2.11.2"
  }
and then bin/webpack-dev-server worked.

That worked fine to me, Thanks. What's the login here? I'm using rails 5.2.2 and I thought rails:webpacker:install was supposed to do all the job.

gsum · 2019-03-04T20:41:10Z

for me command yarn did the trick.

gouthamganesh9889 · 2019-04-15T04:35:59Z

ruby ./bin/webpack-dev-server

When I run this it says no such file or directory. Any idea what I should do? Thanks

Install webpacker in dependencies instead of devDependencies per rails/webpacker#506 (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

koroglumert · 2023-12-14T21:45:06Z

It's 2023 and I'm having this problem and I still can't solve it. Even the npm install webpack-dev-server -g suggestion didn't work.
I'm trying to uninstall the open source project on macOS. My two containers give the error sh: webpack-dev-server: not found. Can anyone help me?

project:
https://github.com/OneUptime/oneuptime/tree/release

ytbryan mentioned this issue Jun 19, 2017

webpack or webpack-dev-server not found #516

Merged

gauravtiwari closed this as completed Jul 7, 2017

mzagaja added a commit to MAPC/trailmap3 that referenced this issue Aug 9, 2019

Resolve Broken Webpacker Issue

0acc2cd

Install webpacker in dependencies instead of devDependencies per rails/webpacker#506 (comment)

Command "webpack-dev-server" not found. #506

Command "webpack-dev-server" not found. #506

Comments

luispcosta commented Jun 15, 2017

System configuration

gauravtiwari commented Jun 15, 2017

luispcosta commented Jun 17, 2017 • edited Loading

ytbryan commented Jun 18, 2017 • edited Loading

gauravtiwari commented Jun 18, 2017

gauravtiwari commented Jun 18, 2017

gauravtiwari commented Jun 22, 2017

luispcosta commented Jun 22, 2017

ytbryan commented Jun 22, 2017

luispcosta commented Jun 22, 2017

gauravtiwari commented Jun 22, 2017

gauravtiwari commented Jun 30, 2017

ghost commented Jul 25, 2017 • edited by ghost Loading

gauravtiwari commented Jul 25, 2017

ghost commented Jul 25, 2017 • edited by ghost Loading

tarr11 commented Aug 16, 2017

hovancik commented Aug 21, 2017

gauravtiwari commented Aug 21, 2017

gauravtiwari commented Aug 21, 2017

hovancik commented Aug 21, 2017

HarikrishnaDS commented Mar 11, 2018

gauravtiwari commented Mar 11, 2018

HarikrishnaDS commented Mar 11, 2018 • edited Loading

gauravtiwari commented Mar 11, 2018

HarikrishnaDS commented Mar 11, 2018

gauravtiwari commented Mar 11, 2018

HarikrishnaDS commented Mar 11, 2018

gauravtiwari commented Mar 11, 2018

HarikrishnaDS commented Mar 11, 2018

gauravtiwari commented Mar 11, 2018

HarikrishnaDS commented Mar 11, 2018

gauravtiwari commented Mar 11, 2018

HarikrishnaDS commented Mar 11, 2018

gauravtiwari commented Mar 11, 2018

HarikrishnaDS commented Mar 11, 2018

gauravtiwari commented Mar 11, 2018

HarikrishnaDS commented Mar 11, 2018

abineetds commented Apr 3, 2018

gauravtiwari commented Apr 4, 2018

abineetds commented Apr 4, 2018 • edited Loading

juantoniomac commented Apr 9, 2018

abineetds commented Apr 10, 2018

gauravtiwari commented Apr 10, 2018

abineetds commented Apr 10, 2018 • edited Loading

gauravtiwari commented Apr 10, 2018

gauravtiwari commented Apr 10, 2018 • edited Loading

abineetds commented Apr 10, 2018 • edited Loading

kingpalethe commented Apr 11, 2018

christiangenco commented Sep 10, 2018

diegocharles commented Jan 20, 2019 • edited Loading

gsum commented Mar 4, 2019

gouthamganesh9889 commented Apr 15, 2019

koroglumert commented Dec 14, 2023

luispcosta commented Jun 17, 2017 •

edited

Loading

ytbryan commented Jun 18, 2017 •

edited

Loading

ghost commented Jul 25, 2017 •

edited by ghost

Loading

ghost commented Jul 25, 2017 •

edited by ghost

Loading

HarikrishnaDS commented Mar 11, 2018 •

edited

Loading

abineetds commented Apr 4, 2018 •

edited

Loading

abineetds commented Apr 10, 2018 •

edited

Loading

gauravtiwari commented Apr 10, 2018 •

edited

Loading

abineetds commented Apr 10, 2018 •

edited

Loading

diegocharles commented Jan 20, 2019 •

edited

Loading