21–30 of 59 posts
I actually think that a simple Webpack configuration for a React project is pretty easy to understand (thanks to Babel). Here is one that I use in one of my projects [1]. Adding Less support is like one additional entry.
[1]: https://github.com/renke/perpetually/blob/master/webpack.con...
It also absolutely blows my mind. This just feels wrong. 17 separate packages, some providing really basic stuff like serving favicons and parsing POST requests that must be a part of bigger framework. Each package is of different quality, testing strategy, and depends on a different developer who's completely free to abandon his project tomorrow or introduce some backwards-incompatible change. This trend as a whole looks unreliable, like a wobbly house of cards near a working fan.
Earlier quoted context omitted.
What are you talking about? I've never seen a 2k lines todomvc.
Here's my unscientific LOC count results (that I did in 5 minutes). I've removed node_modules and bower_components from the items in: https://github.com/tastejs/todomvc/examples I've also deleted "polymer" and "emberjs_require" since they didn't have any files in them and messes up the `wc -l` $ for x in *; do echo $x; wc -l `find $x/ -name '*js*' -type f | egrep -v 'test|lib|public|vendor|.bundle.js|.cache.js'`; ech…
Impressive and awesome. This is perfect to catch up on using build tools. I focus on core programming concepts in my own work, and at work most of that stuff is automated to just a few commands, so I appreciate the gulp.js part of your tutorial most. Thanks for the great work.
I can't claim to be a Gulp expert, but it's always shocking to me how tools like Gulp and Grunt become so pervasive without strong tutorials. I ignored Grunt for years, always implementing my own hackneyed systems in Python, until I eventually discovered this tutorial[1], which at least got me a good introductory "this is how you use this thing that everybody else already knows how to use, dummy" lesson. [1] - http:/…
Yeah they did kind of just sneak up about a year ago it seems. I remember getting into the field two years ago I didn't hear about them. I suspect the tipping point was the full migration to front-end frameworks instead of just plain JS/jQuery.
Earlier quoted context omitted.
What are you talking about? I've never seen a 2k lines todomvc.
Here's my unscientific LOC count results (that I did in 5 minutes). I've removed node_modules and bower_components from the items in: https://github.com/tastejs/todomvc/examples I've also deleted "polymer" and "emberjs_require" since they didn't have any files in them and messes up the `wc -l` $ for x in *; do echo $x; wc -l `find $x/ -name '*js*' -type f | egrep -v 'test|lib|public|vendor|.bundle.js|.cache.js'`; ech…
This is a react render function mentioned in the tutorial (gist with all code here[0]):
render() {
let delta = this.props.delta ? (
0 ? 'text-success' : 'text-danger'}>
{this.props.delta}
) : null;
return (
{delta}
{this.props.title}
);
}
@delta > 0 ? 'text-success' : 'text-danger' ) do %>
[0] https://gist.github.com/alexggordon/820020aab934bf192b81
Earlier quoted context omitted.
I can't claim to be a Gulp expert, but it's always shocking to me how tools like Gulp and Grunt become so pervasive without strong tutorials. I ignored Grunt for years, always implementing my own hackneyed systems in Python, until I eventually discovered this tutorial[1], which at least got me a good introductory "this is how you use this thing that everybody else already knows how to use, dummy" lesson. [1] - http:/…
Thanks for the resource! Yeah they did kind of just sneak up about a year ago it seems. I remember getting into the field two years ago I didn't hear about them. I suspect the tipping point was the full migration to front-end frameworks instead of just plain JS/jQuery.
Now, to be fair to Grunt, my workflow is usually Python or Go on the backend, and I just wanted something to manage my front-end assets, so it was never a necessity for me, but knowing there's something that does what I want it to do, while being unable to make it do the thing that it does is quite frustrating.
Earlier quoted context omitted.
Here's my unscientific LOC count results (that I did in 5 minutes). I've removed node_modules and bower_components from the items in: https://github.com/tastejs/todomvc/examples I've also deleted "polymer" and "emberjs_require" since they didn't have any files in them and messes up the `wc -l` $ for x in *; do echo $x; wc -l `find $x/ -name '*js*' -type f | egrep -v 'test|lib|public|vendor|.bundle.js|.cache.js'`; ech…
You included all the spec / unit test files, and in some instances you included the framework.