My week of 8/24 at npm

This week I’m:

  1. Put together some basic benchmarks for ongoing performance monitoring.
  2. Usher PR #9227 through
  3. Driving across the country! Boston → Oakland

Last week, we didn’t have a 3.x release for primarily ongoing policy reasons combined with a test that only failed under certain circumstances that took a bit longer than usual to iron out. Still, there was a lot queued up for it that’ll get out this week:

  1. Comment on #9227 and #9240
  2. Fix the Travis builds for 3.x
  3. Fix npm --update #9095
  4. Make install order even more consistent (#8995, #9274)
  5. package.bin can be a scalar in addition to an array and npm@3 needs to not crash when it is #9187
  6. npm install x w/o a package.json doesn’t include x in the output. npm ls after one of these installs doesn’t get the logical tree. Maybe some other things. Fix these! #9113

My week of 8/17 at npm

This week I’m wrapping up a lot of small, but IMPORTANT bugs!

  1. Comment on #9227 and #9240
  2. Fix the Travis builds for 3.x
  3. Fix npm --update #9095
  4. Make install order even more consistent (#8995, #9274)
  5. package.bin can be a scalar in addition to an array and npm@3 needs to not crash when it is #9187
  6. npm install x w/o a package.json doesn’t include x in the output. npm ls after one of these installs doesn’t get the logical tree. Maybe some other things. Fix these! #9113

Last week I finally got to one of the root causes of stack explosions. And then some!

  1. Writing tests for #9198 and summary of current behavior of gently-rm
  2. Symlink cycles need to stop exploding npm@3 #9223
  3. Let’s extract npm@3’s tree post-processor for use by npm-init #8176
  4. Plus some misc small things– accepting a patch, renaming a label, triaging next week.

My week of 8/10 at npm

This week I’m:

  1. Writing tests for #9198 and summary of current behavior of gently-rm
  2. Symlink cycles need to stop exploding npm@3 #9223
  3. Let’s extract npm@3’s tree post-processor for use by npm-init #8176
  4. Plus some misc small things– accepting a pull request, renaming a label, triaging next week.

Someday soon I hope to do a rewrite of gently-rm as an external module. It’s already mostly isolated from the rest of npm‘s internals, and it is plausibly useful for other projects. Currently it does have some particular assumptions about npm and everything would be easier to understand without them.

As always the roadmap has all sorts of details

Last week I pushed out 3.2.2 with a bunch of fixes:

  • Fixed a crasher when running npm install --save git+ssh://
  • Fixed a crasher when trying to npm docs a module w/ only prerelease version
  • Made peer deps look from the perspective of the parent of the module with the peer dep when validating their existence
  • FINALLY stopped warning about missing package.json stuff on global installs

Week of 7/27 at npm

So I missed posting this here last week here, but it was up on our roadmap.

My weeks are looking pretty much the same while we burn through the open 3.x bugs. Once the queue is worked through we’ll be ready to move it out of beta!

This week I’m…

  1. Triaging v3.x issues for next weeks release
  2. Completing this weeks issues. (This has gotten its way up to 9 items, so I may be reconsidering some of them. =D
  3. File an issue on npm/issue-tracker to discuss how npm ls should work
  4. Make an issue to track discussion of how deprecation warnings are handled

Last week I…

  • Triaged the weeks v3.x issues into the up coming release buckets.
  • Finished off the v3.2.0 issues. See the tactical roadmap below for details.

And the week before I…

  1. Worked on the v3.1.3 issues (as of this writing): #8891 npm rm -g misbehaving if was a symlink, #8874 linking scoped modules fails, #8812 improve progress bar, #8701 improve permission validation on windows
  2. Triaged v3.x issues for next week (tentatively v3.1.4).

Week of 7/13 at npm

This week I’m…

  1. Working on the v3.1.3 issues (as of this writing): #8891 npm rm -g misbehaving if was a symlink, #8874 linking scoped modules fails, #8812 improve progress bar, #8701 improve permission validation on windows
  2. Triaging v3.x issues for next week (tentatively v3.1.4).
  3. Release and other issue support.

Last week I…

  1. Triage npm@3 bugs + features for this week
  2. DO them and release 3.2.03.1.1
  3. Continue working the npm@3 issues

And early this week I also released 3.1.2 as the 3.1.1 release was critically broken. This was a process issue (last minute inclusions in the release, late night release) which led to errors (tests run against wrong tree) which resulted in pushing out something that couldn’t install local modules. Pretty basic! We’ve altered our processes to say that if something isn’t done by EOD Wednesday then it’s not going in Thursday’s release.

My week of 7/6 at npm

This week is a slightly short week, as I’m taking Friday off so that me and mine can visit Acadia National Park one last time before moving away from the region. This week I’m…

  1. Triage npm@3 bugs + features for this week
  2. DO them and release 3.2.0
  3. Continue working the npm@3 issues

Last week I…

  1. Fixing bugs in the 3.0.13.1.0 milestone
  2. npm@3.0.13.1.0 release

It was a 3.1.0 release because of features ported forward from 2.x

My week of 6/29 at npm

This week is a short week for me– I’m only officially working two days, but I’ll still be doing a npm@3 release this Thursday.

  1. Fixing bugs in the 3.0.1 milestone
  2. npm@3.0.1 release

Last week I released the first beta of:

npm 3!!

Try it out today:

Or try out what’s guaranteed to be the beeldingedgiest, until such time as it’s out of beta:

My week of 6/22 at npm

This week I’m…

  1. 🌟 🌟Preparing to release a public beta of npm@3 🌟 🌟
  2. Nope, that’s probably it.

Last week… omg, so much got done. So as planned…

  1. Fixing the LAST THREE remaining failing tests in npm@3’s test suite!! #7774 This has been the albatross around my neck since late March!
  2. Attending CCSConf in New York this Thursday & Friday. Plus BrooklynJS this Thursday!
  3. #8138 Fix the stack-overflow that shows up with freshly minted ember apps and npm@3. With this, all known npm@3 issues will be resolved!

Then, in addition, I:

  1. Fixed all of the other remaining outstanding npm@3 blockers.
  2. Reran the test suite and found 23 more failing tests!
  3. #8587 Fixed all of those tests / bugs uncovered by those tests.
  4. Started writing the changelog for npm@3… it’s a tome.

My week of 6/15 at npm

Hey you all, so THIS week at npm, I’m.

  1. Fixing the LAST THREE remaining failing tests in npm@3’s test suite!! #7774 This has been the albatross around my neck since late March!
  2. Attending CCSConf in New York this Thursday & Friday. Plus BrooklynJS this Thursday!
  3. #8138 Fix the stack-overflow that shows up with freshly minted ember apps and npm@3. With this, all known npm@3 issues will be resolved!

As always, you can find out what the rest of my team at npm is doing at the roadmap.

Last week (and the week before) I…

  1. Released npm@2.13.3 while the rest of the team was away at NodeConf Adventure.
  2. Fixed a bunch of failing tests in my albatross #7774.
  3. Ended up adding substantially more ability to rollback already completed steps to npm@3 than was previously planned. This also resulted in infrastructure for making all of the changes we make to your node_modules undoable, which will ultimately make it much harder to get your node_modules into a broken state.

My week of 6/1 at npm

This week:

  1. #7774 Getting tests passing for multi-stage and npm@3. I found a nasty bug pre-conference so I’m gonna be landing a fix for that early this week. You’ll also find that the multi-stage branch now sports npm@3 style flat, deduped deps!

Last week, I conferenced at @jsconf all week. It pretty great. Lots of lovely people and fascinating conversations. Looking forward to talking to more of you all at future conferences.

Whatever fills my mind…