| |
@@ -2,11 +2,16 @@
|
| |
"version": "1.0.0",
|
| |
"name": "389-console",
|
| |
"description": "Cockpit plugin for managing 389 Directory Server",
|
| |
+ "repository": {
|
| |
+ "type": "git",
|
| |
+ "url": "https://pagure.io/389-ds-base.git"
|
| |
+ },
|
| |
"author": "",
|
| |
"license": "GPL-3.0-or-later",
|
| |
"main": "index.js",
|
| |
"scripts": {
|
| |
"build": "webpack",
|
| |
+ "audit-ci": "audit-ci --config audit-ci.json",
|
| |
"eslint": "eslint --ext .jsx --ext .es6 src/",
|
| |
"eslint:fix": "eslint --fix --ext .jsx --ext .es6 src/"
|
| |
},
|
| |
@@ -15,12 +20,13 @@
|
| |
"@babel/preset-env": "^7.0.0",
|
| |
"@babel/preset-react": "^7.0.0",
|
| |
"ajv": "^6.0.0",
|
| |
+ "audit-ci": "^1.7.0",
|
| |
"babel-eslint": "^9.0.0",
|
| |
"babel-loader": "^8.0.0",
|
| |
"chrome-remote-interface": "^0.25.5",
|
| |
"compression-webpack-plugin": "^1.1.11",
|
| |
"copy-webpack-plugin": "^4.5.2",
|
| |
- "css-loader": "^0.28.11",
|
| |
+ "css-loader": "^2.1.1",
|
| |
"eslint": "^5.4.0",
|
| |
"eslint-config-standard": "^11.0.0",
|
| |
"eslint-config-standard-react": "^6.0.0",
|
| |
@@ -42,16 +48,16 @@
|
| |
"webpack-cli": "^3.1.0"
|
| |
},
|
| |
"dependencies": {
|
| |
- "patternfly": "3.58.0",
|
| |
- "patternfly-react": "2.24.5",
|
| |
- "bootstrap": "4.2.1",
|
| |
+ "bootstrap": "^4.3.1",
|
| |
"node-sass": "4.11.0",
|
| |
+ "patternfly": "^3.59.1",
|
| |
+ "patternfly-react": "^2.34.3",
|
| |
+ "prop-types": "15.6.2",
|
| |
+ "react": "16.6.1",
|
| |
"react-bootstrap": "0.32.4",
|
| |
"react-bootstrap-typeahead": "3.2.4",
|
| |
- "react": "16.6.1",
|
| |
"react-dom": "16.6.1",
|
| |
- "prop-types": "15.6.2",
|
| |
- "table-resolver": "4.1.1",
|
| |
- "recompose": "0.30.0"
|
| |
+ "recompose": "0.30.0",
|
| |
+ "table-resolver": "4.1.1"
|
| |
}
|
| |
}
|
| |
Bug description: All software changes incur some risk,
and it's critical to be able to manage this risk.
We can use a common way of dealing with it - npm-shrinkwrap.
Fix description: The suggested approach - npm-shrinkwrap - is an "overkill"
for our case. We don't need to publish the package on NPM.
It will be sufficient enough to use existing NPM functionality added in 5.7 version.
Replace
npm install
withnpm ci
which uses package-lock.jsonand throws an error if any inconsistencies with pachage.json are found.
Add package-lock.json to the repo.
When we change the package.json content, a new pachage-lock.json should be
generated (using
npm install
) and the change should be commited.https://pagure.io/389-ds-base/issue/50052
Reviewed by: ?