alioth/nixpkgs
3
0
Fork 0
forked from mirrors/nixpkgs
Code Releases Activity
nixpkgs/pkgs/servers/monitoring/grafana-image-renderer/package.json

70 lines
1.7 KiB
JSON
Raw Normal View History

grafana-image-renderer: init at 2020-12-01 This package[1] is a replacement for the old phantomjs-integration[2] which is practically EOL. It is basically used to render PNGs of panels that triggered an alert in Grafana. This package internally uses `puppeteer`[3] to control a headless Chromium instance. Even though puppeteer recommends to use a fixed revision of `chromium`, I checked that our default `pkgs.chromium` works fine as well. Also, I don't think it's a good idea to use outdated browser versions[4]. I used the latest revision from `master` on purpose since compiling the code with `tsc` from `v2.0` didn't work and I couldn't figure out why. [1] https://grafana.com/grafana/plugins/grafana-image-renderer [2] https://grafana.com/blog/2020/05/07/grafana-7.0-preview-new-image-renderer-plugin-to-replace-phantomjs/ [3] https://github.com/puppeteer/puppeteer [4] currently, puppeteer v2.0.0 is used which recommends revision 706915 (v79.0.3945.130).
2020-12-23 16:36:05 +00:00
{
"name": "renderer",
"version": "1.0.0",
"author": "Grafana Labs",
"license": "Apache-2.0",
"repository": {
"type": "git",
"url": "http://github.com/grafana/grafana-image-renderer.git"
},
"scripts": {
grafana-image-renderer: 2020-12-01 -> 2.0.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v2.0.1
2021-03-07 21:56:28 +00:00
"eslint": "eslint -c eslint.json",
grafana-image-renderer: init at 2020-12-01 This package[1] is a replacement for the old phantomjs-integration[2] which is practically EOL. It is basically used to render PNGs of panels that triggered an alert in Grafana. This package internally uses `puppeteer`[3] to control a headless Chromium instance. Even though puppeteer recommends to use a fixed revision of `chromium`, I checked that our default `pkgs.chromium` works fine as well. Also, I don't think it's a good idea to use outdated browser versions[4]. I used the latest revision from `master` on purpose since compiling the code with `tsc` from `v2.0` didn't work and I couldn't figure out why. [1] https://grafana.com/grafana/plugins/grafana-image-renderer [2] https://grafana.com/blog/2020/05/07/grafana-7.0-preview-new-image-renderer-plugin-to-replace-phantomjs/ [3] https://github.com/puppeteer/puppeteer [4] currently, puppeteer v2.0.0 is used which recommends revision 706915 (v79.0.3945.130).
2020-12-23 16:36:05 +00:00
"typecheck": "tsc --noEmit",
"prettier:check": "prettier --list-different \"**/*.ts\"",
"prettier:write": "prettier --list-different \"**/*.ts\" --write",
grafana-image-renderer: 2020-12-01 -> 2.0.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v2.0.1
2021-03-07 21:56:28 +00:00
"precommit": "npm run eslint & npm run typecheck",
grafana-image-renderer: init at 2020-12-01 This package[1] is a replacement for the old phantomjs-integration[2] which is practically EOL. It is basically used to render PNGs of panels that triggered an alert in Grafana. This package internally uses `puppeteer`[3] to control a headless Chromium instance. Even though puppeteer recommends to use a fixed revision of `chromium`, I checked that our default `pkgs.chromium` works fine as well. Also, I don't think it's a good idea to use outdated browser versions[4]. I used the latest revision from `master` on purpose since compiling the code with `tsc` from `v2.0` didn't work and I couldn't figure out why. [1] https://grafana.com/grafana/plugins/grafana-image-renderer [2] https://grafana.com/blog/2020/05/07/grafana-7.0-preview-new-image-renderer-plugin-to-replace-phantomjs/ [3] https://github.com/puppeteer/puppeteer [4] currently, puppeteer v2.0.0 is used which recommends revision 706915 (v79.0.3945.130).
2020-12-23 16:36:05 +00:00
"watch": "tsc-watch --onSuccess \"node build/app.js server --config=dev.json\"",
"build": "tsc",
"start": "node build/app.js --config=dev.json"
},
"dependencies": {
"@grpc/grpc-js": "^1.0",
"@grpc/proto-loader": "^0.5.4",
"@hapi/boom": "^9.1.0",
grafana-image-renderer: 2020-12-01 -> 2.0.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v2.0.1
2021-03-07 21:56:28 +00:00
"eslint": "^7.13.0",
grafana-image-renderer: init at 2020-12-01 This package[1] is a replacement for the old phantomjs-integration[2] which is practically EOL. It is basically used to render PNGs of panels that triggered an alert in Grafana. This package internally uses `puppeteer`[3] to control a headless Chromium instance. Even though puppeteer recommends to use a fixed revision of `chromium`, I checked that our default `pkgs.chromium` works fine as well. Also, I don't think it's a good idea to use outdated browser versions[4]. I used the latest revision from `master` on purpose since compiling the code with `tsc` from `v2.0` didn't work and I couldn't figure out why. [1] https://grafana.com/grafana/plugins/grafana-image-renderer [2] https://grafana.com/blog/2020/05/07/grafana-7.0-preview-new-image-renderer-plugin-to-replace-phantomjs/ [3] https://github.com/puppeteer/puppeteer [4] currently, puppeteer v2.0.0 is used which recommends revision 706915 (v79.0.3945.130).
2020-12-23 16:36:05 +00:00
"express": "^4.16.3",
"express-prom-bundle": "^5.1.5",
"google-protobuf": "3.5.0",
"lodash": "^4.17.19",
"minimist": "^1.2.0",
"morgan": "^1.9.0",
"mz": "^2.7.0",
"prom-client": "^11.5.3",
"puppeteer": "^2.0.0",
"puppeteer-cluster": "^0.18.0",
"unique-filename": "^1.1.0",
"winston": "^3.2.1"
},
"devDependencies": {
"@types/express": "^4.11.1",
"@types/node": "^10.0.9",
"husky": "^3.1.0",
"lint-staged": "^9.5.0",
"pkg": "4.4.8",
"prettier": "^1.19.1",
"tsc-watch": "^4.2.3",
"typescript": "^3.8.3"
},
"husky": {
"hooks": {
"pre-commit": "lint-staged && npm run precommit"
}
},
"lint-staged": {
"*.ts": [
"prettier --write",
"git add"
]
},
"pkg": {
"assets": "proto/*"
},
"bin": "build/app.js",
"engines": {
"node": ">=12 <13"
},
"volta": {
"node": "12.19.0"
}
}
Copy permalink