@libp2p/utils 4.0.5-d5ef1c91 → 4.0.6-051154dd

package/README.md

@@ -1,5 +1,3 @@
-# @libp2p/utils <!-- omit in toc -->
-
 [![libp2p.io](https://img.shields.io/badge/project-libp2p-yellow.svg?style=flat-square)](http://libp2p.io/)
 [![Discuss](https://img.shields.io/discourse/https/discuss.libp2p.io/posts.svg?style=flat-square)](https://discuss.libp2p.io)
 [![codecov](https://img.shields.io/codecov/c/github/libp2p/js-libp2p.svg?style=flat-square)](https://codecov.io/gh/libp2p/js-libp2p)
@@ -7,22 +5,13 @@
 
 > Package to aggregate shared logic and dependencies for the libp2p ecosystem
 
-## Table of contents <!-- omit in toc -->
-
-- [Install](#install)
-  - [Browser `<script>` tag](#browser-script-tag)
-- [Usage](#usage)
-- [API Docs](#api-docs)
-- [License](#license)
-- [Contribution](#contribution)
-
-## Install
+# Install
 
 ```console
 $ npm i @libp2p/utils
 ```
 
-### Browser `<script>` tag
+## Browser `<script>` tag
 
 Loading this module through a script tag will make it's exports available as `Libp2pUtils` in the global namespace.
 
@@ -30,36 +19,17 @@ Loading this module through a script tag will make it's exports available as `Li
 <script src="https://unpkg.com/@libp2p/utils/dist/index.min.js"></script>
 ```
 
-The libp2p ecosystem has lots of repos with it comes several problems like:
-
-- Domain logic dedupe - all modules shared a lot of logic like validation, streams handling, etc.
-- Dependencies management - it's really easy with so many repos for dependencies to go out of control, they become outdated, different repos use different modules to do the same thing (like merging defaults options), browser bundles ends up with multiple versions of the same package, bumping versions is cumbersome to do because we need to go through several repos, etc.
-
-These problems are the motivation for this package, having shared logic in this package avoids creating cyclic dependencies, centralizes common use modules/functions (exactly like aegir does for the tooling), semantic versioning for 3rd party dependencies is handled in one single place (a good example is going from streams 2 to 3) and maintainers should only care about having `libp2p-utils` updated.
-
-## Usage
-
-Each function should be imported directly.
-
-```js
-import ipAndPortToMultiaddr from '@libp2p/utils/ip-port-to-multiaddr'
-
-const ma = ipAndPortToMultiaddr('127.0.0.1', 9000)
-```
-
-You can check the [API docs](https://libp2p.github.io/js-libp2p-utils).
-
-## API Docs
+# API Docs
 
 - <https://libp2p.github.io/js-libp2p/modules/_libp2p_utils.html>
 
-## License
+# License
 
 Licensed under either of
 
 - Apache 2.0, ([LICENSE-APACHE](LICENSE-APACHE) / <http://www.apache.org/licenses/LICENSE-2.0>)
 - MIT ([LICENSE-MIT](LICENSE-MIT) / <http://opensource.org/licenses/MIT>)
 
-## Contribution
+# Contribution
 
 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.

package/dist/src/index.d.ts

@@ -1,2 +1,22 @@
+/**
+ * @packageDocumentation
+ *
+ * The libp2p ecosystem has lots of repos with it comes several problems like:
+ *
+ * - Domain logic dedupe - all modules shared a lot of logic like validation, streams handling, etc.
+ * - Dependencies management - it's really easy with so many repos for dependencies to go out of control, they become outdated, different repos use different modules to do the same thing (like merging defaults options), browser bundles ends up with multiple versions of the same package, bumping versions is cumbersome to do because we need to go through several repos, etc.
+ *
+ * These problems are the motivation for this package, having shared logic in this package avoids creating cyclic dependencies, centralizes common use modules/functions (exactly like aegir does for the tooling), semantic versioning for 3rd party dependencies is handled in one single place (a good example is going from streams 2 to 3) and maintainers should only care about having `libp2p-utils` updated.
+ *
+ * @example
+ *
+ * Each function should be imported directly.
+ *
+ * ```js
+ * import ipAndPortToMultiaddr from '@libp2p/utils/ip-port-to-multiaddr'
+ *
+ * const ma = ipAndPortToMultiaddr('127.0.0.1', 9000)
+ * ```
+ */
 export {};
 //# sourceMappingURL=index.d.ts.map

package/dist/src/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAA"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AAEH,OAAO,EAAE,CAAA"}

package/dist/src/index.js

@@ -1,2 +1,22 @@
+/**
+ * @packageDocumentation
+ *
+ * The libp2p ecosystem has lots of repos with it comes several problems like:
+ *
+ * - Domain logic dedupe - all modules shared a lot of logic like validation, streams handling, etc.
+ * - Dependencies management - it's really easy with so many repos for dependencies to go out of control, they become outdated, different repos use different modules to do the same thing (like merging defaults options), browser bundles ends up with multiple versions of the same package, bumping versions is cumbersome to do because we need to go through several repos, etc.
+ *
+ * These problems are the motivation for this package, having shared logic in this package avoids creating cyclic dependencies, centralizes common use modules/functions (exactly like aegir does for the tooling), semantic versioning for 3rd party dependencies is handled in one single place (a good example is going from streams 2 to 3) and maintainers should only care about having `libp2p-utils` updated.
+ *
+ * @example
+ *
+ * Each function should be imported directly.
+ *
+ * ```js
+ * import ipAndPortToMultiaddr from '@libp2p/utils/ip-port-to-multiaddr'
+ *
+ * const ma = ipAndPortToMultiaddr('127.0.0.1', 9000)
+ * ```
+ */
 export {};
 //# sourceMappingURL=index.js.map

package/dist/src/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAA"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AAEH,OAAO,EAAE,CAAA"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@libp2p/utils",
-  "version": "4.0.5-d5ef1c91",
+  "version": "4.0.6-051154dd",
   "description": "Package to aggregate shared logic and dependencies for the libp2p ecosystem",
   "license": "Apache-2.0 OR MIT",
   "homepage": "https://github.com/libp2p/js-libp2p/tree/master/packages/utils#readme",
@@ -87,8 +87,8 @@
   },
   "dependencies": {
     "@chainsafe/is-ip": "^2.0.2",
-    "@libp2p/interface": "0.1.4-d5ef1c91",
-    "@libp2p/logger": "3.0.4-d5ef1c91",
+    "@libp2p/interface": "0.1.5-051154dd",
+    "@libp2p/logger": "3.0.5-051154dd",
     "@multiformats/multiaddr": "^12.1.5",
     "@multiformats/multiaddr-matcher": "^1.0.1",
     "is-loopback-addr": "^2.0.1",

package/src/index.ts

@@ -1 +1,22 @@
+/**
+ * @packageDocumentation
+ *
+ * The libp2p ecosystem has lots of repos with it comes several problems like:
+ *
+ * - Domain logic dedupe - all modules shared a lot of logic like validation, streams handling, etc.
+ * - Dependencies management - it's really easy with so many repos for dependencies to go out of control, they become outdated, different repos use different modules to do the same thing (like merging defaults options), browser bundles ends up with multiple versions of the same package, bumping versions is cumbersome to do because we need to go through several repos, etc.
+ *
+ * These problems are the motivation for this package, having shared logic in this package avoids creating cyclic dependencies, centralizes common use modules/functions (exactly like aegir does for the tooling), semantic versioning for 3rd party dependencies is handled in one single place (a good example is going from streams 2 to 3) and maintainers should only care about having `libp2p-utils` updated.
+ *
+ * @example
+ *
+ * Each function should be imported directly.
+ *
+ * ```js
+ * import ipAndPortToMultiaddr from '@libp2p/utils/ip-port-to-multiaddr'
+ *
+ * const ma = ipAndPortToMultiaddr('127.0.0.1', 9000)
+ * ```
+ */
+
 export {}