How come there isn't a Hook or Plugin API Before Configuration/Environment Resolution

[klaireli]

I’m working on a Yarn 4.9+ setup where I need to intercept or inject logic before Yarn reads environment variables or configuration files (e.g. .yarnrc.yml). Specifically, I want to influence env vars or project-specific settings dynamically, without requiring wrapper scripts or forking Yarn.

This would ideally allow early logic to run before things like:

Configuration.find(...)

.yarnrc.yml resolution

Plugin loading (which currently depends on config being resolved)

Use Case
We’re exploring an internal security authentication that:

• Authenticates and sets sensitive env vars dynamically
• Needs to happen before Yarn pulls in plugin configs or variables from .yarnrc.yml

Currently we’re working around this using:

• Custom wrapper scripts but this either requires devs to run an extra command on top of yarn install or requires us to inject code into developers' profiles.

But we'd prefer a cleaner, officially supported way to hook into this lifecycle point — ideally something like:

// Pseudocode idea
yarn.registerEarlyHook(async () => {
  process.env.NPM_TOKEN = await getSecretFromSomewhere();
});

Why the Current Plugins Don’t Work Today
Plugins (like validateProject) are only loaded after the configuration is already resolved. This prevents using them to modify config or envs that Yarn has already cached or used.