
Security News
vlt Launches "reproduce": A New Tool Challenging the Limits of Package Provenance
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
next-client-cookies
Advanced tools
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 which will be pre-render also on the server.
Interface and client side implementation based on the js-cookie package.
yarn add next-client-cookies
client only
component provider:'use client';
import { CookiesProvider } from 'next-client-cookies';
export const ClientCookiesProvider: typeof Provider = (props) => (
<Provider {...props} />
);
app/layout.tsx
file, add the CookiesProvider
:import { cookies } from 'next/headers';
import { ClientCookiesProvider } from './provider';
export default function RootLayout({ children }) {
return (
<ClientCookiesProvider value={cookies().getAll()}>
{children}
</ClientCookiesProvider>
);
}
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.delete('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 = () => {
const cookies = getCookies();
return (
<div>
<p>My cookie value: {cookies.get('my-cookie')}</p>
</div>
);
};
MIT
FAQs
SSR and client support for Next.js v13 cookies (app directory)
The npm package next-client-cookies receives a total of 20,869 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
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.