Discover the latest updates.
Full Changelog: https://github.com/Baroshem/nuxt-security/compare/v0.13.0...v0.13.1
This Release introduces a new approach to registering security headers and middlewares by using the routeRules
. I tried my best to provide backward compatibility but you may experience issues in your projects.
Basically, the configuration provided in security
object in nuxt.config.ts
is now used as a global configuration while any per-route
configuration is now handled by routeRules
.
Check out the docs to see the changes: https://nuxt-security.vercel.app/getting-started/configuration
Full Changelog: https://github.com/Baroshem/nuxt-security/compare/v0.12.0...v0.13.0
Full Changelog: https://github.com/Baroshem/nuxt-security/compare/v0.10.2...v0.11.0
Full Changelog: https://github.com/Baroshem/nuxt-security/compare/v0.10.1...v0.10.2
Full Changelog: https://github.com/Baroshem/nuxt-security/compare/v0.9.0...v0.10.0
npm
with yarn
in readme by @DamianGlowala in #63rateLimiter
by @DamianGlowala in #62Full Changelog: https://github.com/Baroshem/nuxt-security/compare/v0.8.0...v0.9.0
Full Changelog: https://github.com/Baroshem/nuxt-security/compare/v0.6.0...v0.7.0
Full Changelog: https://github.com/Baroshem/nuxt-security/compare/v0.5.0...v0.6.0
Full Changelog: https://github.com/Baroshem/nuxt-security/compare/v0.4.0...v0.5.0
With this version we have refactored the security header middlewares into recently released routeRoules that should be faster and easier to override by the user.
If you have added a custom headers that were supposed to ovveride the the default ones.
Previously security header middleware routes were ''
empty strings and it was causing the middleware to be global.
Right now, with routeRoules, the route should be /**
to make it global.
Full Changelog: https://github.com/Baroshem/nuxt-security/compare/v0.3.0...v0.4.0
Full Changelog: https://github.com/Baroshem/nuxt-security/commits/v0.1.0