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

fpti

v0.3.2

Published

Standardized API for public transportation client libraries.

Downloads

197

Readme

fpti-js

FPTI-JS (Friendly Public Transport Interface) describes a standardized API for public transportation client libraries in JavaScript. See the spec and the list of JS modules.

Proposal, work in progress!

npm version license chat on gitter

API

The purpose of this specification is to outline a standardized API for the most common features of public transportation libraries, such as Journey planning, Departures/Arrivals or Station search. While most libraries certainly don't cover all of the following features, the basic principle for modules complying to fpti-js is that if a certain feature is available, it must be provided with the API described below. Some modules may also include additional functionalities that are not covered within this specification, as long as they don't use the reserved fpti-js method names.

Furthermore, even for additional features that are not covered within the following spec, fpti-js modules return data in the Friendly Public Transport Format v1.x.x wherever possible and use validate-fptf and fpti-tests in their tests.

Method overview

All methods expose an object method.features which contains all supported options and simple descriptions of those options as keys and values, respectively. See the method specifications for examples.

Method | Feature description | Returns -------|---------------------|-------- stations.all([opt]) / stops.all([opt]) / regions.all([opt]) | All stations/stops/regions of the network. | Readablestation / stop / region stations.search(query, [opt]) / stops.search(query, [opt]) / regions.search(query, [opt]) | Search stations/stops/regions by query. | Promise[station] / [stop] / [region] stations.nearby(location, [opt]) / stops.nearby(location, [opt]) / regions.nearby(location, [opt]) | Search stations/stops/regions by location. | Promise[station] / [stop] / [region] journeys(origin, destination, [opt]) | Journeys between stations (or optionally other locations) | Promise[journey] stopovers(station, [opt]) | Departures and arrivals at a given station (or optionally other location) | Promise[stopover]

Contributing

We are looking forward to discuss & extend this format further! If you have a question or want to propose changes, visit the issues page. Keep our contributing guidelines in mind. Note that, by participating in this project, you commit to the code of conduct.