dev-cli
dev-cli copied to clipboard
oclif
`oclif-dev pack:deb` generates `chown/chgrp` permission errors. Is this command intended to be run with sudo / as root? These appear to be the relevant lines: https://github.com/oclif/dev-cli/blob/master/src/commands/pack/deb.ts#L82-L83
## Expected Behavior ## When you run a Windows installer (built with NSIS) to install a new version of your CLI over the top of an old one, it uninstalls...
Dev-cli, being a Node.js package, can't have OS level dependencies. Consider using a purely node based alternative for hashing.
I have a single CLI (TypeScript) and I just realized that there are no commands in the command section of my readme. I found that this is the behavior for...
The readme file was behaving well until recently. Not sure what caused this: https://github.com/mshanemc/shane-sfdx-plugins It's having trouble finding the command names?
Hi team, amazing framework, tank you so much! Is it possible to generate a simple executable file (like regular pkg does) instead of a tar file when running "oclif-dev pack"....
I am trying to use oclif-dev pack command to generate standalone tar balls, but i get the following issue when it tries to create tarball for Windows: oclif-dev: extracting node-v12.16.1-win-x64...
I want to know if it is possible, add arm64 packaging in oclif-dev. I wrote [penguins-eggs](https://github.com/pieroproietti/penguins-eggs) a Linux remaster/installer system using this framework, and I'm able to produce debian packages...
Getting this warning when running `oclif-dev pack:win` ``` oclif-dev: building target enjinn-v1.1.2-win32-x64.tar.gz oclif-dev: building target enjinn-v1.1.2-win32-x86.tar.gz Processing config: /etc/nsisconf.nsh Processing script file: "/home/rshea0/code/enjinn/tmp/windows-x64-installer/enjinn.nsi" (UTF8) Processed 1 file, writing output (x86-ansi):...
Hi there, If you run `oclif-dev readme` it currently generates a bunch of `h2` tags for the commands using `##` but if you put it in a context of a...
