Skip to content
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

Yarn support #132

Open
brianalbers opened this issue Jan 27, 2017 · 1 comment
Open

Yarn support #132

brianalbers opened this issue Jan 27, 2017 · 1 comment

Comments

@brianalbers
Copy link

Meanio has a postinstall script with npm install hardcoded in package.json. If a parent application is built using yarn with meanio as a dependency, the meanio package dependencies are not loaded into the yarn cache. In turn this breaks the very powerful offline and cached dependency build features of yarn. The hardcoded npm install will not look at the yarn cache and the parent build will break.

Possibly allow an env var, some other external config option, to enable the postinstall script to use yarn instead of npm.

@timelf123
Copy link
Contributor

Does yarn support githubuser/package#branch style versions yet? That was the only thing stopping me from messing around with it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants