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

enframe

v0.0.11

Published

Enframe facilitates rapid application creation and continued maintainance.

Downloads

3

Readme

Enframe

Remaining Features to Complete

  1. Ensure idempotency

  2. lint

  3. palantir/tslint-react

  4. Service worker

  5. deploy to app stores?

  6. Investigate post-heroku deploy steps. I.e., automated custom domain setup via heroku CLI? Automated domain registration (far-fetched)?

  7. Programmatic index.html generation?

  8. introduce psql

  9. introduce Redux

  10. introduce integration tests

Before enframing

  • Ensure you have stored your Gitlab SSH key on your dev machine.
  • Ensure you have the Heroku CLI on your dev machine.

Steps

  1. Create a new app.

    mkdir new-app
    cd new-app
  2. Add an enframe.json file.

    {
      "appName": "new-app",
      "gitlabRemoteSSH": "[email protected]:username/new-app.git"
    }
  3. Add and execute enframe.

    yarn add --dev enframe
    yarn enframe

Notes

  • A $HEROKU_API_KEY needs to be stored in your Gitlab project in order for your gitlab-ci.yml file to deploy to Heroku successfully. It is in Heroku User Settings. Copy it into Gitlab under Settings -> CICD -> Variables. Until you do this, the deploy steps will fail.
  • The Gitlab project does not need to exist before you set it as an upstream. Gitlab can create the project for you on first push.