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

brok-monorepo

v0.0.1

Published

BRØK monorepo

Downloads

4

Readme

Development requirements

Getting started

Run make dev

To delete and clear all instances and data run make clean

Development

Choose either vs 👩‍💻 With tasks in VSCode (preferred) or 💻 With make

👩‍💻 With tasks in VSCode (preferred)

In VScode, run task dev ( ⇧⌘B workbench.action.tasks.runTask).

This will fire up all projects in watch mode so you can develop and experience imdiate results (hopefully across pacakges). The graph takes some time to start. Once it is started it will keep running in docker as long as your captable contracts terminal is running. terminal_tabs

💻 With make

Run make start, this will fire up all projects in watch mode so you can develop and experience imdiate results (hopefully across pacakges).

To run The Graph locally, open a new terminal and run make graph-start. This will fire up the docker image, which takes some time and deploys your current capTableRegistry. This requires make start to be running in the background, spesifically the hardhat node.

To see avaiable commands run make

make_commands

Deployment

  • SDK NPM
  • Captable NPM
  • Graph HostedService (connected to robertosnap account)
  • demo-server Heroku
  • demo-frontend [Heroku] (https://dashboard.heroku.com/teams/brok/apps)

So SDK and Captable are NPM packages that needs to be published for changes to propegate. Graph, demo-server and demo-frontend needs to be deployed to their enviroments to progegate changes.

build:captable
build                           - builds everything
build:sdk
deploy
deploy:destroy [env]            - Fulle destroys all deployed heroku apps for env
deploy:destroy:frontend
deploy:destroy:server
deploy:frontend [env]           - Deploys frontend to Heroku
deploy:graph [env]              - Deploys graph to Graph hosted services
deploy:logs:frontned
deploy:logs:server
deploy:server [env]             - Deploys server to Heroku
publish                         - publish packages with changes

Examples

pnpx task deploy dev will deploy graph, demo-server and demo-frontend to their hosting enviroments for enviroment dev

pnpx task deploy:server dev will deploy graph to its hosting enviroments for enviroment `dev

pnpx task publish will publish packages wich changes (interactive) to NPM.

To be able to deploy to Heroku, NPN og The Ghrap hosted service you must have access. Request from admin.

Ugly hacks

  • If the blockchain node (running inside the captable contracts terminal) is killed, the graph node will stop indexing. To fire it up again run make graph-stop then make graph-start.
  • Tasks that errors will continue to run. Should swap out task system for something that can handle errors in shell.