[create] allow organization standards when creating a project
See original GitHub issueFirst of all I think it is great that someone thought about creating standards for WC and a CLI tool to bootstrap a project applying them by default.
The problem starts when you have to create a project for your organization. Then you probably have different coding standards. This ends up using npm init @open-wc
and replacing configuration files after that. Obviously an organization should afford to have own tool to do this but I would argue that @open-wc
is great and is worth using it instead internal tool that will be written once and never maintained.
I would like to see a configuration option to install different modules for prettier
, eslint
, and commits. Or maybe the tool would detect a globally installed module that has required configuration files that will be applied to generated project and the user selects the template in the CLI UI. I think the later is a better UX for developer than configuration option.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top GitHub Comments
This will get really messy really fast. Personally I think it would be better to add docs on how to modify the config or create your own generator based off of this one. there are way too many variables to try to predict end-user custom configs and tooling preferences
Hey there, it’s me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Open Web Components!