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

ts-national-rail-wrapper

v1.0.7

Published

✨Typescript promise based wrapper for National Rail SOAP API.

Downloads

177

Readme

TS National Rail Wrapper

npm version npm downloads types included publish size

✨Typescript promise based wrapper for National Rail SOAP API.

Based on API docs found here

Prerequisite

  • Yarn 🧶

Usage

  • Apply for an API_KEY to be used with the API from National Rail
  • Require package using Yarn
  • Use it 🚀

Yarn:

yarn add ts-national-rail-wrapper

Example Usage:

const { NationalRailWrapper } = require("ts-national-rail-wrapper")

const apiKey = "****-****-****-****"
const nationalRail = new NationalRailWrapper(apiKey)

...

const results = await nationalRail.getDepartures({ fromStation: "LDS", count: 5 })

Methods

getDepartures - Retrieve Departures for Station

const options = { fromStation: "LDS", count: 5 }
const results = await nationalRail.getDepartures(options)

getArrivals - Retrieve Arrivals for Station

const options = { fromStation: "LDS", count: 5 }
const results = await nationalRail.getArrivals(options)

getAll - Retrieve Both Departures and Arrivals for Station

const options = { fromStation: "LDS", count: 10 }
const results = await nationalRail.getAll(options)

getServiceDetails - Retrieve Details about a certain Rail Service

const options = { serviceId: "RAIL_SERVICE_001" }
const results = await nationalRail.getServiceDetails(options)

Tests

Currently tests will use the actual National Rail API to make calls and test data returned, this works but can cause the tests to be flaky due to the ever changing nature of data.

In an ideal situation these API results should be mocked to have the same behaviour all the time, this is a possible improvement I could make.

Tests make use of the dotenv lib which will look for an apiKey set in the .env file, please make sure that exists before running test

Once thats all set up run yarn test to start test suite