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

@financial-times/sourcepoint-cmp

v1.3.0

Published

A package to help you add SourcePoint's CMP to your application.

Downloads

3

Readme

SourcePoint CMP

A package to help you add SourcePoint's CMP to your application.

Installation

Install the package from npm:

npm install @financial-times/sourcepoint-cmp

You then have two options for adding the CMP to your application:

  1. Server-side rendering using JSX
  2. Client-side invocation

Both patterns have reference implementations that you can look at in src/examples/sourcepoint-cmp.

To see them in action run

npm run dev -w src/examples/sourcepoint-cmp

and visit http://localhost:5137 to see each in action: interact with the banner and watch the console output to see your consent choices logged there.

Usage

Rendering with JSX

Import the CMP components and render them in your application's JSX:

import React from "react";
import { CmpScripts } from "@financial-times/sourcepoint-cmp/ssr";

// Import your domain's CMP configuration from the `properties` module.
import { ft } from "@financial-times/sourcepoint-cmp/properties";

export const App = () => (
  <html>
    <head>
      <CmpScripts config={ft}></CmpScripts>;
    </head>
    <body />
  </html>
);

Dynamic insertion

An alternative client-side mechanism is available.

The getCmpScripts method returns a DocumentFragment containing block of scripts that you can to your page's <head> element.

import { getCmpScripts } from "@financial-times/sourcepoint-cmp/client";
import { ft } from "@financial-times/sourcepoint-cmp/properties";

const cmpScripts = getCmpScripts(ft);
document.head.appendChild(cmpScripts);

Debugging

You can verify that the CMP is correctly configured by adding an events map to your configuration: the debug module used in the examples provides a sample implementation:

import { getCmpScripts } from "@financial-times/sourcepoint-cmp/client";
import { ft } from "@financial-times/sourcepoint-cmp/properties";
import { events } from "@financial-times/sourcepoint-cmp/debug";

// Merge the events map into the domain configuration
const config = { ...ft, events };
document.head.appendChild(getCmpScripts(config));

If everything's working then when running the demo app you'll see the CMP log its lifecycle events to the console, even if its UI isn't displayed.

This can easily happen when you've made a previous consent choice and the CMP is now picking it up from local storage. We recommend running in an incognito window during development.