INinsin·Jan 31, 2017
> No one is going to remember all the packages they need to include each time they start a new project. They're doing what I'm doing; copy paste from the last project, like some holy script scrawled by ancient masters from long ago.
If it hurts, don't do that then - put all your build stuff and devDependencies in a separate module and install it into your next project like any other development dependency, adding new capabilities as you need them and bumping the version number when you need to like any other tool. You can start doing it yourself [1] or use one someone else made earlier [2] - there are an increasing number of these toolkits about.
> But seriously I can't use `<SomeThing onClick={this.handleClick}/>`?
You can do exactly that if you're using React or one of the many libraries which use React-like conventions (Preact, Inferno
Read the rest
, Mithril.js etc.), so just use one of them.
> But why do I have to write a cryptic webpack.config.js for every project? Why do I have to install Babel and webpack separately? Why do I need to install 3 other babel related packages? Why do I need a .babelrc? It's just insane. There should just be one tool, one command. "modernjs build". Done.
You don't have to, and there are lots of tools which will take care of this for you (see [2] again). That's the exact same workflow I wanted, so I created it for the types of projects I'm working on [3] - it doesn't take much extra effort to turn your own preferred build setup into a command.
[1] https://github.com/insin/ad-hoc-reckons/blob/master/Creating...
[2] https://github.com/facebookincubator/create-react-app#altern...
[3] https://medium.com/@jbscript/quick-development-with-nwb-35f3...