Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error 'WEBPACK_MANIFEST_PATH'
See original GitHub issueThere is a issue for the update 0.13.0 (06/25/2017).
RuntimeError: Flask-Webpack requires 'WEBPACK_MANIFEST_PATH' to be set and it must point to a valid json file.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9
Top Results From Across the Web
webpack-dev-server manifest paths are incorrect (on windows)
It will complain that the manifest doesn't exist, despite compile: true being set. · Start webpack-dev-server · Refresh. · Check logs and see...
Read more >[New to webpack]autoprefix problem with webpack manifest ...
I tried to use webpack manifest plugin to build manifest.json file that has keys and values of my assets with contenthash in its...
Read more >The Manifest - webpack
webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable...
Read more >webpack-manifest-plugin - npm
This is a problem when other plugins use the deprecated emit hook. The manifest will be written before these other plugins and thus...
Read more >Rails 6: Webpacker::Manifest::MissingEntryError
What the error means is that Webpacker can't find the application, and is failing at square one to compile. None of the files...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Closing this now because it’s stale and it appears that the fix has been found above.
I worked it out!
You need to run
npm run-script buildto build the assets and manifest for the first time. After that, Flask will run happily.It looks like you can also run
npm run-script startto simultaneously run webpack (to recompile assets while you’re developing) and Flask simultaneously.