You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@dherman It looks like init and create are not aliases with each other. Maybe we can resolve this simply by documenting it as npm create instead of npm init? That way if a user substitutes yarn, it will still work.
With that said, it's still going to call out to npm internally.
Subject of the issue
yarn init
runs the standard init process, notcreate-neon
.Your environment
Steps to reproduce
Run
yarn init neon my-project
.Expected behaviour
Should call
create-neon
correctly likenpm init neon my-project
does.Actual behaviour
Running
yarn init neon my-project
only runs the standardyarn init
process to create a NPM package, not thecreate-neon
process.The text was updated successfully, but these errors were encountered: