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

nodata

v0.0.2

Published

node odata client

Downloads

3

Readme

node-odata

An odata client module for Node Build Status

Installation

npm install nodata

Usage

This module generates endpoints based from odata service urls

var odata = require('nodata');

odata.createServices([{name: 'name', url: 'url1', {name: 'name2', url: 'url2']);

This will return a promise containing the potential generated endpoints for each service queried

odata([{name: 'serviceOne', url: 'url1'}])
  .then(function (services) {

    // use services
  });

If passed a 'authUrl', it will generate a login endpoint which can be used to obtain a cookie for subsequent requests.

services.login('username', 'password', function (error, cookie) {

  // I Have a cookie now
});

Each endpoint has a get function

var Oquery = require('nodata').Oquery;

services.someService.someEndpoint
  .get(new Oquery(1).expand('someNavProp'), cookie, function (error, data) {

    // check for errors and do something with data
  });

// Or with a composite key
services.someService.someEndpoint
  .get(new Oquery({key1: 1, key2: 2}), cookie, funciton (error, data) {

    // do stuff
  });

An insert function

services.someService.someEndpoint
  .insert(someJsonItem, cookie, function (err, data) {

    // check for errors and celebrate success
  });

An update function

services.someService.someEndpoint
  .update(1, someJsonItem, cookie, function (err, data) {

    // check for errors and celebrate success
  });

And a delete function

services.someService.someEndpoint
  .delete(1, cookie, function (err, data) {

    // check for errors and celebrate success
  });;

Query Syntax

An Oquery is built from an optional id followed by orderby, filter, expand, skip, top, inlinecount, and select

var Oqeury = require('nodata').Oquery;

var query = new Oquery(1).orderby('id')
  .filter('state eq 2').expand('someNavProp')
  .skip(5).top(10).select('someNavProp').inlinecount();

endpoint.get(query, cookie, function () {});