18 Commits (1ef7198fcba8c7c04c058f691c6468b7e8134936)

 

All Branches   

Search

Author	SHA1	Message	Date
Zed A. Shaw	1ef7198fcb	One more FAQ regarding why not an npm create.	2 years ago
Zed A. Shaw	6278e47308	Drop the version to something more realistic, then make the version command.	2 years ago
Zed A. Shaw	9086f2fdf6	Test out doing updates.	2 years ago
Zed A. Shaw	e8417d30bf	First stab at the documentation.	2 years ago
Zed A. Shaw	3bb8fa35a5	Settling on this name instead.	2 years ago
Zed A. Shaw	b85777eafc	Finally settled on a simple name.	2 years ago
Zed A. Shaw	85385a7eb3	The create command tests out if you can do options and seems to work just fine.	2 years ago
Zed A. Shaw	809e0afefa	You need to have a bin named after what you want people to run, but that means you probably don't even need to name the project the same as the npx command.	2 years ago
Zed A. Shaw	d0a63a7acf	Setting up a base project for this.	2 years ago
Zed A. Shaw	98f11eca8f	Now see if it will work as a create command.	2 years ago
Zed A. Shaw	40eae72a7b	Sigh why is this so stupid.	2 years ago
Zed A. Shaw	51a7519c68	Ok then a different command?	2 years ago
Zed A. Shaw	9c75fda363	Maybe it's the package name?	2 years ago
Zed A. Shaw	8064c0af21	Maybe this time it works?	2 years ago
Zed A. Shaw	22b4490777	Looks like you have to name it the same as the create package name?	2 years ago
Zed A. Shaw	95999abdb7	Change the name since npm insists on it having the name create-	2 years ago
Zed A. Shaw	9126ad601a	Testing how create works.	2 years ago
Zed A. Shaw	4c883eb183	Initial commit	2 years ago