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

Scaffold: Better defaults for webpack-cli init questions #788

Closed
misterdev opened this issue Mar 13, 2019 · 3 comments · Fixed by #817
Closed

Scaffold: Better defaults for webpack-cli init questions #788

misterdev opened this issue Mar 13, 2019 · 3 comments · Fixed by #817

Comments

@misterdev
Copy link
Contributor

misterdev commented Mar 13, 2019

Is your feature request related to a problem? Please describe.
webpack-cli init from my point of view has 2 main purposes, making the setup faster and making it easier expecially for beginners. For these reasons I think the default answers for webpack-cli init should be modified to allow creating the simpler possible setup.

Describe the solution you'd like

  1. ? Will your application have multiple bundles? (Y/n)
    Having multiple bundles is an "advanced" and less common configuration compared to having just one entry point.
    I think the default should be (y/N)

  2. ? Will you use one of the below CSS solutions?
    Same here, the default option is SASS where a better default would be No:

    > SASS
      LESS
      CSS
      PostCSS
      No
    

    Also, I use init mainly to scaffold node projects where I don't use CSS.

Additional context
I think this is a very very small modification that can slightly improve the user experience.

I can work on this if it is something desirable :)

@rkishan516
Copy link

@evenstensberg & @misterdev Can I work on this ?

@misterdev
Copy link
Contributor Author

Hi @rkishan516, I'm already working on this. Thanks for your interest 👍

@anshumanv
Copy link
Member

Fixed in #794
Can be closed. 😄

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

Successfully merging a pull request may close this issue.

4 participants