Since the commit Use Yarn to manage dependencies, cleanup unused bootstrap libs (#6436) · discourse/discourse@dc8a16b · GitHub , running npm install fails. Looking at the log file … 880 silly fetchPackageMetaData error for jquery.autoellipsis@git+https://github.com/pvdspek/jquery.autoellipsis.git p…

This is a development question, not an install question, yes?

Is it? I wasn’t quite sure. Are these dependencies only relevant for Discourse’s testing? Then the category was wrong indeed. Sorry about that.

@pmusaraj any tips here? Also … why are you using npm, we only really test using yarn and only support yarn for dev.

I think the error you’re getting is due to our package.json using yarn syntax for referencing Github versions of dependencies. So, use yarn install instead of npm. Also, yarn install is only required for running frontend (qunit) tests or when a developer is upgrading one of the Discourse dependencie…

I wonder if there is some entry we can add to our package.json that would force npm install to explode with a “sorry, npm is not supported use yarn” Ultra low priority though.

@pmusaraj that seems like a good track to follow: [Ryan Wheale] Force yarn install instead of npm install for Node module? node.js, npm, package.json, yarnpkg answered by Ryan Wheale on 02:15AM - 13 Dec 16 UTC

I did not know that only Yarn is supposed to be used here. I saw a package.json and run npm install a short while ago to run my plugin tests. Now, npm install doesn’t work. It looks like Yarn and NPM use incompatible syntax for referencing remote git repositories via URL so there is no nice common …

@kleinfreund there is absolutely no need to run npm install. And as Sam and Joffrey point out, we will shortly block running npm install on the repo. (Just use yarn install.)

I get it. It’s just that I didn’t previously need Yarn, so I have to install it. That’s not a big deal though.

This commit adds a preinstall hook that stops npm install and outputs “NPM is not supported, please use Yarn instead.” to the user. https://github.com/discourse/discourse/commit/0fdb4d0e46e8a9f0bfae9368546c99b8030b5d48

Npm install fails due to package.json misconfiguration

Development

j.jaffeux (Joffrey Jaffeux) November 5, 2018, 8:11am 8

@pmusaraj that seems like a good track to follow:

Topic		Replies	Views
Discourse core is switching to pnpm for JS package management Development dev-news	24	1769	February 13, 2025
Trouble with theme lint at "install JS Dependencies” step Development	8	356	June 1, 2025
The engine "yarn" is incompatible with this module. Expected version "please-use-pnpm". Got "1.22.19" Product Support	4	466	February 7, 2025
Down after upgrade: yarn: not found Self-hosting	2	839	April 15, 2022
How to install on localhost Self-hosting	10	2512	April 16, 2020

Npm install fails due to package.json misconfiguration

Related topics