-
Notifications
You must be signed in to change notification settings - Fork 4
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
Prevent linking in some cases #3
Comments
Is there any way can detect whether it's being installed with the |
Couldn't find anything in the docs so have to test this. |
Apparently, |
It looks like the npm_config_global env variable isn't set by Relevant issue: yarnpkg/yarn#399 Adding a note to the README would be helpful for anyone else encountering issues when using CI and yarn. |
@nanoxd Can you open a new Yarn issue about it? Their intention is to be compatible with npm, so it probably just an oversight. |
Sure 😄 |
Adding the yarn lockfile will break on CI because it no longer sets `process.env.npm_config_global` to `'true'`. `alfred-link` keys off of that to know if it should link the Workflow to Alfred: Relevant: SamVerschueren/alfred-link#3 (comment)
Actually,
alfred-link
should only be invoked when installed globally. Because of this package, tests foralfred-ng2
oralfred-npms
will break because Travis tries to executealfred-link
. What would be the best way to prevent this? Just return and do nothing when ran on Travis?https://travis-ci.org/sindresorhus/alfred-npms/builds/155452588
The text was updated successfully, but these errors were encountered: