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

in-d-gestion

v0.4.1

Published

Library for ingestion of data from various vendor-specific sources into the Tidepool.org platform for diabetes data

Downloads

43

Readme

in-d-gestion

Library for ingestion of data from various vendor-specific sources into the Tidepool.org platform for diabetes data.

Looking at the code

Primary entry-point is lib/index.js.

Parsing and fetching code is broken down by vendor-specific objects on the thing returned from lib/index.js.

That is currently just carelink right now.

Easiest way to see how to use the parser is to look at test/carelink/testParser.js

Libraries to be aware of

The code leverages the Rx library pretty extensively for stream processing. There is a lot to this library. You can read about its philosophy at http://reactive-extensions.github.io/RxJS/ or its documentation at https://github.com/Reactive-Extensions/RxJS/tree/master/doc

We implement a few extensions to it in the lib/rx directory. These extensions are added to the rx.Observable.prototype, so the usage can appear the same as if we are using a native rx method. If you are trying to figure out what a method does and you are unfamiliar with it/you cannot find the docs for it on the main RxJS page, make sure to check the various extensions under lib/rx.

Command Line

Carelink

Fetch

You can fetch raw data from carelink with

./bin/carelink/mmcsv fetch -u <username> -p <password> -d <num_days> stdout

Parse

You can parse raw data fetched from carelink with

node bin/carelink/parse.js <csv_file_to_parse>

Diasend

Fetch

You can fetch data from diasend with

node bin/diasend/fetch.js -u <username> -p <password> -d <num_days> stdout

Parse

You can parse data fetched from diasend with

node bin/diasend/parse.js <xls_file_to_parse>

t:connect

Fetch

You can fetch data from t:connect with

node bin/tconnect/fetch.js -u <username> -p <password> -d <num_days> stdout

Parse

You can parse data fetched from t:connect with

node bin/tconnect/parse.js <xml_file_to_parse>