ethpm-spec - npm Package Compare versions
Comparing version 1.0.0 to 1.0.1
| { | ||
| "name": "ethpm-spec", | ||
| "version": "1.0.0", | ||
| "version": "1.0.1", | ||
| "description": "Ethereum Package Manager Specifications", | ||
@@ -5,0 +5,0 @@ "main": "index.js", |
@@ -30,5 +30,11 @@ # EVM Smart Contract Packaging Specification | ||
| An URI in the format `ipfs://<multihash>[/<path>]` | ||
| An URI which matches the regular expression `^ipfs:/?/?.*$` | ||
| This allows for either one of the following ipfs supported formats: | ||
| - `ipfs://Qm...` | ||
| - `ipfs:/Qm...` | ||
| - `ipfs:Qm...` | ||
| ### Chain Definition via BIP122 URI | ||
@@ -56,3 +62,3 @@ | ||
| The following use cases were considered during the creation of this | ||
| specification. | ||
| specification. | ||
@@ -212,3 +218,3 @@ 1. [`owned`](#stand-alone-package-with-inheritable-contract): A package which contains contracts which are not meant to be used by themselves but rather as base contracts to provide functionality to other contracts through inheritance. | ||
| This package will contain two solidity source files. | ||
| This package will contain two solidity source files. | ||
@@ -275,3 +281,3 @@ * [`./contracts/AbstractToken.sol`](./examples/standard-token/contracts/AbstractToken.sol) | ||
| contract that is ready to be deployed, lets explore a package that also | ||
| includes a deployed instance of that contract. | ||
| includes a deployed instance of that contract. | ||
@@ -403,3 +409,3 @@ Solidity Libraries are an | ||
| We are going to use the `standard-token` package we created earlier and include | ||
| a deployed version of the `StandardToken` contract. | ||
| a deployed version of the `StandardToken` contract. | ||
@@ -549,3 +555,3 @@ Our package will be called `piper-coin` and will not contain any source files | ||
| deployed *contract instances* from the local package we'll explore an example | ||
| with link dependencies that rely on contracts from the package dependencies. | ||
| with link dependencies that rely on contracts from the package dependencies. | ||
@@ -552,0 +558,0 @@ In this example we'll be writing the `wallet` package which includes a wallet |
@@ -192,9 +192,9 @@ # Release Lockfile Specification | ||
| The `package_meta` field defines a location for metadata about the package | ||
| The `meta` field defines a location for metadata about the package | ||
| which is not integral in nature for package installation, but may be important | ||
| or convenient to have on-hand for other reasons. This field **should** be | ||
| cinluded in all release lockfiles. | ||
| included in all release lockfiles. | ||
| * Required: No | ||
| * Key: `package_meta` | ||
| * Key: `meta` | ||
| * Type: Object (String: *Package Meta* object) | ||
@@ -574,3 +574,6 @@ | ||
| The `version` field defines the version of the compiler. | ||
| The `version` field defines the version of the compiler. The field **should** be OS | ||
| agnostic (OS not included in the string) and take the form of either the stable version | ||
| in semver format or if built on a nightly should be denoted in the form of | ||
| `<semver>-<commit-hash>` ex: `0.4.8-commit.60cc1668`. | ||
@@ -577,0 +580,0 @@ * Required: Yes |
@@ -10,3 +10,2 @@ { | ||
| "version": "1", | ||
| "additionalProperties": false, | ||
| "properties": { | ||
@@ -186,3 +185,3 @@ "lockfile_version": { | ||
| "LinkValue": { | ||
| "title": "A value for an individual link reference in a contract's bytecode", | ||
| "title": "A value for an individual link reference in a contract's bytecode", | ||
| "type": "object", | ||
@@ -189,0 +188,0 @@ "required": [ |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by0.34%
90840
- Number of lines in readme file
- increased by0.91%
664
Worsened metrics
- Lines of code
- decreased by-0.13%
763