`addPlugin` from `@nuxt/kit` prepends plugins

Environment

---

• Operating System: Linux
• Node Version: v16.14.2
• Nuxt Version: 3.0.0-rc.4
• Package Manager: npm@7.17.0
• Builder: vite
• User Config: modules
• Runtime Modules: @/modules/pinia, @/modules/my-module
• Build Modules: -

---

Reproduction

https://stackblitz.com/edit/github-ba6rwp?file=nuxt.config.ts

Describe the bug

addPlugin, by default, prepends to the list of plugins. This is great for the purpose described in code comment.

There are two problems though:

a) a module depends on other modules, the natural approach is to order them in a manner that dependencies are first

modules: [
  '@pinia/nuxt', 
  'my-module-depends-on-pinia' // <-- uses pinia
]

b) a module can expose more than one plugin depending on each other

addPlugin(resolver.resolve('./plugins/api.js')
addPlugin(resolver.resolve('./plugins/auth.js') // <-- calls api

In both cases, the module / plugin registered later does not have access to the plugins added prior. Adding { append: true } is not ideal, as it puts the module plugins after user plugins.

Additional context

No response

Logs

No response

[pi0]

Hi @Aareksio These two are not related with the built-in app:created hook and plugin ordering.

Closing this issue because default preprend behavior is intended explained in previous comment.

[Aareksio]

Linking here as discussions tend to be overlooked and it is heavily related: https://github.com/nuxt/framework/discussions/6436