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 🙏

© 2026 – Pkg Stats / Ryan Hefner

fiftyone.pipeline.cloudrequestengine

v4.5.41

Published

Cloud request engine for the 51Degrees Pipeline API

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

51d51deugenedorfmaneugenedorfmanroman.sroman.s

Keywords

51degreespipelinedataservicecloud

Readme

51Degrees 51Degrees Pipeline Cloud Request Engine

Developer Documentation

Introduction

The 51Degrees Pipeline API is a generic web request intelligence and data processing solution with the ability to add a range of 51Degrees and/or custom plug ins (Engines).

This package - fiftyone.pipeline.cloudrequestengine

This package uses the engines class created by the fiftyone.pipeline.engines. It makes available:

  • A Cloud Request Engine which calls the 51Degrees cloud service to fetch properties and metadata about them based on a provided resource key. A resource key with the free properties used by the tests can be created here.
  • A Cloud Engine template which reads data from the Cloud Request Engine.

It is used by the cloud versions of the following 51Degrees engines:

Installation

npm install fiftyone.pipeline.cloudrequestengine

Tests

To run tests you will need to install the jest library.

npm install jest --global

Then, navigate to the module directory and execute:

npm test

The integration tests read the resource key from the aligned _51DEGREES_RESOURCE_KEY environment variable first, then the legacy RESOURCE_KEY variable.

Pointing the engine at another host

The engine calls https://cloud.51degrees.com/api/v4/ unless the baseURL option is given or the FOD_CLOUD_API_URL environment variable is set, in which case that value is the API base including the /api/v4/ segment (a missing trailing slash is added). Every engine and example built on this package, in this repository and in the device detection and geolocation packages, inherits that choice, so setting the variable once points all of them at the same place.

A host other than cloud.51degrees.com would be used to (a) use an on premise web server, or (b) use a privately hosted version of the 51Degrees cloud for performance reasons. This is the private hosting option of the 51Degrees cloud service. Both run the same service, so an example works unchanged.

FOD_CLOUD_API_URL=https://cloud.example.com/api/v4/ _51DEGREES_RESOURCE_KEY=<resource key> node yourExample.js