Releases: raptor-js/kernel
Releases · raptor-js/kernel
v0.25.0
v0.24.0
v0.23.0
v0.22.0
v0.21.0
Changes
- Added new
hostnameconfiguration option to Kernel, allowing you to specific a different hostname from localhost, such as0.0.0.0when working within a docker container. - Return the
Responseinstance immediately if found within the middleware stack.
No changes required for existing applications in this release.
v0.20.1
v0.20.0
Changes
- Moved from recursive middleware chain execution to iterative, which improves performance as systems scale. This performance improvement helps Raptor to become the fastest of all tested middleware frameworks in Deno (other runtimes should reflect the same performance statistics).
- Improve config-driven support for overriding the
ServerManagerandResponseManager, as well as support for adding and configuring response processors.
v0.19.0
v0.18.0
Changes
- Kernel options have now been moved to a configuration object, this is aligned with the rest of the Raptor ecosystem now moving to a consistent, configurable instantiation of core classes.
Upgrading from 0.17.x to 0.18.0
The only real change required is to change the definition of port from the serve method to the new Config object, which is passed optionally to the Kernel constructor.
Example
const app = new Kernel({ port: 8000 });
app.serve();