npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@team-griffin/uteals

v3.0.0

Published

Utilities for Tealium

Downloads

15

Readme

teal-utils

Consent

(
  mappings: {
    [id: string]: string,
  },
) => Object
import { Consent } from '@team-griffin/uteals';

The consent module allows you to fetch and update the opt out preferences.

To create an optOut instance, call it with a mapping of category ids to aliases:

const o = new Consent({
  0: 'default',
  c11: 'analytics',
});

This means you can reference the preferences by their aliases rather than their ids.

get

(
  categories?: Array<string>,
  consent: string,
) => {
  [id: string]: boolean,
}

Fetches the categories, with a boolean value to indicate whether the user has given consent for that option.

o.get([ 'default' ], '0:1|c:0') // -> { default: true }

The categories list is optional, if you call get with no arguments, it will return all categories:

o.get(null, '0:0|c:1'). // -> { default: true, analytics: false }

set

(
  categories: {
    [id: string]: boolean,
  },
  consent: string,
) => string;

Sets the consent flag for the given categories. Any categories not passed into this method will be preserved.

o.set({
  default: false,
}, '0:1|c:0')

getByOrder

(
  categories: Array<string>,
  consent: string,
) => {
  [category: string]: {
    id: string,
    value: boolean,
  },
}

If you don't know the ids of your categories, but you know the order they will be in, you can use this method to extract the ids and flags based purely on their order.

const o = consent();

o.getByOrder([ 'default', 'analytics' ], '0:1|c:0') // { default: { id: '0', value: false }, analytics: { id: 'c', value: true }}

Cookie Consent

(
  mappings: {
    [id: string]: string,
  },
  cookieOptions?: Object,
) => Object
import { CookieConsent } from '@team-griffin/uteals';

This variation fetches the consent data from a cookie rather than being passed in explicitly.

To create an instance, call it with a mapping of category ids to aliases:

const o = new CookieConsent({
  0: 'default',
  c11: 'analytics',
});

This means you can reference the preferences by their aliases rather than their ids.

get

(
  categories?: Array<string>,
) => {
  [id: string]: boolean,
}

Fetches the categories, with a boolean value to indicate whether the user has given consent for that option.

o.get([ 'default' ]).getOrElse() // -> { default: true }

The categories list is optional, if you call get with no arguments, it will return all categories:

o.get().getOrElse() // -> { default: true, analytics: false }

set

(
  categories: {
    [id: string]: boolean,
  },
) => string;

Sets the consent flag for the given categories. Any categories not passed into this method will be preserved.

o.set({
  default: false,
}).getOrElse()

getByOrder

(
  categories: Array<string>,
) => {
  [category: string]: {
    id: string,
    value: boolean,
  },
}

If you don't know the ids of your categories, but you know the order they will be in, you can use this method to extract the ids and flags based purely on their order.

const o = consent();

o.getByOrder([ 'default', 'analytics' ]).getOrElse() // { default: { id: '0', value: false }, analytics: { id: 'c', value: true }}

Identity Consent

(
  mappings: {
    [id: string]: string,
  },
  consent: string,
) => Object
import { IdentityConsent } from '@team-griffin/uteals';

This variation is very similar to the standard consent except that you can provide the consent string at instantiation time.

To create an instance, call it with a mapping of category ids to aliases:

const o = new IdentityConsent({
  0: 'default',
  c11: 'analytics',
}, '0:1|c:0');

This means you can reference the preferences by their aliases rather than their ids.

get

(
  categories?: Array<string>,
) => {
  [id: string]: boolean,
}

Fetches the categories, with a boolean value to indicate whether the user has given consent for that option.

o.get([ 'default' ]) // -> { default: true }

The categories list is optional, if you call get with no arguments, it will return all categories:

o.get() // -> { default: true, analytics: false }

set

(
  categories: {
    [id: string]: boolean,
  },
) => string;

Sets the consent flag for the given categories. Any categories not passed into this method will be preserved.

o.set({
  default: false,
}).getOrElse()

getByOrder

(
  categories: Array<string>,
) => {
  [category: string]: {
    id: string,
    value: boolean,
  },
}

If you don't know the ids of your categories, but you know the order they will be in, you can use this method to extract the ids and flags based purely on their order.

const o = consent();

o.getByOrder([ 'default', 'analytics' ]) // { default: { id: '0', value: false }, analytics: { id: 'c', value: true }}