Skip to content
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

WARNING to all yalc users: your npm and yarn versions matter! (docs might need updating) #187

Open
Domiii opened this issue Mar 30, 2022 · 1 comment

Comments

@Domiii
Copy link

Domiii commented Mar 30, 2022

TL;DR

Attempt 1

Steps to repro (after yalc publish):

  • yalc add @my-scope/my-package
  • npm install
  • It complains that it cannot find @my-scope/my-package on the registry: ERROR: ... no matching version found ...
  • Do a npm cache clean --force (explained here)
  • Still the same....

Attempt 2

This time, reverse the order:

  • npm install
  • yalc add @my-scope/my-package
  • Seems to work!
  • npm start
  • Now, it complains about missing dependencies of @my-scope/my-package because it evidently did not install it quite right.

Sln

  • volta install node@16.13.1 (i.e. upgrade to node@16.13.1 from my previous node@16.13.0)
  • NOTE: This also upgrades npm to 8.1.2.
  • Try again: It works now!

NOTE: From the npm changelog between 8.1.0 and 8.1.2, I don't see why 8.1.2 works. But I'm glad it does.

Also note that it generally has the same problems with yarn@1, but supposedly works with yarn@2 and yarn@3 (haven't tried that yet).

@Domiii Domiii changed the title WARNING to all yalc users: your npm version matters! (docs might need updating) WARNING to all yalc users: your npm and yarn versions matter! (docs might need updating) Mar 30, 2022
@jafin
Copy link

jafin commented Jan 31, 2023

node 16.13.2
npm 9.4.0
npm ci
error: No matching version found for <yalc package>

revert npm to 8.1.2
npm ci works again.

Other npm versions I tested:

failed

  • 8.19.3
  • 8.13.0
  • 8.8
  • 8.5
  • 8.4.1
  • 8.4

passed

  • 8.3.2
  • 8.3
  • 8.1.2

So perhaps 8.3.2 ... 8.4+ broke something

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants