Closed smcguinness closed 7 years ago
Sounds like a big in yarn..
I posted the issue to Yarn https://github.com/yarnpkg/yarn/issues/3935 and they pointed out that the package in Yarn actually references 3.9.1 in the published package.json.
I'm not sure how Yarn got that, whether it was a bug in them grabbing the NPM package, or with this package being published to Yarn having that reference.
I'd like to help resolve if I can, though I'm not sure what I can do, other than raise the issue as I have done here and with Yarn.
Looks like something happened in the prepublish script, and npm didn't catch it as a bug. I published an actual 3.9.1.
Include the command or code you used.
or
Include your output/error.
Yarn installed package.json in node_modules
NPM installed package.json in node_modules