ngx-cookie-service

What is ngx-cookie-service?

The ngx-cookie-service is an Angular service for handling cookies. It provides a simple API to set, get, and delete cookies in an Angular application.

What are ngx-cookie-service's main functionalities?

Set a Cookie

This feature allows you to set a cookie with a specified name and value. In this example, a cookie named 'test' with the value 'Hello World' is set.

import { CookieService } from 'ngx-cookie-service';

constructor(private cookieService: CookieService) { }

this.cookieService.set('test', 'Hello World');

Get a Cookie

This feature allows you to retrieve the value of a cookie by its name. In this example, the value of the cookie named 'test' is retrieved and logged to the console.

import { CookieService } from 'ngx-cookie-service';

constructor(private cookieService: CookieService) { }

const value = this.cookieService.get('test');
console.log(value);

Delete a Cookie

This feature allows you to delete a cookie by its name. In this example, the cookie named 'test' is deleted.

import { CookieService } from 'ngx-cookie-service';

constructor(private cookieService: CookieService) { }

this.cookieService.delete('test');

Check if a Cookie Exists

This feature allows you to check if a cookie exists by its name. In this example, it checks if the cookie named 'test' exists and logs the result to the console.

import { CookieService } from 'ngx-cookie-service';

constructor(private cookieService: CookieService) { }

const exists = this.cookieService.check('test');
console.log(exists);

Other packages similar to ngx-cookie-service

ngx-cookie

ngx-cookie is another Angular package for handling cookies. It provides similar functionalities to ngx-cookie-service, such as setting, getting, and deleting cookies. However, ngx-cookie also offers additional features like cookie serialization and deserialization.

angular2-cookie

angular2-cookie is an older package for managing cookies in Angular applications. It offers basic cookie operations similar to ngx-cookie-service but is less actively maintained and may not support the latest Angular versions.

README

NGX Cookie Service

An (AOT ready) Angular (4.2+) service for cookies. Originally based on the ng2-cookies library.

Installation

npm install ngx-cookie-service --save

# or

yarn add ngx-cookie-service

Add the cookie service to your app.module.ts as a provider:

import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { FormsModule } from '@angular/forms';
import { HttpModule } from '@angular/http';

import { AppComponent } from './app.component';
import { CookieService } from 'ngx-cookie-service';

@NgModule({
  declarations: [ AppComponent ],
  imports: [ BrowserModule, FormsModule, HttpModule ],
  providers: [ CookieService ],
  bootstrap: [ AppComponent ]
})
export class AppModule { }

Then, import and inject it into a component:

import { Component, OnInit } from '@angular/core';
import { CookieService } from 'ngx-cookie-service';

@Component({
  selector: 'demo-root',
  templateUrl: './app.component.html',
  styleUrls: [ './app.component.scss' ]
})
export class AppComponent implements OnInit {
  cookieValue = 'UNKNOWN';

  constructor( private cookieService: CookieService ) { }

  ngOnInit(): void {
    this.cookieService.set( 'Test', 'Hello World' );
    this.cookieValue = this.cookieService.get('Test');
  }
}

That's it!

What to do now?

• Run npm run test to run the tests for the cookie service (located in the demo-app folder)
• Have a look at and play around with the demo-app to get to know the cookie service with npm run start (open http://localhost:4200/ in your favourite browser)
• If you do not want to install this via NPM, you can run npm run compile and use the *.d.ts and *.js files in the dist-lib folder

Methods

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' ): void;

cookieService.set( 'test', 'Hello World' );

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.

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.

delete( name: string, path?: string, domain?: string ): void;

cookieService.delete('test');

Deletes a cookie with the specified name. It is best practice to always define a path. If you are unsure about the path value, use '/'.

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 ): void;

cookieService.deleteAll();

Deletes all cookies that can currently be accessed. It is best practice to always define a path. If you are unsure about the path value, use '/'.

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.cookie manually (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).

• Open a new pull request

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:

• paroe
• CunningFatalist
• kthy
• JaredClemence
• flakolefluk
• mattbanks
• DBaker85
• mattlewis92

License

MIT

Changelog

2.2.0

• use ng-packagr instead of our own outdated build script
• use one single readme file for both NPM and GitHub
• update package.json scripts