Hi, I'm looking for a J-O-B. I love building dev tools & maintaining #OSS. recently: maintainer of #Appium (automation framework for arbitrary devices). before: OSPO, #NodeJS core, Mocha, etc. I am on the @jsparty podcast. I am cool and smart and funny. 20 YoE. remote only
question for other #nodejs#javascript devs out there. is there a way to get the predictability of reproducible versioning between dev and deployed without having to lock down your package.json to exact versions? concern is that locking down versions now introduces a quarterly upgrade cycle that sucks up dev time. i'm also not a fan of dependabot's yarn.lock only updates.
this whole convo started w/ #nextjs 13.3.1 release with a nasty bug.
Breaking change²: data is now evaluated in virtual machine contexts.
If you were persisting custom objects³ and referencing classes from global scope (globalThis) to have your objects keep their types when read, you must now explicitly register your list of custom classes using the new classes property of the options object when calling JSDB.open().
I saw @Uraael mention how their engagement had really skyrocketed with the influx of folks from #mastodon at calckey.social and they posted a screenshot of their activity graph. Thought I'd heck mine, too.
@jo One thing that attracted me to #calckey (in conversation with a recent migrant to there) was that it's a nodejs based codebase, which makes it more likely that I'd one day dig into the internals (than say Ruby/Mastodon or Elixir/Akkoma).
How do you find developing a *key platform? Is being #nodejs based a factor in your liking it?
Wondering how to get readline working in a non-primary Node.js cluster process while keeping colour output via Chalk in your CLI app?
(I’m pretty sure you’re not but, hey, I ran into this today and I’m documenting it in hopes it might help someone else sometime.)
Check out the implementation in Kitten’s development-time process manager (this little file is what Kitten uses in place of a heavyweight module like Nodemon):
Developers: It takes a really long time to delete my node_modules directory #Microsoft: What do you want us to do about it?
Developers: I don't know, use a better filesystem or something?
Microsoft: Here, have an entire fucking #Linux virtual machine that you can use to run #nodejs
Developers: ...this is fine actually
Heya, I'm looking for my next role! I am a Full Stack Node.js developer but I would love my next role to be backend focused (or game dev but I'm not so sure how to make that switch!).
I'm a quick learner and I love making tools for other developers to be more productive like SDKs and CLIs.
This is hilarious. A #Google engineer invented #zx to make command line scripting easier with #NodeJS, because at a certain point #shell scripts get too complicated and you need a Real #Programming Language.
This is exactly #Perl’s use case from thirty-six years ago. But the kids want #JavaScript everywhere and would rather it take more work to convert their ascended #Bash scripts to a vastly different syntax.
“#ShellJS is a portable implementation of #Unix#shell commands on top of the #NodeJS API. […] say goodbye to those gnarly #Bash scripts!”
Of course, #PerlPowerTools also exists if you want Unix commands that work the same everywhere. It has exactly four dependencies to download from #CPAN outside of the #Perl core.