Optionaloptions: CookieParseOptionsDeletes a cookie by setting its value to an empty string and setting the expiry date in the past.
You must specify a path for the cookie. In most cases you should explicitly set path: '/' to make the cookie available throughout your app. You can use relative paths, or set path: '' to make the cookie only available on the current path and its children
the name of the cookie
the options, passed directly to cookie.serialize. The path must match the path of the cookie you want to delete. See documentation here
Gets a cookie that was previously set with cookies.set, or from the request headers.
the name of the cookie
Gets all cookies that were previously set with cookies.set, or from the request headers.
Serialize a cookie name-value pair into a Set-Cookie header string, but don't apply it to the response.
The httpOnly and secure options are true by default (except on http://localhost, where secure is false), and must be explicitly disabled if you want cookies to be readable by client-side JavaScript and/or transmitted over HTTP. The sameSite option defaults to lax.
You must specify a path for the cookie. In most cases you should explicitly set path: '/' to make the cookie available throughout your app. You can use relative paths, or set path: '' to make the cookie only available on the current path and its children
the name of the cookie
the cookie value
the options, passed directly to cookie.serialize. See documentation here
Sets a cookie. This will add a set-cookie header to the response, but also make the cookie available via cookies.get or cookies.getAll during the current request.
The httpOnly and secure options are true by default (except on http://localhost, where secure is false), and must be explicitly disabled if you want cookies to be readable by client-side JavaScript and/or transmitted over HTTP. The sameSite option defaults to lax.
You must specify a path for the cookie. In most cases you should explicitly set path: '/' to make the cookie available throughout your app. You can use relative paths, or set path: '' to make the cookie only available on the current path and its children
the name of the cookie
the cookie value
the options, passed directly to cookie.serialize. See documentation here
Minimal SvelteKit-compatible cookie implementation for non-SvelteKit servers. Reads cookies from the incoming Request and collects Set-Cookie values for the outgoing response.