Run `applyToEnvironment` before `resolveConfig`

Important limitations

• This may be one public report, not widespread demand.
• Current independent report count: 1.
• This is currently a single independent report. It has not passed clustering or human review as a verified signal.
• No market size, willingness to pay, competition, or trend claims are inferred here.

What was reported

Who is affected

Frontend application developer

Job to be done

Configure an application runtime reliably

Workflow

Per documentation (https://vite.dev/guide/api-environment-plugins#per-environment-plugins-using-the-applytoenvironment-hook) the `applyToEnvironment` hook (which is also used in `perEnvironmentPlugin`) runs after `resolveConfig`.

Desired outcome

I've kinda fixed it here using `buildStart` https://github.com/sveltejs/vite-plugin-svelte/pull/1385, but I agree with @teemingc that this should probably be solved in `vite` since a lot of plugins might resort to this type of logic.

Severity

Not enough evidence yet.

Urgency

Not enough evidence yet.

Evidence indicators

What would upgrade this

• Additional independent reports from distinct communities or authors.
• Human clustering into a review signal, then explicit publication approval.
• Counter-evidence review and durable original-source verification.

Original source

Open the original public report