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

@dao-dao/types

v2.5.0-rc.2

Published

A collection of types used across packages.

Downloads

27

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

noahsasonoahsasoekezekezebakerebakercommon-gardencommon-garden

Keywords

Readme

@dao-dao/types

A collection of types used across packages.

Layout

| Location | Summary | | ---------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | | components | Types related to both stateless and stateful components and the respective packages. | | contracts | Smart contract types generated by @cosmwasm/ts-codegen. | | protobuf | Protobuf types generated by @cosmology/telescope. | | actions.ts | Types related to the @dao-dao/stateful/actions system. | | chain.ts | Types related to the chain. | | command.ts | Types related to the @dao-dao/stateful/command system. | | dao.ts | Types related to DAOs. | | helpers.ts | Helper types. | | inbox.ts | Types related to the inbox. | | nft.ts | Types related to NFTs. | | proposal-module-adapter.ts | Types related to the @dao-dao/stateful/proposal-module-adapter system. | | proposal.ts | Types related to proposals. | | state.ts | Types related to the @dao-dao/state package. | | units.ts | Types related to units. | | voting-module-adapter.ts | Types related to the @dao-dao/stateful/voting-module-adapter system. | | wallet.ts | Types related to wallets. |

Protobufs

This package contains Cosmos SDK protobuf definitions generated by Cosmology's Telescope.

To generate protobufs:

yarn protobuf

Sometimes definitions need to be manually fixed due to bugs and other discrepancies. There is a patch file that records these modifications in protobuf/patches.diff.

To update the patch file when new changes are made:

  1. Commit the changes so that the current branch is up-to-date with the desired changes.

  2. Run:

    yarn protobuf:patch:update

    This will regenerate the protobufs, undoing all patches. Then, it records the reverse diff between the committed changes and the regenerated protobufs (since we want to undo the current changes). Lastly, it reapplies the latest patches, and all changes should be made. If this works, only the patches.diff file should have changes.

  3. Update the previous commit with the new patches.

    git add protobuf/patches.diff
git commit --amend