feat: support async plugins

[MarijnMensinga]

🔗 Linked issue

#915

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Plugins should be loaded async to make the plugins bootstrap propperly.

This fixes potential race-conditions when creating plugins that are called before they are bootstrapped correctly.

Resolves #915

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly. (not needed)

[pi0]

This is a nice feature to have! The main issue is that support for top-level await is limited and many providers are currently depending on nonasync API.

Putting a pending label for now. It is likely we could only support async plugins in Nitropack v3 and some breaking changes.

[Hebilicious]

@pi0 Can't we work around the top level await issue with a closure ?

const createNitroApp = () => {

const installPlugins = async () => {
  for (const plugin of plugins) {
    await plugin(app);
  }
}

installPlugins()
}

[pi0]

@Hebilicious no we lose order this way. (plugins can initialize too late and while/after first requests coming). Such example (dangling promises, can be already done inside a plugin and is a bad practice everywhere to left promises unanttended.

[pi0]

Thanks for PR again dear @MarijnMensinga. It is not mergeable without breaking changes. Let's keep track via #915 (i might have some ideas to introduce as non breaking)