protons-runtime
Advanced tools
Shared code to make your bundle smaller when running protons in your app
Shared code to make your bundle smaller when running protons in your app
This module contains serialization/deserialization code used when encoding/decoding protobufs.
It should be declared as a dependency of your project:
npm i protons-runtime
$ npm i protons-runtime
Contains shared code to reduce code duplication between modules transpiled by protons.
Licensed under either of
Contributions welcome! Please check out the issues.
Also see our contributing document for more information on how we work, and about contributing in general.
Please be aware that all interactions related to this repo are subject to the IPFS Code of Conduct.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
FAQs
Shared code to make your bundle smaller when running protons in your app
The npm package protons-runtime receives a total of 32,642 weekly downloads. As such, protons-runtime popularity was classified as popular.
We found that protons-runtime demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.