We've moved discussions to Discord

Join Discord

Error on clean install

Manuel Crosthwaite •
I am setting up everything to start a new project and I'm unable to make it run properly

i get the following error, and the thing is I don't want to mess it up, so I can keep getting updates from the jumpstart repo


Webpacker::Manifest::MissingEntryError in Static#index



Webpacker can't find application.css in /sites/project/public/packs/manifest.json. Possible causes:
1. You want to set webpacker.yml value of compile to true for your environment
   unless you are using the `webpack -w` or the webpack-dev-server.
2. webpack has not yet re-run to reflect updates.
3. You have misconfigured Webpacker's config/webpacker.yml file.
4. Your webpack configuration is not creating a manifest.
Your manifest contains:
{
  "administrate.js": "/packs/js/administrate-efe50b919205eda225cd.js",
  "administrate.js.map": "/packs/js/administrate-efe50b919205eda225cd.js.map",
  "application.js": "/packs/js/application-09148dd701148232d85b.js",
  "application.js.map": "/packs/js/application-09148dd701148232d85b.js.map",
  "entrypoints": {
    "administrate": {
      "js": [
        "/packs/js/administrate-efe50b919205eda225cd.js"
      ],
      "js.map": [
        "/packs/js/administrate-efe50b919205eda225cd.js.map"
      ]
    },
    "application": {
      "js": [
        "/packs/js/application-09148dd701148232d85b.js"
      ],
      "js.map": [
        "/packs/js/application-09148dd701148232d85b.js.map"
      ]
    },
    "jumpstart": {
      "js": [
        "/packs/js/jumpstart-3a25d3df1cc7d09412fc.js"
      ],
      "js.map": [
        "/packs/js/jumpstart-3a25d3df1cc7d09412fc.js.map"
      ]
    }
  },
  "jumpstart.js": "/packs/js/jumpstart-3a25d3df1cc7d09412fc.js",
  "jumpstart.js.map": "/packs/js/jumpstart-3a25d3df1cc7d09412fc.js.map"
}

and highlight the following code

<%# All assets are defined in Webpacker app/javascripts now %>

    <%= javascript_pack_tag 'application', 'data-turbolinks-track': 'reload' %>

    <%= stylesheet_pack_tag 'application', media: 'all', 'data-turbolinks-track': 'reload' %>

    <%= stylesheet_link_tag 'application', media: 'all', 'data-turbolinks-track': 'reload' %>



    <%# Be sure to add your own custom favicons %>
Thanks for your help.
Chris Oliver •
Hey Manuel!

This was caused by some major changes in the Webpacker gem. They've removed all CSS support out of the box which was unexpected! 😅

I've pushed up some fixes that should do the trick. 👍
Alex O •
On a fresh install just now webpacker couldn't find application.js, I updated webpacker on my system and it still didn't work. Went back to the old install and now that is broken too with the same error as OP. Had to downgrade webpacker version in my gemfile on my old app for it to run. Sadly doing the same didn't help with the fresh install 
NG DAVID •
I encounter the same issue on a fresh install.  What webpacker version should I use ?

Neema •
I'm experiencing this problem too Chris Oliver .

I've started with a fresh install and I get a similar error, although my manifest appears a little different:

Webpacker can't find application.css in /Users/primary/Dropbox/Projects/new_project/public/packs/manifest.json. Possible causes:
1. You want to set webpacker.yml value of compile to true for your environment
   unless you are using the `webpack -w` or the webpack-dev-server.
2. webpack has not yet re-run to reflect updates.
3. You have misconfigured Webpacker's config/webpacker.yml file.
4. Your webpack configuration is not creating a manifest.
Your manifest contains:
{
  "administrate.js": "/packs/js/administrate-6105e481ca2c91208428.js",
  "application.js": "/packs/js/application-d9f8d6fc07e5e3f4dae6.js",
  "entrypoints": {
    "administrate": {
      "assets": {
        "js": [
          "/packs/js/runtime-4f445db1f03cca8765f9.js",
          "/packs/js/vendors-node_modules_webpack-dev-server_client_index_js_http_localhost_3035-node_modules_webp-d87aec-c3f64b93a94b2ce23845.js",
          "/packs/js/administrate-6105e481ca2c91208428.js"
        ]
      }
    },
    "application": {
      "assets": {
        "js": [
          "/packs/js/runtime-4f445db1f03cca8765f9.js",
          "/packs/js/vendors-node_modules_webpack-dev-server_client_index_js_http_localhost_3035-node_modules_webp-d87aec-c3f64b93a94b2ce23845.js",
          "/packs/js/application-d9f8d6fc07e5e3f4dae6.js"
        ]
      }
    }
  },
  "js/vendors-node_modules_webpack-dev-server_client_index_js_http_localhost_3035-node_modules_webp-d87aec-c3f64b93a94b2ce23845.js": "/packs/js/vendors-node_modules_webpack-dev-server_client_index_js_http_localhost_3035-node_modules_webp-d87aec-c3f64b93a94b2ce23845.js",
  "runtime.js": "/packs/js/runtime-4f445db1f03cca8765f9.js"
}

I tried various solutions on StackOverflow, one or two I found on this forum, and from other Google results, and nothing is working.

Do you happen to know what is going on and how I can solve this issue?

Thanks!
Robert Graff •
Having this issue as well

Update: Fixed this by running `yarn install` locally.
Jean Carlo •
I am having the same error
Yong Bakos •
Jean Carlo Did you run `yarn install` ?

Jean Carlo •
Yong Bakos  it was solved with yarn upgrade thanks
My Discussions Participating All Discussions
Notifications
You’re not receiving notifications from this thread.