[FR] Enable Hot Module Replacement for Plugin Development

[GustavoOS]

Proposal Summary

Allow hot module reload for plugin development

Motivation

• What is the use case for this feature? Quick feedback for plugin development
• Why is this use case valuable to support for FiftyOne users in general? Allow developers to quickly evaluate changes
• Why is this use case valuable to support for your project(s) or organization? Less time wasted on rebuilding project
• Why is it currently difficult to achieve this use case? Fiftyone setup does not support Hot Module Replacement

What areas of FiftyOne does this feature affect?

• App: FiftyOne application
• Core: Core fiftyone Python library
• Server: FiftyOne server

Details

Usual scenario:

• Usually, HMR is achieved with a bundler, like Webpack, Turbopack, Rollup, Rolldown or SWC
• The application (plugin) runs in a developer mode
• When code changes, the bundler recompiles only the changed module

So I think a solution may need to allow a fiftyone developer mode that allows HMR

Willingness to contribute

The FiftyOne Community welcomes contributions! Would you or another member of your organization be willing to contribute an implementation of this feature?

• Yes. I can contribute this feature independently
• Yes. I would be willing to contribute this feature with guidance from the FiftyOne community
• No. I cannot contribute this feature at this time