Common Errors & Solutions

ERROR: Missing Manifest error in browser

Error:

# Error displayed in browser
Description:
Webpacker::Manifest::MissingEntryError at /kits/button
Webpacker can't find main in /home/app/src/lib/../public/packs/manifest.json.

Solution #1

This error is most often seen if you try to load http://localhost:8080 in the browser before webpacker has finished compiling assets.

Make sure to wait for your terminal to display Compiled Successfully as the last line before loading in browser window.

Solution #2

If you did wait for terminal to display Compiled Successfully, but still see the error in your browser...

Open terminal, and scroll up. Do you see a lot of SCSS errors referring to node-sass requiring a rebuild or Node Sass could not find a binding?

# In terminal run the following commands
$ make shell
$ yarn add --force node-sass
$ exit
$ make start

ERROR: Rebuild Node-Sass error

Error:

# Error displayed in terminal
$ webpacker_1  | Node Sass could not find a binding for your current environment: Linux 64-bit with Node.js 8.x
$ webpacker_1  |
$ webpacker_1  | Found bindings for the following environments:
$ webpacker_1  |   - OS X 64-bit with Node.js 8.x
$ webpacker_1  |
$ webpacker_1  | This usually happens because your environment has changed since running `npm install`.
$ webpacker_1  | Run `npm rebuild node-sass` to download the binding for your current environment.

Solution:

# In terminal run the following commands
$ docker-compose run web yarn add --force node-sass

ERROR: Server Already Running, PID error

Solution:

# In terminal run the following commands
$ make shell
$ rm /home/app/src/spec/dummy/tmp/pids/server.pid
$ exit
$ make start

ERROR: Can't find clean-webpack-plugin or can't find webpack-dev-server

# Error displayed in terminal
$ webpacker_1  | can't find clean-webpack-plugin

# Error displayed in terminal
$ webpacker_1  | can't find webpack-dev-server

Solution

# In terminal run the following commands
$ docker-compose run web yarn