-
-
Notifications
You must be signed in to change notification settings - Fork 940
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
Add the pnpm create
command
#3829
Conversation
Oh wow, I just found out that |
For another thought, I kind of like Yarn's interface more with this. They have two commands:
There are two reasons why I like this:
All in all, I propose we have |
I'm having trouble with
Could you help me diagnose this? |
Sounds good. |
I never used watch. Try running |
it will be easier if you create a separate PR for |
Yeah, that was an accident. My bad |
Hello, I meet the same problem. Is there any solution can fix it? |
I'd like to start a discussion about the
init
command forpnpm
.Here's how I see it:
pnpm init
behaves similarly tonpm init
, produces an interactive wizard for creating a new Node projectnpm
asks for a test command, and if you omit it, it creates a script"test": "echo \"Error: no test specified\" && exit 1"
. I believe this is unnecessary clutter since most of the time, it's too early to decide on thetest
command when the project is just initialized. And it's not like a Node project isn't valid unless it defines atest
script.pnpm init react-app
behaves similarly tonpm init react-app
, essentially transforming the call intopnpm dlx create-react-app
.Command-line options:
-y
,--yes
: Forpnpm init
, skips all the questions and produces a defaultpackage.json
. Ignored forpnpm init <pkg>
.Unlike
npm
, the--force
option is not supported. I couldn't figure out what it does :pNot sure what to do about workspaces. Should this option support being run in workspaces?