On Windows, absolute paths must be valid file:// URLs. Received protocol 'g:'

[toshicoxyz]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 14268
  Available CPU cores: 4
Binaries:
  Node: 18.17.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.0 // Latest available version is detected (14.2.0).
  eslint-config-next: 14.2.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: N/A

Which example does this report relate to?

Last version Next.js

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

Version next@canary

Expected Behavior

That worked in previous versions, this did not happen.

To Reproduce

Just use the instructions from the official nextjs documentation "start a project" https://nextjs.org/docs/getting-started/installation

[JamesCicada]

I had same issue I downgraded to next@14.1.0 and edit postcss.config.mjs to postcss.config.cjs
you should change the export line in same file from
export default config; -> module.exports = config;
hope this works for you too

[rsarkarr]

downgrade the version. There is a problem with the latest version

[ztanner]

This has been fixed in 14.2.1 by #64386. Thanks for the report!

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.