We currently do not inject our entry code into single-file anonymous entries error
See original GitHub issueHi,
Using "error-overlay-webpack-plugin": "^0.2.0"
and "webpack": "^4.30.0"
, I got this error:
Error: We currently do not inject our entry code into single-file anonymous entries. Please use a multi-main (array) or object-form
entry
setting for now. at adjustEntry (PATH\node_modules\error-overlay-webpack-plugin\lib\index.js:56:11)
After removing error-overlay-webpack-plugin
everything works fine.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:16 (6 by maintainers)
Top Results From Across the Web
We currently do not inject our entry code into single-file ...
Hi, Using "error-overlay-webpack-plugin": "^0.2.0" and "webpack": "^4.30.0", I got this error: Error: We currently do not inject our entry ...
Read more >Error in using the webpack mini-css-extract-plugin plugin
I have loaded the bootstrap in index.js so I removed it thinking that it could be the cause, also not good. can you...
Read more >PowerApps Download file button? - Power Platform Community
Solved: Is it possible to have a download button in the powerapps? Now we show the results (stored in the file) in the...
Read more >How to fix "error no 1062" in MySQL servers and clusters
Simply put, error 1062 is displayed when MySQL finds a DUPLICATE of a row you are trying to insert. We've seen primarily 4...
Read more >rollup.js
Rollup allows you to write your code using the new module system, ... This will not throw an error if one of the...
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 FreeTop 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
Top GitHub Comments
@neoziro if you can’t fix the issue (because of time limit or whatever), at least don’t close the issue with simple answer that don’t even fix the issue (I guess you are not sure neither as you mentioned I think in your answer). obviously I can not change my webpack config just because your plugin likes it that way.
Please don’t contribute to open source, but if you do be professional at it. I’ll remove your plugin, simply because I can not write my webpack config based on your buggy code.
I see you added
help wanted
tag to almost all issues. if you can not support (clearly you can’t), at least add a note in README, so users can make better decision about using your code.To anyone who like to have error overlay without
error-overlay-webpack-plugin
, the solution is very simple, just runnpm i react-dev-utils -D
and change theentry
option of yourwebpack.config.js
to:[require.resolve('react-dev-utils/webpackHotDevClient'), './index.jsx']
, I’m using this method for months.Remember, you should use
react-dev-utils
only indevelopment
mode.