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

sbahn-berlin-tweets

v1.2.1

Published

Fetch & parse @SBahnBerlin tweets about the operating status of S-Bahn Berlin.

Downloads

11

Readme

sbahn-berlin-tweets

Fetch & parse @SBahnBerlin tweets on the operating status of S-Bahn Berlin. Caveats:

  • It guesses lines and stations just by their name. This is brittle.
  • It relies on specific phrases & keywords commonly used by the SBahnBerlin twitter account.

npm version build status ISC-licensed minimum Node.js version chat with me on Gitter support me on Patreon

Installation

npm install sbahn-berlin-tweets

Usage

fetching & parsing tweets

const fetchAndParseTweets = require('sbahn-berlin-tweets')

const [tweet] = await fetchAndParseTweets(1, {
	formatLine: l => l.id,
	formatStation: s => s.id
})
console.log(tweet)
{
	id: '1169225032700239872',
	cause: 'medical-emergency',
	effect: 'disruptions',
	affected: ['S3', 'S5', 'S7', 'S9'],
	runsOnlyBetween: null,
	stations: ['900000024204'], // Savignyplatz
	useLines: []
}

parsing tweets

const parse = require('sbahn-berlin-tweets/parse')

console.log(parse({
	id: '1169246704291524608',
	text: [
		{type: 'hashtag', content: 'S7'},
		{type: 'plain', content: ': Wegen einer Weichenstörung in '},
		{type: 'hashtag', content: 'Olympiastadion'},
		{type: 'plain', content: ' verkehrt die S7 nur zwischen '},
		{type: 'hashtag', content: 'Ahrensfelde'},
		{type: 'plain', content: ' <> '},
		{type: 'hashtag', content: 'Westkreuz'},
		{type: 'plain', content: '. Der 10-Minutentakt kann nur zwischen Ahrensfelde <> '},
		{type: 'hashtag', content: 'Charlottenburg'},
		{type: 'plain', content: ' angeboten werden. Von/nach Olympiastadion/Spandau nutzen Sie bitte die Züge der '},
		{type: 'hashtag', content: 'S3'},
		{type: 'plain', content: ' und '},
		{type: 'hashtag', content: 'S9'},
		{type: 'plain', content: '.'}
	]
}))
{
	cause: 'switch-failure',
	effect: 'skipped-stops',
	affected: [
		// from the `vbb-lines` npm package
		{id: '10162_109', name: 'S7'}
	],
	stations: [
		// from the `vbb-stations` npm package
		{id: '900000025321', name: 'S Olympiastadion'}
	],
	useLines: [
		// from the `vbb-lines` npm package
		{id: '10148_109', name: 'S3'},
		{id: '10170_109', name: 'S9'}
	],
	runsOnlyBetween: null
}

Related

Contributing

If you have a question or need support using sbahn-berlin-tweets, please double-check your code and setup first. If you think you have found a bug or want to propose a feature, refer to the issues page.