embarklabs
/
embark
mirror of https://github.com/embarklabs/embark.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
embark/packages/plugins/nethermind/package.json

70 lines
1.7 KiB
JSON
Raw Normal View History

feat(@embark/nethermind): add Nethermind blockchain client plugin
2020-01-08 21:17:13 +00:00
{
"name": "embark-nethermind",
chore(prerelease): 5.3.0-nightly.3
2020-03-04 00:15:48 +00:00
"version": "5.3.0-nightly.3",
feat(@embark/nethermind): add Nethermind blockchain client plugin
2020-01-08 21:17:13 +00:00
"author": "Iuri Matias <iuri.matias@gmail.com>",
"contributors": [],
"description": "Nethermind blockchain client plugin for Embark",
chore: rename org references from embark-framework to embarklabs
2020-01-16 19:37:59 +00:00
"homepage": "https://github.com/embarklabs/embark/tree/master/packages/plugins/nethermind#readme",
"bugs": "https://github.com/embarklabs/embark/issues",
feat(@embark/nethermind): add Nethermind blockchain client plugin
2020-01-08 21:17:13 +00:00
"keywords": [
"blockchain",
"dapps",
"ethereum",
"serverless",
"nethermind"
],
"files": [
fix: ensure that packages properly specify their dependencies Many packages in the monorepo did not specify all of their dependencies; they were effectively relying on resolution in the monorepo's root `node_modules`. In a production release of `embark` and `embark[js]-*` packages this can lead to broken packages. To fix the problem currently and to help prevent it from happening again, make use of the `eslint-plugin-import` package's `import/no-extraneous-dependencies` and `import/no-unresolved` rules. In the root `tslint.json` set `"no-implicit-dependencies": true`, wich is the tslint equivalent of `import/no-extraneous-dependencies`; there is no tslint equivalent for `import/no-unresolved`, but we will eventually replace tslint with an eslint configuration that checks both `.js` and `.ts` files. For `import/no-unresolved` to work in our monorepo setup, in most packages add an `index.js` that has: ```js module.exports = require('./dist'); // or './dist/lib' in some cases ``` And point `"main"` in `package.json` to `"./index.js"`. Despite what's indicated in npm's documentation for `package.json`, it's also necessary to add `"index.js"` to the `"files"` array. Make sure that all `.js` files that can and should be linted are in fact linted. For example, files in `packages/embark/src/cmd/` weren't being linted and many test suites weren't being linted. Bump all relevant packages to `eslint@6.8.0`. Fix all linter errors that arose after these changes. Implement a `check-yarn-lock` script that's run as part of `"ci:full"` and `"qa:full"`, and can manually be invoked via `yarn cylock` in the root of the monorepo. The script exits with error if any specifiers are found in `yarn.lock` for `embark[js][-*]` and/or `@embarklabs/*` (with a few exceptions, cf. `scripts/check-yarn-lock.js`).
2020-02-20 23:47:01 +00:00
"dist",
"index.js"
feat(@embark/nethermind): add Nethermind blockchain client plugin
2020-01-08 21:17:13 +00:00
],
"license": "MIT",
"repository": {
"directory": "packages/plugins/nethermind",
"type": "git",
chore: rename org references from embark-framework to embarklabs
2020-01-16 19:37:59 +00:00
"url": "https://github.com/embarklabs/embark.git"
feat(@embark/nethermind): add Nethermind blockchain client plugin
2020-01-08 21:17:13 +00:00
},
fix: ensure that packages properly specify their dependencies Many packages in the monorepo did not specify all of their dependencies; they were effectively relying on resolution in the monorepo's root `node_modules`. In a production release of `embark` and `embark[js]-*` packages this can lead to broken packages. To fix the problem currently and to help prevent it from happening again, make use of the `eslint-plugin-import` package's `import/no-extraneous-dependencies` and `import/no-unresolved` rules. In the root `tslint.json` set `"no-implicit-dependencies": true`, wich is the tslint equivalent of `import/no-extraneous-dependencies`; there is no tslint equivalent for `import/no-unresolved`, but we will eventually replace tslint with an eslint configuration that checks both `.js` and `.ts` files. For `import/no-unresolved` to work in our monorepo setup, in most packages add an `index.js` that has: ```js module.exports = require('./dist'); // or './dist/lib' in some cases ``` And point `"main"` in `package.json` to `"./index.js"`. Despite what's indicated in npm's documentation for `package.json`, it's also necessary to add `"index.js"` to the `"files"` array. Make sure that all `.js` files that can and should be linted are in fact linted. For example, files in `packages/embark/src/cmd/` weren't being linted and many test suites weren't being linted. Bump all relevant packages to `eslint@6.8.0`. Fix all linter errors that arose after these changes. Implement a `check-yarn-lock` script that's run as part of `"ci:full"` and `"qa:full"`, and can manually be invoked via `yarn cylock` in the root of the monorepo. The script exits with error if any specifiers are found in `yarn.lock` for `embark[js][-*]` and/or `@embarklabs/*` (with a few exceptions, cf. `scripts/check-yarn-lock.js`).
2020-02-20 23:47:01 +00:00
"main": "./index.js",
feat(@embark/nethermind): add Nethermind blockchain client plugin
2020-01-08 21:17:13 +00:00
"types": "./dist/index.d.ts",
"embark-collective": {
"build:node": true,
"typecheck": true
},
"scripts": {
"_build": "npm run solo -- build",
"_typecheck": "npm run solo -- typecheck",
"ci": "npm run qa",
"clean": "npm run reset",
"lint": "eslint src/",
"qa": "npm-run-all lint _typecheck _build",
"reset": "npx rimraf dist embark-*.tgz package",
"solo": "embark-solo"
},
"eslintConfig": {
"extends": "../../../.eslintrc.json"
},
"dependencies": {
"@babel/runtime-corejs3": "7.7.4",
"async": "2.6.1",
"core-js": "3.4.3",
chore(prerelease): 5.3.0-nightly.3
2020-03-04 00:15:48 +00:00
"embark-core": "^5.3.0-nightly.3",
chore(release): 5.2.3
2020-02-25 21:09:29 +00:00
"embark-i18n": "^5.2.3",
chore(prerelease): 5.3.0-nightly.2
2020-03-03 00:14:47 +00:00
"embark-logger": "^5.3.0-nightly.2",
chore(prerelease): 5.3.0-nightly.3
2020-03-04 00:15:48 +00:00
"embark-utils": "^5.3.0-nightly.3",
feat(@embark/nethermind): add Nethermind blockchain client plugin
2020-01-08 21:17:13 +00:00
"fs-extra": "8.1.0",
"netcat": "1.3.5",
"semver": "5.6.0",
"ws": "7.1.2"
},
"devDependencies": {
chore(release): 5.2.3
2020-02-25 21:09:29 +00:00
"embark-solo": "^5.2.3",
fix: ensure that packages properly specify their dependencies Many packages in the monorepo did not specify all of their dependencies; they were effectively relying on resolution in the monorepo's root `node_modules`. In a production release of `embark` and `embark[js]-*` packages this can lead to broken packages. To fix the problem currently and to help prevent it from happening again, make use of the `eslint-plugin-import` package's `import/no-extraneous-dependencies` and `import/no-unresolved` rules. In the root `tslint.json` set `"no-implicit-dependencies": true`, wich is the tslint equivalent of `import/no-extraneous-dependencies`; there is no tslint equivalent for `import/no-unresolved`, but we will eventually replace tslint with an eslint configuration that checks both `.js` and `.ts` files. For `import/no-unresolved` to work in our monorepo setup, in most packages add an `index.js` that has: ```js module.exports = require('./dist'); // or './dist/lib' in some cases ``` And point `"main"` in `package.json` to `"./index.js"`. Despite what's indicated in npm's documentation for `package.json`, it's also necessary to add `"index.js"` to the `"files"` array. Make sure that all `.js` files that can and should be linted are in fact linted. For example, files in `packages/embark/src/cmd/` weren't being linted and many test suites weren't being linted. Bump all relevant packages to `eslint@6.8.0`. Fix all linter errors that arose after these changes. Implement a `check-yarn-lock` script that's run as part of `"ci:full"` and `"qa:full"`, and can manually be invoked via `yarn cylock` in the root of the monorepo. The script exits with error if any specifiers are found in `yarn.lock` for `embark[js][-*]` and/or `@embarklabs/*` (with a few exceptions, cf. `scripts/check-yarn-lock.js`).
2020-02-20 23:47:01 +00:00
"eslint": "6.8.0",
feat(@embark/nethermind): add Nethermind blockchain client plugin
2020-01-08 21:17:13 +00:00
"npm-run-all": "4.1.5",
"rimraf": "3.0.0"
},
"engines": {
feat: support Node.js v12.x and newer Remove the `<12.0.0` restriction re: Node.js version in the `"engines"` settings for all the packages in the monorepo that had that restriction. Add missing `"engines"` settings in `packages/plugins/snark/package.json`. Adjust the Azure Pipelines config to include builds for Node.js v12.x and v13.x. Bump `solc` to `0.4.26` in `dapps/tests/app` and `dapps/tests/contracts`. It was discovered that older versions suffered a fatal `Maximum call stack size exceeded` error when run on Windows with Node.js v12.x or newer. Display a warning re: the bad combo (solc version + Windows + Node version) if it's detected at runtime. Adjust the root `yarn.lock` so that the `sha3` transitive dependency resolves to a newer version that is compatible with Node v13.x.
2020-01-17 17:32:32 +00:00
"node": ">=10.17.0",
feat(@embark/nethermind): add Nethermind blockchain client plugin
2020-01-08 21:17:13 +00:00
"npm": ">=6.11.3",
"yarn": ">=1.19.1"
}
}