Package Exports

@celo/utils
@celo/utils/lib
@celo/utils/lib/address
@celo/utils/lib/address.js
@celo/utils/lib/async
@celo/utils/lib/async.js
@celo/utils/lib/collections
@celo/utils/lib/collections.js
@celo/utils/lib/ecdh
@celo/utils/lib/ecdh.js
@celo/utils/lib/ecies
@celo/utils/lib/ecies.js
@celo/utils/lib/fixidity
@celo/utils/lib/fixidity.js
@celo/utils/lib/future
@celo/utils/lib/future.js
@celo/utils/lib/index.js
@celo/utils/lib/io
@celo/utils/lib/io.js
@celo/utils/lib/istanbul
@celo/utils/lib/istanbul.js
@celo/utils/lib/levenshtein
@celo/utils/lib/levenshtein.js
@celo/utils/lib/parsing
@celo/utils/lib/parsing.js
@celo/utils/lib/sign-typed-data-utils
@celo/utils/lib/sign-typed-data-utils.js
@celo/utils/lib/signatureUtils
@celo/utils/lib/signatureUtils.js
@celo/utils/lib/solidity
@celo/utils/lib/solidity.js
@celo/utils/lib/string
@celo/utils/lib/string.js
@celo/utils/lib/typed-data-constructors
@celo/utils/lib/typed-data-constructors.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@celo/utils) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

@celo/utils

Various utility functions used across Celo SDKs.

How we work

We are a GitHub-first team, which means we have a strong preference for communicating via GitHub. Please use GitHub to:

🐞 File a bug report

💬 Ask a question

✨ Suggest a feature

🧑‍💻 Contribute!

🚔 Report a security vulnerability

[!TIP]

Please avoid messaging us via Slack, Telegram, or email. We are more likely to respond to you on GitHub than if you message us anywhere else. We actively monitor GitHub, and will get back to you shortly 🌟