38 Commits (b9308ba4166ff0d9b774f9393e0dbd82d5f4c97f)
 

Author SHA1 Message Date
Zed A. Shaw b9308ba416 Warn the M1 mac users. 2 years ago
Zed A. Shaw 933db224a4 Got the git URL wrong for the option --using. 2 years ago
Zed A. Shaw ebdcf509fb Simplify the process by just assuming my own git. 2 years ago
Zed A. Shaw 82813aec03 The recursive remove doesn't work on Windows. Still not sure if cmd.exe or powershell will be used on all platforms but this rd command works. 2 years ago
Zed A. Shaw 5f0432fb70 VERSION 0.3.0: Upgrades to Node 18 LTS and adds the option to keep the .git directory for development or exploration/tracking changes. 2 years ago
Zed A. Shaw 954e74b8bc Version bump. 2 years ago
Zed A. Shaw 30969b5e22 Small fixes to path problems on windows. 2 years ago
Zed A. Shaw 99c787ce92 Now it will copy the contents of the template directory, but with no processing currently. 2 years ago
Zed A. Shaw f9bed87ffb Apparently, git's clone --templates feature is nothing like what the documentation describes. It _only_ installs files that are on the local machine, rather than from the repository content which is what I'd expect based on the documentation. 2 years ago
Zed A. Shaw dde93d5f27 Wrong spelling on the git option. 2 years ago
Zed A. Shaw 52a9ba3cee Wrong spelling on the git option. 2 years ago
Zed A. Shaw d3d695bb33 Add in the git templates for testing. 2 years ago
Zed A. Shaw b164a9091f Create now checks out the real repository at bandolier-template. 2 years ago
Zed A. Shaw 1f472d7256 Update the README to handle the common Windows SSL certificate expired. 2 years ago
Zed A. Shaw f0421a2976 First sort of working isntaller. 2 years ago
Zed A. Shaw 06212d993a Update the script with the real name. 2 years ago
Zed A. Shaw d95bb1a511 Significant cleanup thanks to @AmyShackles on Twitter. 2 years ago
Zed A. Shaw 05cdc03f31 Clean up and get ready to dev the real command. 2 years ago
Zed A. Shaw d85a5b9e52 Make executable. 2 years ago
Zed A. Shaw f73423c1bb Up the version. 2 years ago
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