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

contentful-content-management

v0.2.0

Published

Wrapper for Contentful JS SDK with straightforward connections, queuing/rate limiting, and progress bars

Downloads

5

Readme

Contentful Content Management

This is a wrapper for the Contentful's Content Management API Node.js library.

It provides syntactic sugar for getting connected to a Space quickly, and adds queuing/retry functionality for when you need to send large numbers of API requests and don't want to lose data to Contentful's rate limiting.

Getting started

Install as normal:

$ npm install --save contentful-content-management

Use as follows:


var ContentfulManagement = require('contentful-content-management');

var contentful = new ContentfulManagement();

// Set up some data to insert
var items = [
    {title: 'Page 1', body: 'Content for Page 1'},
    {title: 'Page 2', body: 'Lorem ipsum.'},
    {title: 'Page 3', body: 'Dolor sit amet.'},
];

// use the .formatItems() method to add localisation to the data
items = contentful.formatItems(items);

// the .space() method quickly creates a Contentful Space
contentful.space(function(space){

    // standard API calls work as normal
    space.getEntries()
    .then(function(entries){
        console.log(entries);
    })

    // the Space now has a .queue() method for queueing calls
    space.queue('createEntry', 'myContentTypeId', items)
    .then(function(entries){
        // returns an array of whatever you would expect the function to return, in this case the newly-created Entries
        console.log(entries);
        // the .itemQueue() method allows you to queue method calls on an array of Entries or an EntryCollection:
        contentful.itemQueue('publish', entries)
    });

})

API

You should call the library function as you require it, to avoid having to pass options with subsequent calls.

.space(fn)

This is just a wrapper for contentful.createClient then contentful.getSpace, with an additional queue method injected into the Space object (see below).

The method returns a Promise that resolves the connected Space, which is passed to the callback function.

contentful.space(function(space){
    space.getEntries()
    .then(function(entries){
        console.log(entries);
    });
})

Space.queue(method, [...args], items)

The library injects a .queue() function into the resolved Space. Returns a Promise that resolves to an Array of whatever the method you're calling is supposed to return.

Parameters:

  • method [String]: the Contentful API method you wish to call on items.
  • args [Mixed]: Additional arguments to pass to the API method
  • items [Array]: an Array of data you wish to use with the API.
contentful.space(function(space){
    // note that the method is called on the Space, not on the Contentful library directly
    space.queue('createEntries', 'contentTypeID', data)
    .then(function(entries){
        console.log(entries);
    });
});

See the Contentful JS SDK docs for a list of methods you can call on a Space.

.itemQueue(method, items)

Allows you to queue method calls on a collection of Entries or Assets.

Parameters

  • method [String]: The method you wish to call on each Item
  • items [Array/Collection]: The Items that you wish to call method on, either as an Array of Entries/Assets (e.g. returned from Space.queue() or a Contentful EntryCollection (e.g. returned from Space.getEntries()).

contentful.space(function(space){
    space.getEntries({status:'draft'})
    .then(function(entries){
        contentful.itemQueue('publish', entries);
    });
});

See the Contenful JS SDK docs for a list of methods you can call on Entries or Assets.

.formatItems(items, locale)

Convenience method for formatting entry data, and adding locale information.

Contentful expects entry data to be stored in the fields key, and to contain localisation information:

    {
        fields: {
            title: {
                'en-US': 'My Title'
            },
            body: {
                'en-US': 'My body text...'
            }
        }
    }

This is annoying if you're mostly working with data in a simpler format:

    {
        title: 'My title',
        body:  'My body text...'
    }

Enter .formatItems()...

    
    var data = [{
        title: 'Test',
        body:  'Test content...'
    },
    {
        title: 'Test 2',
        body:  'Test content 2...'
    }];
    var data = contentful.formatItems(data);
    /*
    data.should.deep.equal(
        [
            {
                fields: {
                    title: {
                        'en-US': 'Test',
                    },
                    body: {
                        'en-US': 'Test content...'
                    }
                }
            },
            {
                fields: {
                    title: {
                        'en-US': 'Test 2',
                    },
                    body: {
                        'en-US': 'Test content 2...'
                    }
                }
            },
        ]
    );
    */

Parameters:

  • items [Array/Object]: Array containing items to format. Each item should be a hash of the fields and field values you wish to submit to Contentful. Can also be a single Entry object, in which case the function also returns a single Entry.

Uses the locale option specified in the constructor, which defaults to en-US.

.client

Reference to the underlying Contentful client created by Contentful.createClient()

Options

You can specify options in the constructor:

var contentful = new ContentfulManagement({
    progress: false
});

Auto-Loading Environment Vars

The library uses dotenv to add environment variables. You should never store API tokens in source code, so it's better to use a .env file in your project that isn't checked into git.

.env should look like the following:

CONTENTFUL_MANAGEMENT_ACCESS_TOKEN=<your contentful CMA key>
CONTENTFUL_SPACE=<your contentful space>

You can get your personal Contentful Content Management API key by opening the Space, clicking on the 'APIs' button in the toolbar, clicking on the 'Content Management Keys' tab, then following the link to the documentation. You should be able to copy your key from there.

Option reference

contentful_space

String: The ID of your Contentful space. If should probably specify this as an environment variable instead. Defaults to process.env.CONTENTFUL_SPACE

contentful_management_access_token

String: Your Contentful Content Management API access token. If should probably specify this as an environment variable instead. Defaults to process.env.CONTENTFUL_MANAGEMENT_ACCESS_TOKEN

locale

String: The locale that you wish to use in calls to .formatItems(). Defaults to en-USnpm.

progress

Boolean: Display a progress bar when using queues.

queue_options

Object: Passed directly to the bluebird-queue library. If nothing is specified, you'll get promise-queue's default behaviour.

retry_options

Object: Passed directly to the promise-retry library. If nothing is specified, you'll get promise-retry's default behaviour.

Default options

{
    locale: 'en-US',
    contentful_space: process.env.CONTENTFUL_SPACE,
    contentful_management_access_token: process.env.CONTENTFUL_MANAGEMENT_ACCESS_TOKEN,
    progress: true,
    queue_options: {
        concurrency: 15
    },
    retry_options: {}
}

Testing

$ npm run test

Before you can run tests, you'll need to create a Contentful space to test with, and add a .env file to the project root (see above).

The test data is designed to work with Contentful's demo 'Blog' space. Click 'Add a new Space' in the Spaces menu, choose the 'Use an example space' radio button, click the 'Blog' tab, then click 'Create Space'.