I'd like to make it easy to do a thin wrapper so a company could run company-ui add and get Sly without having to specify the whole tool name. General consumers wouldn't need to know they're using Sly
this might just require coming up with a nice way to do it and then document it
custom npm package that forwards requests to the Sly CLI, maybe with a default sly.json?
local script in the codebase that does the above and people npm install that instead?
package.json#scripts like "add": "REGISTRY_URL=http://example.com/registry sly add @example/lib" and then they run npm run add -- dialog
I'd like to make it easy to do a thin wrapper so a company could run
company-ui addand get Sly without having to specify the whole tool name. General consumers wouldn't need to know they're using Slythis might just require coming up with a nice way to do it and then document it
"add": "REGISTRY_URL=http://example.com/registry sly add @example/lib"and then they runnpm run add -- dialog