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

@past3lle/skilltree-contracts

v0.1.8

Published

## Building the project

Downloads

1,715

Readme

Getting Started

Building the project

After any changes to the contract, run:

npm run build
# or
yarn build

Deploying

Use the hardhat deploy task callable via the package.json scripts: deploy, deploy:amoy which runs the tasks inside scripts/tasks/deploy.js by default.

Set env variables [here as example we set the goerli envs]:

export GOERLI_RPC_URL=https://goerli.infura.io/v3/f9d3e18111964a048ee83915a082ccf7
export PK=<your key>
export ETHERSCAN_API_KEY=<your key>

Example usage in the CLI:

yarn deploy \
--metadata-uri <URL_TO_COLLECTION_METADATA> \
--contract CollectionsManager \

Minting

Use the hardhat minting task callable via the package.json scripts: mint, mint:amoy which runs the tasks inside scripts/tasks/mintNewSkillForCollection.js by default.

Example usage in the CLI:

# Mint collection (e.g for goerli)
yarn mintCollection:goerli --name GENESIS --metadata-uri ipfs://Qm_SOME_IPFS_URL_AND_FORWARD_SLASH/

and it can be verified like this (as an example)

yarn verifySkills:goerli --metadata-uri <metadataUriConstructorArg> --name <collectionNameConstructorArg> --controller <controllerConstructorArg> --skills-addr <deployedSkillsContractAddress>

CLI Contract testing

Start the console: npx hardhat console or yarn run console

Paste this example line to get CollectionsManager, PSTLCollection_1 deployed, along with owner address cached in let owner

let Collections,collections,skills1,owner;ethers.getSigners().then(res => {owner = res[0].address});ethers.getContractFactory("CollectionsManager").then(res => {Collections = res;return Collections.deploy("ipfs://QmNzUQ9Txa5BLmd6ycngZ4M4pRgrY2AGVcLRt4PdTCKP4U/", owner)}).then(res => {collections = res;return ethers.getSigners(); }).then(res => {owner = res[0]});

This gives you access to cached vars:

  1. collections -> deployed CollectionsManager.sol
  2. owner -> (await ethers.getSigner())[0]