Currently the only way to register plugin is to define
main.ts (or main.js)
with
export default class MyPlugin extends Plugin { ... }
From what I see in implementation of loadPlugin() in in app.js, that’s the only way Obsidian plugin system can discover the plugin.
However, using export default is considered a bad practice in the modern ts/js.
It would be great if Obsidian provides a way to avoid the export default approach to enforce modern best practices.
class MyPlugin extends Plugin { ... }
export { MyPlugin as SomeMagicNameThatObsidianRecognizes };