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

bullhornjs

v1.0.1

Published

Javascript library to conviently connect to the Bullhorn REST Api.

Downloads

30

Readme

BullhornJS

BullhornJS is a micro-library that makes it easy to use the Bullhorn REST APIs in JavaScript applications. BullhornJS allows you to easily login into Bullhorn using OAuth, and to manipulate your Bullhorn data using a simple API.

This is an early version. I appreciate any feedback, comments, and help if you think this library is useful.

Key Characteristics

  • No jQuery dependency
  • Plain JavaScript
  • Works transparently in the browser
  • Simple API to manipulate data (create, update, delete, upsert)
  • CommonJS format

Installation

NPM
npm install --save bullhornjs
Bower
bower install --save bullhornjs

Usage

  1. Initialize
var bullhorn = new Bullhorn({
    BhRestToken: '~BULLHORN_REST_TOKEN~',
    restUrl: '~BULLHORN_REST_URL~',
});
  1. Check if logged in:
bullhorn.isLoggedIn()
    .then(function(success){
        alert('Login success: ' + success);
    })
    .catch(function(error){
        alert('Error: ' + error.message);
    });
  1. Invoke a function: Search(), Query(), Entity(), Meta():
// Most functions are all fluent (ie. they return 'this')
var job = new Entity('entity/JobOrder').fields('title');
// the 'fields' function created a getter and setter for 'title'
job.title = 'My New Job';
job.save(); //returns a promise
  1. Use a convenience method: CandidateSearch(), JobOrder(), ContactMeta(), etc...:
// This command creates the convenience functions
Bullhorn.initDefaults();
// Now you can use them
var job = new Job().fields('title'); //works the same as above
job.get(123).then(function(response){
    console.log('Job Title is ', job.title);
});

Sample App

Check out the demo in the demo folder. To run the demo:

> git clone https://github.com/bullhorn/bullhornjs.git
> cd bullhornjs
> npm install
> npm run bundle
> npm install -g http-server
> http-server

open http://localhost:8080/demo in your browser

Server

Because the browser should not know your CLIENT_ID or CLIENT_SECRET your will need to handle the OAuth flow separately then have the server provide the BhRestToken and restUrl to the client.

Building

We build two versions of the source, 1) we create a bundle using rollup and 2) we compile all the sources separately with babel. All transpiled files are stored in the lib directory.

Rollup Bundle
This uses `rollup.config.js` to determine how to rollup the source. The bundle is located in `lib/bundle.js`. Configuration options are available [here](https://github.com/rollup/rollup/wiki/Command-Line-Interface). To create a new bundle:

npm run bundle
Babel Compile
This uses `.babelrc` to determine how to babel compiles the source. The files are transpiled to the `lib/` directory. Other configuration options are available [here](http://babeljs.io/docs/usage/babelrc/). To rebuild these:

npm run compile

Testing

We use Jest to run all of our unit test. To run the tests, in the working directory:

npm test