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

@r-group/shell-contracts

v1.1.0

Published

Smart contracts for `shell`.

Downloads

4

Readme

shell-contracts

Smart contracts for shell.

Development

Install dependencies:

yarn

Compile all artifacts and generate typechain types:

yarn build

Run unit tests:

yarn test

Run unit tests showing gas usage by function and deploy costs:

REPORT_GAS=1 yarn test

Run unit tests and report coverage:

yarn test:coverage

If you have shell-subgraph and shell-frontend repos as sibling directories to this one, you can copy built ABIs to the appropriate location in those repos:

./copy-pasta-abis.sh

Deployment

Copy .env.example to .env and override the default values before deploying.

Deploy a contract (eg, ShellFactory):

yarn deploy --network rinkeby --contract ShellFactory

This will output the deployed contract address in the console and update the ./tasks/deployments.json file.

NOTE: The contract will automatically be verified on etherscan

Deploying Implementations

To deploy a token model / implementation and register it with the corresponding shell factory:

yarn deploy:implementation --network rinkeby --contract ShellERC721 --implementation erc721-v1

This will deploy and verify the contract, as well as call the register method on the factory. This won't work if factory ownership has been transferred to a non-dev wallet.

To register an existing deployment:

yarn register --network rinkeby --address 0x123..123 --implementation erc721-prototype

Verification

The deploy task will automatically verify contracts generally.

This can occasionally fail. If it does, verify manually:

yarn verify --network rinkeby $CONTRACT_ADDRESS

Verification may fail if run too quickly after contract deployment.

If you are verifying for polygon or mumbai networks, set the POLYGON env var:

POLYGON=1 yarn verify --network polygon $CONTRACT_ADDRESS

If you are verifying for the arbitrum or arbitrum-rinkeby network, set the ARBITRUM env var:

ARBITRUM=1 yarn verify --network arbitrum $CONTRACT_ADDRESS

If you are verifying for the fantom network, set the FANTOM env var:

FANTOM=1 yarn verify --network fantom $CONTRACT_ADDRESS

Publishing

This repo is published to npm so it can be installed as a dependency to downstream smart contract repos (such as engines).

Create a new version:

npm version 1.1.0

Make sure build artifacts are recent:

yarn clean && yarn build

Publish:

npm publish