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.

My week of 5/26 at npm

This week, I’m at @jsconf all week. I may or may not get anything else done, but I’m not investing in a checklist this week.

Last week, I:

  • Did npm’s release, which thank’s to @othiym23‘s excellent documentation went almost flawlessly.
  • Fix a bunch more tests in #7774 (the npm@3/multi-stage branch test fixing ticket). I also found an error in rolling back optional dependency failures in dependency configurations. (Eg, deps that are both optional to one dep and non-optional to another, especially when more layers of indirection are involved.)

My week of 5/18 at npm

This week…

  1. #7774 npm@3 tests, I really want to get a lot of them done.
  2. If things go as planned, I’ll also be doing the release this week.

Last week I…

  • #8055 #8052 Documented a new module, a git repo manager which will be used in resolving these tickets. It’s shelved for the time being while I push on getting npm@3 out the door.
  • #7774 Got about a third of the tests passing
  • Interviewed four candidates for a position as a coworker on the CLI team. Everyone was amazing, and if we had the resources we’d hire them all. We’re doing additional interviews with the wider npm team this week, but eeee, we’re close to having more folks on our team!
  • I talked at the Boston Ember.js meetup (pics, video) about what’s new in npm@3. This was a repeat from a talk I gave earlier at a local Node.js meetup, but with a few updates.

My week of 5/11 at npm

I’m going back to finishing tests in the multi-stage branch, but I have one carry-over I want to get done. As always, this’ll be updated as we go over on the npm roadmap.

  1. #7774 Getting tests passing for multi-stage and npm@3
  2. #8055 #8052 Isolating git support in npm and making update and outdated checking work well– I started this last week and will be making a separate github repo for it shortly. It will likely be shelved after Monday, while I work on tests in multi-stage.
  3. Pluuus we’re going to start interviewing CLI candidates…

Last week I…

  • Got married!

  • Started work on #8055 #8052 Isolating git support in npm and making update and outdated checking work well

My week of 5/4 at npm

This week, I’m away for most of it getting married. Or rather, I got married on Sunday and now I’m recovering. 😉

Last week I worked on:

  1. I’m working through the various high priority git issues– specifically:
    1. #7202 Race conditions w/ multiple git deps pointing at the same repo but with different committishes. Fixed and test in progress.
    2. #7994 Upon reflection, was actually behaving as intended.
  2. Meeting with @stefanpenner to discuss ember-cli coordination

The week of 4/27 at npm

This week, Forrest and I are swapping our focuses. He’s gonna dig into the multi-stage test suite and I’m gonna dig into outstanding git issues and handling pull requests. This is a short week for me– I’m not around on Friday, busy getting married and all. 😉

  1. I’m working through the various high priority git issues– I’ve not dug in detail yet so I’m not sure how many we’ll get fixed this week. But some of them.
  2. Meeting with @stefanpenner to discuss ember-cli coordination
  3. Manage pull requests, which basically involves reviewing and getting pull requests into a shape we can accept them. Plus the purely mechanical act of merging them. 😜

Last week, again involved a bunch of off-the-roadmap work:

  1. #7774 (partial) Got node test/run.js working in multi-stage
  2. #6942 Write action validator that checks permissions.
  3. 2b51fce Eliminate stray progress bar display cruft
  4. 844e72a Rewrote shrinkwrap to not use npm ls. And other shrinkwrap improvements:
    1. 999be86 Don’t install missing modules from the shrinkwrap when explicitly installing modules (eg npm install foo)
    2. 19e9d6b @thefourtheye gave us a fix to get fixing test/run.js working, which meant making the target directory if it doesn’t exist when installing globally.
    3. 8369df9 Update fetch-package-metadata’s tarball streamer, which is used to read shrinkwraps, to support ungzipped tars and plain JS files, just like cache/tar.
  5. Fixes to read-package-tree’s link marking:
    1. e3d3721 Folders should only be marked as links if they’re symlinked deeper than the top of the tree.
    2. 38207e7 The path attribute we put on nodes should be based on the path passed in to read-package-tree, not off it’s actual symlink-free name.

The week of 4/20 at npm

As usual, this is posted and updated live in the npm roadmap wiki.

  1. #7774 Getting tests passing for multi-stage and npm@3 (ongoing)
  2. #6932 Make npm install --link work
  3. #6942 Write action validator that checks permissions.

These are all carry overs from last week- and really the first needs breaking out further, at least for the purposes of todo lists. Last week was busy– I was in Oakland visiting the mother ship, and I got a bunch of things done including a slew not originally planned:

  1. #5090 npm install doesn’t update changed git url dependencies.
  2. #6926 Reorder installation steps such that if A depends on B, we don’t run A’s lifecycles till B’s have run first.
  3. #6934 Implemented linked directory semantics.
  4. Make global installs/uninstalls not waste time looking at other packages in the global tree
  5. Fix outstanding dedupe bugs
  6. #5693 Not installing deps of deps from shrinkwrap
  7. #5779 Make npm-shrinkwrap idempotent. This means both deep sorting AND consistent _from fields.
  8. Fix outstanding shrinkwrap bugs. Specifically: A) warnings during shrinkwraps left progress bar cruft on screen and B) npm install modulename when you had a shrinkwrap would remove any dev deps (and any other deps not in the shrinkwrap).

Whatever fills my mind…