2.0.0 #36
Merged
2.0.0 #36
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Refactored code internally to add support for multiple frameworks * Added sveltekit integration * Exposed lower-level api * Added more unit tests
* removed unnecessary dependencies * fixed exports in package.json * fixed error export * next14 and sveltekit examples are working
* added types to package.json, moved peerDependencies to optionalDependencies * fixed build externals issue * updated examples * fixed linting issue * updated pnpm-lock.yaml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request implements a new major version of Edge-CSRF (2.0.0) with several breaking changes:
@edge-csrf/nextjs- Next.js integration library@edge-csrf/sveltekit- SvelteKit integration library@edge-csrf/core- Core APIcreateCsrfMiddleware(),createCsrfHandle())createCsrfProtect())