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

Idea: Configuration file wizard webapp #4

Closed
andywer opened this issue Nov 20, 2016 · 4 comments
Closed

Idea: Configuration file wizard webapp #4

andywer opened this issue Nov 20, 2016 · 4 comments

Comments

@andywer
Copy link
Owner

andywer commented Nov 20, 2016

Build a simple webapp for creating webpack configs.

Input:

  • Entry point(s)
  • Output file path(s)
  • Features like babel, dev-server/dashboard, postcss, css modules, sass, ... (select babel, dev-server and autoprefixer by default)

Output:

  • Webpack config file (+ download button)

Show next steps:

  • start and build scripts to add to package.json
  • How to run the dev server / how to trigger a production build
@andywer andywer changed the title Webapp: Configuration file wizard Idea: Configuration file wizard webapp Nov 30, 2016
@vitorbal
Copy link

vitorbal commented Dec 7, 2016

Thank you for the awesome project! This is a great idea and I plan on trying webpack-blocks for my next app.

Just throwing it out there, what do you think about alternatively making the wizard a CLI tool? We use Inquirer for ESLint's --init command and at the end of the process create all the necessary config files, install all npm packages, etc. based on your answers.

@andywer
Copy link
Owner Author

andywer commented Dec 7, 2016

@vitorbal That would be #7 then :)

But maybe I should close this issue for now in favor of #7 which covers a CLI tool and presets.

@andywer andywer closed this as completed Dec 7, 2016
@andywer
Copy link
Owner Author

andywer commented Dec 7, 2016

@vitorbal PS: But feel free to add further thoughts here or in the other issue ;)

@vitorbal
Copy link

vitorbal commented Dec 7, 2016

@andywer Oops, sorry, totally missed #7. Thanks for the quick reply :) I'll add some further thoughts to #7 if I think of anything 👍

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

No branches or pull requests

2 participants