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

Choosing yarn leads to npm recommendations :) #495

Closed
jlengrand opened this issue Jun 14, 2019 · 3 comments
Closed

Choosing yarn leads to npm recommendations :) #495

jlengrand opened this issue Jun 14, 2019 · 3 comments

Comments

@jlengrand
Copy link
Contributor

Heyo,

A small one, but nonetheless.

During the init process, I choose yarn. Result is as expected, I get a yarn.lock file.

However, at the very end of the process :

All you need to do is run:
  cd under-cover
  npm run start

I'm being asked to use npm :).

@stale
Copy link

stale bot commented Jul 5, 2019

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

@stale stale bot added the inactive label Jul 5, 2019
@LarsDenBakker
Copy link
Member

I don't really mind this, probably it's a lot of work to customize all these messages. Defaulting to npm is fine I think.

@stale stale bot removed the inactive label Jul 28, 2019
@jlengrand
Copy link
Contributor Author

It's most likely not gonna lead to any big errors. It's just counterintuitive. Can be closed if you don't intend to do anything 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