Webpack dev server cannot start at first hivemind in Part 1
Adsidera opened this issue · comments
hello, I encounter this problem when trying to launch hivemind
for the first time in part 1 of the tutorial. The webpack-dev-server cannot start,
hivemind
assets | Running...
server | Running...
server | => Booting Puma
server | => Rails 5.1.5 application starting in development
server | => Run `rails server -h` for more startup options
assets | /Users/adsidera/projects/webpack/evil_chat/node_modules/webpack-dev-server/bin/webpack-dev-server.js:405
assets | throw e;
assets | ^
assets |
assets | TypeError: Cannot read property 'compile' of undefined
assets | at addCompilerHooks (/Users/adsidera/projects/webpack/evil_chat/node_modules/webpack-dev-server/lib/Server.js:71:15)
assets | at new Server (/Users/adsidera/projects/webpack/evil_chat/node_modules/webpack-dev-server/lib/Server.js:81:5)
assets | at startDevServer (/Users/adsidera/projects/webpack/evil_chat/node_modules/webpack-dev-server/bin/webpack-dev-server.js:398:14)
assets | at processOptions (/Users/adsidera/projects/webpack/evil_chat/node_modules/webpack-dev-server/bin/webpack-dev-server.js:361:5)
assets | at Object.<anonymous> (/Users/adsidera/projects/webpack/evil_chat/node_modules/webpack-dev-server/bin/webpack-dev-server.js:504:1)
assets | at Module._compile (module.js:573:30)
assets | at Object.Module._extensions..js (module.js:584:10)
assets | at Module.load (module.js:507:32)
assets | at tryModuleLoad (module.js:470:12)
assets | at Function.Module._load (module.js:462:3)
assets | exit status 1
server | Interrupting...
server | Exiting
server | Process exited
Hi! There is in fact an issue with webpack-dev-server
and Rails 5.1.5, we are trying to investigate and will keep you updated
Perhaps, you can try downgrading webpack-dev-server
as described here rails/webpacker#1303
thanks @progapandist I will try :)
yarn upgrade -D webpack-dev-server@^2.11.1
just worked for me, seems to be the only solution till the incompatibility with 5.1.5 is fixed
Hope it worked! Feel free to re-open the issue if necessary