![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
next-client-cookies
Advanced tools
SSR and client support for Next.js v13 cookies (app directory)
Client cookies with support for SSR on the newest Next.js 13 (app directory).
SSR are client components that can be rendered both on the client and server side. Server components are server only components that can only be rendered on the server side. This library can support all 3 cases and will give you everything you need to work with cookies on the client and server side.
Please note that Next.js currently does NOT support updating cookies on Server Components (only on Actions or Routes are allowed to make changes to cookies within the server). If you need to update cookies on the server, please switch to a Client Component. Client components can be rendered on the server side (via SSR) and will support also updating cookies via special dehydration mechanism implemented by this library.
Interface and client side implementation based on the js-cookie package.
npm add next-client-cookies
app/layout.tsx
file, add the CookiesProvider
:import { CookiesProvider } from 'next-client-cookies/server';
export default function RootLayout({ children }) {
return <CookiesProvider>{children}</CookiesProvider>;
}
Please note this will make the entire app to opted out of static generation. If you want to opt out only some pages, you can use the CookiesProvider
on a per page basis and create a custom server-side layout.tsx
file for those pages.
This will work BOTH on the client and server side for SSR.
'use client';
import { useCookies } from 'next-client-cookies';
const MyComponent = () => {
const cookies = useCookies();
return (
<div>
<p>My cookie value: {cookies.get('my-cookie')}</p>
<button onClick={() => cookies.set('my-cookie', 'my-value')}>
Set cookie
</button>
{' | '}
<button onClick={() => cookies.remove('my-cookie')}>Delete cookie</button>
</div>
);
};
Will produce the same Cookies
interfaces using Next.js's cookies()
helper.
import { getCookies } from 'next-client-cookies/server';
const MyComponent = async () => {
const cookies = await getCookies();
return (
<div>
<p>My cookie value: {cookies.get('my-cookie')}</p>
</div>
);
};
v1
If you are migrating from v1
, you will need to add await
to the getCookies
function. This is because Next.js's cookies()
function is now async and will return a promise.
- const cookies = getCookies();
+ const cookies = await getCookies();
MIT
FAQs
SSR and client support for Next.js v13 cookies (app directory)
The npm package next-client-cookies receives a total of 21,407 weekly downloads. As such, next-client-cookies popularity was classified as popular.
We found that next-client-cookies demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.