rfcs
rfcs copied to clipboard
npm
rfc: install size information logging
I haven't had as many spare cycles as I expected. I've made preliminary steps (cloned down the code, ran the specs, ~reviewed~ glanced at the code which will need changing) but haven't gotten traction enough for an initial code change yet. When I do have work in progress, I'll throw a PR against npm/npm referencing this RFC.
Does closing the RFC PR mean that the proposal is formally ready to be worked on?
@strand this RFC is considered "ratified" after we merge it, correct. Until then, a lot of stuff is up in the air.
I had some conversations with the registry folks, and it's possible that in the next couple of months we'll backfill tarball information using do-you-even-lift, but until then, we won't be able to actually execute this RFC properly. You're free to start poking at an implementation, and that sort of thing can help get more ideas, but this RFC is at a pretty early stage right now so it's bound to change a lot.
I'm glad I've gotten some familiarity with the codebase and a high-level understanding of the problem, and will let this work lay fallow until the ratification and tooling work is completed.
TODO: I need to update this with the intended/expected additions to the registry, as I'm thinking of them now, and how those are going to be put together into a final answer, and we can iterate over it once registry folks can take a gander.
Brief update: We've moved this internally to appropriate channels and we'll be doing an internal review + prioritization of this feature. No timeline until that's done.