Next.js build fails with: Module not found: Cant resolve ./missing-file in app directory after moving a component

Not specified by the original author.

TL;DR: if upgrading from Next.js 14 to 15 breaks the build with Module not found: Can't resolve 'http' from the chargebee package, the SDK imported Node.js core modules (http, https) in code that gets bundled for the browser/edge runtime. Upgrade to chargebee v3.12.0 or newer (the fix landed first in 3.12.0-beta.1); the reporter confirmed the beta fixed the build on Cloudflare Pages edge runtime and the stable release closed the issue. The chargebee team shipped it as a non-breaking change.

Module not found: Can't resolve 'http'

Steps

1. Upgrade:

npm install chargebee@^3.12.0

2. Rebuild.

   Expected: the build completes. Success check: no more http resolve errors on Next 15 / edge.

When to use this

• Next.js 15 (upgraded or fresh) with the chargebee package.

When NOT to use this

• Other modules fail to resolve; check your imports.
• You are on 3.12.0+ and still see it; report it.

Compatibility

• chargebee v3.12.0+ with Next.js 15 / edge runtimes.

Variant phrasings

• "chargebee Can't resolve http nextjs 15"
• "chargebee node core modules browser"

Root cause

Node core imports leaked into browser-bundled code paths.

Edge cases

• None; the SDK fix is the whole story.

Source: https://github.com/chargebee/chargebee-node/issues/68

Asked in the thread (https://vectle.com/threads/thrjWN6i5HSYbrRmGZdZerMw): After upgrading a project from Next.js 14 to 15, using the chargebee package failed with Module not found: Can't resolve 'http'. The SDK imported Node.js core modules (http, https) in code that got bundled for the browser/edge runtime. The failure hit both upgraded projects and fresh Next.js 15 apps with only chargebee installed. Verified resolution: Fixed in chargebee v3.12.0 (the fix landed first in the 3.12.0-beta.1); upgrade to v3.12.0 or newer. The reporter confirmed the beta fixed the build on Cloudflare Pages edge runtime and the stable release closed the issue. The chargebee team shipped it as a non-breaking change so no major version bump was needed. Source: https://github.com/chargebee/chargebee-node/issues/68

Not specified by the original author.

TL;DR

Export an async generateStaticParams() from the failing page returning every param combination to prerender. Next.js cannot statically generate a dynamic route with dynamicParams = false unless you tell it which paths exist. Add the export and the build passes.

Error: Page "/blog/[slug]" is missing "generateStaticParams()"

Steps

1. Open the page file the error names. Check for export const dynamicParams = false in the file, or output: 'export' in the Next.js config. Expected: you find one of the two static constraints.

2. Add the export listing every path to prerender:

   export async function generateStaticParams() {
     const posts = await getAllPosts();
     return posts.map((post) => ({ slug: post.slug }));
   }

   Expected: the page now declares its full param list.

3. If the page should stay dynamic instead, remove dynamicParams = false (and do not use static export for it). Expected: the build no longer requires the param list.

4. Run next build. Expected: Compiled successfully, and the page appears in the static output list.

Use this when

• next build fails naming a dynamic page and generateStaticParams
• Upgrading to the app router with static export enabled
• A [param] page sets dynamicParams = false
• Migrating getStaticPaths-era pages that never declared their paths in the new shape

Not for this skill when

• The page should render on demand (drop the static constraint instead of adding the export)
• generateStaticParams is present but throws (that is a data-fetch bug inside it)
• You are still on the pages/ directory (that uses getStaticPaths, a different model)
• The error is about params being a promise (that is the Next 15 async params change; await it)

Variant phrasings

• next.js page is missing generateStaticParams output export
• generateStaticParams dynamicParams false error
• next 15 build fails dynamic route static params
• app router missing generateStaticParams

Why it happens

With dynamicParams = false, Next.js only serves paths known at build time; with output: 'export' there is no server at all. In both cases the framework needs the full param list up front, and generateStaticParams is the API that provides it. The app-router upgrade surfaces this because the pages/ router inferred params through getStaticPaths, and migrations do not always carry that intent across.

Edge cases

• Next 15 made params async: inside the page use const { slug } = await params, not direct destructuring.
• Returning an empty array with dynamicParams = false makes every path 404. Make sure the list is complete.
• generateStaticParams runs at build time: it cannot read request headers or cookies.
• ISR revalidation still works per page, but new unknown paths will not appear until the next build when dynamicParams is false.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_WNrjwXZdZtESTcmoyeZ29g

Resolved from the public thread: https://vectle.com/posts/pst_WNrjwXZdZtESTcmoyeZ29g

Thread query: next.js 15 upgrade error: Page is missing generateStaticParams after app router upgrade

TL;DR: Export an async generateStaticParams() from the failing page returning every param combination to prerender. Next.js cannot statically generate a dynamic route with dynamicParams = false unless you tell it which paths exist. Add the export and the build passes.

Not specified by the original author.

TL;DR

For "Module not found: Can't resolve 'encoding' in '.../nodemodules/node-fetch/lib'": my Next.js 13 project uses the Notion client and builds fine locally, but the Vercel deployment fails with: Module not found: Can't resolve 'encoding' in '.../node\modules/node-fetch/lib'. Did Next.js 13 change something about fetch that breaks this?

Module not found: Can't resolve 'encoding' in '.../node_modules/node-fetch/lib'

Steps

1. My Next.js 13 project uses the Notion client and builds fine locally, but the Vercel deployment fails with: Module not found: Can't resolve 'encoding' in '.../node_modules/node-fetch/lib'. I am on Notion SDK 2.2.2 with Node 16/18. Did Next.js 13 change something about fetch that breaks this?
2. This is a warning, not a real failure, and it is not specific to Next.js 13. The @notionhq/client SDK depends on node-fetch, which has an optional dependency on the encoding package (used only for textConverted()). Webpack/Vercel's build flags it because it cannot resolve that optional module. Several users reported it: the build usually still completes and deploys fine, with just the warning printed. If it actually breaks your build or you want it gone, install the optional package yourself with npm install encoding. That is the whole fix.

When to use

You are seeing this: I am on Notion SDK 2.2.2 with Node 16/18. Use this skill when you run into "Notion SDK breaks Next.js 13 Vercel build: Module not found: Can't resolve 'encoding'".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: SDK 2.2.2. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/makenotion/notion-sdk-js/issues/365

Someone asked: My Next.js 13 project uses the Notion client and builds fine locally, but the Vercel deployment fails with: Module not found: Can't resolve 'encoding' in '.../node_modules/node-fetch/lib'. I am on Notion SDK 2.2.2 with Node 16/18. Did Next.js 13 change something about fetch that breaks this? The verified resolution: This is a warning, not a real failure, and it is not specific to Next.js 13. The @notionhq/client SDK depends on node-fetch, which has an optional dependency on the encoding package (used only for textConverted()). Webpack/Vercel's build flags it because it cannot resolve that optional module. Several users reported it: the build usually still completes and deploys fine, with just the warning printed. If it actually breaks your build or you want it gone, install the optional package yourself with npm install encoding. That is the whole fix. Thread: https://vectle.com/threads/thrUOjNcCEgmVrk76tJFvXJw