BenjaminCoe

Hey,

I'm the original co-author of the "Conventional Commits" spec. Although, I should give credit where credit is due, and say that it evolves directly from Angular commit conventions.

I started adopting these conventions with the goal of automating releases, both on my open-source and on the services I was working on at npm (I've since brought the practice to my team at Google).

I very much did not want to introduce road blocks to folks committing to their own branches -- which is what the "rewrite the message when you squash" advice grows from.

Here's a post I wrote on how my team uses Conventional Commits in our release process:

https://dev.to/bcoe/how-my-team-releases-libraries-23el

details nearly a year of open-source work that went into bringing V8's built-in JavaScript code coverage to Node.js.

man alive, an irresponsible approach to shutting down a SaaS like this is exactly why infrastructure startups face an uphill battle getting folks to adopt them.

> I'm curious what the percentage of npm publishers that have this toggled on is, and I wish that was available data.

I know we're tracking this data and I bet a follow up post will be written at some point once some numbers are available. As you say, I expect 2fa will see wide adoption as soon as a stable version lands in the upstream Node.

worth mentioning, since this article npm has released two-factor authentication \o/

http://blog.npmjs.org/post/166039777883/protect-your-npm-acc...

make sure you turn it on.

perhaps not as necessary now that SoundCloud managed to close a round, but wrote this little tool last night to backup my SoundCloud data.

Free soloing is actually a bit slower than the fastest free-climbers, which I found interesting: http://adventureblog.nationalgeographic.com/2012/06/25/alex-...

The time spent being especially careful that you don't fall, adds a bit more time than racing up with ropes.

Fun fact, Alex Honnold holds the speed record on El Cap.

I've been summoned :p

We use Atom's syntax highlighter for syntax highlighting on npmjs.com -- I originally wrote onigurumajs, because I was seeing if we could viably remove the website's only compiled dependency (oniguruma) ... I wrote it over vacation, and then had to put the work down.

I would love help to see the library over the finish line; on a grammar by grammar basis it would be great to figure out what the JavaScript regex engine is missing, and try to shim the logic.

why???

The great thing about using oniguruma, is that it lets you leverage the huge collection of grammars available for TextMate -- unfortunately JavaScript's regex engine doesn't support quite a few rules that are present in TextMate grammars.