search

GoogleChromeLabs / prerender-loader

📰 Painless universal pre-rendering for Webpack.
https://npm.im/prerender-loader
Apache License 2.0
1.9k stars 50 forks source link

Cannot find module 'webpack/lib/MultiEntryPlugin' #53

Open ziven27 opened 3 years ago

ziven27 commented 3 years ago

image

when I run webpack it turn out this. I can not find webpack/lib/MultiEntryPluginin webpack5 lib. but how to fix this?

dwoznicki commented 3 years ago

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.

ziven27 commented 3 years ago

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

edwardfxiao commented 3 years ago

Is there any plan on supporting webpack 5? :thought_balloon: @developit

dakotaewigman commented 3 years ago

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?

developit commented 3 years ago

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...

dwoznicki commented 3 years ago

@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?

developit commented 3 years ago

That makes it a bit more difficult. I'm assuming these are functional changes?

dwoznicki commented 3 years ago

Well, it's a mixed bag. Off the top of my head, the other changes I've made include:

rootlinux2 commented 3 years ago

Hi guys, any update here?

snowinmars commented 3 years ago

Upgrading webpack is so painfull. But awaiting for PR is pure suffering. Wazup?

dwoznicki commented 3 years ago

@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?

snowinmars commented 3 years ago

@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?

dwoznicki commented 3 years ago

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",
snowinmars commented 3 years ago

Wtf, I can do this? Lol. / () __ () \

ajukraine commented 3 years ago

@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

jmbastidas commented 3 years ago

Any news on this one?

ernie-h commented 2 years ago

Sadly seems dead :(

jonathanobino commented 2 years ago

Can someone ping a maintainer of this repo to fix the compatibility with webpack 5?