Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
ziven27 opened this issue Jan 3, 2021 · 18 comments
Open

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

ziven27 opened this issue Jan 3, 2021 · 18 comments

Comments

@ziven27
Copy link

ziven27 commented Jan 3, 2021

  • "prerender-loader": "^1.3.0",
  • "webpack": "^5.3.2",
  • "webpack-cli": "^3.3.12",

image

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

@dwoznicki
Copy link

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
Copy link
Author

ziven27 commented Jan 5, 2021

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
Copy link

Is there any plan on supporting webpack 5? 💭 @developit

@dakotaewigman
Copy link

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
Copy link
Collaborator

developit commented Feb 26, 2021

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
Copy link

@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
Copy link
Collaborator

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

@dwoznicki
Copy link

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

@rootlinux2
Copy link

Hi guys, any update here?

@snowinmars
Copy link

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

@dwoznicki
Copy link

@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
Copy link

@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
Copy link

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
Copy link

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

@ajukraine
Copy link

ajukraine commented Sep 11, 2021

@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
Copy link

Any news on this one?

@ernie-h
Copy link

ernie-h commented Apr 15, 2022

Sadly seems dead :(

@jonathanobino
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests