Releases: ben-ryder/kangojs
kangojs v1.1.2
A small bug fix release that changes an interface but shouldn't really affect anything.
🐛 Bug Fixes
- Changing return interface of validator functions from
Promise<any>
toany
.
error-handler v0.1.0
Inital public release of @kangojs/error-handler
.
This package is useable enough for an initial release, but is still under development.
I'm planning to use it on a few more projects first to ensure I'm happy with the basic funcitonality/interface etc before I make a v1.0.0
release
kangojs v1.1.1
This version makes some behind the scenes refactors but does not affect how the package functions.
common-middleware v1.2.0
kangojs v1.1.0
Release v1.1.0 of the core kangojs framework package.
🐛 Bug Fixes
⚠️ Changedexpress
to be a peer dependency rather than just a dependency. (#1)
class-validation v1.0.3
Minor bug fix release.
🐛 Bug Fixes
- Fixing query request data being added to the request object as
bodyDto
notqueryDto
.
class-validation v1.0.2
A small bug fix release that ensures the internal error prettier (classValidatorErrorPrettier
) can deal with an array of errors.
If multiple validation issues are found class-validator can return an array of ValidationError
, but the prettier was always assuming only a single ValidationError
could ever be returned.
🐛 Bug Fixes
- Fixing fatal error that occurred when class-validator found multiple validation errors in request data.
serve-spa v1.0.0
I've ironed out a number of issues and think this package is now stable enough for a v1 release.
🐛 Bug Fixes
- Fixed error handling not working for
res.sendFile
, now the fallback message works as expected. - Fixed the default base route being
/
not/*
which meant the app was only served on the root Express path. - Fixed
folderPath
handling by removing__dirname
references, now the folder path actually works.
🛠️ Changes
- Default fallback message updated to
There has been an unexpected error loading this page. Please try again later.
serve-spa v0.1.0
The first public release of serve-spa.
Kept at pre v1.0.0 release for the moment as I've not used it enough to be sure it works ok.
common-middleware v1.1.0
Adds a new path
option to useNotFoundMiddleware
which lets you specifiy what path you want the middleware to apply for, just like you would with app.use(path, (req, res) => {})
.
This is useful in situations where the response should only be given for certain paths. An example would be where API requests made to /api/*
should return the response but all others should be rooted to a frontend single-page app like React.