Jest: dependency mismatch between github and npm

[ashnur]

🐛 Bug Report

[email protected] installs old jsdom 11.12.0 that includes [email protected]

in github seems to be fixed, but in practice the version installed is still the one above, not the one in the package.json on github

To Reproduce

mkdir test-jestjsdom
cd jestjsdom
npm init --yest
npm i -D jest
npm ls left-pad

Expected behavior

no left-pad to appear as a dependency

envinfo

  System:
    OS: macOS 10.15.1
    CPU: (4) x64 Intel(R) Core(TM) i5-5350U CPU @ 1.80GHz
  Binaries:
    Node: 13.1.0 - ~/.nvm/versions/node/v13.1.0/bin/node
    Yarn: 1.13.0 - /usr/local/bin/yarn
    npm: 6.13.0 - ~/.nvm/versions/node/v13.1.0/bin/npm
  npmPackages:
    jest: ^24.9.0 => 24.9.0 

[thymikee]

Yes, there is mismatch, how is that a bug? npm and GitHub are different services and would need some kind of sync, which is not necessary at all. We publish independently of working on the source. It would be cool to set up automatic releases at some point though. Closing.

[ashnur]

Well, it's a bug to get a different thing than what you are promised - or that's what I thought. And I wasn't sure what else I could say it is? I also do not get you answer, what's the solution here for me?

[markdingram]

@ashnur - It's clearer to see from the timeline here: https://github.com/facebook/jest/commits/master/packages/jest-environment-jsdom/package.json

This change just missed the previous release by a few days, use the tag to confirm what was published to NPM https://github.com/facebook/jest/blob/v24.9.0/packages/jest-environment-jsdom/package.json

Looking at the pattern of previous releases I'd say that a 24.10 release is due pretty soon, so waiting it out could be a solution, that's my plan anyway...

[ashnur]

@markdingram Thank you, I appreciate both your and @thymikee's time that you put into answering me in this issue. Though, there seems to be a misunderstanding.
No amount of detail about the past answers my question, because it is about the future. My question is, what is my solution? We are in the second part of November, end of Fall. This change was introduced a season ago, at the end of August. It seems bizarre to me that millions of jest users still use left-pad because "the patch missed the release". You seem to consider these things as something out of your power, like the weather. But it is not the weather, it's software, the thing we created exactly because it's malleable. So please tell me, what is my solution here? Waiting for the weather to change and the release to arrive is not a solution, is the opposite of a solution :)

P.S. I tried 25.0.0 which btw I think worked more or less on linux, but on catalina it didn't even install, probably for reasons not even related to jest. My overall frustration - if detectable - has nothing to do with this current issue, don't take me too seriously.