[v15] Module parse failed: Bad character escape sequence

[faisalrehmanlums]

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/condescending-haze-go8s7s

To Reproduce

1. run this commad: npx create-next-app@latest
2. This will install latest version of nextjs like in package.json is "dependencies": { "react": "19.0.0-rc-65a56d0e-20241020", "react-dom": "19.0.0-rc-65a56d0e-20241020", "next": "15.0.0" }, "devDependencies": { "typescript": "^5", "@types/node": "^20", "@types/react": "^18", "@types/react-dom": "^18", "postcss": "^8", "tailwindcss": "^3.4.1", "eslint": "^8", "eslint-config-next": "15.0.0" }
3. npm run dev
4. browser showing error `Module parse failed: Bad character escape sequence (11:57)
   | const fileSizeInMB = buffer.byteLength / 1024 / 1024

`

Current vs. Expected behavior

I have just not changed any default value during app creation like shown in screenshot
it should spin up dev server without error. which it dose but after within seconds error pop out.

Provide environment information

test

Which area(s) are affected? (Select all that apply)

create-next-app

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

When i step down to version 14 its working fine with 14.2.15 npx create-next-app@14 test-project

[fkajerry]

v15 stable has this bug it's CRAZY!

Is anyone in the next.js community actually reviewing code?

[Sayakie]

Looks like this started appearing in next@15.0.0-canary.180 on Windows platform.

• feat(next): throw when twitter-image or opengraph-image file size exceeds #70353

[darthmaim]

What node.js version are you using (please fill out the entire issue template next time)? There was a bug in some recent Node.js versions recently (mainly 22.7.0) that had some similar symptoms, you should try upgrading if you are using that version.

[kdy1]

I think we should not inline the path into the string, or we should replace \ with \\ on windows. cc @devjiwonchoi

[faisalrehmanlums]

What node.js version are you using (please fill out the entire issue template next time)? There was a bug in some recent Node.js versions recently (mainly 22.7.0) that had some similar symptoms, you should try upgrading if you are using that version.

I'm using node verion v20.18.0 with npm version 10.9.0