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

n-recommendations-client

v2.0.0

Published

Client to get data from the recommendations API

Downloads

7

Readme

n-recommendations-client

This client provides client-side and server-side interfaces for calling the Recommendations API.

If you are putting recommendations onto a highly-cached page, you should not use the server-side version.

Within the app calling this library, you will need to provide a RECOMMENDATIONS_API_KEY environmental variable. Contact the myFT team to get a key.

Install

$ npm install --save n-recommendations-client

Usage

Using the Next-API

If you want recommendations with their data expanded beyond content ID and title, you should use the Next API. For this call, use the user ID instead of the session token. Next API will check the session token matches the user ID.

tbc

Server-side Implementation

const recommendationsClient = require('n-recommendations-client');

recommedationsClient.behavioural(secureSessionToken, uuid, options)
	.then(results)
	.catch(errHandler)

Client-side Implementation

First set up a route in your application to act as a proxy. We do this so that we don't expose keys in our client-side XMLHttpRequest calls.

// in app.js or similar
const recommendationsClient = require('n-recommendations-client');

// :type is important
app.request('/your/proxy/:type/:uuid', recommendationsClient.proxy);

Then set up your call like so:

fetch('/your/proxy/behavioural/someuuid', {
	headers:{
		'ft-s-session': 'user-secure-session-token'
	}
})
	.then(fetchres.json)
	.then(result) //articles data is in result.recommendations.articles
	.catch(err);

You don't have to use fetchres, but you will need something to read the body data into JSON.

You can then hit your endpoint e.g. /your/proxy/behavioural/someuuid?count=5. The request should have either a header called ft-s-session or a cookie called FTSession_s containing the user's secure session token.

Options

Options all have defaults but can be

  • count: n (how many articles to get back)
  • recency: n (how many days back to cover)
  • sort: [rel|pop|date] (relevancy, popularity or date sort)
  • contentid: somecontentid (option to add in article ID as an extra filter for results)