Closed zaydek closed 3 years ago
Now published, albeit broken:
npm ERR! code ENOENT
npm ERR! syscall chmod
npm ERR! path /Users/zaydek/.npm/_npx/29d4925160783d66/node_modules/@zaydek/create-retro-app/bin/create-retro-app
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, chmod '/Users/zaydek/.npm/_npx/29d4925160783d66/node_modules/@zaydek/create-retro-app/bin/create-retro-app'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/zaydek/.npm/_logs/2021-01-30T01_46_26_202Z-debug.log
It’s working!
In principle all create-retro-app should do is create a blanket project. We can initialize dependencies but we don’t have to. I think that’s how Maho works, or maybe it was Sørvør. Anyway, Maybe we just write a small JS script that initializes the folder and dependencies and then the user uses the CLI (e.g. retro-scripts) going forwards.
Can’t we just do like
npx retro-scripts create x
? This is more likely to break because that would be a binary, but still. We should look at how Maho did this because the implementation was tiny.