CLI config
See original GitHub issueWhat are your thoughts on adding config via a CLI as an alternative to using package.json
. We’d love to start using this on our apps but would rather not have to update each apps’ package.json
?
I’d be happy to attempt a PR but want to know your thoughts?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Configuring the AWS CLI - AWS Command Line Interface
This section explains how to configure the settings that the AWS Command Line Interface (AWS CLI) uses to interact with AWS. These include...
Read more >cli-config - npm
A 'one call' API maps lib to a command line interface. Merges settings from package, home, project, project group, command options, ...
Read more >configure — AWS CLI 2.9.11 Command Reference
Description¶. Configure AWS CLI options. If this command is run with no arguments, you will be prompted for configuration values such as your...
Read more >Configuring the CLI - Oracle Help Center
Configuring the CLI · Specify a default profile. · Set default values for command options so you don't have to type them into...
Read more >wp config | WP-CLI Command
Refreshes the salts defined in the wp-config.php file. Command documentation is regenerated at every release. To add or update an example, please submit...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
So thinking of some other tools that have a few ways of configuring it, there seems to be a sort of option of
a.
package.json
properties (as bundlesize currently uses) b..config.yml
or.config.json
c. CLI argsFor simple things you could use CLI but then when you want more config you can move to a or b to make it less bloated. I think CLI is good for simple config like
@leggsimon I think we should skip option b for now (
config.yml
) and only implement CLI params