framework · inferred from evidence
Next.js
A React framework for building web applications.
- react-calendly in Next.js: Target container is not a DOM element
Only render the Calendly component on the client. Either wrap it in a client-side guard that only renders when window is defined (passing the PopupButton its url, rootElement and text props), or load it with next/dynamic with server-side re
- window.createLemonSqueezy is not a function (script not loaded before components)
The library initializes itself once the script loads, so either ensure the script tag loads before your components run, or disable the button that opens the checkout until the script is loaded and initialized. The maintainer confirmed this
- Notion SDK breaks Next.js 13 Vercel build: `Module not found: Can't resolve 'encoding'`
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 bu
- Module build failed: UnhandledSchemeError: Reading from "node:crypto" is not handled by plugins...
The Next.js instrumentation file pulled in @axiomhq/nextjs's node-utils, which imports node:crypto; webpack's client-side build cannot handle the node: URI scheme. This was fixed upstream in axiom-js PR #298 (shipped in @axiomhq/nextjs rele
- Clerk not compatible with Next.js 15 (auth() must be async)
Clerk added Next.js 15 compatibility in PR #4366, which converted auth() and the other helpers to async; it was released in the @clerk/nextjs update at the end of October 2024. Upgrade @clerk/nextjs past that release and await the now-async
- Cannot find module 'next/dist/compiled/source-map' — 500 on every API route in production
A maintainer identified the cause: outputFileTracingRoot was set to a machine-specific absolute path from the reporter's own computer that does not exist in the Vercel build environment. That excludes Next.js runtime files, including next/d
- Can't find stylesheet to import after upgrading to Next.js 16 — sassOptions additionalData and includePaths broken
Maintainer-verified: Next.js 16 moved to sass-loader v16 and the modern Sass API, where the legacy includePaths option was replaced by loadPaths. Migrate your config to sassOptions: { loadPaths: [path.join(__dirname, "assets/styles")], addi
- TypeError: e._formData.get is not a function when calling a Server Action in Next.js
The culprit is the isomorphic-form-data package, pulled in by older Appwrite and Twilio SDKs: it overwrites Node's native global.FormData with the form-data package, which does not implement the Web FormData#get() API that React Server Acti