prerender-loader
prerender-loader copied to clipboard
GoogleChromeLabs
Cannot find module 'webpack/lib/MultiEntryPlugin'
- "prerender-loader": "^1.3.0",
- "webpack": "^5.3.2",
- "webpack-cli": "^3.3.12",
when I run webpack it turn out this.
I can not find webpack/lib/MultiEntryPluginin webpack5 lib.
but how to fix this?
It looks like webpack 5 has deprecated the MultiEntryPlugin. The fix isn't too bad, but there's several other changes in webpack 5 that break this plugin. I have a working fork up at https://github.com/nettoolkit/prerender-loader, but I've only tested it for my project.
It looks like webpack 5 has deprecated the MultiEntryPlugin. The fix isn't too bad, but there's several other changes in webpack 5 that break this plugin. I have a working fork up at https://github.com/nettoolkit/prerender-loader, but I've only tested it for my project.
thx for your answer
Is there any plan on supporting webpack 5? :thought_balloon: @developit
It looks like webpack 5 has deprecated the MultiEntryPlugin. The fix isn't too bad, but there's several other changes in webpack 5 that break this plugin. I have a working fork up at https://github.com/nettoolkit/prerender-loader, but I've only tested it for my project.
@dwoznicki Any plans to publish this package, since this project seems dead?
This project isn't dead, the fork just needs to be a Pull Request. Happy to review if anyone takes the time to do that...
@developit I can make a PR for my fork, but I have a number of additional changes that are unrelated to the Webpack 5 upgrade. Is that okay?
That makes it a bit more difficult. I'm assuming these are functional changes?
Well, it's a mixed bag. Off the top of my head, the other changes I've made include:
- fix for #51
- removed microbundle as a dependency (I can't build the current version due to developit/microbundle#74)
- various dependency upgrades
Upgrading webpack is so painfull. But awaiting for PR is pure suffering. Wazup?
@developit It looks like I'm no longer blocked by developit/microbundle#74, so I'll look into making my fork into a PR.
I'd really like to do something about #51 though. I can't incorporate prerender-loader into my project without this fix, so even if I submit a webpack 5 patch, I'll still need to keep using my fork. Is there something I could do to get this fix merged?
@dwoznicki , I'm fine using your fork, but can't find @nettoolkit/prerender-loader at npmjs.
Can you push it into public repo as temporary workaround?
Have you tried referencing the GitHub repo in your package.json? I currently have the following line in my dependencies to keep prerender-loader up-to-date:
"prerender-loader": "github:nettoolkit/prerender-loader#master",
@dwoznicki thank you so much for the fix! it seems that prerender-loader is the only working webpack5 tool to generate static files. Others (https://github.com/markdalgleish/static-site-generator-webpack-plugin) didn't work for me.
It's quite sad that most of such tools are getting deprecated in favour of heavyweight frameworks like Gatsby or Next.js
Can someone ping a maintainer of this repo to fix the compatibility with webpack 5?
