There is an issue when running next dev after next build.

[ltlylfun]

Summary

There is an issue when running next dev after next build.

After installing rimraf as a dev dependency with:

pnpm add -D rimraf

then modifying the package.json scripts to:

"scripts": {
  "dev": "rimraf .next && next dev",
  "build": "next build",
  "start": "next start",
  "lint": "next lint"
}

the problem was solved.

What exactly is this issue, and has anyone else encountered it?

pnpm run build

[email protected] build D:\project\ResumeToJob

next build

▲ Next.js 14.2.31

Experiments (use with caution):

· esmExternals

Creating an optimized production build ...

⚠ For production Image Optimization with Next.js, the optional 'sharp' package is strongly recommended. Run 'npm i sharp', and Next.js will use it automatically for Image Optimization.

Read more: https://nextjs.org/docs/messages/sharp-missing-in-production

✓ Compiled successfully

./src/app/components/animations/LogoFallingAnimation.tsx

135:11 Warning: Using <img> could result in slower LCP and higher bandwidth. Consider using <Image /> from next/image to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

./src/app/components/Resume/ResumePDF/ResumePDFProfile.tsx

79:11 Warning: Using <img> could result in slower LCP and higher bandwidth. Consider using <Image /> from next/image to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

./src/app/components/ResumeForm/ProfileForm.tsx

177:19 Warning: Using <img> could result in slower LCP and higher bandwidth. Consider using <Image /> from next/image to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

./src/app/components/TopNavBar.tsx

116:13 Warning: Using <img> could result in slower LCP and higher bandwidth. Consider using <Image /> from next/image to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element

info - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules

✓ Linting and checking validity of types

✓ Collecting page data

Generating static pages (4/6) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.

(Use node --trace-deprecation ... to show where the warning was created)

(node:23992) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.

(Use node --trace-deprecation ... to show where the warning was created)

✓ Generating static pages (6/6)

✓ Collecting build traces

✓ Finalizing page optimization

Route (app) Size First Load JS

┌ ○ / 10.3 kB 565 kB

├ ○ /_not-found 872 B 88.5 kB

└ ○ /resume-builder 92.7 kB 639 kB

First Load JS shared by all 87.6 kB

├ chunks/554-f8580fc9aa4ee6ae.js 31.6 kB

├ chunks/c32ffa36-68678a32f8bad7a6.js 53.6 kB

└ other shared chunks (total) 2.38 kB

○ (Static) prerendered as static content

终端将被任务重用，按任意键关闭。

正在执行任务: pnpm run dev

[email protected] dev D:\project\ResumeToJob

next dev

▲ Next.js 14.2.31

Local: http://localhost:3000

Experiments (use with caution):

· esmExternals

✓ Starting...

Error: Cannot find module 'next/dist/pages/_app'

Require stack:

D:\project\ResumeToJob\node_modules.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\build\entries.js

D:\project\ResumeToJob\node_modules.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\server\dev\hot-reloader-webpack.js

D:\project\ResumeToJob\node_modules.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\server\lib\router-utils\setup-dev-bundler.js

D:\project\ResumeToJob\node_modules.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\server\lib\router-server.js

D:\project\ResumeToJob\node_modules.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\server\lib\start-server.js

at Function.<anonymous> (node:internal/modules/cjs/loader:1249:15)

at D:\project\ResumeToJob\node_modules.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\server\require-hook.js:55:36

at Function.resolve (node:internal/modules/helpers:148:19)

at getPageFilePath (D:\project\ResumeToJob\node_modules.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\build\entries.js:181:20)

at D:\project\ResumeToJob\node_modules.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\build\entries.js:403:34

at Array.map (<anonymous>)

at createEntrypoints (D:\project\ResumeToJob\node_modules.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\build\entries.js:549:50)

at D:\project\ResumeToJob\node_modules.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\server\dev\hot-reloader-webpack.js:492:138

at Span.traceAsyncFn (D:\project\ResumeToJob\node_modules.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\trace\trace.js:154:26)

at D:\project\ResumeToJob\node_modules.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\server\dev\hot-reloader-webpack.js:492:90 {

code: 'MODULE_NOT_FOUND',

requireStack: [

'D:\project\ResumeToJob\node_modules\.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\build\entries.js',

'D:\project\ResumeToJob\node_modules\.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\server\dev\hot-reloader-webpack.js',

'D:\project\ResumeToJob\node_modules\.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\server\lib\router-utils\setup-dev-bundler.js',

'D:\project\ResumeToJob\node_modules\.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\server\lib\router-server.js',

'D:\project\ResumeToJob\node_modules\.pnpm\[email protected][email protected][email protected][email protected]\node_modules\next\dist\server\lib\start-server.js'

]

}

Additional information

No response

Example

No response

[icyJoseph]

Are you able to reproduce this in latest? I reckon there's some files (a manifest likely) leftover by the build command, that the dev mode finds and tries to load?

[ltlylfun]

It feels like it is just trying to circle back around your input, without making any actual statements.

I made an app with 14.2.31 - pnpm build and pnpm dev - and it doesn't show this error.

Are you doing anything special in your next.config.js?

/** @type {import('next').NextConfig} */
const nextConfig = {
  output: "standalone",
  experimental: {
    esmExternals: "loose",
  },
  transpilePackages: ["@react-pdf/renderer"],
  webpack: (config) => {
    config.resolve.alias.canvas = false;
    config.resolve.alias.encoding = false;
    return config;
  },
};

module.exports = nextConfig;

it originally used npm with Next.js 13, but later I switched it to pnpm with Next.js 14.

the project url

[icyJoseph]

I could not repro with your link ~ I did npx next build and npx next dev invoking next directly, and also through pnpm in the package.json (removing rimraf)

are you using Windows OS?

[ltlylfun]

I could not repro with your link ~ I did npx next build and npx next dev invoking next directly, and also through pnpm in the package.json (removing rimraf)

are you using Windows OS?

Yes, I'm using Windows 11. I tried it on a Mac today and there was indeed no problem, but there was a problem with Windows 11.

[icyJoseph]

I wonder if its a permissions issue - also that it happens in 14 is a bit odd 🤔 I don't have access to a Windows machine to further investigate 😅

[ltlylfun]

I wonder if its a permissions issue - also that it happens in 14 is a bit odd 🤔 I don't have access to a Windows machine to further investigate 😅

It's ok, thanks for your help.