News for hackers. Stuff that matters.

A comment on The Node ecosystem still has tooling problems. Parent comment

Re:The Node ecosystem still has tooling problems by ravenstine on Saturday July 30, 2022 @06:17PM (#32290921)
Yes, there is a lot of shit, but stick to ES2015+ and you'll be mostly fine. No reason to continue with the .cjs .mjs crap. Either set "type": "module" or use Deno (the superior option) and don't look back. If others still want to use Common JS, that's their problem. Yeah, a lot of modules won't work out of the box because they're Common JS, and visa versa, but screw Common JS. That and goofy junkware like Gulp and Grunt which are overcomplicated, change their APIs frequently, and don't really do anything better than a Makefile. Ok, Gulp might be helpful if you're running Windows, but I pity those who still do web development on Windows without WSL2.
[ Parent | on HN ]
Re:The Node ecosystem still has tooling problems by andrew_ on Saturday July 30, 2022 @06:46PM (#32291136)
Gulp and Grunt? Are you a time traveler from 2012?
[ Parent | on HN ]
Re:The Node ecosystem still has tooling problems by jitl on Saturday July 30, 2022 @09:38PM (#32292316)
¯\_(ツ)_/¯ used to build Typescript: https://github.com/microsoft/TypeScript/blob/main/Gulpfile.j...
[ Parent | on HN ]
Re:The Node ecosystem still has tooling problems by andrew_ on Saturday July 30, 2022 @09:48PM (#32292379)
That is freaking bananas. Thanks for sharing.
[ Parent | on HN ]
Re:The Node ecosystem still has tooling problems by aordano on Saturday July 30, 2022 @09:47PM (#32292372)
Gulp is practical to insert extra behavior if you have a multi-step build process and are allergic to Webpack. Just write a gulpfile and spawn whatever you need spawning, like some glorified bash that is already in JS so you don't need to manage more languages.
[ Parent | on HN ]
Re:The Node ecosystem still has tooling problems by bluefirebrand on Saturday July 30, 2022 @08:38PM (#32291868)
I worked on a project using Gulp and Grunt as recently as 2020.

This was a product the company I was working for inherited from a merger. They bought the company for this product.

It was a nightmare of bad software practices. Still using Gulp in 2020 was only the tip of the iceberg.

[ Parent | on HN ]
Re:The Node ecosystem still has tooling problems by toomanybeersies on Sunday July 31, 2022 @02:19AM (#32293642)
At least (I hope) you weren't still using Bower.
[ Parent | on HN ]
Re:The Node ecosystem still has tooling problems by azangru on Saturday July 30, 2022 @08:02PM (#32291651)
Look at the source code of web.dev site :-) It's Eleventy with gulp for asset management.

https://github.com/GoogleChrome/web.dev

[ Parent | on HN ]
Re:The Node ecosystem still has tooling problems by jeroenhd on Saturday July 30, 2022 @06:53PM (#32291183)
Both still work fine to this day. I don't know what the exact (dis)advantages of the competing toolsets are, but if you know Gulp and Grunt then I don't see why you wouldn't use them.
[ Parent | on HN ]
Re:The Node ecosystem still has tooling problems by coredog64 on Saturday July 30, 2022 @07:21PM (#32291375)
Was helping an org migrate off of CloudFoundry and Grunt gave us no end of trouble. In the end, we wound up building with Node 8(!) and then praying that everything would still work with a 12.x runtime.
[ Parent | on HN ]
Re:The Node ecosystem still has tooling problems by andrew_ on Sunday July 31, 2022 @06:57PM (#32299652)
unless one is in need of piping files (and streams) in a complex and prolific way, npm scripts or a makefile can supplant Gulp/Grunt with much less overhead.
[ Parent | on HN ]
Re:The Node ecosystem still has tooling problems by ravenstine on Saturday July 30, 2022 @06:58PM (#32291223)
Yeah Grunt is pretty ancient but Gulp is still used in many places.
[ Parent | on HN ]
Re:The Node ecosystem still has tooling problems by Zardoz84 on Sunday July 31, 2022 @03:32AM (#32293932)
Gulp it's really useful when your workflow gets out of what webpack, esbuild & cia expects
[ Parent | on HN ]
Re:The Node ecosystem still has tooling problems by theteapot on Sunday July 31, 2022 @12:18AM (#32293140)
2012 === bad. 2022 == awesome!
[ Parent | on HN ]
Re:The Node ecosystem still has tooling problems by klodolph on Saturday July 30, 2022 @09:44PM (#32292343)
Problem is that a ton of random stuff breaks when you "type": "module". Unexpected stuff, like Prettier.
[ Parent | on HN ]
Re:The Node ecosystem still has tooling problems by BigJono on Sunday July 31, 2022 @02:36AM (#32293712)
Oh no, whatever will the world do without Prettier turning nicely formatted JS into a pile of unreadable shit because line 218 was 71 characters long instead of 69.
[ Parent | on HN ]
Re:The Node ecosystem still has tooling problems by ThalesX on Sunday July 31, 2022 @03:23AM (#32293898)
I’ve recently had a PR that Prettier would add 2 extra whitespace and Lint would complain about it. And these were in the same build process. The resolution was for me to change my code…
[ Parent | on HN ]