nodejs
doc: add "Do I still need this dependency for my Node.js app?" to ambassadors program
Also included is:
- a63292945d5c85960ee7fd236f34af31e963d20b - fixing some typos in previous content
- 20c83cfb701246eaa3d1f25ff86ef035958cace3 - normalizing the markdown headers. without this, the levels bled into one another incorrectly (⬇️ now fixed)
I chose to include all this together for review clarity and noise, but open to feedback of any kind. Cheers! Understand most of this won't be acted upon until after collab summit, but I wanted to follow through here.
make does not work on my Windows machine, so trying to approximate it with node tools/lint-md/lint-md.mjs --format .\doc\contributing\advocacy-ambassador-program.md 🤞
presented today at Minnestar 19 in Minneapolis, MN
Overhwelming feedback from the standing-room only crowd was that they wished there was an official list of this somewhere.
https://noti.st/brianmuenzenmeyer/5ep4ZM/do-i-still-need-this-dependency-for-my-node-js-app
@bmuenzenmeyer there are a few suggestions/comments on the PR. If you could address them we could get this landed.
@bmuenzenmeyer there are a few suggestions/comments on the PR. If you could address them we could get this landed.
done - of course the TypeScript stuff especially is a moving target, with Node.js 23.6.0 unflagging strip typing, and transform types now available too. I suggest when this is taken up by an ambassador or more formally adopted, features on the newer side should be audited for similar relevancy.