feat: plugin auto-importer with vite-plugin-resolve

[JellyBrick]

cc @ArjixWasTaken @Su-Yong

[ArjixWasTaken]

Instead of having a named export, how about having a default export?

That way, you don't need to alias the imported constant every time.

[JellyBrick]

Instead of having a named export, how about having a default export?

That way, you don't need to alias the imported constant every time.

https://basarat.gitbook.io/typescript/main-1/defaultisbad

For the above reasons, I wanted to avoid using the default export. What do you think?

[ArjixWasTaken]

Hmm, then what about having a different named export for each context?
Just like feat/codegen.

[JellyBrick]

Hmm, then what about having a different named export for each context? Just like feat/codegen.

• Before I do this, I want to rename front.ts to renderer.ts and back.ts to main.ts.
  • (to clarify the context in which the plugin is running)
  • (frontPluginList -> rendererPluginList, backPluginList -> mainPluginList)
• So, is it okay if I merge this pull request before doing a rename task?