I=['daddy']; I.concat(['gineer', 'trepreneur'].map(x => 'en'+x))

console.log(null || undefined || 0 || '?')

node.js

A collection of 15 posts

Burn It All Down: The Open-Source Communities Unholy Hypocrisy

Burn It All Down: The Open-Source Communities Unholy Hypocrisy

"Furious about Node.js' blatant favoritism. It takes months/year for innovation to trickle down because of gatekeepers & haters in the open-source community."

Riding the Express Lane: How Node.js Powers Modern Web Development

Riding the Express Lane: How Node.js Powers Modern Web Development

In the bustling landscape of modern web development, one technology stands out like a bright green beacon amidst the chaos: Node.js. But what does a forgotten motorized mobility cart outside a grocery store have to do with Node.js, you might ask? Well, let's embark on a

Unlocking Efficient Debugging: Why NiM Should Be Your Go-To Tool for Node.js (server side Javascript) Development

Unlocking Efficient Debugging: Why NiM Should Be Your Go-To Tool for Node.js (server side Javascript) Development

As Node.js developers, we've all been there - stuck trying to debug our applications, wasting precious time and resources on tedious tasks like creating multiple instances of node inspector or switching between different Chrome DevTools tabs. But what if I told you there's a better

NiM + Troubleshooting: Resolving the Lingering Inspector Issue

NiM + Troubleshooting: Resolving the Lingering Inspector Issue

If you're a Node.js developer, you're likely familiar with NiM, the handy V8 Inspector tool, and of course the Nodemon utility that monitors changes in your Node.js applications and automatically restarts the server when it detects modifications to your code. It's a

NiMV3 (Google Chrome Manifest V3) Update

NiMV3 (Google Chrome Manifest V3) Update

So I spent the better part of this week working on migrating NiM to mv3 and so far so good. It was actually refreshing to dig through old code to see how my own coding skills have improved (or maybe that's just a pipe dream)... anyway, huge changes

Inspect Node.js With Grunt-SWATCH (!watch) And Fiveo

Inspect Node.js With Grunt-SWATCH (!watch) And Fiveo

I know, I know... the socket in the cover picture isn't really the type of socket we're talking about in this post, but I've been preoccupied lately with the idea of building a new workstation and the ThreadRipper is a monster! I mean it

LightGallery Plugin for NodeBB

LightGallery Plugin for NodeBB

I just started using NodeBB about a week ago. A project came up that required the use of a forum and being that I have such an affinity towards Node.js... the results of my search for open source forum software quickly narrowed down to NodeBB. Previously I've

The DevToolsCompat setting

The DevToolsCompat setting

A while ago I wrote a post about DevTools missing the source tree... So oddly the DevTools versions of late have been missing the source file tree normally found on the left hand side of the debugger under Sources > Page: At the end of that short post I wrote

Node.js Governance Similar to Parler Elimination by Big Tech?

TL;DR A Project (my project in fact)... NiM which has been linked from Nodejs.org's site for years, was removed because of (in my opinion) nepotism toward corporations, and a governance model which is currently operating on an uneven playing field. I should add that my intent

More than "UX sugar"

More than "UX sugar"

Node.js V8 --inspector Manager (NiM) "adds some nice UX sugar on top"... of Node.js debugging. That's for sure. However now that the DevTools team has built in a solution for the UUID problem, some have disparaged NiM, out of what I would call ignorance

Absolute Simplest Node.js Debugging - VSCode/DevTools

node.js Featured

Absolute Simplest Node.js Debugging - VSCode/DevTools

In my opinion, debugging Node.js (Node) code hasn't ever been that big of a pain point, largely because of the excellent debugger baked into Node, which has been the case for at least as long as I've been involved with writing software in Node. Python

Squash Node Bugs with DevTools on Edge

Squash Node Bugs with DevTools on Edge

With the newest release of Microsoft's Edge browser, installing Chrome Web Store extensions on Edge is now possible as Edge is now built upon the Chromium code base. Further, Chrome DevTools is also included in Edge. And with the final piece of the puzzle being NiM (Chrome Web

NiM with Tabs for 2019!

NiM with Tabs for 2019!

NiM inspect multiple Node.js debug sessions.

NiM Custom DevTools URLs

NiM Custom DevTools URLs

Sometimes Chrome introduces a breaking change that affects Node.js developer debugging. NiM provides a solution via a custom DevTools version setting, providing mix and match DevTools/Browser options.

NIM (Node Inspection Monitor)

NIM (Node Inspection Monitor)

What is it? A Chrome Extension that monitors the integrated Node V8 inspector and automates the management of Chrome DevTools during development using Node.js. Excerpts taken from various online forums: Is there a way to get chrome-devtools (--inspect) to automatically detach from a process that has ended?[1] How