fix(turbopack-node) postcss.config.js path resolution on Windows

[bgw]

Description

Absolute paths don't work for imports on windows because c:\ is interpreted as a URI scheme. The workaround is to use an unambiguous file:// URI.

Fixes vercel/next.js#63755

Similar to vercel/next.js#64386

Testing Instructions

patch next.js's Cargo.toml to point to the updated branch

bgw@BENJAMINWOOCDA2 CLANGARM64 ~/Documents/next.js (canary)
$ git diff Cargo.toml
diff --git a/Cargo.toml b/Cargo.toml
index ffabdcc19..3ce91bc04 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -37,11 +37,11 @@ swc_core = { version = "0.90.30", features = [
 testing = { version = "0.35.22" }

 # Turbo crates
-turbopack-binding = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-240416.1" }
+turbopack-binding = { git = "https://github.com/vercel/turbo.git", branch = "bgw/windows-postcss-config-path" }
 # [TODO]: need to refactor embed_directory! macro usages, as well as resolving turbo_tasks::function, macros..
-turbo-tasks = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-240416.1" }
+turbo-tasks = { git = "https://github.com/vercel/turbo.git", branch = "bgw/windows-postcss-config-path" }
 # [TODO]: need to refactor embed_directory! macro usage in next-core
-turbo-tasks-fs = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-240416.1" }
+turbo-tasks-fs = { git = "https://github.com/vercel/turbo.git", branch = "bgw/windows-postcss-config-path" }

 # General Deps

build the next-swc binary

cd next.js
turbo run build-native-no-plugin-woa-release

Run `next dev` in the test repo

cd ~/Documents/browserslist-file-resolution-turbo-win32
__INTERNAL_CUSTOM_TURBOPACK_BINDINGS=~/Documents/next.js/packages/next-swc/native/next-swc.win32-arm64-msvc.node node_modules/.bin/next dev --turbo

Closes PACK-2972

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
examples-nonmonorepo	✅ Ready (Inspect)	Visit Preview	Apr 17, 2024 0:47am
rust-docs	✅ Ready (Inspect)	Visit Preview	Apr 17, 2024 0:47am

8 Ignored Deployments

Name	Status	Preview	Updated (UTC)
examples-basic-web	⬜️ Ignored (Inspect)		Apr 17, 2024 0:47am
examples-designsystem-docs	⬜️ Ignored (Inspect)		Apr 17, 2024 0:47am
examples-gatsby-web	⬜️ Ignored (Inspect)		Apr 17, 2024 0:47am
examples-kitchensink-blog	⬜️ Ignored (Inspect)		Apr 17, 2024 0:47am
examples-native-web	⬜️ Ignored (Inspect)		Apr 17, 2024 0:47am
examples-svelte-web	⬜️ Ignored (Inspect)		Apr 17, 2024 0:47am
examples-tailwind-web	⬜️ Ignored (Inspect)		Apr 17, 2024 0:47am
examples-vite-web	⬜️ Ignored (Inspect)		Apr 17, 2024 0:47am

[github-actions]

🟢 Turbopack Benchmark CI successful 🟢

Thanks

[github-actions]

✅ This change can build next-swc

[github-actions]

⚠️ CI failed ⚠️

The following steps have failed in CI:

• Turbopack Rust tests (mac/win, non-blocking)

See workflow summary for details

[bgw]

There's a CI failure on Windows:

Caused by:
  for `node-file-trace`, command `'D:\a\turbo\turbo\target\release\deps\node_file_trace-68c90777c206c864.exe' --list --format terse` exited with code 0xc0000142: A dynamic link library (DLL) initialization routine failed. (os error 1114)

However, other pull requests appear to be failing with this same error, so I don't think this is related to my PR. I'm going to go ahead and merge.

[sokra]

This would better use path.join since the / is technically not the correct path separator on windows.

[bgw]

@sokra I was trying to keep the change small, and I saw in the node documentation that:

On Windows, both the forward slash (/) and backward slash () are accepted as path segment separators; however, the path methods only add backward slashes ().

If you'd like, I can submit a follow-up PR.

Edit: #8105