-
Notifications
You must be signed in to change notification settings - Fork 30
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
Incompatible with Nextjs 5 #37
Comments
Saw that @miukimiu posted on a similar issue that was resolved: #33 (comment) Are there plans for Elastic UI Kit to support Webpack 5? |
We don't have any active plans to upgrade this repo to the latest Next + Webpack, but it is something we want. From reading the stack trace & next.js thread you linked to, it's may be possible this specific error can be resolved by updating some dependencies. |
@chandlerprall Thanks for the quick response! For clarification, do you suggest forking the repo and updating some dependencies (such as html-webpack-plugin) for this to be solved on my end? Or are you suggesting that I may be able to solve this without forking? |
I'd try forking and updating those dependencies. If you get a functioning build with the latest next.js and webpack (or close to a functioning build), I'd be happy to review a pull request with any changes! |
I opened a PR with a functioning webpack config :) |
Hi there,
Thanks for creating this starter repo! I've cloned it and updated next to
"next": "^11.0.1"
in package.json to run Next.js 5 and Webpack 5and am running into the following error:
It seems that
html-webpack-plugin
is the dependency that's causing this problemAnyone have ideas for how to get around this?
I've tried specifying a resolution in package.json but no change:
Mentioned this in their adoption thread: vercel/next.js#23498 (reply in thread)
The text was updated successfully, but these errors were encountered: