-
Notifications
You must be signed in to change notification settings - Fork 21
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
[FR] Install peerdeps from local package #62
Comments
No eslint things should be installed globally; eslint v6 forces local installs more aggressively anyways. |
Global things aren’t requireable, so theycant satisfy peer dep requirements anyways. |
Yeah I've tried to get everything working with eslint
Don't understand this, could you elaborate? |
Yes. You can’t |
I mean installing the peerDeps before publishing lets me test eslint out from the command line to make sure it's working fine, so the globally installed peerDeps do make a difference (I suppose?). |
I’m not sure what you mean. If you want to test a shared config before publishing, you’d npm link it, and each of its peer deps, into another project (or, install it from git in the other project). |
I'm just trying to test a shared config myself before publishing to make sure it works. Doesn't matter though - I figured I'll just use |
Don't know if this isn't already possible, but I'd like to be able to install peerdeps globally from a local package.
I have a local package (eslint-config-sarpik) which I have installed globally (not via linking (should I just use linking?)).
Sometimes I add some peerDependencies & I'd like to be able to install them myself globally prior to publishing.
Being able to do something like
npx install-peerdeps --global --yarn ./
would be awesome.See also #51 for locally linked packages.
The text was updated successfully, but these errors were encountered: