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

tester-dt

v0.0.26-beta

Published

## Run Locally

Downloads

4

Readme

DAO Terminal

Run Locally

Clone the project

  git clone https://link-to-project

Install dependencies

  npm install

Create a .env file in the root directory

  touch .env

Environment Variables

To run this project, you will need to add the following environment variables to your .env file.

BASE_API_URL -> Contact team for current url.

ALCHEMY_ID -> ETH Mainnet Alchemy ID (free)

WALLCONNECT_PROJECT_ID -> WalletConnect Cloud Project ID (free)

Run the component locally

  npm run storybook

Local Deployment

  npm run build-lib
  npm pack

From there you can copy the path of the tgz file created and in a React app run

npm i `full-path-to-tarball.tgz`

Usage/Examples

If you are using Next.js you must import the package dynamically

import dynamic from "next/dynamic";
const DaoTerminal = dynamic(() => import("package-name").then(({ DaoTerminal }) => DaoTerminal), {
  ssr: false,
});

function App() {
  return (
    <div style={{ height: "80vh" }}>
      <DaoTerminal icon={"/qwan-logo.svg"} theme={"dark"} spaceId="ty-sir.eth" />
    </div>
  );
}

If using CRA or there is not SSR initially you can import it named

import { DaoTerminal } from "package-name";

function App() {
  return (
    <div style={{ height: "80vh" }}>
      <DaoTerminal icon={"/qwan-logo.svg"} theme={"dark"} spaceId="ty-sir.eth" />
    </div>
  );
}

DaoTerminal Required Props

| Name | Description | Type | | ------- | --------------------------------------------------- | ----------------- | | theme | Defines whether package is in dark or light mode. | "light" or "dark" | | icon | Logo seen in nav-bars. Use a path to a local image. | string | | spaceId | ENS name of snapshot space. | string |

Deployment

To deploy this project change the name and version values in package.json

  npm run build-lib
  git add .
  git commit -m "deployment"
  git push origin [branch-name]
  npm login
  npm publish

The package will then be live on npm and can be installed as shown in Usage/Examples