Commands
secco init
Section titled “secco init”Run this command inside your destination folder. You’ll be asked questions about your source folder and at the end of the questionnaire a new .seccorc config file will be created.
By default, the secco init command is an interactive prompt. However, if you want to use it in non-interactive environments you can provide both --source and --yes flags.
secco init --source=/absolute-path/to/directory --yesOptional flags:
--source: Absolute path to the source directory--yes: Skip confirmation prompts
secco will scan your destination’s package.json file and compare it with the available packages inside your source. It’ll then copy over all changes into your destination’s node_modules folder. Additionally, a watch task is started to continue copying over changes. Packages that have "private": true set will be ignored.
Typically you’ll want to also start a watch script inside your source to continuously compile your package artifacts.
secco packages
Section titled “secco packages”If you don’t want the default secco command to copy over all packages of your source, you can use the secco packages command.
It allows you to provide a list of packages for secco to watch. Separate them by spaces like so:
secco packages ars aureaYou need to use the exact package names, things like regexp or glob patterns are not supported.