-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Double Quote Symbolic Path Links for Windows to Work #6601
Conversation
I had to double quote these regular expressions for them to work on Windows.
I had to double quote these regular expressions to work on Windows. Windows doesn't have symbolic links.
I had to double quote these regular expressions to work on Windows. Windows doesn't have symbolic links.
I had to double quote these regular expressions to work on Windows. Windows doesn't have symbolic links.
I had to double quote these regular expressions to work on Windows. Windows doesn't have symbolic links.
I had to double quote these regular expressions to work on Windows. Windows doesn't have symbolic links.
I had to double quote these regular expressions to work on Windows. Windows doesn't have symbolic links.
I had to double quote these regular expressions to work on Windows. Windows doesn't have symbolic links.
I had to double quote these regular expressions to work on Windows. Windows doesn't have symbolic links.
Windows definitely has symbolic links and has for decades https://learn.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/create-symbolic-links |
There are some issues with local development for the repo on Windows w/r/t symlinks. I've fixed those and a few other things as part of #6586. |
Hi @lukekarrys After I worked around the broken symlink, I then ran into another error about the constructor not being found for Arborist. Just FYI. |
Can you try with the |
Hi @ljharb, I mean in the context of this work. It doesn't seem like the NPM packages are utilizing Windows symbolic links. I looked over the changes from Node 16.13.0 to Node 20+... and the same directories were deleted and replaced with these file to directory placeholders. several lib* directories Now my CLI is saying Arborist is not a constructor. It's not loading the classes properly even after reading these simulated symbolic placeholders on Windows. It was working when they were just directories on Node 16.13. I isolated the break between Node 16.13 and Node 16.14 when NPM jumped from: node 16.13.0 TO node 16.14.0 I have to workaround this with Yarn because I cannot troubleshoot anything on NPM since the CLI is not working when it starts loading the packages.... e.g. "npm i" As soon as I upgrade Node and NPM... the CLI mostly falls over whenever it tries to traverse the file tree structure with Arborist. |
PS C:\Users\nates\github\20> npm install npm@latest -g ERROR: SyntaxError: Unexpected token '.' ERROR: npm v9.6.7 is known not to run on Node.js v20.3.1. This version of npm supports the following node versions: ERROR: SyntaxError: Unexpected token '.' PS C:\Users\nates\github\20> yarn add npm@latest -g ERROR: SyntaxError: Unexpected token '.' ERROR: npm v9.6.7 is known not to run on Node.js v20.3.1. This version of npm supports the following node versions: ERROR: SyntaxError: Unexpected token '.' PS C:\Users\nates\github\20> ls
Mode LastWriteTime Length Name d----- 7/9/2023 9:28 AM node_modules PS C:\Users\nates\github\20> rm .\package-lock.json ERROR: SyntaxError: Unexpected token '.' ERROR: npm v9.6.7 is known not to run on Node.js v20.3.1. This version of npm supports the following node versions: ERROR: SyntaxError: Unexpected token '.' PS C:\Users\nates\github\20> node -v |
PS C:\Users\nates\github\20> yarn |
It's not allowing me to install the latest NPM version directly from the Github. It's getting hung up on Arborist again. Windows and Linux allow for different max char paths. |
This is on Linux nate@mexico:/mnt/c/Users/nates/github/20$ yarn |
I had to double quote these regular expressions to work on Windows. Can we use Windows Symbolic Links instead of these files that contain directory paths?
#4234
@fritzy