-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Separate detection for npm and Yarn #9
Comments
From the package description:
|
Sorry, I thought this package had a different purpose... |
I'm curious about your use-case. Why do you need to explicitly know whether it's npm or Yarn? |
I'm using In a |
Hmm, I think we could maybe do a breaking release and make it: -const {isNpm} = require('is-npm');
+const {isNpmOrYarn, isNpm, isYarn} = require('is-npm'); That would also make it more explicit. |
Nice, thanks |
Fixes sindresorhus#9. Breaking change.
I found this library gives false positives when used in a lifecycle script, for example, importing
is-npm
in a script called byprepublishOnly
returnstrue
when executingyarn publish
.This worked for me:
The text was updated successfully, but these errors were encountered: