You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
because nx just flat refuses to build new projects for windows outside of the hard drive the OS is on, im forced to create my workspace on my OS hdd then move it over to my hard drive of choice. that worked well until just recently when i started getting the same errors on the OS hdd as i did on secondary ones. It just exits with Error Code 1 and a path to a generated log file.
Expected Behavior
creating a new project.
GitHub Repo
No response
Steps to Reproduce
using a windows OS pnpm dlx create-nx-workspace --packageManager="pnpm" with following settings
√ Where would you like to create your workspace? · org
√ Which stack do you want to use? · react
√ What framework would you like to use? · nextjs
√ Integrated monorepo, or standalone project? · integrated
√ Application name · web-app
√ Would you like to use the App Router (recommended)? · Yes
√ Test runner to use for end to end (E2E) tests · cypress
√ Default stylesheet format · css
√ Enable distributed caching to make your CI faster · No
I couldn't reproduce this fully on my machine. Running create-nx-workspace on the drive with the host OS worked fine, but trying to install on a separate disk failed. #18753 should fix the secondary drive issue though.
Current Behavior
because nx just flat refuses to build new projects for windows outside of the hard drive the OS is on, im forced to create my workspace on my OS hdd then move it over to my hard drive of choice. that worked well until just recently when i started getting the same errors on the OS hdd as i did on secondary ones. It just exits with Error Code 1 and a path to a generated log file.
Expected Behavior
creating a new project.
GitHub Repo
No response
Steps to Reproduce
pnpm dlx create-nx-workspace --packageManager="pnpm"
with following settingsNx Report
Failure Logs
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: