We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
configResolved
Plugins may want to do asynchronous setup based on information available from the configResolved hook.
usecase for me: reading svelte config with dynamic import sveltejs/vite-plugin-svelte#29
I'm willing to provide a PR with the needed changes.
Make configResolved async and await the on the calls.
Plugins could try to work around this by adding special handling to the first call of transform but that feels wrong.
config hook has been made async recently: #2798 but it has less information available.
config
The text was updated successfully, but these errors were encountered:
feat(plugin-api): support async configResolved hooks (fixes vitejs#2949)
06e008e
3196616
feat(plugin-api): support async configResolved hooks (fixes #2949) (#…
8b38168
…2951)
Successfully merging a pull request may close this issue.
Clear and concise description of the problem
Plugins may want to do asynchronous setup based on information available from the
configResolved
hook.usecase for me: reading svelte config with dynamic import sveltejs/vite-plugin-svelte#29
I'm willing to provide a PR with the needed changes.
Suggested solution
Make configResolved async and await the on the calls.
Alternative
Plugins could try to work around this by adding special handling to the first call of transform but that feels wrong.
Additional context
config
hook has been made async recently: #2798 but it has less information available.The text was updated successfully, but these errors were encountered: