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

111 lines
3.0 KiB
JSON
Raw Normal View History

refactor(@embark/embarkjs): move module into own package (#1945) **TODO:** The `embark eject-webpack` command needs to be updated. @michaelsbradleyjr - do you have suggestions as to how we could port this over? We could **assume** that the `basic-pipeline` plugin will be installed, and then read the embark config and overrides from the file system, however this feels like we are sort adding a dependency to a plugin, which is not right. Any suggestions?
2019-10-14 07:05:17 +00:00
{
"name": "embark-basic-pipeline",
chore(release): 5.0.0-alpha.1
2019-11-05 20:55:06 +00:00
"version": "5.0.0-alpha.1",
refactor(@embark/embarkjs): move module into own package (#1945) **TODO:** The `embark eject-webpack` command needs to be updated. @michaelsbradleyjr - do you have suggestions as to how we could port this over? We could **assume** that the `basic-pipeline` plugin will be installed, and then read the embark config and overrides from the file system, however this feels like we are sort adding a dependency to a plugin, which is not right. Any suggestions?
2019-10-14 07:05:17 +00:00
"author": "Iuri Matias <iuri.matias@gmail.com>",
"contributors": [],
"description": "Basic pipeline for Embark that builds a DApp's frontend assets using webpack",
"homepage": "https://github.com/embark-framework/embark/tree/master/packages/plugins/basic-pipeline#readme",
"bugs": "https://github.com/embark-framework/embark/issues",
"keywords": [
"blockchain",
"dapps",
"ethereum",
"ipfs",
"serverless",
"solc",
"solidity"
],
"files": [
"dist"
],
"license": "MIT",
"repository": {
"directory": "packages/plugins/basic-pipeline",
"type": "git",
"url": "https://github.com/embark-framework/embark.git"
},
"main": "./dist/index.js",
"embark-collective": {
"build:node": true
},
"scripts": {
"_build": "npm run solo -- build",
"ci": "npm run qa",
"clean": "npm run reset",
"lint": "eslint src/",
Fix/solo spawn (#1981) * build(@embark/stack/blockchain-client): remove unneeded typescript related scripts and deps In addition to being unneeded their presence is causing build errors. * build(embark): remove unneeded typescript related scripts and deps In addition to being unneeded their presence is causing build errors. * build(@embark/plugins/ethereum-blockchain-client): remove unneeded typescript related scripts, deps In addition to being unneeded their presence is causing build errors. * build(@embark/plugins/ganache): remove unneeded typescript related scripts and deps In addition to being unneeded their presence is causing build errors. * build(@embark/plugins/geth): remove unneeded typescript related scripts and deps In addition to being unneeded their presence is causing build errors. * fix(@embark/plugins/transaction-logger): require 'web3' not 'Web3' * fix(@embark/utils/solo): spawn npm(.cmd) instead of npx(.cmd) * test(@embark/plugins/basic-pipeline): add test stub * test(@embark/stack/blockchain): add test stub
2019-10-22 13:27:28 +00:00
"qa": "npm-run-all lint _build test",
refactor(@embark/embarkjs): move module into own package (#1945) **TODO:** The `embark eject-webpack` command needs to be updated. @michaelsbradleyjr - do you have suggestions as to how we could port this over? We could **assume** that the `basic-pipeline` plugin will be installed, and then read the embark config and overrides from the file system, however this feels like we are sort adding a dependency to a plugin, which is not right. Any suggestions?
2019-10-14 07:05:17 +00:00
"reset": "npx rimraf dist embark-*.tgz package",
"solo": "embark-solo",
"test": "jest"
},
"eslintConfig": {
"extends": "../../../.eslintrc.json"
},
"dependencies": {
build(deps/-dev): update babel and babel-related deps and devDeps to latest versions
2019-11-25 23:59:07 +00:00
"@babel/core": "7.7.4",
"@babel/plugin-proposal-class-properties": "7.7.4",
"@babel/plugin-proposal-decorators": "7.7.4",
"@babel/plugin-proposal-object-rest-spread": "7.7.4",
"@babel/plugin-syntax-dynamic-import": "7.7.4",
"@babel/plugin-transform-destructuring": "7.7.4",
"@babel/plugin-transform-flow-strip-types": "7.7.4",
"@babel/plugin-transform-runtime": "7.7.4",
"@babel/preset-env": "7.7.4",
"@babel/preset-react": "7.7.4",
"@babel/preset-typescript": "7.7.4",
"@babel/runtime-corejs3": "7.7.4",
refactor(@embark/embarkjs): move module into own package (#1945) **TODO:** The `embark eject-webpack` command needs to be updated. @michaelsbradleyjr - do you have suggestions as to how we could port this over? We could **assume** that the `basic-pipeline` plugin will be installed, and then read the embark config and overrides from the file system, however this feels like we are sort adding a dependency to a plugin, which is not right. Any suggestions?
2019-10-14 07:05:17 +00:00
"async": "2.6.1",
build(deps): move deps needed by embark-basic-pipeline from packages/embark Introduce additional refactors to ensure the packages can be resolved by the basic pipeline's webpack child process.
2019-10-25 14:52:11 +00:00
"babel-loader": "8.0.6",
build(deps/-dev): update babel and babel-related deps and devDeps to latest versions
2019-11-25 23:59:07 +00:00
"babel-plugin-macros": "2.7.1",
build(deps): move deps needed by embark-basic-pipeline from packages/embark Introduce additional refactors to ensure the packages can be resolved by the basic pipeline's webpack child process.
2019-10-25 14:52:11 +00:00
"babel-plugin-module-resolver": "3.2.0",
"babel-plugin-transform-react-remove-prop-types": "0.4.24",
chore(release): 5.0.0-alpha.0
2019-10-28 21:05:13 +00:00
"clone-deep": "4.0.0",
build(deps): move deps needed by embark-basic-pipeline from packages/embark Introduce additional refactors to ensure the packages can be resolved by the basic pipeline's webpack child process.
2019-10-25 14:52:11 +00:00
"colors": "1.3.2",
build(deps): bump core-js from 3.3.5 to 3.4.3
2019-11-26 20:28:43 +00:00
"core-js": "3.4.3",
build(deps): move deps needed by embark-basic-pipeline from packages/embark Introduce additional refactors to ensure the packages can be resolved by the basic pipeline's webpack child process.
2019-10-25 14:52:11 +00:00
"css-loader": "3.2.0",
chore(release): 5.0.0-alpha.1
2019-11-05 20:55:06 +00:00
"embark-core": "^5.0.0-alpha.1",
"embark-i18n": "^5.0.0-alpha.1",
"embark-utils": "^5.0.0-alpha.1",
build(deps): move deps needed by embark-basic-pipeline from packages/embark Introduce additional refactors to ensure the packages can be resolved by the basic pipeline's webpack child process.
2019-10-25 14:52:11 +00:00
"file-loader": "4.2.0",
"find-up": "4.1.0",
refactor(@embark/embarkjs): move module into own package (#1945) **TODO:** The `embark eject-webpack` command needs to be updated. @michaelsbradleyjr - do you have suggestions as to how we could port this over? We could **assume** that the `basic-pipeline` plugin will be installed, and then read the embark config and overrides from the file system, however this feels like we are sort adding a dependency to a plugin, which is not right. Any suggestions?
2019-10-14 07:05:17 +00:00
"fs-extra": "8.1.0",
build(deps): move deps needed by embark-basic-pipeline from packages/embark Introduce additional refactors to ensure the packages can be resolved by the basic pipeline's webpack child process.
2019-10-25 14:52:11 +00:00
"glob": "7.1.4",
"hard-source-webpack-plugin": "0.13.1",
"lodash.clonedeep": "4.5.0",
"node-sass": "4.13.0",
"sass-loader": "8.0.0",
"style-loader": "1.0.0",
"url-loader": "2.2.0",
build: update babel and webpack dependencies (#1987) Includes a switch from core-js@2 to core-js@3
2019-10-24 21:41:28 +00:00
"webpack": "4.41.2"
refactor(@embark/embarkjs): move module into own package (#1945) **TODO:** The `embark eject-webpack` command needs to be updated. @michaelsbradleyjr - do you have suggestions as to how we could port this over? We could **assume** that the `basic-pipeline` plugin will be installed, and then read the embark config and overrides from the file system, however this feels like we are sort adding a dependency to a plugin, which is not right. Any suggestions?
2019-10-14 07:05:17 +00:00
},
"devDependencies": {
"babel-jest": "24.9.0",
chore(release): 5.0.0-alpha.0
2019-10-28 21:05:13 +00:00
"embark-solo": "^5.0.0-alpha.0",
chore(release): 5.0.0-alpha.1
2019-11-05 20:55:06 +00:00
"embark-testing": "^5.0.0-alpha.1",
refactor(@embark/embarkjs): move module into own package (#1945) **TODO:** The `embark eject-webpack` command needs to be updated. @michaelsbradleyjr - do you have suggestions as to how we could port this over? We could **assume** that the `basic-pipeline` plugin will be installed, and then read the embark config and overrides from the file system, however this feels like we are sort adding a dependency to a plugin, which is not right. Any suggestions?
2019-10-14 07:05:17 +00:00
"eslint": "5.7.0",
"jest": "24.9.0",
"npm-run-all": "4.1.5",
"rimraf": "3.0.0"
},
"engines": {
build: bump all packages' engines settings (#1985) BREAKING CHANGE: node: >=10.17.0 <12.0.0 npm: >=6.11.3 yarn: >=1.19.1 node v10.17.0 is the latest in the 10.x series and is still in the Active LTS lifecycle. Embark is still not compatible with node's 12.x and 13.x series (because of some dependencies), otherwise it would probably make sense to bump our minimum supported node version all the way to the most recent 12.x release. npm v6.11.3 is the version that's bundled with node v10.17.0. yarn v1.19.1 is the most recent version as of the time node v10.17.0 was released.
2019-10-24 13:52:05 +00:00
"node": ">=10.17.0 <12.0.0",
"npm": ">=6.11.3",
"yarn": ">=1.19.1"
refactor(@embark/embarkjs): move module into own package (#1945) **TODO:** The `embark eject-webpack` command needs to be updated. @michaelsbradleyjr - do you have suggestions as to how we could port this over? We could **assume** that the `basic-pipeline` plugin will be installed, and then read the embark config and overrides from the file system, however this feels like we are sort adding a dependency to a plugin, which is not right. Any suggestions?
2019-10-14 07:05:17 +00:00
},
"jest": {
"collectCoverage": true,
"testEnvironment": "node",
"testMatch": [
"**/test/**/*.js"
],
"transform": {
"\\.js$": [
"babel-jest",
{
"rootMode": "upward"
}
]
}
}
}