stevermeister/ngx-cookie-service
stevermeister/ngx-cookie-service has 561 GitHub stars and 88 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-17 03:03 UTC. Last push 2026-11-14.
Measured star growth
- in 24h
- 0
- in 7 days
- Collecting history
- in 15 days
- Collecting history
- in 1 month
- Collecting history
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
About
Angular (4.2+ ...12) service for cookies. Originally based on the `ng2-cookies` library.
Developer ToolsREADME.md
OriginalNGX Cookie Service
Angular service to read, set and delete browser cookies. Originally based on the ng2-cookies library. This service is lightweight, and its bundle size is 1.3 Kb to ensure fast loading times and optimal performance.
Installation
npm i ngx-cookie-service
# or
yarn add ngx-cookie-service
Demo
Cooke Service Demo: https://stackblitz.com/~/github.com/pavankjadda/ngx-cookie-service-demo
SSR Cookie Service Demo: https://ngx-cookie-service-ssr-demo.netlify.app/
Usage
In standalone components, import the CookieService directly into the component
import { CookieService } from 'ngx-cookie-service'; import { Component } from '@angular/core'; @Component({ selector: 'my-component', template: `<h1>Hello World</h1>`, providers: [CookieService], }) export class HelloComponent { constructor(private cookieService: CookieService) { this.cookieService.set('token', 'Hello World'); console.log(this.cookieService.get('token')); } }You can also use
inject()method in v14+ to inject the service into the componentimport { CookieService } from 'ngx-cookie-service'; import { Component, inject } from '@angular/core'; @Component({ selector: 'my-component', template: `<h1>Hello World</h1>`, providers: [CookieService], }) export class HelloComponent { cookieService = inject(CookieService); constructor() { this.cookieService.set('token', 'Hello World'); console.log(this.cookieService.get('token')); } }
Server Side Rendering
Ngx Cookie Service supports Server Side Rendering (SSR) via dedicated
library ngx-cookie-service-ssr.
Only install ngx-cookie-service-ssr library (and skip ngx-cookie-service) for SSR
Install the library using below command
npm install ngx-cookie-service-ssr --save # or yarn add ngx-cookie-service-ssrBy default, browser cookies are not available in SSR because
documentobject is not available. To overcome this, navigate toserver.tsfile in your SSR project, and replace the following codeserver.get('*', (req, res) => { res.render(indexHtml, { req, providers: [{ provide: APP_BASE_HREF, useValue: req.baseUrl }] }); });
with this
server.get('*', (req, res) => {
res.render(indexHtml, {
req,
providers: [
{ provide: APP_BASE_HREF, useValue: req.baseUrl },
{ provide: 'REQUEST', useValue: req },
{ provide: 'RESPONSE', useValue: res },
],
});
});
- This will make sure the cookies are available in
REQUESTobject, and thengx-cookie-service-ssrcan useREQUEST.cookiesto access the cookies in SSR. Then proceed to usengx-cookie-serviceas usual. - See the sample repo for more details.
- On the server,
get(),check()andgetAll()also see cookies set or deleted earlier while rendering the same request, whatever theirpathordomain. Cookies withhttpOnly: truecan only be set on the server; in the browser the call is skipped with a console warning.
Supported Versions
We follow angular LTS versions. The latest version of the library supports Angular 22.x.x. Angular 14.x.x or below is not supported.
| Angular Version | Supported Version |
|---|---|
| 22.x.x | 22.x.x |
| 21.x.x | 21.x.x |
| 20.x.x | 20.x.x |
| 19.x.x | 19.x.x |
| 18.x.x | 18.x.x |
| 17.x.x | 17.x.x |
| 16.x.x | 16.x.x |
| 15.x.x | 15.x.x |
API
check( name: string ): boolean;
const cookieExists: boolean = cookieService.check('test');
Checks if a cookie with the givenname can be accessed or found.
get( name: string ): string;
const value: string = cookieService.get('test');
Gets the value of the cookie with the specified name.
getAll(): {};
const allCookies: {} = cookieService.getAll();
Returns a map of key-value pairs for cookies that can be accessed.
set( name: string, value: string, expires?: number | Date, path?: string, domain?: string, secure?: boolean, sameSite?: 'Lax' | 'Strict' | 'None' ): void;
set( name: string, value: string, options?: { expires?: number | Date, path?: string, domain?: string, secure?: boolean, sameSite?: 'Lax' | 'None' | 'Strict'}): void;
cookieService.set('test', 'Hello World');
cookieService.set('test', 'Hello World', { expires: 2, sameSite: 'Lax' });
Sets a cookie with the specified name and value. It is good practice to specify a path. If you are unsure about the
path value, use '/'. If no path or domain is explicitly defined, the current location is assumed. sameSite defaults
to Lax.
Important: For security reasons, it is not possible to define cookies for other domains. Browsers do not allow this. Read this and this StackOverflow answer for a more in-depth explanation.
Important: Browsers do not accept cookies flagged sameSite = 'None' or partitioned unless the secure flag is set as well. CookieService will override the secure flag to true if sameSite='None' or partitioned is true.
If path or domain contains ; or a control character, the cookie is not written or deleted, and a warning is
logged to the console. An invalid expires or sameSite value is ignored with a warning.
delete( name: string, path?: string, domain?: string, secure?: boolean, sameSite: 'Lax' | 'None' | 'Strict' = 'Lax'): void;
delete( name: string, options?: { path?: string, domain?: string, secure?: boolean, sameSite?: 'Lax' | 'None' | 'Strict', partitioned?: boolean }): void;
cookieService.delete('test');
cookieService.delete('test', { path: '/', secure: true, sameSite: 'None', partitioned: true });
Deletes a cookie with the specified name. The attributes must match the ones the cookie was set with: path and
domain select the cookie, and partitioned: true is needed to delete a Partitioned cookie.
It is best practice to always define a path. If you are unsure about the path value, use '/'. Without a path, the
browser uses the directory of the URL the page was loaded at, so in a single-page app the result depends on the URL the
user first landed on.
Important: For security reasons, it is not possible to delete cookies for other domains. Browsers do not allow this. Read this and this StackOverflow answer for a more in-depth explanation.
deleteAll( path?: string, domain?: string, secure?: boolean, sameSite: 'Lax' | 'None' | 'Strict' = 'Lax' ): void;
deleteAll( options?: { path?: string, domain?: string, secure?: boolean, sameSite?: 'Lax' | 'None' | 'Strict', partitioned?: boolean }): void;
cookieService.deleteAll();
cookieService.deleteAll({ path: '/' });
Deletes all cookies that can currently be accessed, using the same attributes for each one. It is best practice to
always define a path. If you are unsure about the path value, use '/'.
provideCookieOptions( options: CookieOptions ): EnvironmentProviders;
// app.config.ts
import { provideCookieOptions } from 'ngx-cookie-service'; // or 'ngx-cookie-service-ssr'
export const appConfig: ApplicationConfig = {
providers: [provideCookieOptions({ path: '/', secure: true, sameSite: 'Strict' })],
};
Sets default options for every set(), delete() and deleteAll() call, so you don't have to repeat them. Options
passed to a call win over the defaults, and undefined values don't override them. A call that passes its own expires
(or maxAge in ngx-cookie-service-ssr) replaces the default lifetime, so delete() always expires the cookie.
Setting path: '/' here is recommended. Without a path, the browser uses the directory of the URL the page was loaded
at, so the same code can read or delete different cookies depending on where the user landed.
provideCookieEncoding( encoding: 'uri' | 'minimal' | CookieCodec ): EnvironmentProviders;
// app.config.ts
import { provideCookieEncoding } from 'ngx-cookie-service'; // or 'ngx-cookie-service-ssr'
export const appConfig: ApplicationConfig = {
providers: [provideCookieEncoding('minimal')],
};
Sets how cookie values are encoded when they are written and decoded when they are read. Cookie names keep the default encoding.
'uri'(default): values are encoded withencodeURIComponent, soab+/cd==is stored asab%2B%2Fcd%3D%3D.'minimal': values made only of characters allowed in a cookie value are stored as-is, soab+/cd==staysab+/cd==. Other values fall back toencodeURIComponent. Use it when a server reads cookies without URL-decoding them, for example JWT or base64 values. Express encodes cookie values the same way.- A custom
{ encode(value, name), decode(value, name) }object for any other scheme. If the encoded value contains;or a control character, the cookie is not written and a warning is logged.
FAQ
General tips
Checking out the following resources usually solves most of the problems people seem to have with this cookie service:
- article about cookies in general @MDN (recommended read!)
- common localhost problems @StackOverflow
- problems with secure cookies @StackOverflow
- how do browser cookie domains work? @StackOverflow
- get cookies from different paths
The following general steps are usually very helpful when debugging problems with this cookie service or cookies in general:
- check out if there are any open or closed issues that answer your question
- check out the actual value(s) of
document.cookie - does it work if you use
document.cookiemanually (i.e. in a console of your choice)? - set explicit paths for your cookies
- explain to your local rubber duck why your code should work and why it (probably) does not
I am always getting a "token missing" or "no provider" error.
Package managers are a well known source of frustration. If you have "token missing" or "no provider" errors, a simple re-installation of your node modules might suffice:
rm -rf node_modules
yarn # or `npm install`
I have a problem with framework X or library Y. What can I do?
Please be aware that we cannot help you with problems that are out of scope. For example, we cannot debug a Symfony or Springboot application for you. In that case, you are better off asking the nice folks over at StackOverflow for help.
Do you support Angular Universal?
There is an issue for that. Check out this comment for more information about future support.
Opening issues
Please make sure to check out our FAQ before you open a new issue. Also, try to give us as much information as you can when you open an issue. Maybe you can even supply a test environment or test cases, if necessary?
Contributing
We are happy to accept pull requests or test cases for things that do not work. Feel free to submit one of those.
However, we will only accept pull requests that pass all tests and include some new ones (as long as it makes sense to add them, of course).
Author
This cookie service is brought to you by 7leads GmbH. We built it for one of our apps, because the other cookie packages we found were either not designed "the Angular way" or caused trouble during AOT compilation.
Contributors
Thanks to all contributors:
- Pavan Kumar Jadda
- paroe
- CunningFatalist
- kthy
- JaredClemence
- flakolefluk
- mattbanks
- DBaker85
- mattlewis92
- IceBreakerG
- rojedalopez
- Nikel163