Start with the tech stuff. I'm a #programmer. Mostly writing web apps using #ReactJS and #NodeJS with some #mongodb. Been dabbling with #mui for a recent project too.
I've been messing computer since a child and have fond memories of being asked to spend £1000 of my dad's friends money to build him a computer. The look on his face when he walked into his dining room to see bits of computer scattered all over the table and me, age 9, ready to put it together. Not going to say my age now, but it was a 486DX2-66 with a whole 8MB of memory.
Outside of tech, I'm outdoorsy. I like a good #hike, or #walk in the woods. I love nature and campaign to protect the #climate and #biodiversity.
I #cycle lots of places but just to save on petrol and parking. My #bike was free and I don't own lycra.
I have an #allotment where I grow a lot of my own food. I eat a mostly #vegetarian diet, so that keeps the food bill lower.
Learning #guitar and #French... Sometimes at the same time!
I have to confess to some hubris. After evaluating the various Node.js testing frameworks, I've decided to write my own instead. In this 🧵, I'll explain why. Mostly so I can remember it for the future.
Anyone know of any good ActivityPub packages for #nodeJS or #nextJS?
I want to bring AP updates to a static/serverless site hosted on Vercel. Nothing out there seems to quite fit the bill, or requires an amount of tinkering that currently goes over my head.
If you’re using HTML Validate (you should; it’s ace), update to 7.15.2. It no longer flags multiple buttons with the same name used in forms as a validation error (this is a valid pattern that lets you interpret a form differently on the server based on which button it was submitted with).
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