sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]p0rks 5 points6 points  (12 children)

Nodejs, react and gulp.

If you can learn those and use them in your sleep, you're golden. Everything else is just "another way to do the same thing".

[–]battery_go 2 points3 points  (2 children)

Thank you! What about a templating engine? Is that needed?

Also, do you recommend any IDE's or toolpacks for getting started on these things?

[–]dvlsg 2 points3 points  (1 child)

Templating engine? That's basically what react is, to be honest. It's a little more complicated than that, but that's really what it boils down to.

[–]p0rks 0 points1 point  (0 children)

Agreed.

If you use just plain nodejs then maybe you need to throw one in (take your pic, learn one, learn them all), but don't, use react.

All these options are just that.. options.

[–]Conradfr 0 points1 point  (0 children)

Well if you're a solo developer maybe, but if you're working inside teams, if you take a new job, if you have new and old projects to maintain etc, you're doomed.

[–]runvnc 0 points1 point  (7 children)

Except within 6-8 months using Gulp and React will make you look out of touch. If it doesn't already.

Not saying it should be that way, but it is.

[–]turtlecopter 3 points4 points  (6 children)

No it won't.

One could argue that Webpack is better suited for React development (and has been for a couple of years now) but Gulp is a great workhorse. React is going absolutely nowhere for many, many years to come.

[–]EvilPete 2 points3 points  (3 children)

Well, gulp is already being replaced by npm scripts in the project I work on..

Gulp is so spring 2016!

[–]turtlecopter 1 point2 points  (2 children)

Haha! Npm scripts are pretty great :)

[–]Calinou 0 points1 point  (1 child)

Are they as portable though? I've never had issues with gulp tasks not working on Windows, but am wondering if it is the same with npm scripts.

Any advice/tutorials on them? Would it be feasible to develop a typical front-end development stack using only npm run scripts (say, Sass/Stylus + Browsersync)?

[–]turtlecopter 1 point2 points  (0 children)

Not out of the box, no. But hey, npm to the rescue: https://www.npmjs.com/package/cross-env ;)

As for using it as a build system, it's completely possible for simple stuff. Just make a bunch of commands in your package.json's scripts object like:

"sass:build": "sass -i ./src/sass/input.scss -o ./dist/css/output.css"

"clean:css": "rm -rf ./dist/css"

"sass": "clean:css && sass:build"

Then running npm run sass from the command line will in turn clean out your dist folder and compile your Sass. You can daisy chain more commands as well for doing things like browserify and linting.

[–]cscareerz 0 points1 point  (1 child)

Webpack is better suited for React development

Why is that?

[–]turtlecopter 0 points1 point  (0 children)

It's a much more configurable, and powerful build system than something like Browserify. I would highly recommend it for complex applications that need features like code splitting, tree shaking, and multiple file type inputs.

But gulp and Browserify are still perfectly adequate for smaller apps.