fix: use maxAge
instead of expires
#30
Merged
+1
−1
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.
According to
@fastify/session
v9 (the version used by this example),expires
is supposed to be adate
, not anumber
.maxAge
can be used instead since it is expecting anumber
.Documentation for reference: https://github.com/fastify/session/tree/v9.0.0#cookie
Checklist
npm run test
and(doesn't exist)npm run benchmark
and the Code of conduct