./postcss.config.js: Error [ERRUNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'). Since version 14.1.2-canary.4 about next.js HOT 10 CLOSED

Renaming postcss.config.js to postcss.config.cjs did the trick for me.

from next.js.

Renaming postcss.config.js to postcss.config.cjs did the trick for me.

It really helped, but it's weird. As if it needs to be fixed anyway.

----worked for me too

from next.js.

The second problem:

Since version 14.1.2-canary.4, the project just won't even open in dev mode

./src/app/globals.css
Error evaluating Node.js code
Error: Failed to load external module C:\Users\Asus\Desktop\petProjects\shopco/./postcss.config.js: Error [ERRUNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
at externalImport (/turbopack/[turbopack]/shared-node/base-externals-utils.ts:16:11) [C:\Users\Asus\Desktop\petProjects\shopco.next\chunks[output]__next_transform_ad1f0f.js:1318:15]
[at process.processTicksAndRejections (node:internal/process/task_queues:95:5)]
at async (postcss.config.js.loader.mjs:3:13) [C:\Users\Asus\Desktop\petProjects\shopco.next\chunks_0b8f1c._.js:11:13]

from next.js.

postcss/postcss#1931

The posts developers replied to me that these are your problems. You can find my post CSS config at the link

from next.js.

next.js config

ts.config

from next.js.

Just the latest version next.js

from next.js.

one of the 2 problems has been solved #63109

from next.js.

Having the same issue here, Canary (14.2.0-canary.26) seems to be working fine when disabling Turbopack on Windows.
Seems to be working fine in a Linux environment

from next.js.

Renaming postcss.config.js to postcss.config.cjs did the trick for me.

It really helped, but it's weird. As if it needs to be fixed anyway.

from next.js.

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.

from next.js.