-
Notifications
You must be signed in to change notification settings - Fork 211
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
No prebuild or local build of @parcel/watcher found #1808
Comments
Hi, I maintain |
@devongovett gave the solution, i was running vscode 32bit. Installing the 64bit version fixed the problem. |
@devongovett I'm seeing this same issue running on Windows 10 inside a parallels arm64 vm. |
Is it possible that you accidentally installed the 32-bit version of node rather than the 64-bit one? Could you follow the steps here to see which version of windows you are running? https://support.microsoft.com/en-us/windows/32-bit-and-64-bit-windows-frequently-asked-questions-c6ca9541-8dce-4d48-0415-94a3faa2e13d |
Yep, that is the issue. Thank you. |
I'm seeing the same error message on nixos (linux). I'll investigate what the prebuild identifier should be. ETA: The OS uses glibc. The error says "Tried @parcel/watcher-linux-x64-glibc". It's likely an issue on the nixos side. |
@devongovett I can replicate this error in docker with just |
@bradmarder did you follow the error message instructions? Does the package it printed exist, or is your platform not supported (i.e. does not exist in the npm registry)? If it is, then can you determine why it wasn't installed by your package manager (e.g. configured not to install optional dependencies)? I'll need more info if I am to help you further. |
@devongovett Sorry, I should have been more clear. I'm attempting to run |
Started having the same issue here in a docker node:16 image on a kubernetes cluster, not sure if there is an easy fix?
|
I suspect npm/cli#4828 |
@devongovett I get same errors on my windows machine when I installed the "Nx Console" extension. I verified that I'm using VS Code 64bit installed too. |
I'm not sure what I'm supposed to do if a package manager fails to install the dependencies correctly. The package clearly exists. I don't know what package manager vscode uses, but if it is npm, then the above issue I linked is probably the place to report this. |
@sanjaymereddy are you also using the 64 bit version of node? |
@MaxKless Yes, I'm using 64bit node |
I think I've identified the root cause -- it's in @parcel/watcher and how it loads extensions. TL;dr the loading algorithm is too simple -- it's computing the expected filename and has hardcoded its search path. But these assumptions don't work on every OS and the module isn't found. (See index.js in @parcel/watcher) Once I can build a stand-alone reproducible case, I'll file a bug and PR on watcher. |
Note: I deleted a comment that said conflicting directory layouts were to blame (pre-watcher 2.2.0 vs. post-2.2.0) since it's also failing with the correct directory layout and loading code. I'm still debugging this. (But maybe bringing all versions of watcher to 2.2.0 and losing the duplicate in yarn.lock is still a good idea.) |
@sarahec Thank you for looking at this issue. Please let me know when there is a fix or if there is any work around that I can try to run the extensions. |
To set expectations: I'm a volunteer looking into this. It's becoming clear that My current working hypothesis: VSCode extensions have their own node_modules, and vscode makes assumptions about where these will be installed. It's either vscode setting the wrong path for My next step is to reproduce the bug in a code sample and have you all run it as well. That'll show what needs to happen to fix it. |
service initializing failes
To have a working nx console
Steps to Reproduce
create a new workspace
npx create-nx-workspace@latest
Failure Logs
Environment
The text was updated successfully, but these errors were encountered: