Skip to content

next.config.js error fixed#39

Open
IronMan-31 wants to merge 1 commit intohalvardssm:mainfrom
IronMan-31:main
Open

next.config.js error fixed#39
IronMan-31 wants to merge 1 commit intohalvardssm:mainfrom
IronMan-31:main

Conversation

@IronMan-31
Copy link

Error: future.webpack5 in next.config.js has moved to the top level webpack5 flag https://nextjs.org/docs/messages/future-webpack5-moved-to-webpack5
at Object.loadWebpackHook (C:\Users\04-06-24\OneDrive\Documents\hacktoberfest\first\frontend-starter-hacktober\node_modules\next\dist\server\config-utils.js:94:15)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async Object.loadConfig [as default] (C:\Users\04-06-24\OneDrive\Documents\hacktoberfest\first\frontend-starter-hacktober\node_modules\next\dist\server\config.js:332:5)
at async NextServer.loadConfig (C:\Users\04-06-24\OneDrive\Documents\hacktoberfest\first\frontend-starter-hacktober\node_modules\next\dist\server\next.js:112:22)
at async NextServer.prepare (C:\Users\04-06-24\OneDrive\Documents\hacktoberfest\first\frontend-starter-hacktober\node_modules\next\dist\server\next.js:94:24)
at async C:\Users\04-06-24\OneDrive\Documents\hacktoberfest\first\frontend-starter-hacktober\node_modules\next\dist\cli\next-dev.js:121:9

This errror has been fixed in the above code which was caused due to outdate issues in the repo

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

Successfully merging this pull request may close these issues.

1 participant