-
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
Cannot npm run dev
nor npm install
because of different versions of esbuild
#2865
Comments
Could you check if there is an env I guess this is probably caused by your system level esbuild was installed by |
Yes, this sounds like another problem caused by this. They really should not be doing that. I'm not sure what you should do about this. I'm not at all familiar with Arch Linux. If possible, removing the package with that shell script that set the
Markdown has a strange quirk where if you mix HTML and Markdown, there has to be a blank line in between the HTML and the Markdown (or vice versa). So like this:
not like this:
|
Running
I don't recall installing this software on my own, if pacman installed it then it must have been a dependency of something.
A friend has complained about similar problems, on a Windows machine. I've asked them to run
Running And thanks for the info about the markdown-html stuff, and editing my comment yourself! |
Yes, that was it. I ran Solved! Thanks for your assistance. |
fix: do not set ESBUILD_BINARY_PATH see: evanw/esbuild#2865 (comment)
fix: do not set ESBUILD_BINARY_PATH see: evanw/esbuild#2865 (comment)
FYI: AUR package has been just fixed (0.17.5-2). |
I don't know much about this software, I was trying to
npm run dev
in a project but there were issues so I thought a reinstall would help, but it kept happening so I deletednode_modules
to reinstall from a blank slate. Every time it gave me such an error:I am unable to take a look at this problematic
install.js
file as thenode_modules
folder disappears.The whole log is below.
but unfortunately the Details section on GitHub does not seem to support code block formatting. It tried to group all the lines into one paragraph so I had to separate them one by one, and put each into code lines asSee lower comment by evanw for how to avoid this behaviour with Markdown.:link:
would become 🔗 for example.Irregardless, the whole log as well as the error above are completely the same as they were output, except for changing the username and path to the project.
Whole log here
I've tried things as in #1711 (comment):
npm i [email protected]
, it complains:Error: Expected "0.17.4" but got "0.17.3"
;npm i [email protected]
(as in the comment), it complains:Error: Expected "0.13.3" but got "0.17.3"
;npm i [email protected]
, it complains:Error: Expected "0.16.17" but got "0.17.3"
;npm update
;0.16.*
version this time;npm i [email protected]
, it complains:Error: Expected "0.16.17" but got "0.17.3"
;npm i [email protected]
, which is the newest version, it complains:Error: Expected "0.17.4" but got "0.17.3"
;0.17.4
.I am on Arch Linux, fully updated at the moment,
6.1.7-arch1-1
.pacman -Q | grep esbuild
givesesbuild 0.17.3-1
, as expected because every error saysgot "0.17.3"
;npm show esbuild
giveslatest: 0.17.4
among other things, but as written above, I am unable get the latest version;npm-check-updates
does not detect esbuild being newer, only other software, which cannot be updated because of the error above.This happens in any project. Everything worked three days ago and
npm show esbuild
says the latest version came out two days ago.Is this a problem with the software or with my own inexperience with it? What steps should I take to make these projects usable again? Or is this out of my control, maybe something that'll sort itself through time and updates?
If you need any other outputs, please tell me which commands you need me to run, and excuse any problems with my English as it's not my native language.
The text was updated successfully, but these errors were encountered: