I copied [package.json](https://github.com/discourse/discourse-theme-skeleton/blob/main/package.json) from the latest discourse-theme-skeleton/package.json at main · discourse/discourse-theme-skeleton · GitHub It’s not big: { private: true, devDependencies: { @discourse/lint-configs: "2.21.0", emb…

[이미지] pfaffman: Run yarn install --frozen-lockfile FWIW this looks like the problem step? Yarn should not be running full stop? (PS don’t you just love it when you take 15 minutes to update a repo, then some meta issue takes you hours :sweat_smile: )

This is your problem: .github/workflows/discourse-theme.yml 0efb1ef3d if [ -f yarn.lock ]; then Remove your yarn.lock file from the repo but leave (and update!) your pnpm-lock.yaml file Bonus points :sports_medal: Idea…

[이미지] merefield: Bonus points: Ideally this should have been a PR so you haven’t got failing CI on your main branch. That’s true. I’m starting to try to remember to do that; it’s just not automatized yet. I’m up to doing it about 30% of the time. :slight_smile: Now I’ve got this: Run pnpm …

[이미지] pfaffman: Run pnpm install --frozen-lockfile ERR_PNPM_LOCKFILE_CONFIG_MISMATCH Cannot proceed with the frozen installation. The current "settings.autoInstallPeers" configuration doesn't match the value found in the lockfile Update your lockfile using "pnpm install --no-frozen-lockfile" …

But when I ran pnpm install --no-frozen-lockfile and then used the new lock file, github then gave me the bundler error. I should be able to use the one in discourse-theme-skeleton, right?

[이미지] pfaffman: Could not locate Gemfile Add the Gemfile

Wait. The Gemfile is for ruby, right? But here: pfaffman@noreno:~$ cd src/discourse-repos/discourse-theme-skeleton/ (main) pfaffman@noreno:~/src/discourse-repos/discourse-theme-skeleton$ cp pnpm-lock.yaml Gemfile.lock Gemfile package.json stylelint.config.mjs ~/src/pfaffman/discourse-custom-home…

[이미지] pfaffman: Wait. The Gemfile is for ruby, right? Guess it’s for any specs, it’s required by the CI script.

“JS 의존성 설치” 단계에서 테마 린트 오류 발생

개발

merefield (Robert) 6월 1, 2025, 4:25오후 4

This is your problem:

Remove your yarn.lock file from the repo but leave (and update!) your pnpm-lock.yaml file

Bonus points Ideally this should have been a PR so you haven’t got failing CI on your main branch.

글		댓글	조회수
Discourse core is switching to pnpm for JS package management Development dev-news	24	1527	2월 13, 2025
The engine "yarn" is incompatible with this module. Expected version "please-use-pnpm". Got "1.22.19" Support	4	427	2월 7, 2025
Trouble with eslint since recent change to plugin-skeleton because failed to run yarn install Development	0	498	11월 29, 2023
Ember addons are resolving as incorrect peer dependencies. -- fixed by removing "content-tag@3.1.0": "patches/content-tag@3.1.0.patch", Development	8	445	2월 12, 2025
Npm install fails due to package.json misconfiguration Development	10	5082	11월 5, 2018

“JS 의존성 설치” 단계에서 테마 린트 오류 발생

Related topics