Guides - Starter Kits about webpack.js.org HOT 18 CLOSED

@mxstbr Hey the more boilerplates the better. However I think its extremely important to note SOMEWHERE, that:

Boilerplates should be used as Proof of Concepts to help you learn different webpack techniques for respective frameworks to apply to your own.

Should not be used to copypasta everything and try to fit your flow around it. Or something like that. Anyone disagree?

from webpack.js.org.

@skipjack good catch - the description field was supposed to be there all along but there was a bug that caused it not to show up. I have fixed it in tool-list 0.9.2.

from webpack.js.org.

Pff, who needs RSK, react-boilerplate is where it's at! https://github.com/mxstbr/react-boilerplate

😉

from webpack.js.org.

@ahfarmer Would it make sense to join forces here given you maintain a list like this already? It would push the scope a notch (not just React), but at least we would have it all in one place then.

from webpack.js.org.

@bebraw possibly - most of the projects on my list use Webpack but many use other bundlers like browserify or rollup

I'd be happy to provide the starters from my list that do use Webpack - but do you want to list all of them in the guide? There are over 80.

from webpack.js.org.

@ahfarmer Yeah, good point.

One option - we'll push the data to some repo in JSON format (you can maintain this if you want to). Then we'll consume the webpack specific one here and you can accept PRs against it. This repo could be consumed as a npm dependency at the sites and it would push the problem to the right place while allowing sharing work.

After this we would hook up some way to visualize the JSON data on the site (simple table would do) and that would be it.

from webpack.js.org.

@bebraw mulled it over - sounds like a great idea. Will just take a couple days to get the repo and npm package up. I'll post a comment here when I'm done.

from webpack.js.org.

@bebraw I've published the npm package tool-list (github). Data can be accessed with JSON or JavaScript. Please let me know if this is useful or if you were picturing something else.

Right now there are 107 React starter projects, 81 of which use Webpack. I'll work on filling it out with more non-React starters soon.

from webpack.js.org.

@ahfarmer That looks great. Maybe it would be nice to expose a mechanism to update stats (stars etc.) at consumer side so you don't have to worry about releasing new versions. This way I could refresh the data on build.

from webpack.js.org.

Never mind. That's the way it rolls. Nice. 👍

from webpack.js.org.

I can tackle adding a guide for this...

I'll start with a introduction mentioning @TheLarkInn's point that:

Boilerplates should be used as Proof of Concepts to help you learn different webpack techniques for respective frameworks to apply to your own.

and not to just copy and paste and code. We should also probably state that none of these are officially supported by us.

From there I'll list the 5 starter kits mentioned at the top by @Awk34 and @mxstbr and then if anyone wants to pr more, great! @webpack/documentation-team if no one has any issue with this I'll pr this sometime soon. @bebraw unless you still wanted to tackle it?

from webpack.js.org.

@skipjack A good starting point would be to consume JSON from tool-list and then construct a table based on that. Sorting etc. can be added later. Remember to credit Andrew on the page.

from webpack.js.org.

A good starting point would be to consume JSON from tool-list and then construct a table based on that.

Hmmm, I see the value in that but then how would people add new ones? Would they have to submit a PR to the tool-list repository or tag their repository a certain way?

Remember to credit Andrew on the page.

Sure thing.

from webpack.js.org.

@skipjack To add something to the list, you have to PR against this file. I don't see any other option as there are literally thousands of boilerplates out there. At least now it's curated.

from webpack.js.org.

FYI I do plan on keeping tool-list up-to-date for the foreseeable future - and if I do ever fall behind on that, others can always fork it. I merge pull requests roughly every 1-2 weeks.

from webpack.js.org.

@ahfarmer @bebraw ok great thanks for the clarification. I'm happy with moving forward with that approach then...

@bebraw feel free to start if you have any bandwidth, if not, I may tackle it as soon as I have a chance. Were you thinking of pulling the JSON in during the build or at runtime?

from webpack.js.org.

@skipjack If the JSON is small enough, it might make sense to pull it during the build. The first version doesn't have to be particularly pretty.

from webpack.js.org.

@ahfarmer just starting this now.. should have a pr in the works by sometime tomorrow. Do you plan on adding a description to each starter kit object at some point? If you're looking to pull it dynamically, maybe that little sentence at the top of each git repo would do?

from webpack.js.org.