-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
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
Make plugins async #915
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This issue is on track and I might have some ideas to support it in a nonbreaking change version with slight behavior-only changes. In the meantime, please consider issue 👍🏼 on main issue if you also want this feature 🙏🏼 |
It all seems relatively straightforward. The last step is the only tricky one
This will ensure that the semantics of order and waiting for one plugin to finish before the next runs are retained. I guess I don't understand why this is complicated... |
Sadly, it is not that straightforward without behavior changes / overhead because not all nitro presets are compatible with an async entry today but thanks for your feedback dear @robertpatrick. |
For the benefit of bootstrapping plugins it is usefull to make plugins load async.
nitro/src/runtime/app.ts
Lines 89 to 91 in ed3a480
Can someone explain to me if there is a good reason to load plugins synchronously?
The text was updated successfully, but these errors were encountered: