Closed FossPrime closed 1 year ago
If you follow the guide as intended that command should always work since a generated v5 app will always install the CLI as a devDependency
.
I'd still be curious if you ran into a problem with it? I know a few people had issues with the old CLI still being installed globally.
I was guiding a newbie on Feathers CLI and he managed to get this while generating a service... not sure if it was because originally the app was created with custom service, or because of some SIGKILL interruption. I don't use the CLI much as 99% of the time, I'm making a prototype and don't want to deal with binary DB's, but do want a real adapter like feathers-memory or what feathers-NeDB used to be. If I see the issue again I'll report.
Summary
This could work 100% of the time... but right now it only works IF you have feathersjs/cli installed globally or in the devDependencies. If you don't you'll have to know it's in
@feathersjs/cli
somehow. That's specially not obvious as the Getting Started guide usescreate-feathers
not the CLI explicitly.Daffl could replace https://www.npmjs.com/package/feathers with the CLI to make it work... Perhaps it's worth cross-publishing.