crypto.randomUUID() is now stable in Chrome 92 \o/
thank you
@domenic
,
@ctavan
,
@broofa
, and many others, for helping advocate for this feature.
hope folks enjoy 🎉
having joined
@npmjs
as employee
#3
, I'm proud to have helped the company grow from 5 to 60 employees.
next week I will be joining
@JustinBeckwith
's team at Google as a DPE.
I'm looking forward to continuing to contribute to the future of JavaScript:
pushing breaking changes to libraries with 26,000,000 downloads/week ... that haven't been updated in 4 years ... from a plane ✈️!
what could possibly go wrong.
just published an early shim of the argument parser intended for Node.js core.
tons of people have been contributing (folks from Commander, yargs, npm, IBM, Node.js core), join the conversation 😊
Surprised I'm not seeing more cheering on Twitter for
@nodejs
finally releasing a version (10.12.0) with recursive fs.mkdir() and fs.mkdirSync(). Solid contribution from
@BenjaminCoe
.
the service my team at Google uses for managing npm publications in large organizations has been open-sourced 🎉
It handles 2FA for you, so that you don't need to turn it off in automation.
many folks contributed:
@JustinBeckwith
,
@soldair
,
@ofrobots
I think you've got this backwards -- your company has raised $80M and is on track to an IPO. Companies like you need to set an example by contributing money and developers to the open-source projects you rely on.
no, I'm not going to patch a 3-year-old version of a library, because someone opened a CVE for a command line argument parser.
Can we figure out another way to monetize open-source please, thanks bye.
I joined npm, Inc as the third engineer in 2014 (along with
@ceejbot
, and
@rockbot
). I'm very proud of what I built there, and grew a ton in my career. I'm happy to see it get a good home.
We’re excited to announce that
@npmjs
will be joining GitHub. Millions of JavaScript developers rely on npm, and we’re honored to support this community in a new way. Learn more at
nvm install 12.12.0
Thanks
@BridgeAR
and the cast of
@nodejs
thousands that made this release possible.
I'm especially excited about `--source-map-support`. Thanks,
@BenjaminCoe
!
I'm making progress on my first product feature at
@getsentry
- Cache Monitoring 💫
Do you use Sentry for application monitoring?
Does your application use caches?
I'd love your feedback:
It took a long time, and there's still work to do, but I'm excited to be able to play with v4 UUIDs in Chrome Canary.
It's been a great experience working with
@broofa
and
@ctavan
, who wrote the uuid npm module, to make this possible.
this Istanbul report was generated in Node.js using the native coverage support
@schuay
and I have been working on in Chromium. I'm pretty excited about how close we're getting to a working prototype.
this is bound to be a somewhat controversial conversation, but I'm very excited about the potential of wildly popular modules like rimraf, or uuid, occasionally being pulled into the platform:
Today was my last day at Google. Overall, it was a good experience. I especially appreciated the opportunity to grow as an engineering manager.
I'll share news about my new gig soon ☺️
this is my favorite meme to share with fellow developers, here's why:
- programming requires life long learning. it's okay if you sometimes feel like this very good boy.
- it normalizes the fact that *even* senior developers often feel this way.
- it's a cute dog wearing a tie.
just attended back to back to back
@openjsf
summit,
@jsconfeu
, and
@TC39
... I’m physically exhausted, but feeling super positive about the future of JavaScript.
last night
@nodejs
coverage build used V8's built in coverage \o/
this is a culmination of months of work, thanks to
@hashseed
@schuay
,
@mhdawson1
and others for patience with me.
there are still lots of bugs to fix, let me know if you want to help.
it was an awesome experience to PM the new npm Enterprise product. It's the spiritual successor to our on-premises product (which was my first project at
@npmjs
5 years ago).
big thanks to all the amazing engineers at npm, Inc that made it possible.
we are delighted to announce the release of npm enterprise! npm ceo
@bbogens
talks about the insights that led us to creating this product and how it will fundamentally change the way enterprises use javascript:
have been working with
@izs
to bring
@nodejs
' mkdir recursive to feature parity with mkdirp:
In future Node.js versions, expect a blazing fast mkdirp shim.
with JavaScript, through the popularity of TypeScript, babel, etc., becoming more and more a transpiled language, let's start talking about building source map support into runtimes:
just published a fairly major update to the specification; my hopes are that we're close to a v1.0.0 of the document.
if you like conventional commit messages (or hate them) feedback is very much appreciated.
the amazing team I mentored at
@HackIllinois
built a tool for reporting Istanbul test coverage from a headless Chrome -- folks are going to use the heck out of this.
Would love people's feedback, regarding the addition of a minimal command-line argument parser to Node.js:
There's a chance it lands early in the lifetime of Node v18:
every time I attempt to write a moderately "edgy" tweet, I immediately regret it and delete it.
mark my words, one of these days I'll manage to squash my friendly Canadian demeanor.
@ThisIsMissEm
they were early on, and when we migrated the registry to no longer be case sensitive, we left the colliding package names alone.
At least this is my recollection.
@matteocollina
@nodejs
I feel that everyone is trying to get a handle on what an appropriate tool chain looks like for ESM.
I've found the Jest folks quite responsive on GitHub, might be worth trying to loop them in about the issues.
I've been working on a formal grammar/parser for "Conventional Commit" messages with
@wesleytodd
and
@cedricvanputten
.
It's some of the most fun I've had working on open-source:
that realization that the TC39 proposal you didn't fully understand 6 months ago, you *need right now!*
this would cleanup the cache I'm writing for source maps in Node core immensely.
CC:
@_gsathya
,
@littledan
over the past few years, yargs has slowly become one of the most popular tools for writing command-line applications in Node.js. I'm really excited about yargs v10 which overhauls positional arguments, and will be released within the next week.