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

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

NiM

A collection of 14 posts

Chromium Bugs: How NiM's Flexibility Provides Smart Workarounds for JavaScript Developers

Chrome DevTools

Chromium Bugs: How NiM's Flexibility Provides Smart Workarounds for JavaScript Developers

Discover how NiM, a versatile JavaScript developer tool, helped resolve a critical bug in Chromium's DevTools front-end. Learn about the benefits of using NiM, including flexibility, enhanced debugging, and community support.

NiM Update: Expanded Tools and Searchable Node.js Docs

NiM Update: Expanded Tools and Searchable Node.js Docs

The newest feature in the next version of NiM reworks the current REPL popup/shortcut feature into a general-purpose window that maintains your web developer tool state. This includes the REPL and adds searchable Node.js docs! The docs have been made searchable thanks to the folks over at Algolia,

JavaScript REPL for Quick Debugging and Testing

JavaScript REPL for Quick Debugging and Testing

I often find myself wanting to test a snippet of JavaScript code and at those times my general path was always a different one, sometimes I would open up a CMD terminal locally on my Windows machine, or other times I might use a remote terminal maybe on Ubuntu or

Insist on Using about:inspect to Debug Node.js? It Just Got an Upgrade!

Insist on Using about:inspect to Debug Node.js? It Just Got an Upgrade!

Insist on Using about:inspect to Debug Node.js? It Just Got an Upgrade! I've said it before and I'll say it again, debugging with NiM, is superior to `about:inspect` and the newest feature of NiM makes this point even more compelling. With NiM you

NiM V3 Manifest V3 Update 2

NiM V3 Manifest V3 Update 2

Since my last update specifically addressing the transition to Google Manifest V3, which occurred at least a year ago, both I and a small segment of the community have been continuously using NiM with very few issues—those that arose have since been resolved. Google has recently resumed discussions about

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

BrakeCODE + NiM Alert Feature

BrakeCODE + NiM Alert Feature

Gazing into multiple monitors each day and in turn multiple tabs of multiple windows of said multiple monitors (I'm back down to 4 now)... I wanted a way to quickly identify when my builds were finishing without obviously going back to the browser tab where I had GitHub

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

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

DevTools Missing Page File Tree

DevTools Missing Page File 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: Debugging seems to work fine and if you click on the menu icon to open the file manually, it works. But why

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.

Debugging NiM

* Set "Developer mode" by checking the "Developer mode" checkbox at the chrome://extensions page * Now go to the NiM extension item on the same page (you may have to scroll down if you have lots of extensions installed) and you should now see the background.html