Skip to content
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.

create-project defaults to yarn if present even when run via npx #1260

Closed
edmorley opened this issue Dec 19, 2018 · 4 comments · Fixed by #1396
Closed

create-project defaults to yarn if present even when run via npx #1260

edmorley opened this issue Dec 19, 2018 · 4 comments · Fixed by #1396
Labels
Milestone

Comments

@edmorley
Copy link
Member

To try and reproduce #1249 locally I was hoping to run create-project using npm rather than yarn.

However running npx @neutrinojs/create-project somename always results in yarn being used (if it's installed) rather than npm, for the various commands that are run during project creation (such as package installation and initial lint fix).

We should make create-project use the same package manager as it was run with.

@edmorley edmorley added the bug label Dec 19, 2018
@edmorley edmorley added this to the v9 milestone Dec 19, 2018
@edmorley edmorley removed this from the v9 milestone Dec 19, 2018
@eliperelman
Copy link
Member

See also yarnpkg/yarn#5063

@eliperelman
Copy link
Member

yarnpkg/yarn#7127

@eliperelman
Copy link
Member

As soon as yarn v1.16.0 is out of RC we can remove the current yarn check and use the presence of an environment variable.

@eliperelman
Copy link
Member

Yarn has been updated to v1.16.0.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

Successfully merging a pull request may close this issue.

2 participants