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

@blinkk/editor

v1.2.1

Published

Structured content editor with live previews.

Downloads

30

Readme

Live Editor

Experimental.

Editor for providing a rich UI for editing structured data with live previews.

See the typescript docs or example.

codecov

Developing

To start developing on the live editor UI run the following:

yarn install
yarn run serve

Then visit https://localhost:8888/ to iterate and improve the editor.

Live edit server

The live edit server is used to deploy the live editor UI using Cloud Run. It contains logic for connecting to different live edit connectors (such as github and local) and loads in the specialized fields (such as for Grow or Amagaki sites) as needed.

To develop locally run yarn run hosted and visit https://localhost:8080/ and iterate and improve. If you are developing on the editor UI, use the yarn run serve command from above instead.

Deployment

The live editor is built for production using a Docker image and Google Cloud Run.

Every commit to main builds the docker image with a :main tag and updates the cloud run image for beta.editor.dev. Every tag builds the docker image with a version tag (ex: v1.0.5) and the :latest tag then updates the cloud run image for editor.dev.

If there is an issue with the latest release for the prod you can roll back to an earlier version.

To switch the production deployment run make deploy-prod tag=<VERSION> where <VERSION> is the desired version to roll back to. For example: make deploy-prod tag=v1.0.5.

Service account

The builds use gcloud to build and deploy to a Cloud Run service.

The service account needs to be setup to be a member of the -compute@ service account to deploy from cloud build.:

gcloud iam service-accounts add-iam-policy-binding \
  --project=$PROJECT \
  --member="serviceAccount:$SERVICE_ACCOUNT_EMAIL" \
  --role="roles/iam.serviceAccountUser" \
  [email protected]

The service account also needs to have a set of permissions to be able to build and deploy to cloud run.