Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support microbundle config file #249

Closed
xiaoxiangmoe opened this issue Nov 16, 2018 · 6 comments
Closed

support microbundle config file #249

xiaoxiangmoe opened this issue Nov 16, 2018 · 6 comments

Comments

@xiaoxiangmoe
Copy link

xiaoxiangmoe commented Nov 16, 2018

microbundle.config.json microbundle.config.yaml ,etc.

@xiaoxiangmoe xiaoxiangmoe changed the title support .microbundlerc.json file support microbundle config file Nov 16, 2018
@ForsakenHarmony
Copy link
Collaborator

What are you looking to configure? It's supposed to be minimal and zero config

@xiaoxiangmoe
Copy link
Author

xiaoxiangmoe commented Dec 1, 2018

@ForsakenHarmony no-compress,strict,format

@ForsakenHarmony
Copy link
Collaborator

you can do that with cli

@paulmelnikow
Copy link

Good defaults and minimal config is great and I'm all for that. 👍 Though, wanted to lend a voice of support for config files when there are necessary options, especially yml which lends itself to human readability.

Breathing room makes the configuration more understandable and maintainable. You can leave comments, and more easily transfer settings across projects. It also avoids using negative options (like no-compress), which are harder to understand than positive ones (compress, defaulting to true).

@adjohnston
Copy link

What are you looking to configure? It's supposed to be minimal and zero config

I would like the chance to configure some of what PostCSS is doing. Specifically, whether to use modules, extract true or false and change the generated scope names.

@treshugart
Copy link

treshugart commented Jan 25, 2019

It would be much easier to specify names for external packages and other options using the cosmiconfig conventions. While something can be targeted as zero config, I think it's pragmatic to provide an ergonomic way to do this. This is especially true if you have multiple microbundle commands specified in your scripts.

I'd expect to be able to configure most things you can on the CLI from an external configuration.

I'd be happy to provide a PR for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants