[RUBY] Solution when you get the error Webpacker :: Manifest :: MissingEntryError in Devise :: Sessions # new

Development environment

・ Rails 6.0.3.1 ・ Ruby 2.6.6

Situation at the time of error

$ rails s

When I run the command and access localost3000,

【error contents】


Webpacker::Manifest::MissingEntryError in Devise::Sessions#new
Showing /Users/XXXX_XXXX/Desktop/XXX_XXX_XXX/app/views/layouts/application.html.erb where line #9 raised:

Webpacker can't find application in /Users/XXXX_XXXX/Desktop/XXX_XXX_XXX/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:

I got the error.

The relevant part is

application.html.erb



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

It is written.

Solution

$ bundle exec rails webpacker:install

I was able to resolve the error.

Recommended Posts

Solution when you get the error Webpacker :: Manifest :: MissingEntryError in Devise :: Sessions # new
[Solution] Webpacker :: Manifest :: MissingEntryError in Rails
When you get lost in the class name
[Solution] Rails6 Webpacker :: Manifest :: MissingEntryError
Error in bundle install when running rails new
[Rails] Solution when migration error occurs in acts-as-taggable-on
[No Method Error] Solution when new action occurs
About the solution of the error that occurred when trying to create a Japanese file of devise in the Docker development environment
Webpacker :: Manifest :: MissingEntryError
I get Mysql2 :: Error :: ConnectionError in the production environment
Solution if you delete the migration file in the up state
In Redmine you can get the project with Project.find (<identifier>)
If you get a "Quantum Renderer: no suitable pipeline found" error when running the jar file
What to do if you get a JNI shared library error when trying to build in Eclipse