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 🙏

© 2025 – Pkg Stats / Ryan Hefner

isofire

v0.4.10

Published

### Link Isofire within your Project 1. Link Isofire to your Project ``` cd PATH_TO/isofire npm link

Downloads

79

Readme

Development

Link Isofire within your Project

  1. Link Isofire to your Project
cd PATH_TO/isofire
npm link

cd PATH_TO/project
npm link isofire
  1. Link your Project's rxjs to Isofire (the other way around)
cd node_modules/rxjs
npm link

cd PATH_TO/isofire
npm link rxjs

npm start

Start a new App

mkdir 11bookings && cd 11bookings
code .
git init
git remote add origin [email protected]:rechenberger/11bookings.git
ng new --style=scss --routing --skip-tests --directory client eleven-bookings
code .gitignore
# dependencies
**/node_modules

# IDEs and editors
/.idea
.project
.classpath
.c9/
*.launch
.settings/
*.sublime-workspace

# IDE - VSCode
.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json

# System Files
.DS_Store
Thumbs.db

# VS Code Share (?)
.vs/slnx.sqlite

# Firebase Tools Cache
.firebase
mv client/package.json package.json
mv client/package-lock.json package-lock.json
mv client/node_modules/ node_modules
mv client/angular.json angular.json
sed -i '' s/src/client\\/src/g angular.json
mv client/tslint.json tslint.json
sed -i '' s/..\\/tslint.json/..\\/..\\/tslint.json/g client/src/tslint.json
code tslint.json
# Customize the file as you like

# remove e2e form angular.json to do:
ng lint --fix
ng add @angular/material
npm i rxjs-compat
code client/src/rxjs-compat.ts
# ... add your imports
code client/src/main.ts
# add the following:
import './rxjs-compat'