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

@joincivil/core

v5.3.11

Published

The core library allowing for interfacing with the whole Civil ecosystem

Downloads

39

Readme

@joincivil/core

This library is the main-entry point for any developer wanting to work with the Civil ecosystem. It abstracts communication with the Ethereum blockchain as well as storing and loading articles from file storage servers.

license

Installation

yarn add @joincivil/core

Usage

import { Civil } from "@joincivil/core";

const MY_NEWSROOM_NAME = "Example Newsroom";
const MY_CONTENT_URI = "https://example.com/article/123";
const MY_CONTENT_HASH = "0x123abc";

(async () => {
  const civil = new Civil();

  // This will launch web3 wallet, e.g. MetaMask, to confirm transaction:
  const newsroomTx = await civil.newsroomDeployTrusted(MY_NEWSROOM_NAME);
  console.log("Waiting for newsroom creation tx", newsroomTx.txHash, "to complete...");

  const newsroom = await newsroomTx.awaitReceipt();
  console.log("Newsroom created with name", await newsroom.getName(), "at address", newsroom.address);

  const pendingTx = await newsroom.publishURIAndHash(MY_CONTENT_URI, MY_CONTENT_HASH);
  console.log("Waiting for publish tx", pendingTx.txHash, "to complete...");

  const contentId = await pendingTx.awaitReceipt();
  console.log("Content published with ID", contentId);
  console.log("Content:", await newsroom.loadArticle(contentId));
})().catch(console.error);

Check the documentation directory for more

Contributing

Civil's ecosystem is free and open-source, we're all part of it and you're encouraged to be a part of it with us. Best place to start hacking would be to use this package and build some application on top of the protocol.

If you're itching to dwelve deeper inside, help wanted and good first issue labels are good places to get started and learn the architecture.

Developing on ganache

This package has artifacts with singleton addresses of smart-contracts deployed on multiple Ethereum networks, one of which is our Ganache instance, that is set-up to be completely predictable. This means that whenever we run migrations on @joincivil/contracts in Ganache, the addresses are gonna be the same as the ones included in this packages.

Migrations are run automatically when yarn ganache in the root of monorepo is called.

Code generation

Civil.ts uses auto-generated code from Smart-Contract .json artifacts. Run yarn build or explicitly yarn generate to create them in the src/contracts/generated/ directory, afterwards develop as normal.

Adding new smart-contracts

  • [ ] Write new or change some smart-contracts in @joincivil/contracts
  • [ ] Add migration files and build.
  • [ ] Run yarn ganache in the root to make migrations
  • [ ] cp ../contracts/build/artifacts/MyContract.json ./src/artifacts/ (merge manually if deployed on Rinkeby or Mainnet)
  • [ ] Run yarn generate
  • [ ] Enjoy automatically generated code

The templates for code generation can be found src/templates/.