nlf

i've opened issues for the remaining work to be done to the agent itself in its own repo https://github.com/npm/agent/issues the config work is not represented in an issue yet, i'll...

if i'm understanding you correctly, i think i would rephrase this feature as supporting includes in config files - not necessarily supporting two project config files. we can maintain the...

the consensus we reached internally and within the open office hours call where we discussed this flag was that it's unlikely a user will want to selectively enable experiments, the...

i've changed this pull request to a draft while i work on revising some things and greatly reducing the scope of this process

> Would it be possible to get a quick high level call out in the description of what (if anything) is fundamentally changing with the new process proposal compared to...

i agree with all of the points that this validation does not belong in the package manager. this should be an external tool that can be run as part of...

i'm a little confused how `--before` doesn't solve for this.. yes, you have to form the timestamp yourself but it won't install anything that's newer than the date listed, so...

> So maybe there should be no global `[headers]` section in an existing or new RFC to do this, and only a section such as this: > > ``` >...

I've reached a point where I can't decide if this is actually a new feature or if it's really just some enhancements to optional dependencies If we frame it as...

> @nlf i don't think optional dep features would address the "full vs minimal" file set tho :-/ this is true, we would need a different solution for that. there's...