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

@openoscom/imart-toolkit

v2.0.0-stable

Published

IMart frontend packages

Downloads

607

Readme

⚒️ IMart frontend packages

To pull and install package via the NPM CLI, you'll need:

A personal access token (you can create a personal acess token here) The personal access token with the correct scopes, repo and read:packages to be granted access to the GitHub Package Registry.

Authentication via npm login, using your Github email for the username and the personal access token as your password:

Installation

npm install @openos-labs/imart-toolkit

Usage

import { Contractor } from "@openos-labs/imart-toolkit/contracts";
const configuration = {
    addresses: {
      creation: imartToken.address,
      curation: curation.address,
      market: "",
    },
    provider: ethers.getDefaultProvider(),
  };
const contractor = Contractor(Evm, config);
await contractor.createGallery(
    {
      collection: spaceContract,
      tokenIdentifier: spaceTokenId.toString(),
      spaceType: "art",
      name: "Hollywood",
      metadataUri:
        "https://mixverse-spaces.s3.amazonaws.com/mixverse-gallery-1.json",
    },                                                                          // payload
    curator                                                                     // signer
  );

Development

Local test

// start hardhat node
yarn workspace @imart/contracts hardhat node

// run tests
yarn workspace @imart/contracts hardhat test

Publish

// generate github access token
// https://github.com/settings/tokens

// password == github access token
npm login --registry=https://npm.pkg.github.com

// upgrade package version before publish
export GITHUB_ACCESS_TOKEN=xxxxxxx
npm publish