Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

Development Tools Introduction to Front End Performance Optimization Combine and Minify Assets Minify Assets

Gavin Ralston
Gavin Ralston
28,770 Points

Grunt vs Gulp vs npm

So this article on not using js build tools makes a compelling case for not relying on build tools with scary config files.

Would npm be a good way to introduce the use of a service like this, or is that just one guys' convincing but not-necessarily-accurate opinion?

The complaints about grunt and gulp come across as 'mountains out of mole-hills' type rhetoric - but, I'm genuinely interested in Keith's followup blog post How to Use npm as a Build Tool. The syntax he uses looks great.

Gavin Ralston
Gavin Ralston
28,770 Points

See, I was thinking there could be inadvertent mountain-building there, but the logic that "you're building solutions for solutions and creating massive, unwieldly dependency trees" is fairly convincing. Especially when you just see the glimpse of the npm configs being a trivial key/value pair.

If it's really a "99% of the time solution" I'd say why not start there at least?