-
Notifications
You must be signed in to change notification settings - Fork 1.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
Install script uses wrong registry #1485
Comments
It's supposed to pick up the registry setting from npm's configuration. See #1193 (comment). It sounds like Yarn has bugs with nested npm invocations picking up the correct configuration, as does npm. But this isn't a problem with esbuild (esbuild is just running the In case you're wondering, the reason why you're seeing the download from I'm working on an alternate installation strategy that doesn't use a |
@sschneider-ihre-pvs, |
that sounds promising |
This is affecting us now too. Angular v12 application builds are failing corporate-wide because esbuild is trying to install something from the yarn registry instead of our internal artifact store. If installing an older version of esbuild fixes it, then it seems like this is a regression issue and not just some bug with npm/yarn. |
A possible cause for this is mentioned in the linked issue above. I would also like to see a solution here indeed. Maybe not doing a cwd would already fix it? |
Do you have a self-contained way to reproduce this issue? Then we could figure out if there's a configuration issue and/or which piece of software needs to be fixed. |
That's going to be tricky without being behind some kind of firewall. We did find something that helped with this, in case it points towards a root cause. We were still having issues (but with a slightly different error) after rolling back to 0.12.6. Our build boxes didn't have yarnrc files on them, just npmrc, which has worked fine for us til now, since yarn falls back on that. After also explicitly setting the registry in a yarnrc to our registry, the esbuild postinstall went through. But still with the older version. But even that doesn't really help @woppa684's issue though, with project level npmrc files not being picked up |
I'll retry in the morning with the newer version and that setup. |
I tried a fresh vite project which has esbuild as dep. When I try to run
npm install
i see that the install script is trying to download something from a different registry than npm is configured with.Is there a way to override the url from the install.js so it is asking the correct registry for the package?
The text was updated successfully, but these errors were encountered: