-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Closed
Closed
Copy link
Labels
area: windowsIssues specifically reproducing on WindowsIssues specifically reproducing on Windowskind: bugSomething isn't workingSomething isn't working
Description
Verify canary release
- I verified that the issue exists in the latest Turborepo canary release.
Link to code that reproduces this issue
https://github.com/hornta/test-turborepo
Which canary version will you have in your reproduction?
turbo@2.5.6-canary.2
Environment information
CLI:
Version: 2.5.6-canary.2
Path to executable: C:\Users\me\Desktop\test-turborepo\node_modules\turbo-windows-64\bin\turbo.exe
Daemon status: Running
Package manager: npm
Platform:
Architecture: x86_64
Operating system: windows
WSL: false
Available memory (MB): 25414
Available CPU cores: 16
Environment:
CI: None
Terminal (TERM): unknown
Terminal program (TERM_PROGRAM): vscode
Terminal program version (TERM_PROGRAM_VERSION): 1.103.1
Shell (SHELL): unknown
stdin: false
Expected behavior
I expect the script to log the correct value of process.env.windir
Actual behavior
The console.log outputs undefined.
To Reproduce
On windows platform:
- Clone the reproducing repository
- Run
npm install - Run
npm run dev - Observe how it logs
undefined
It correctly outputs C:\WINDOWS if I cd apps/my-app and run npm run dev.
Additional context
No response
Metadata
Metadata
Assignees
Labels
area: windowsIssues specifically reproducing on WindowsIssues specifically reproducing on Windowskind: bugSomething isn't workingSomething isn't working