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

Use npm (instead of Yarn) as default package manager #166

Open
tinesoft opened this issue Oct 22, 2018 · 1 comment
Open

Use npm (instead of Yarn) as default package manager #166

tinesoft opened this issue Oct 22, 2018 · 1 comment

Comments

@tinesoft
Copy link
Owner

tinesoft commented Oct 22, 2018

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ x] feature request

Desired functionality.

Yarn is giving me too much trouble, and it's no longer so better as latest npm in speed, consistency and features. For example, it is not working well with nvm.

In fact, when using nvm in a library, the gulp link(npm link) will symlink the project folder to a global node_modules matching the node version being used (for eg: ~/.nvm/versions/node/v8.12.0/lib/node_modules/)

But running yarn install in demo/ app , is not linking to the library in that nvm-node-related global modules, but instead to /usr/local/lib/node_modules/<your-project>.

Mention any other details that might be useful.

  • npm option should default to true and save in .yo-rc.json as useYarn key
  • config/helpers#installDependencies() should consider that useYarn flag
  • update .travis.yml's cache section accordingly
@ghost
Copy link

ghost commented Oct 29, 2018

Let me try

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

No branches or pull requests

1 participant