Releases: tuftjs/tuft
Tuft 2.5.1
The preHandlers option when calling tuft() has been changed to prehandlers (now with a lowercase 'h'). preHandlers can still be used, but support for it might be removed in a future major release.
If both versions are provided, then prehandlers will take precedence:
const app = tuft({
prehandlers: [FunctionOne],
preHandlers: [FunctionTwo] // will be ignored
})Tuft 2.5.0
CORS support has been added in this release via the cors route map option. See the official docs for detailed usage information.
Tuft 2.4.2
Fixed a bug where response objects with a status property and no other properties were not being handled.
Tuft 2.4.1
The default response now sends a body of 'OK' in addition to the 200 status code.
Tuft 2.4.0
This release includes a new built-in prehandler extension called Session, which is a simple middleware function for managing user sessions via cookies.
For detailed information on its usage, please see the official documentation.
Tuft 2.3.1
This is a patch release to remove some very minor redundant code that gets inserted by TypeScript during the compilation process.
Tuft 2.3.0
Further optimizations have been made to extract as much performance as possible out of the request/response cycle without removing features.
Tuft 2.2.0
This release includes further optimizations to built-in response handling performance.
Tuft 2.1.0
This release includes minor optimizations to built-in response handling performance.
Tuft 2.0.0
The pre-release tag is being removed to more closely align with standard versioning practices for open source software. However, any project that implements Tuft should still be thoroughly tested if intended for use in a production environment.