Rebecca Turner

Huh, I was under the impression that Yarn was using `npm` to run lifecycle scripts? Is that just for an `npm run` stand in?

Kind of, they don't support `prepare` or `prepublishOnly`, which are in npm today and were specced out from around the time they started work on yarn (maybe before). =p

Ok, so the main delay here was that I wanted to verify that install was the only time Yarn would run `prepublish`. It is not. Yarn has a publish command...

@garthk It's not clear to me what you're trying to change? Can you PR that so I can see a diff?

@iclanzan: Your suggestion makes sense to me. @sebastienbarre: Hmm, `npm cache add` too in that case. In so far as this is "not on install".

@sebastienbarre So, things like `prepublish` and `publish` and `postpublish` in your `package.json` are something we call "lifecycle scripts". These are triggered by npm when its doing various tasks– not by...

FYI: I moved my spec tests to here, so they can be more easily included in other projects: https://github.com/iarna/toml-spec-tests You can see how I ensure my project uses an up-to-date...

Today you can already do: `"dependencies": { "iojs-bin": "^1.2.0" }` Thanks to a clever hack from @aredridel (`node-bin` is also available as a dep.) It works pretty much exactly is...

This will need a test before we land it. `fstream` releated tests are hard to work with, so I'll write one at some point, but that work isn't scheduled yet....

Ok so yeah, I do have this largely implemented. This is how I approached it: I added another field to the CSV (inserted just after the existing field) that contains...