Upgrade Next.js to 10.1 and enable Webpack 5

[urish]

This should make the project run faster (in dev mode), speed up npm install and make node_modules smaller.

Background info: https://nextjs.org/blog/next-10-1

How to enable webpack 5: https://nextjs.org/docs/messages/webpack5

In a nutshell:

1. Update next.js version in package.json
2. Add a few lines to next.config.js, as explained here
3. Check that everything is working

[EladTal14]

Hi Uri, I can take this one.

[urish]

Go for it :)

[EladTal14]

Hi Uri, I Read the docs about both things and added a next.config.js file and followed the instructions, but I'm getting a warning that I haven't found a solution for tell me if you know this one. @urish

[urish]

Hmm there's an open issue about this:

https://github.com/vercel/next.js/issues/23533

Sounds like it's only a warning and it should still work, but you can try asking on that issue if anybody found a solution or a workaround

[EladTal14]

Awesome I will. also posted on stackoverflow.

[domosedov]

Hi Uri, I Read the docs about both things and added a next.config.js file and followed the instructions, but I'm getting a warning that I haven't found a solution for tell me if you know this one. @urish

rm -rf node_modules && npm i helped me fix it

[EladTal14]

Tried your solution but the warning still comes up, did you do anything else or found diffrent solution. @domosedov

[phibersoft]

I m getting this warning too. I deleted package-lock.json and node modules folder and still getting.

Is any different solutions?

[EladTal14]

Just talked with the guys in webpack they said they will fix this bug after their holidays. He said its just a warning our build will work but persistent caching won't work. @urish

[urish]

Thanks!

[urish]

Note: Next.js 10.2 has just been released and should fix the Webpack issue. So let's upgrade to 10.2