Module not found: Can't resolve 'encoding' #54109
Unanswered
louis030195
asked this question in
Help
Replies: 3 comments 1 reply
-
It's a known issue, not a Next.js problem. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Am having the same issue |
Beta Was this translation helpful? Give feedback.
0 replies
-
I had the same issue in my Next.js project and fixed it by adding // next.config.js
/** @type {import('next').NextConfig} */
const nextConfig = {
webpack: (config) => {
config.externals.push('encoding', /* add any other modules that might be causing the error */);
return config;
},
};
module.exports = nextConfig; |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
Hi, getting bunch of warning since 5 months since using nextjs in different projects and could not find a solution
i procrastinated enough now and it f** my console of warnings
i guess it's because these deps don't work in edge runtime (i tested), how can i fix this issue
(i checked perplexity.ai, chatgpt, github, and google beforehand)
Additional information
Beta Was this translation helpful? Give feedback.
All reactions