A lot of Harper's core functionality is implemented as built-in extensions. We plan to deprecate (but still support) extensions in v5. As part of that deprecation effort, we must also migrate all of the build-in extensions to use the new plugin API.
In general, this will unlock significant new capabilities for our core features. The plugin API only runs on worker threads and so these features will be able to take advantage of restarts more effectively. Similarly, the new file watcher system for plugins makes them much more flexible and some may not even need restarts to handle configuration changes at runtime.
A good example of an built-ins that have already been converted to the plugin API are jsResource and static
This issue will track sub-issues for each of the remaining build-in extension migrations.
A lot of Harper's core functionality is implemented as built-in extensions. We plan to deprecate (but still support) extensions in v5. As part of that deprecation effort, we must also migrate all of the build-in extensions to use the new plugin API.
In general, this will unlock significant new capabilities for our core features. The plugin API only runs on worker threads and so these features will be able to take advantage of restarts more effectively. Similarly, the new file watcher system for plugins makes them much more flexible and some may not even need restarts to handle configuration changes at runtime.
A good example of an built-ins that have already been converted to the plugin API are jsResource and static
This issue will track sub-issues for each of the remaining build-in extension migrations.