nordic-dev.net/nixpkgs
nordic-dev.net/nixpkgs
2
0
Fork 0
mirror of https://github.com/NixOS/nixpkgs.git synced 2024-11-28 01:43:15 +00:00
Code Issues Packages Projects Releases Wiki Activity
ecbb9e669d
nixpkgs/pkgs/servers/monitoring/grafana-image-renderer/yarn.nix

4310 lines
156 KiB
Nix
Raw Normal View History

treewide: runCommandNoCC -> runCommand in generated code This has been synonymous for ~5y. Note that many of these runCommand bindings are unused, but that's ok for generated code.
2021-08-15 15:16:57 +00:00
{ fetchurl, fetchgit, linkFarm, runCommand, gnutar }: rec {
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
offline_cache = linkFarm "offline" packages;
packages = [
{
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
name = "_babel_code_frame___code_frame_7.12.11.tgz";
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
path = fetchurl {
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
name = "_babel_code_frame___code_frame_7.12.11.tgz";
url = "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.12.11.tgz";
sha1 = "f4ad435aa263db935b8f10f2c552d23fb716a63f";
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
};
}
{
grafana-image-renderer: 3.2.1 -> 3.3.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.3.0
2021-11-21 16:18:57 +00:00
name = "_babel_code_frame___code_frame_7.14.5.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.1 -> 3.3.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.3.0
2021-11-21 16:18:57 +00:00
name = "_babel_code_frame___code_frame_7.14.5.tgz";
url = "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.14.5.tgz";
sha1 = "23b08d740e83f49c5e59945fbf1b43e80bbf4edb";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_babel_helper_validator_identifier___helper_validator_identifier_7.15.7.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_babel_helper_validator_identifier___helper_validator_identifier_7.15.7.tgz";
url = "https://registry.yarnpkg.com/@babel/helper-validator-identifier/-/helper-validator-identifier-7.15.7.tgz";
sha1 = "220df993bfe904a4a6b02ab4f3385a5ebf6e2389";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_babel_highlight___highlight_7.14.5.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_babel_highlight___highlight_7.14.5.tgz";
url = "https://registry.yarnpkg.com/@babel/highlight/-/highlight-7.14.5.tgz";
sha1 = "6861a52f03966405001f6aa534a01a24d99e8cd9";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "_babel_parser___parser_7.13.13.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "_babel_parser___parser_7.13.13.tgz";
url = "https://registry.yarnpkg.com/@babel/parser/-/parser-7.13.13.tgz";
sha1 = "42f03862f4aed50461e543270916b47dd501f0df";
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
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "_babel_types___types_7.13.12.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "_babel_types___types_7.13.12.tgz";
url = "https://registry.yarnpkg.com/@babel/types/-/types-7.13.12.tgz";
sha1 = "edbf99208ef48852acdff1c8a681a1e4ade580cd";
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
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "_dabh_diagnostics___diagnostics_2.0.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "_dabh_diagnostics___diagnostics_2.0.2.tgz";
url = "https://registry.yarnpkg.com/@dabh/diagnostics/-/diagnostics-2.0.2.tgz";
sha1 = "290d08f7b381b8f94607dc8f471a12c675f9db31";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_es_joy_jsdoccomment___jsdoccomment_0.10.8.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_es_joy_jsdoccomment___jsdoccomment_0.10.8.tgz";
url = "https://registry.yarnpkg.com/@es-joy/jsdoccomment/-/jsdoccomment-0.10.8.tgz";
sha1 = "b3152887e25246410ed4ea569a55926ec13b2b05";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_eslint_eslintrc___eslintrc_0.4.3.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_eslint_eslintrc___eslintrc_0.4.3.tgz";
url = "https://registry.yarnpkg.com/@eslint/eslintrc/-/eslintrc-0.4.3.tgz";
sha1 = "9e42981ef035beb3dd49add17acb96e8ff6f394c";
};
}
{
name = "_grafana_eslint_config___eslint_config_2.5.0.tgz";
path = fetchurl {
name = "_grafana_eslint_config___eslint_config_2.5.0.tgz";
url = "https://registry.yarnpkg.com/@grafana/eslint-config/-/eslint-config-2.5.0.tgz";
sha1 = "d028898e201f242748a94d5582f0e14a493f5853";
};
}
{
name = "_grpc_grpc_js___grpc_js_1.3.7.tgz";
path = fetchurl {
name = "_grpc_grpc_js___grpc_js_1.3.7.tgz";
url = "https://registry.yarnpkg.com/@grpc/grpc-js/-/grpc-js-1.3.7.tgz";
sha1 = "58b687aff93b743aafde237fd2ee9a3259d7f2d8";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "_grpc_proto_loader___proto_loader_0.5.6.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "_grpc_proto_loader___proto_loader_0.5.6.tgz";
url = "https://registry.yarnpkg.com/@grpc/proto-loader/-/proto-loader-0.5.6.tgz";
sha1 = "1dea4b8a6412b05e2d58514d507137b63a52a98d";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_hapi_boom___boom_9.1.4.tgz";
path = fetchurl {
name = "_hapi_boom___boom_9.1.4.tgz";
url = "https://registry.yarnpkg.com/@hapi/boom/-/boom-9.1.4.tgz";
sha1 = "1f9dad367c6a7da9f8def24b4a986fc5a7bd9db6";
};
}
{
name = "_hapi_hoek___hoek_9.2.1.tgz";
path = fetchurl {
name = "_hapi_hoek___hoek_9.2.1.tgz";
url = "https://registry.yarnpkg.com/@hapi/hoek/-/hoek-9.2.1.tgz";
sha1 = "9551142a1980503752536b5050fd99f4a7f13b17";
};
}
{
name = "_humanwhocodes_config_array___config_array_0.5.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_humanwhocodes_config_array___config_array_0.5.0.tgz";
url = "https://registry.yarnpkg.com/@humanwhocodes/config-array/-/config-array-0.5.0.tgz";
sha1 = "1407967d4c6eecd7388f83acf1eaf4d0c6e58ef9";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_humanwhocodes_object_schema___object_schema_1.2.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_humanwhocodes_object_schema___object_schema_1.2.0.tgz";
url = "https://registry.yarnpkg.com/@humanwhocodes/object-schema/-/object-schema-1.2.0.tgz";
sha1 = "87de7af9c231826fdd68ac7258f77c429e0e5fcf";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_nodelib_fs.scandir___fs.scandir_2.1.5.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_nodelib_fs.scandir___fs.scandir_2.1.5.tgz";
url = "https://registry.yarnpkg.com/@nodelib/fs.scandir/-/fs.scandir-2.1.5.tgz";
sha1 = "7619c2eb21b25483f6d167548b4cfd5a7488c3d5";
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_nodelib_fs.stat___fs.stat_2.0.5.tgz";
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_nodelib_fs.stat___fs.stat_2.0.5.tgz";
url = "https://registry.yarnpkg.com/@nodelib/fs.stat/-/fs.stat-2.0.5.tgz";
sha1 = "5bd262af94e9d25bd1e71b05deed44876a222e8b";
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_nodelib_fs.walk___fs.walk_1.2.8.tgz";
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_nodelib_fs.walk___fs.walk_1.2.8.tgz";
url = "https://registry.yarnpkg.com/@nodelib/fs.walk/-/fs.walk-1.2.8.tgz";
sha1 = "e95737e8bb6746ddedf69c556953494f196fe69a";
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 = "_protobufjs_aspromise___aspromise_1.1.2.tgz";
path = fetchurl {
name = "_protobufjs_aspromise___aspromise_1.1.2.tgz";
url = "https://registry.yarnpkg.com/@protobufjs/aspromise/-/aspromise-1.1.2.tgz";
sha1 = "9b8b0cc663d669a7d8f6f5d0893a14d348f30fbf";
};
}
{
name = "_protobufjs_base64___base64_1.1.2.tgz";
path = fetchurl {
name = "_protobufjs_base64___base64_1.1.2.tgz";
url = "https://registry.yarnpkg.com/@protobufjs/base64/-/base64-1.1.2.tgz";
sha1 = "4c85730e59b9a1f1f349047dbf24296034bb2735";
};
}
{
name = "_protobufjs_codegen___codegen_2.0.4.tgz";
path = fetchurl {
name = "_protobufjs_codegen___codegen_2.0.4.tgz";
url = "https://registry.yarnpkg.com/@protobufjs/codegen/-/codegen-2.0.4.tgz";
sha1 = "7ef37f0d010fb028ad1ad59722e506d9262815cb";
};
}
{
name = "_protobufjs_eventemitter___eventemitter_1.1.0.tgz";
path = fetchurl {
name = "_protobufjs_eventemitter___eventemitter_1.1.0.tgz";
url = "https://registry.yarnpkg.com/@protobufjs/eventemitter/-/eventemitter-1.1.0.tgz";
sha1 = "355cbc98bafad5978f9ed095f397621f1d066b70";
};
}
{
name = "_protobufjs_fetch___fetch_1.1.0.tgz";
path = fetchurl {
name = "_protobufjs_fetch___fetch_1.1.0.tgz";
url = "https://registry.yarnpkg.com/@protobufjs/fetch/-/fetch-1.1.0.tgz";
sha1 = "ba99fb598614af65700c1619ff06d454b0d84c45";
};
}
{
name = "_protobufjs_float___float_1.0.2.tgz";
path = fetchurl {
name = "_protobufjs_float___float_1.0.2.tgz";
url = "https://registry.yarnpkg.com/@protobufjs/float/-/float-1.0.2.tgz";
sha1 = "5e9e1abdcb73fc0a7cb8b291df78c8cbd97b87d1";
};
}
{
name = "_protobufjs_inquire___inquire_1.1.0.tgz";
path = fetchurl {
name = "_protobufjs_inquire___inquire_1.1.0.tgz";
url = "https://registry.yarnpkg.com/@protobufjs/inquire/-/inquire-1.1.0.tgz";
sha1 = "ff200e3e7cf2429e2dcafc1140828e8cc638f089";
};
}
{
name = "_protobufjs_path___path_1.1.2.tgz";
path = fetchurl {
name = "_protobufjs_path___path_1.1.2.tgz";
url = "https://registry.yarnpkg.com/@protobufjs/path/-/path-1.1.2.tgz";
sha1 = "6cc2b20c5c9ad6ad0dccfd21ca7673d8d7fbf68d";
};
}
{
name = "_protobufjs_pool___pool_1.1.0.tgz";
path = fetchurl {
name = "_protobufjs_pool___pool_1.1.0.tgz";
url = "https://registry.yarnpkg.com/@protobufjs/pool/-/pool-1.1.0.tgz";
sha1 = "09fd15f2d6d3abfa9b65bc366506d6ad7846ff54";
};
}
{
name = "_protobufjs_utf8___utf8_1.1.0.tgz";
path = fetchurl {
name = "_protobufjs_utf8___utf8_1.1.0.tgz";
url = "https://registry.yarnpkg.com/@protobufjs/utf8/-/utf8-1.1.0.tgz";
sha1 = "a777360b5b39a1a2e5106f8e858f2fd2d060c570";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_types_body_parser___body_parser_1.19.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_types_body_parser___body_parser_1.19.1.tgz";
url = "https://registry.yarnpkg.com/@types/body-parser/-/body-parser-1.19.1.tgz";
sha1 = "0c0174c42a7d017b818303d4b5d969cb0b75929c";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_types_connect___connect_3.4.35.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_types_connect___connect_3.4.35.tgz";
url = "https://registry.yarnpkg.com/@types/connect/-/connect-3.4.35.tgz";
sha1 = "5fcf6ae445e4021d1fc2219a4873cc73a3bb2ad1";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_types_express_serve_static_core___express_serve_static_core_4.17.24.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_types_express_serve_static_core___express_serve_static_core_4.17.24.tgz";
url = "https://registry.yarnpkg.com/@types/express-serve-static-core/-/express-serve-static-core-4.17.24.tgz";
sha1 = "ea41f93bf7e0d59cd5a76665068ed6aab6815c07";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_types_express___express_4.17.13.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_types_express___express_4.17.13.tgz";
url = "https://registry.yarnpkg.com/@types/express/-/express-4.17.13.tgz";
sha1 = "a76e2995728999bab51a33fabce1d705a3709034";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_types_json_schema___json_schema_7.0.9.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_types_json_schema___json_schema_7.0.9.tgz";
url = "https://registry.yarnpkg.com/@types/json-schema/-/json-schema-7.0.9.tgz";
sha1 = "97edc9037ea0c38585320b28964dde3b39e4660d";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "_types_long___long_4.0.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "_types_long___long_4.0.1.tgz";
url = "https://registry.yarnpkg.com/@types/long/-/long-4.0.1.tgz";
sha1 = "459c65fa1867dafe6a8f322c4c51695663cc55e9";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "_types_mime___mime_1.3.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "_types_mime___mime_1.3.2.tgz";
url = "https://registry.yarnpkg.com/@types/mime/-/mime-1.3.2.tgz";
sha1 = "93e25bf9ee75fe0fd80b594bc4feb0e862111b5a";
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
};
}
{
grafana-image-renderer: 3.2.1 -> 3.3.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.3.0
2021-11-21 16:18:57 +00:00
name = "_types_node___node_16.10.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.1 -> 3.3.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.3.0
2021-11-21 16:18:57 +00:00
name = "_types_node___node_16.10.2.tgz";
url = "https://registry.yarnpkg.com/@types/node/-/node-16.10.2.tgz";
sha1 = "5764ca9aa94470adb4e1185fe2e9f19458992b2e";
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
};
}
{
grafana-image-renderer: 3.2.1 -> 3.3.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.3.0
2021-11-21 16:18:57 +00:00
name = "_types_node___node_14.17.20.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.1 -> 3.3.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.3.0
2021-11-21 16:18:57 +00:00
name = "_types_node___node_14.17.20.tgz";
url = "https://registry.yarnpkg.com/@types/node/-/node-14.17.20.tgz";
sha1 = "74cc80438fd0467dc4377ee5bbad89a886df3c10";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "_types_parse_json___parse_json_4.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "_types_parse_json___parse_json_4.0.0.tgz";
url = "https://registry.yarnpkg.com/@types/parse-json/-/parse-json-4.0.0.tgz";
sha1 = "2f8bb441434d163b35fb8ffdccd7138927ffb8c0";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_types_qs___qs_6.9.7.tgz";
path = fetchurl {
name = "_types_qs___qs_6.9.7.tgz";
url = "https://registry.yarnpkg.com/@types/qs/-/qs-6.9.7.tgz";
sha1 = "63bb7d067db107cc1e457c303bc25d511febf6cb";
};
}
{
name = "_types_range_parser___range_parser_1.2.4.tgz";
path = fetchurl {
name = "_types_range_parser___range_parser_1.2.4.tgz";
url = "https://registry.yarnpkg.com/@types/range-parser/-/range-parser-1.2.4.tgz";
sha1 = "cd667bcfdd025213aafb7ca5915a932590acdcdc";
};
}
{
name = "_types_serve_static___serve_static_1.13.10.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_types_serve_static___serve_static_1.13.10.tgz";
url = "https://registry.yarnpkg.com/@types/serve-static/-/serve-static-1.13.10.tgz";
sha1 = "f5e0ce8797d2d7cc5ebeda48a52c96c4fa47a8d9";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_types_yauzl___yauzl_2.9.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_types_yauzl___yauzl_2.9.2.tgz";
url = "https://registry.yarnpkg.com/@types/yauzl/-/yauzl-2.9.2.tgz";
sha1 = "c48e5d56aff1444409e39fa164b0b4d4552a7b7a";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_typescript_eslint_eslint_plugin___eslint_plugin_4.28.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_typescript_eslint_eslint_plugin___eslint_plugin_4.28.0.tgz";
url = "https://registry.yarnpkg.com/@typescript-eslint/eslint-plugin/-/eslint-plugin-4.28.0.tgz";
sha1 = "1a66f03b264844387beb7dc85e1f1d403bd1803f";
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_typescript_eslint_eslint_plugin___eslint_plugin_4.33.0.tgz";
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "_typescript_eslint_eslint_plugin___eslint_plugin_4.33.0.tgz";
url = "https://registry.yarnpkg.com/@typescript-eslint/eslint-plugin/-/eslint-plugin-4.33.0.tgz";
sha1 = "c24dc7c8069c7706bc40d99f6fa87edcb2005276";
};
}
{
name = "_typescript_eslint_experimental_utils___experimental_utils_4.28.0.tgz";
path = fetchurl {
name = "_typescript_eslint_experimental_utils___experimental_utils_4.28.0.tgz";
url = "https://registry.yarnpkg.com/@typescript-eslint/experimental-utils/-/experimental-utils-4.28.0.tgz";
sha1 = "13167ed991320684bdc23588135ae62115b30ee0";
};
}
{
name = "_typescript_eslint_experimental_utils___experimental_utils_4.33.0.tgz";
path = fetchurl {
name = "_typescript_eslint_experimental_utils___experimental_utils_4.33.0.tgz";
url = "https://registry.yarnpkg.com/@typescript-eslint/experimental-utils/-/experimental-utils-4.33.0.tgz";
sha1 = "6f2a786a4209fa2222989e9380b5331b2810f7fd";
};
}
{
name = "_typescript_eslint_parser___parser_4.28.0.tgz";
path = fetchurl {
name = "_typescript_eslint_parser___parser_4.28.0.tgz";
url = "https://registry.yarnpkg.com/@typescript-eslint/parser/-/parser-4.28.0.tgz";
sha1 = "2404c16751a28616ef3abab77c8e51d680a12caa";
};
}
{
name = "_typescript_eslint_parser___parser_4.33.0.tgz";
path = fetchurl {
name = "_typescript_eslint_parser___parser_4.33.0.tgz";
url = "https://registry.yarnpkg.com/@typescript-eslint/parser/-/parser-4.33.0.tgz";
sha1 = "dfe797570d9694e560528d18eecad86c8c744899";
};
}
{
name = "_typescript_eslint_scope_manager___scope_manager_4.28.0.tgz";
path = fetchurl {
name = "_typescript_eslint_scope_manager___scope_manager_4.28.0.tgz";
url = "https://registry.yarnpkg.com/@typescript-eslint/scope-manager/-/scope-manager-4.28.0.tgz";
sha1 = "6a3009d2ab64a30fc8a1e257a1a320067f36a0ce";
};
}
{
name = "_typescript_eslint_scope_manager___scope_manager_4.33.0.tgz";
path = fetchurl {
name = "_typescript_eslint_scope_manager___scope_manager_4.33.0.tgz";
url = "https://registry.yarnpkg.com/@typescript-eslint/scope-manager/-/scope-manager-4.33.0.tgz";
sha1 = "d38e49280d983e8772e29121cf8c6e9221f280a3";
};
}
{
name = "_typescript_eslint_types___types_4.28.0.tgz";
path = fetchurl {
name = "_typescript_eslint_types___types_4.28.0.tgz";
url = "https://registry.yarnpkg.com/@typescript-eslint/types/-/types-4.28.0.tgz";
sha1 = "a33504e1ce7ac51fc39035f5fe6f15079d4dafb0";
};
}
{
name = "_typescript_eslint_types___types_4.33.0.tgz";
path = fetchurl {
name = "_typescript_eslint_types___types_4.33.0.tgz";
url = "https://registry.yarnpkg.com/@typescript-eslint/types/-/types-4.33.0.tgz";
sha1 = "a1e59036a3b53ae8430ceebf2a919dc7f9af6d72";
};
}
{
name = "_typescript_eslint_typescript_estree___typescript_estree_4.28.0.tgz";
path = fetchurl {
name = "_typescript_eslint_typescript_estree___typescript_estree_4.28.0.tgz";
url = "https://registry.yarnpkg.com/@typescript-eslint/typescript-estree/-/typescript-estree-4.28.0.tgz";
sha1 = "e66d4e5aa2ede66fec8af434898fe61af10c71cf";
};
}
{
name = "_typescript_eslint_typescript_estree___typescript_estree_4.33.0.tgz";
path = fetchurl {
name = "_typescript_eslint_typescript_estree___typescript_estree_4.33.0.tgz";
url = "https://registry.yarnpkg.com/@typescript-eslint/typescript-estree/-/typescript-estree-4.33.0.tgz";
sha1 = "0dfb51c2908f68c5c08d82aefeaf166a17c24609";
};
}
{
name = "_typescript_eslint_visitor_keys___visitor_keys_4.28.0.tgz";
path = fetchurl {
name = "_typescript_eslint_visitor_keys___visitor_keys_4.28.0.tgz";
url = "https://registry.yarnpkg.com/@typescript-eslint/visitor-keys/-/visitor-keys-4.28.0.tgz";
sha1 = "255c67c966ec294104169a6939d96f91c8a89434";
};
}
{
name = "_typescript_eslint_visitor_keys___visitor_keys_4.33.0.tgz";
path = fetchurl {
name = "_typescript_eslint_visitor_keys___visitor_keys_4.33.0.tgz";
url = "https://registry.yarnpkg.com/@typescript-eslint/visitor-keys/-/visitor-keys-4.33.0.tgz";
sha1 = "2a22f77a41604289b7a186586e9ec48ca92ef1dd";
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 = "accepts___accepts_1.3.7.tgz";
path = fetchurl {
name = "accepts___accepts_1.3.7.tgz";
url = "https://registry.yarnpkg.com/accepts/-/accepts-1.3.7.tgz";
sha1 = "531bc726517a3b2b41f850021c6cc15eaab507cd";
};
}
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
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "acorn_jsx___acorn_jsx_5.3.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "acorn_jsx___acorn_jsx_5.3.2.tgz";
url = "https://registry.yarnpkg.com/acorn-jsx/-/acorn-jsx-5.3.2.tgz";
sha1 = "7ed5bb55908b3b2f1bc55c6af1653bada7f07937";
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
};
}
{
name = "acorn___acorn_7.4.1.tgz";
path = fetchurl {
name = "acorn___acorn_7.4.1.tgz";
url = "https://registry.yarnpkg.com/acorn/-/acorn-7.4.1.tgz";
sha1 = "feaed255973d2e77555b83dbc08851a6c63520fa";
};
}
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
{
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
name = "agent_base___agent_base_6.0.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
name = "agent_base___agent_base_6.0.2.tgz";
url = "https://registry.yarnpkg.com/agent-base/-/agent-base-6.0.2.tgz";
sha1 = "49fff58577cfee3f37176feab4c22e00f86d7f77";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "aggregate_error___aggregate_error_3.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "aggregate_error___aggregate_error_3.1.0.tgz";
url = "https://registry.yarnpkg.com/aggregate-error/-/aggregate-error-3.1.0.tgz";
sha1 = "92670ff50f5359bdb7a3e0d40d0ec30c5737687a";
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
};
}
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
{
name = "ajv___ajv_6.12.6.tgz";
path = fetchurl {
name = "ajv___ajv_6.12.6.tgz";
url = "https://registry.yarnpkg.com/ajv/-/ajv-6.12.6.tgz";
sha1 = "baf5a62e802b07d977034586f8c3baf5adf26df4";
};
}
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
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "ajv___ajv_8.6.3.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "ajv___ajv_8.6.3.tgz";
url = "https://registry.yarnpkg.com/ajv/-/ajv-8.6.3.tgz";
sha1 = "11a66527761dc3e9a3845ea775d2d3c0414e8764";
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
};
}
{
name = "ansi_colors___ansi_colors_4.1.1.tgz";
path = fetchurl {
name = "ansi_colors___ansi_colors_4.1.1.tgz";
url = "https://registry.yarnpkg.com/ansi-colors/-/ansi-colors-4.1.1.tgz";
sha1 = "cbb9ae256bf750af1eab344f229aa27fe94ba348";
};
}
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
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "ansi_escapes___ansi_escapes_4.3.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "ansi_escapes___ansi_escapes_4.3.2.tgz";
url = "https://registry.yarnpkg.com/ansi-escapes/-/ansi-escapes-4.3.2.tgz";
sha1 = "6b2291d1db7d98b6521d5f1efa42d0f3a9feb65e";
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 = "ansi_regex___ansi_regex_2.1.1.tgz";
path = fetchurl {
name = "ansi_regex___ansi_regex_2.1.1.tgz";
url = "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-2.1.1.tgz";
sha1 = "c3b33ab5ee360d86e0e628f0468ae7ef27d654df";
};
}
{
name = "ansi_regex___ansi_regex_3.0.0.tgz";
path = fetchurl {
name = "ansi_regex___ansi_regex_3.0.0.tgz";
url = "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-3.0.0.tgz";
sha1 = "ed0317c322064f79466c02966bddb605ab37d998";
};
}
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
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "ansi_regex___ansi_regex_5.0.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "ansi_regex___ansi_regex_5.0.1.tgz";
url = "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-5.0.1.tgz";
sha1 = "082cb2c89c9fe8659a311a53bd6a4dc5301db304";
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 = "ansi_styles___ansi_styles_3.2.1.tgz";
path = fetchurl {
name = "ansi_styles___ansi_styles_3.2.1.tgz";
url = "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-3.2.1.tgz";
sha1 = "41fbb20243e50b12be0f04b8dedbf07520ce841d";
};
}
{
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
name = "ansi_styles___ansi_styles_4.3.0.tgz";
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
path = fetchurl {
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
name = "ansi_styles___ansi_styles_4.3.0.tgz";
url = "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-4.3.0.tgz";
sha1 = "edd803628ae71c04c85ae7a0906edad34b648937";
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
};
}
grafana-image-renderer: 2.1.0 -> 3.0.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.0
2021-06-07 21:38:04 +00:00
{
name = "anymatch___anymatch_3.1.2.tgz";
path = fetchurl {
name = "anymatch___anymatch_3.1.2.tgz";
url = "https://registry.yarnpkg.com/anymatch/-/anymatch-3.1.2.tgz";
sha1 = "c0557c096af32f106198f4f4e2a383537e378716";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "aproba___aproba_1.2.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "aproba___aproba_1.2.0.tgz";
url = "https://registry.yarnpkg.com/aproba/-/aproba-1.2.0.tgz";
sha1 = "6802e6264efd18c790a1b0d517f0f2627bf2c94a";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "are_we_there_yet___are_we_there_yet_1.1.7.tgz";
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "are_we_there_yet___are_we_there_yet_1.1.7.tgz";
url = "https://registry.yarnpkg.com/are-we-there-yet/-/are-we-there-yet-1.1.7.tgz";
sha1 = "b15474a932adab4ff8a50d9adfa7e4e926f21146";
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 = "argparse___argparse_1.0.10.tgz";
path = fetchurl {
name = "argparse___argparse_1.0.10.tgz";
url = "https://registry.yarnpkg.com/argparse/-/argparse-1.0.10.tgz";
sha1 = "bcd6791ea5ae09725e17e5ad988134cd40b3d911";
};
}
{
name = "array_flatten___array_flatten_1.1.1.tgz";
path = fetchurl {
name = "array_flatten___array_flatten_1.1.1.tgz";
url = "https://registry.yarnpkg.com/array-flatten/-/array-flatten-1.1.1.tgz";
sha1 = "9a5f699051b1e7073328f2a008968b64ea2955d2";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "array_includes___array_includes_3.1.4.tgz";
path = fetchurl {
name = "array_includes___array_includes_3.1.4.tgz";
url = "https://registry.yarnpkg.com/array-includes/-/array-includes-3.1.4.tgz";
sha1 = "f5b493162c760f3539631f005ba2bb46acb45ba9";
};
}
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 = "array_union___array_union_2.1.0.tgz";
path = fetchurl {
name = "array_union___array_union_2.1.0.tgz";
url = "https://registry.yarnpkg.com/array-union/-/array-union-2.1.0.tgz";
sha1 = "b798420adbeb1de828d84acd8a2e23d3efe85e8d";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "array.prototype.flatmap___array.prototype.flatmap_1.2.5.tgz";
path = fetchurl {
name = "array.prototype.flatmap___array.prototype.flatmap_1.2.5.tgz";
url = "https://registry.yarnpkg.com/array.prototype.flatmap/-/array.prototype.flatmap-1.2.5.tgz";
sha1 = "908dc82d8a406930fdf38598d51e7411d18d4446";
};
}
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
{
name = "astral_regex___astral_regex_2.0.0.tgz";
path = fetchurl {
name = "astral_regex___astral_regex_2.0.0.tgz";
url = "https://registry.yarnpkg.com/astral-regex/-/astral-regex-2.0.0.tgz";
sha1 = "483143c567aeed4785759c0865786dc77d7d2e31";
};
}
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
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "async___async_3.2.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "async___async_3.2.1.tgz";
url = "https://registry.yarnpkg.com/async/-/async-3.2.1.tgz";
sha1 = "d3274ec66d107a47476a4c49136aacdb00665fc8";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "at_least_node___at_least_node_1.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "at_least_node___at_least_node_1.0.0.tgz";
url = "https://registry.yarnpkg.com/at-least-node/-/at-least-node-1.0.0.tgz";
sha1 = "602cd4b46e844ad4effc92a8011a3c46e0238dc2";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "balanced_match___balanced_match_1.0.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "balanced_match___balanced_match_1.0.2.tgz";
url = "https://registry.yarnpkg.com/balanced-match/-/balanced-match-1.0.2.tgz";
sha1 = "e83e3a7e3f300b34cb9d87f615fa0cbf357690ee";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "base64_js___base64_js_1.5.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "base64_js___base64_js_1.5.1.tgz";
url = "https://registry.yarnpkg.com/base64-js/-/base64-js-1.5.1.tgz";
sha1 = "1b1b440160a5bf7ad40b650f095963481903930a";
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 = "basic_auth___basic_auth_2.0.1.tgz";
path = fetchurl {
name = "basic_auth___basic_auth_2.0.1.tgz";
url = "https://registry.yarnpkg.com/basic-auth/-/basic-auth-2.0.1.tgz";
sha1 = "b998279bf47ce38344b4f3cf916d4679bbf51e3a";
};
}
grafana-image-renderer: 2.1.0 -> 3.0.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.0
2021-06-07 21:38:04 +00:00
{
name = "binary_extensions___binary_extensions_2.2.0.tgz";
path = fetchurl {
name = "binary_extensions___binary_extensions_2.2.0.tgz";
url = "https://registry.yarnpkg.com/binary-extensions/-/binary-extensions-2.2.0.tgz";
sha1 = "75f502eeaf9ffde42fc98829645be4ea76bd9e2d";
};
}
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 = "bintrees___bintrees_1.0.1.tgz";
path = fetchurl {
name = "bintrees___bintrees_1.0.1.tgz";
url = "https://registry.yarnpkg.com/bintrees/-/bintrees-1.0.1.tgz";
sha1 = "0e655c9b9c2435eaab68bf4027226d2b55a34524";
};
}
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
{
name = "bl___bl_4.1.0.tgz";
path = fetchurl {
name = "bl___bl_4.1.0.tgz";
url = "https://registry.yarnpkg.com/bl/-/bl-4.1.0.tgz";
sha1 = "451535264182bec2fbbc83a62ab98cf11d9f7b3a";
};
}
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 = "body_parser___body_parser_1.19.0.tgz";
path = fetchurl {
name = "body_parser___body_parser_1.19.0.tgz";
url = "https://registry.yarnpkg.com/body-parser/-/body-parser-1.19.0.tgz";
sha1 = "96b2709e57c9c4e09a6fd66a8fd979844f69f08a";
};
}
{
name = "brace_expansion___brace_expansion_1.1.11.tgz";
path = fetchurl {
name = "brace_expansion___brace_expansion_1.1.11.tgz";
url = "https://registry.yarnpkg.com/brace-expansion/-/brace-expansion-1.1.11.tgz";
sha1 = "3c7fcbf529d87226f3d2f52b966ff5271eb441dd";
};
}
{
name = "braces___braces_3.0.2.tgz";
path = fetchurl {
name = "braces___braces_3.0.2.tgz";
url = "https://registry.yarnpkg.com/braces/-/braces-3.0.2.tgz";
sha1 = "3454e1a462ee8d599e236df336cd9ea4f8afe107";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "buffer_crc32___buffer_crc32_0.2.13.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "buffer_crc32___buffer_crc32_0.2.13.tgz";
url = "https://registry.yarnpkg.com/buffer-crc32/-/buffer-crc32-0.2.13.tgz";
sha1 = "0d333e3f00eac50aa1454abd30ef8c2a5d9a7242";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "buffer___buffer_5.7.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "buffer___buffer_5.7.1.tgz";
url = "https://registry.yarnpkg.com/buffer/-/buffer-5.7.1.tgz";
sha1 = "ba62e7c13133053582197160851a8f648e99eed0";
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 = "bytes___bytes_3.1.0.tgz";
path = fetchurl {
name = "bytes___bytes_3.1.0.tgz";
url = "https://registry.yarnpkg.com/bytes/-/bytes-3.1.0.tgz";
sha1 = "f6cf7933a360e0588fa9fde85651cdc7f805d1f6";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "call_bind___call_bind_1.0.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "call_bind___call_bind_1.0.2.tgz";
url = "https://registry.yarnpkg.com/call-bind/-/call-bind-1.0.2.tgz";
sha1 = "b1d4e89e688119c3c9a903ad30abb2f6a919be3c";
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
};
}
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
{
name = "callsites___callsites_3.1.0.tgz";
path = fetchurl {
name = "callsites___callsites_3.1.0.tgz";
url = "https://registry.yarnpkg.com/callsites/-/callsites-3.1.0.tgz";
sha1 = "b3630abd8943432f54b3f0519238e33cd7df2f73";
};
}
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 = "chalk___chalk_2.4.2.tgz";
path = fetchurl {
name = "chalk___chalk_2.4.2.tgz";
url = "https://registry.yarnpkg.com/chalk/-/chalk-2.4.2.tgz";
sha1 = "cd42541677a54333cf541a49108c1432b44c9424";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "chalk___chalk_4.1.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "chalk___chalk_4.1.2.tgz";
url = "https://registry.yarnpkg.com/chalk/-/chalk-4.1.2.tgz";
sha1 = "aac4e2b7734a740867aeb16bf02aad556a1e7a01";
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
};
}
grafana-image-renderer: 2.1.0 -> 3.0.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.0
2021-06-07 21:38:04 +00:00
{
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
name = "chokidar___chokidar_3.5.2.tgz";
grafana-image-renderer: 2.1.0 -> 3.0.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.0
2021-06-07 21:38:04 +00:00
path = fetchurl {
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
name = "chokidar___chokidar_3.5.2.tgz";
url = "https://registry.yarnpkg.com/chokidar/-/chokidar-3.5.2.tgz";
sha1 = "dba3976fcadb016f66fd365021d91600d01c1e75";
grafana-image-renderer: 2.1.0 -> 3.0.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.0
2021-06-07 21:38:04 +00:00
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "chownr___chownr_1.1.4.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "chownr___chownr_1.1.4.tgz";
url = "https://registry.yarnpkg.com/chownr/-/chownr-1.1.4.tgz";
sha1 = "6fc9d7b42d32a583596337666e7d08084da2cc6b";
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
};
}
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 = "ci_info___ci_info_2.0.0.tgz";
path = fetchurl {
name = "ci_info___ci_info_2.0.0.tgz";
url = "https://registry.yarnpkg.com/ci-info/-/ci-info-2.0.0.tgz";
sha1 = "67a9e964be31a51e15e5010d58e6f12834002f46";
};
}
{
name = "clean_stack___clean_stack_2.2.0.tgz";
path = fetchurl {
name = "clean_stack___clean_stack_2.2.0.tgz";
url = "https://registry.yarnpkg.com/clean-stack/-/clean-stack-2.2.0.tgz";
sha1 = "ee8472dbb129e727b31e8a10a427dee9dfe4008b";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "cli_cursor___cli_cursor_3.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "cli_cursor___cli_cursor_3.1.0.tgz";
url = "https://registry.yarnpkg.com/cli-cursor/-/cli-cursor-3.1.0.tgz";
sha1 = "264305a7ae490d1d03bf0c9ba7c925d1753af307";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "cli_truncate___cli_truncate_2.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "cli_truncate___cli_truncate_2.1.0.tgz";
url = "https://registry.yarnpkg.com/cli-truncate/-/cli-truncate-2.1.0.tgz";
sha1 = "c39e28bf05edcde5be3b98992a22deed5a2b93c7";
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
};
}
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
{
name = "cliui___cliui_7.0.4.tgz";
path = fetchurl {
name = "cliui___cliui_7.0.4.tgz";
url = "https://registry.yarnpkg.com/cliui/-/cliui-7.0.4.tgz";
sha1 = "a0265ee655476fc807aea9df3df8df7783808b4f";
};
}
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 = "code_point_at___code_point_at_1.1.0.tgz";
path = fetchurl {
name = "code_point_at___code_point_at_1.1.0.tgz";
url = "https://registry.yarnpkg.com/code-point-at/-/code-point-at-1.1.0.tgz";
sha1 = "0d070b4d043a5bea33a2f1a40e2edb3d9a4ccf77";
};
}
{
name = "color_convert___color_convert_1.9.3.tgz";
path = fetchurl {
name = "color_convert___color_convert_1.9.3.tgz";
url = "https://registry.yarnpkg.com/color-convert/-/color-convert-1.9.3.tgz";
sha1 = "bb71850690e1f136567de629d2d5471deda4c1e8";
};
}
{
name = "color_convert___color_convert_2.0.1.tgz";
path = fetchurl {
name = "color_convert___color_convert_2.0.1.tgz";
url = "https://registry.yarnpkg.com/color-convert/-/color-convert-2.0.1.tgz";
sha1 = "72d3a68d598c9bdb3af2ad1e84f21d896abd4de3";
};
}
{
name = "color_name___color_name_1.1.3.tgz";
path = fetchurl {
name = "color_name___color_name_1.1.3.tgz";
url = "https://registry.yarnpkg.com/color-name/-/color-name-1.1.3.tgz";
sha1 = "a7d0558bd89c42f795dd42328f740831ca53bc25";
};
}
{
name = "color_name___color_name_1.1.4.tgz";
path = fetchurl {
name = "color_name___color_name_1.1.4.tgz";
url = "https://registry.yarnpkg.com/color-name/-/color-name-1.1.4.tgz";
sha1 = "c2a09a87acbde69543de6f63fa3995c826c536a2";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "color_string___color_string_1.6.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "color_string___color_string_1.6.0.tgz";
url = "https://registry.yarnpkg.com/color-string/-/color-string-1.6.0.tgz";
sha1 = "c3915f61fe267672cb7e1e064c9d692219f6c312";
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 = "color___color_3.0.0.tgz";
path = fetchurl {
name = "color___color_3.0.0.tgz";
url = "https://registry.yarnpkg.com/color/-/color-3.0.0.tgz";
sha1 = "d920b4328d534a3ac8295d68f7bd4ba6c427be9a";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "colorette___colorette_1.4.0.tgz";
path = fetchurl {
name = "colorette___colorette_1.4.0.tgz";
url = "https://registry.yarnpkg.com/colorette/-/colorette-1.4.0.tgz";
sha1 = "5190fbb87276259a86ad700bff2c6d6faa3fca40";
};
}
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 = "colors___colors_1.4.0.tgz";
path = fetchurl {
name = "colors___colors_1.4.0.tgz";
url = "https://registry.yarnpkg.com/colors/-/colors-1.4.0.tgz";
sha1 = "c50491479d4c1bdaed2c9ced32cf7c7dc2360f78";
};
}
{
name = "colorspace___colorspace_1.1.2.tgz";
path = fetchurl {
name = "colorspace___colorspace_1.1.2.tgz";
url = "https://registry.yarnpkg.com/colorspace/-/colorspace-1.1.2.tgz";
sha1 = "e0128950d082b86a2168580796a0aa5d6c68d8c5";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "commander___commander_8.2.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "commander___commander_8.2.0.tgz";
url = "https://registry.yarnpkg.com/commander/-/commander-8.2.0.tgz";
sha1 = "37fe2bde301d87d47a53adeff8b5915db1381ca8";
};
}
{
name = "comment_parser___comment_parser_1.1.2.tgz";
path = fetchurl {
name = "comment_parser___comment_parser_1.1.2.tgz";
url = "https://registry.yarnpkg.com/comment-parser/-/comment-parser-1.1.2.tgz";
sha1 = "e5317d7a2ec22b470dcb54a29b25426c30bf39d8";
};
}
{
name = "comment_parser___comment_parser_1.2.4.tgz";
path = fetchurl {
name = "comment_parser___comment_parser_1.2.4.tgz";
url = "https://registry.yarnpkg.com/comment-parser/-/comment-parser-1.2.4.tgz";
sha1 = "489f3ee55dfd184a6e4bffb31baba284453cb760";
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
};
}
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
{
name = "compare_versions___compare_versions_3.6.0.tgz";
path = fetchurl {
name = "compare_versions___compare_versions_3.6.0.tgz";
url = "https://registry.yarnpkg.com/compare-versions/-/compare-versions-3.6.0.tgz";
sha1 = "1a5689913685e5a87637b8d3ffca75514ec41d62";
};
}
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 = "concat_map___concat_map_0.0.1.tgz";
path = fetchurl {
name = "concat_map___concat_map_0.0.1.tgz";
url = "https://registry.yarnpkg.com/concat-map/-/concat-map-0.0.1.tgz";
sha1 = "d8a96bd77fd68df7793a73036a3ba0d5405d477b";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "console_control_strings___console_control_strings_1.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "console_control_strings___console_control_strings_1.1.0.tgz";
url = "https://registry.yarnpkg.com/console-control-strings/-/console-control-strings-1.1.0.tgz";
sha1 = "3d7cf4464db6446ea644bf4b39507f9851008e8e";
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 = "content_disposition___content_disposition_0.5.3.tgz";
path = fetchurl {
name = "content_disposition___content_disposition_0.5.3.tgz";
url = "https://registry.yarnpkg.com/content-disposition/-/content-disposition-0.5.3.tgz";
sha1 = "e130caf7e7279087c5616c2007d0485698984fbd";
};
}
{
name = "content_type___content_type_1.0.4.tgz";
path = fetchurl {
name = "content_type___content_type_1.0.4.tgz";
url = "https://registry.yarnpkg.com/content-type/-/content-type-1.0.4.tgz";
sha1 = "e138cc75e040c727b1966fe5e5f8c9aee256fe3b";
};
}
{
name = "cookie_signature___cookie_signature_1.0.6.tgz";
path = fetchurl {
name = "cookie_signature___cookie_signature_1.0.6.tgz";
url = "https://registry.yarnpkg.com/cookie-signature/-/cookie-signature-1.0.6.tgz";
sha1 = "e303a882b342cc3ee8ca513a79999734dab3ae2c";
};
}
{
name = "cookie___cookie_0.4.0.tgz";
path = fetchurl {
name = "cookie___cookie_0.4.0.tgz";
url = "https://registry.yarnpkg.com/cookie/-/cookie-0.4.0.tgz";
sha1 = "beb437e7022b3b6d49019d088665303ebe9c14ba";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "core_util_is___core_util_is_1.0.3.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "core_util_is___core_util_is_1.0.3.tgz";
url = "https://registry.yarnpkg.com/core-util-is/-/core-util-is-1.0.3.tgz";
sha1 = "a6042d3634c2b27e9328f837b965fac83808db85";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "cosmiconfig___cosmiconfig_7.0.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "cosmiconfig___cosmiconfig_7.0.1.tgz";
url = "https://registry.yarnpkg.com/cosmiconfig/-/cosmiconfig-7.0.1.tgz";
sha1 = "714d756522cace867867ccb4474c5d01bbae5d6d";
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
};
}
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
{
name = "cross_spawn___cross_spawn_7.0.3.tgz";
path = fetchurl {
name = "cross_spawn___cross_spawn_7.0.3.tgz";
url = "https://registry.yarnpkg.com/cross-spawn/-/cross-spawn-7.0.3.tgz";
sha1 = "f73a85b9d5d41d045551c177e2882d4ac85728a6";
};
}
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 = "debug___debug_2.6.9.tgz";
path = fetchurl {
name = "debug___debug_2.6.9.tgz";
url = "https://registry.yarnpkg.com/debug/-/debug-2.6.9.tgz";
sha1 = "5d128515df134ff327e90a4c93f4e077a536341f";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "debug___debug_4.3.2.tgz";
path = fetchurl {
name = "debug___debug_4.3.2.tgz";
url = "https://registry.yarnpkg.com/debug/-/debug-4.3.2.tgz";
sha1 = "f0a49c18ac8779e31d4a0c6029dfb76873c7428b";
};
}
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
{
name = "debug___debug_4.3.1.tgz";
path = fetchurl {
name = "debug___debug_4.3.1.tgz";
url = "https://registry.yarnpkg.com/debug/-/debug-4.3.1.tgz";
sha1 = "f0d229c505e0c6d8c49ac553d1b13dc183f6b2ee";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "decompress_response___decompress_response_4.2.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "decompress_response___decompress_response_4.2.1.tgz";
url = "https://registry.yarnpkg.com/decompress-response/-/decompress-response-4.2.1.tgz";
sha1 = "414023cc7a302da25ce2ec82d0d5238ccafd8986";
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
};
}
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
{
name = "deep_extend___deep_extend_0.6.0.tgz";
path = fetchurl {
name = "deep_extend___deep_extend_0.6.0.tgz";
url = "https://registry.yarnpkg.com/deep-extend/-/deep-extend-0.6.0.tgz";
sha1 = "c4fa7c95404a17a9c3e8ca7e1537312b736330ac";
};
}
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
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "deep_is___deep_is_0.1.4.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "deep_is___deep_is_0.1.4.tgz";
url = "https://registry.yarnpkg.com/deep-is/-/deep-is-0.1.4.tgz";
sha1 = "a6f2dce612fadd2ef1f519b73551f17e85199831";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "define_properties___define_properties_1.1.3.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "define_properties___define_properties_1.1.3.tgz";
url = "https://registry.yarnpkg.com/define-properties/-/define-properties-1.1.3.tgz";
sha1 = "cf88da6cbee26fe6db7094f61d870cbd84cee9f1";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "delegates___delegates_1.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "delegates___delegates_1.0.0.tgz";
url = "https://registry.yarnpkg.com/delegates/-/delegates-1.0.0.tgz";
sha1 = "84c6e159b81904fdca59a0ef44cd870d31250f9a";
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 = "depd___depd_1.1.2.tgz";
path = fetchurl {
name = "depd___depd_1.1.2.tgz";
url = "https://registry.yarnpkg.com/depd/-/depd-1.1.2.tgz";
sha1 = "9bcd52e14c097763e749b274c4346ed2e560b5a9";
};
}
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
{
name = "depd___depd_2.0.0.tgz";
path = fetchurl {
name = "depd___depd_2.0.0.tgz";
url = "https://registry.yarnpkg.com/depd/-/depd-2.0.0.tgz";
sha1 = "b696163cc757560d09cf22cc8fad1571b79e76df";
};
}
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 = "destroy___destroy_1.0.4.tgz";
path = fetchurl {
name = "destroy___destroy_1.0.4.tgz";
url = "https://registry.yarnpkg.com/destroy/-/destroy-1.0.4.tgz";
sha1 = "978857442c44749e4206613e37946205826abd80";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "detect_libc___detect_libc_1.0.3.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "detect_libc___detect_libc_1.0.3.tgz";
url = "https://registry.yarnpkg.com/detect-libc/-/detect-libc-1.0.3.tgz";
sha1 = "fa137c4bd698edf55cd5cd02ac559f91a4c4ba9b";
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
};
}
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "devtools_protocol___devtools_protocol_0.0.901419.tgz";
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "devtools_protocol___devtools_protocol_0.0.901419.tgz";
url = "https://registry.yarnpkg.com/devtools-protocol/-/devtools-protocol-0.0.901419.tgz";
sha1 = "79b5459c48fe7e1c5563c02bd72f8fec3e0cebcd";
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
};
}
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 = "dir_glob___dir_glob_3.0.1.tgz";
path = fetchurl {
name = "dir_glob___dir_glob_3.0.1.tgz";
url = "https://registry.yarnpkg.com/dir-glob/-/dir-glob-3.0.1.tgz";
sha1 = "56dbf73d992a4a93ba1584f4534063fd2e41717f";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "doctrine___doctrine_2.1.0.tgz";
path = fetchurl {
name = "doctrine___doctrine_2.1.0.tgz";
url = "https://registry.yarnpkg.com/doctrine/-/doctrine-2.1.0.tgz";
sha1 = "5cd01fc101621b42c4cd7f5d1a66243716d3f39d";
};
}
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
{
name = "doctrine___doctrine_3.0.0.tgz";
path = fetchurl {
name = "doctrine___doctrine_3.0.0.tgz";
url = "https://registry.yarnpkg.com/doctrine/-/doctrine-3.0.0.tgz";
sha1 = "addebead72a6574db783639dc87a121773973961";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "duplexer___duplexer_0.1.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "duplexer___duplexer_0.1.2.tgz";
url = "https://registry.yarnpkg.com/duplexer/-/duplexer-0.1.2.tgz";
sha1 = "3abe43aef3835f8ae077d136ddce0f276b0400e6";
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 = "ee_first___ee_first_1.1.1.tgz";
path = fetchurl {
name = "ee_first___ee_first_1.1.1.tgz";
url = "https://registry.yarnpkg.com/ee-first/-/ee-first-1.1.1.tgz";
sha1 = "590c61156b0ae2f4f0255732a158b266bc56b21d";
};
}
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
{
name = "emoji_regex___emoji_regex_8.0.0.tgz";
path = fetchurl {
name = "emoji_regex___emoji_regex_8.0.0.tgz";
url = "https://registry.yarnpkg.com/emoji-regex/-/emoji-regex-8.0.0.tgz";
sha1 = "e818fd69ce5ccfcb404594f842963bf53164cc37";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "enabled___enabled_2.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "enabled___enabled_2.0.0.tgz";
url = "https://registry.yarnpkg.com/enabled/-/enabled-2.0.0.tgz";
sha1 = "f9dd92ec2d6f4bbc0d5d1e64e21d61cd4665e7c2";
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 = "encodeurl___encodeurl_1.0.2.tgz";
path = fetchurl {
name = "encodeurl___encodeurl_1.0.2.tgz";
url = "https://registry.yarnpkg.com/encodeurl/-/encodeurl-1.0.2.tgz";
sha1 = "ad3ff4c86ec2d029322f5a02c3a9a606c95b3f59";
};
}
{
name = "end_of_stream___end_of_stream_1.4.4.tgz";
path = fetchurl {
name = "end_of_stream___end_of_stream_1.4.4.tgz";
url = "https://registry.yarnpkg.com/end-of-stream/-/end-of-stream-1.4.4.tgz";
sha1 = "5ae64a5f45057baf3626ec14da0ca5e4b2431eb0";
};
}
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
{
name = "enquirer___enquirer_2.3.6.tgz";
path = fetchurl {
name = "enquirer___enquirer_2.3.6.tgz";
url = "https://registry.yarnpkg.com/enquirer/-/enquirer-2.3.6.tgz";
sha1 = "2a7fe5dd634a1e4125a975ec994ff5456dc3734d";
};
}
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 = "error_ex___error_ex_1.3.2.tgz";
path = fetchurl {
name = "error_ex___error_ex_1.3.2.tgz";
url = "https://registry.yarnpkg.com/error-ex/-/error-ex-1.3.2.tgz";
sha1 = "b4ac40648107fdcdcfae242f428bea8a14d4f1bf";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "es_abstract___es_abstract_1.19.1.tgz";
path = fetchurl {
name = "es_abstract___es_abstract_1.19.1.tgz";
url = "https://registry.yarnpkg.com/es-abstract/-/es-abstract-1.19.1.tgz";
sha1 = "d4885796876916959de78edaa0df456627115ec3";
};
}
{
name = "es_to_primitive___es_to_primitive_1.2.1.tgz";
path = fetchurl {
name = "es_to_primitive___es_to_primitive_1.2.1.tgz";
url = "https://registry.yarnpkg.com/es-to-primitive/-/es-to-primitive-1.2.1.tgz";
sha1 = "e55cd4c9cdc188bcefb03b366c736323fc5c898a";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "escalade___escalade_3.1.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "escalade___escalade_3.1.1.tgz";
url = "https://registry.yarnpkg.com/escalade/-/escalade-3.1.1.tgz";
sha1 = "d8cfdc7000965c5a0174b4a82eaa5c0552742e40";
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 = "escape_html___escape_html_1.0.3.tgz";
path = fetchurl {
name = "escape_html___escape_html_1.0.3.tgz";
url = "https://registry.yarnpkg.com/escape-html/-/escape-html-1.0.3.tgz";
sha1 = "0258eae4d3d0c0974de1c169188ef0051d1d1988";
};
}
{
name = "escape_string_regexp___escape_string_regexp_1.0.5.tgz";
path = fetchurl {
name = "escape_string_regexp___escape_string_regexp_1.0.5.tgz";
url = "https://registry.yarnpkg.com/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz";
sha1 = "1b61c0562190a8dff6ae3bb2cf0200ca130b86d4";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "escape_string_regexp___escape_string_regexp_4.0.0.tgz";
path = fetchurl {
name = "escape_string_regexp___escape_string_regexp_4.0.0.tgz";
url = "https://registry.yarnpkg.com/escape-string-regexp/-/escape-string-regexp-4.0.0.tgz";
sha1 = "14ba83a5d373e3d311e5afca29cf5bfad965bf34";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "escodegen___escodegen_2.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "escodegen___escodegen_2.0.0.tgz";
url = "https://registry.yarnpkg.com/escodegen/-/escodegen-2.0.0.tgz";
sha1 = "5e32b12833e8aa8fa35e1bf0befa89380484c7dd";
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
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "eslint_config_prettier___eslint_config_prettier_7.2.0.tgz";
path = fetchurl {
name = "eslint_config_prettier___eslint_config_prettier_7.2.0.tgz";
url = "https://registry.yarnpkg.com/eslint-config-prettier/-/eslint-config-prettier-7.2.0.tgz";
sha1 = "f4a4bd2832e810e8cc7c1411ec85b3e85c0c53f9";
};
}
{
name = "eslint_config_prettier___eslint_config_prettier_8.3.0.tgz";
path = fetchurl {
name = "eslint_config_prettier___eslint_config_prettier_8.3.0.tgz";
url = "https://registry.yarnpkg.com/eslint-config-prettier/-/eslint-config-prettier-8.3.0.tgz";
sha1 = "f7471b20b6fe8a9a9254cc684454202886a2dd7a";
};
}
{
name = "eslint_plugin_jsdoc___eslint_plugin_jsdoc_31.6.1.tgz";
path = fetchurl {
name = "eslint_plugin_jsdoc___eslint_plugin_jsdoc_31.6.1.tgz";
url = "https://registry.yarnpkg.com/eslint-plugin-jsdoc/-/eslint-plugin-jsdoc-31.6.1.tgz";
sha1 = "98040c801500572fff71c984a097d89946f1e450";
};
}
{
grafana-image-renderer: 3.2.1 -> 3.3.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.3.0
2021-11-21 16:18:57 +00:00
name = "eslint_plugin_jsdoc___eslint_plugin_jsdoc_36.1.0.tgz";
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
path = fetchurl {
grafana-image-renderer: 3.2.1 -> 3.3.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.3.0
2021-11-21 16:18:57 +00:00
name = "eslint_plugin_jsdoc___eslint_plugin_jsdoc_36.1.0.tgz";
url = "https://registry.yarnpkg.com/eslint-plugin-jsdoc/-/eslint-plugin-jsdoc-36.1.0.tgz";
sha1 = "8dfe5f27edfb6aa3812e6d86ccaea849ddc86b03";
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
};
}
{
name = "eslint_plugin_prettier___eslint_plugin_prettier_3.3.1.tgz";
path = fetchurl {
name = "eslint_plugin_prettier___eslint_plugin_prettier_3.3.1.tgz";
url = "https://registry.yarnpkg.com/eslint-plugin-prettier/-/eslint-plugin-prettier-3.3.1.tgz";
sha1 = "7079cfa2497078905011e6f82e8dd8453d1371b7";
};
}
{
name = "eslint_plugin_prettier___eslint_plugin_prettier_4.0.0.tgz";
path = fetchurl {
name = "eslint_plugin_prettier___eslint_plugin_prettier_4.0.0.tgz";
url = "https://registry.yarnpkg.com/eslint-plugin-prettier/-/eslint-plugin-prettier-4.0.0.tgz";
sha1 = "8b99d1e4b8b24a762472b4567992023619cb98e0";
};
}
{
name = "eslint_plugin_react_hooks___eslint_plugin_react_hooks_4.2.0.tgz";
path = fetchurl {
name = "eslint_plugin_react_hooks___eslint_plugin_react_hooks_4.2.0.tgz";
url = "https://registry.yarnpkg.com/eslint-plugin-react-hooks/-/eslint-plugin-react-hooks-4.2.0.tgz";
sha1 = "8c229c268d468956334c943bb45fc860280f5556";
};
}
{
name = "eslint_plugin_react___eslint_plugin_react_7.22.0.tgz";
path = fetchurl {
name = "eslint_plugin_react___eslint_plugin_react_7.22.0.tgz";
url = "https://registry.yarnpkg.com/eslint-plugin-react/-/eslint-plugin-react-7.22.0.tgz";
sha1 = "3d1c542d1d3169c45421c1215d9470e341707269";
};
}
{
name = "eslint_plugin_react___eslint_plugin_react_7.26.1.tgz";
path = fetchurl {
name = "eslint_plugin_react___eslint_plugin_react_7.26.1.tgz";
url = "https://registry.yarnpkg.com/eslint-plugin-react/-/eslint-plugin-react-7.26.1.tgz";
sha1 = "41bcfe3e39e6a5ac040971c1af94437c80daa40e";
};
}
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
{
name = "eslint_scope___eslint_scope_5.1.1.tgz";
path = fetchurl {
name = "eslint_scope___eslint_scope_5.1.1.tgz";
url = "https://registry.yarnpkg.com/eslint-scope/-/eslint-scope-5.1.1.tgz";
sha1 = "e786e59a66cb92b3f6c1fb0d508aab174848f48c";
};
}
{
name = "eslint_utils___eslint_utils_2.1.0.tgz";
path = fetchurl {
name = "eslint_utils___eslint_utils_2.1.0.tgz";
url = "https://registry.yarnpkg.com/eslint-utils/-/eslint-utils-2.1.0.tgz";
sha1 = "d2de5e03424e707dc10c74068ddedae708741b27";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "eslint_utils___eslint_utils_3.0.0.tgz";
path = fetchurl {
name = "eslint_utils___eslint_utils_3.0.0.tgz";
url = "https://registry.yarnpkg.com/eslint-utils/-/eslint-utils-3.0.0.tgz";
sha1 = "8aebaface7345bb33559db0a1f13a1d2d48c3672";
};
}
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
{
name = "eslint_visitor_keys___eslint_visitor_keys_1.3.0.tgz";
path = fetchurl {
name = "eslint_visitor_keys___eslint_visitor_keys_1.3.0.tgz";
url = "https://registry.yarnpkg.com/eslint-visitor-keys/-/eslint-visitor-keys-1.3.0.tgz";
sha1 = "30ebd1ef7c2fdff01c3a4f151044af25fab0523e";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "eslint_visitor_keys___eslint_visitor_keys_2.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "eslint_visitor_keys___eslint_visitor_keys_2.1.0.tgz";
url = "https://registry.yarnpkg.com/eslint-visitor-keys/-/eslint-visitor-keys-2.1.0.tgz";
sha1 = "f65328259305927392c938ed44eb0a5c9b2bd303";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "eslint___eslint_7.21.0.tgz";
path = fetchurl {
name = "eslint___eslint_7.21.0.tgz";
url = "https://registry.yarnpkg.com/eslint/-/eslint-7.21.0.tgz";
sha1 = "4ecd5b8c5b44f5dedc9b8a110b01bbfeb15d1c83";
};
}
{
name = "eslint___eslint_7.32.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "eslint___eslint_7.32.0.tgz";
url = "https://registry.yarnpkg.com/eslint/-/eslint-7.32.0.tgz";
sha1 = "c6d328a14be3fb08c8d1d21e12c02fdb7a2a812d";
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
};
}
{
name = "espree___espree_7.3.1.tgz";
path = fetchurl {
name = "espree___espree_7.3.1.tgz";
url = "https://registry.yarnpkg.com/espree/-/espree-7.3.1.tgz";
sha1 = "f2df330b752c6f55019f8bd89b7660039c1bbbb6";
};
}
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 = "esprima___esprima_4.0.1.tgz";
path = fetchurl {
name = "esprima___esprima_4.0.1.tgz";
url = "https://registry.yarnpkg.com/esprima/-/esprima-4.0.1.tgz";
sha1 = "13b04cdb3e6c5d19df91ab6987a8695619b0aa71";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "esquery___esquery_1.4.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "esquery___esquery_1.4.0.tgz";
url = "https://registry.yarnpkg.com/esquery/-/esquery-1.4.0.tgz";
sha1 = "2148ffc38b82e8c7057dfed48425b3e61f0f24a5";
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
};
}
{
name = "esrecurse___esrecurse_4.3.0.tgz";
path = fetchurl {
name = "esrecurse___esrecurse_4.3.0.tgz";
url = "https://registry.yarnpkg.com/esrecurse/-/esrecurse-4.3.0.tgz";
sha1 = "7ad7964d679abb28bee72cec63758b1c5d2c9921";
};
}
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 = "estraverse___estraverse_4.3.0.tgz";
path = fetchurl {
name = "estraverse___estraverse_4.3.0.tgz";
url = "https://registry.yarnpkg.com/estraverse/-/estraverse-4.3.0.tgz";
sha1 = "398ad3f3c5a24948be7725e83d11a7de28cdbd1d";
};
}
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
{
name = "estraverse___estraverse_5.2.0.tgz";
path = fetchurl {
name = "estraverse___estraverse_5.2.0.tgz";
url = "https://registry.yarnpkg.com/estraverse/-/estraverse-5.2.0.tgz";
sha1 = "307df42547e6cc7324d3cf03c155d5cdb8c53880";
};
}
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 = "esutils___esutils_2.0.3.tgz";
path = fetchurl {
name = "esutils___esutils_2.0.3.tgz";
url = "https://registry.yarnpkg.com/esutils/-/esutils-2.0.3.tgz";
sha1 = "74d2eb4de0b8da1293711910d50775b9b710ef64";
};
}
{
name = "etag___etag_1.8.1.tgz";
path = fetchurl {
name = "etag___etag_1.8.1.tgz";
url = "https://registry.yarnpkg.com/etag/-/etag-1.8.1.tgz";
sha1 = "41ae2eeb65efa62268aebfea83ac7d79299b0887";
};
}
{
name = "event_stream___event_stream_3.3.4.tgz";
path = fetchurl {
name = "event_stream___event_stream_3.3.4.tgz";
url = "https://registry.yarnpkg.com/event-stream/-/event-stream-3.3.4.tgz";
sha1 = "4ab4c9a0f5a54db9338b4c34d86bfce8f4b35571";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "execa___execa_5.1.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "execa___execa_5.1.1.tgz";
url = "https://registry.yarnpkg.com/execa/-/execa-5.1.1.tgz";
sha1 = "f80ad9cbf4298f7bd1d4c9555c21e93741c411dd";
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 = "expand_template___expand_template_2.0.3.tgz";
path = fetchurl {
name = "expand_template___expand_template_2.0.3.tgz";
url = "https://registry.yarnpkg.com/expand-template/-/expand-template-2.0.3.tgz";
sha1 = "6e14b3fcee0f3a6340ecb57d2e8918692052a47c";
};
}
{
name = "express_prom_bundle___express_prom_bundle_5.1.5.tgz";
path = fetchurl {
name = "express_prom_bundle___express_prom_bundle_5.1.5.tgz";
url = "https://registry.yarnpkg.com/express-prom-bundle/-/express-prom-bundle-5.1.5.tgz";
sha1 = "f298615879299a58cf8ec1350186f4de91d91fa4";
};
}
{
name = "express___express_4.17.1.tgz";
path = fetchurl {
name = "express___express_4.17.1.tgz";
url = "https://registry.yarnpkg.com/express/-/express-4.17.1.tgz";
sha1 = "4491fc38605cf51f8629d39c2b5d026f98a4c134";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "extract_zip___extract_zip_2.0.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "extract_zip___extract_zip_2.0.1.tgz";
url = "https://registry.yarnpkg.com/extract-zip/-/extract-zip-2.0.1.tgz";
sha1 = "663dca56fe46df890d5f131ef4a06d22bb8ba13a";
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
};
}
{
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
name = "fast_deep_equal___fast_deep_equal_3.1.3.tgz";
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
path = fetchurl {
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
name = "fast_deep_equal___fast_deep_equal_3.1.3.tgz";
url = "https://registry.yarnpkg.com/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz";
sha1 = "3a7d56b559d6cbc3eb512325244e619a65c6c525";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "fast_diff___fast_diff_1.2.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "fast_diff___fast_diff_1.2.0.tgz";
url = "https://registry.yarnpkg.com/fast-diff/-/fast-diff-1.2.0.tgz";
sha1 = "73ee11982d86caaf7959828d519cfe927fac5f03";
};
}
{
name = "fast_glob___fast_glob_3.2.7.tgz";
path = fetchurl {
name = "fast_glob___fast_glob_3.2.7.tgz";
url = "https://registry.yarnpkg.com/fast-glob/-/fast-glob-3.2.7.tgz";
sha1 = "fd6cb7a2d7e9aa7a7846111e85a196d6b2f766a1";
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 = "fast_json_stable_stringify___fast_json_stable_stringify_2.1.0.tgz";
path = fetchurl {
name = "fast_json_stable_stringify___fast_json_stable_stringify_2.1.0.tgz";
url = "https://registry.yarnpkg.com/fast-json-stable-stringify/-/fast-json-stable-stringify-2.1.0.tgz";
sha1 = "874bf69c6f404c2b5d99c481341399fd55892633";
};
}
{
name = "fast_levenshtein___fast_levenshtein_2.0.6.tgz";
path = fetchurl {
name = "fast_levenshtein___fast_levenshtein_2.0.6.tgz";
url = "https://registry.yarnpkg.com/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz";
sha1 = "3d8a5c66883a16a30ca8643e851f19baa7797917";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "fastq___fastq_1.13.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "fastq___fastq_1.13.0.tgz";
url = "https://registry.yarnpkg.com/fastq/-/fastq-1.13.0.tgz";
sha1 = "616760f88a7526bdfc596b7cab8c18938c36b98c";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "fd_slicer___fd_slicer_1.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "fd_slicer___fd_slicer_1.1.0.tgz";
url = "https://registry.yarnpkg.com/fd-slicer/-/fd-slicer-1.1.0.tgz";
sha1 = "25c7c89cb1f9077f8891bbe61d8f390eae256f1e";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "fecha___fecha_4.2.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "fecha___fecha_4.2.1.tgz";
url = "https://registry.yarnpkg.com/fecha/-/fecha-4.2.1.tgz";
sha1 = "0a83ad8f86ef62a091e22bb5a039cd03d23eecce";
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
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "file_entry_cache___file_entry_cache_6.0.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "file_entry_cache___file_entry_cache_6.0.1.tgz";
url = "https://registry.yarnpkg.com/file-entry-cache/-/file-entry-cache-6.0.1.tgz";
sha1 = "211b2dd9659cb0394b073e7323ac3c933d522027";
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
};
}
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 = "fill_range___fill_range_7.0.1.tgz";
path = fetchurl {
name = "fill_range___fill_range_7.0.1.tgz";
url = "https://registry.yarnpkg.com/fill-range/-/fill-range-7.0.1.tgz";
sha1 = "1919a6a7c75fe38b2c7c77e5198535da9acdda40";
};
}
{
name = "finalhandler___finalhandler_1.1.2.tgz";
path = fetchurl {
name = "finalhandler___finalhandler_1.1.2.tgz";
url = "https://registry.yarnpkg.com/finalhandler/-/finalhandler-1.1.2.tgz";
sha1 = "b7e7d000ffd11938d0fdb053506f6ebabe9f587d";
};
}
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
{
name = "find_up___find_up_4.1.0.tgz";
path = fetchurl {
name = "find_up___find_up_4.1.0.tgz";
url = "https://registry.yarnpkg.com/find-up/-/find-up-4.1.0.tgz";
sha1 = "97afe7d6cdc0bc5928584b7c8d7b16e8a9aa5d19";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "find_up___find_up_5.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "find_up___find_up_5.0.0.tgz";
url = "https://registry.yarnpkg.com/find-up/-/find-up-5.0.0.tgz";
sha1 = "4c92819ecb7083561e4f4a240a86be5198f536fc";
};
}
{
name = "find_versions___find_versions_4.0.0.tgz";
path = fetchurl {
name = "find_versions___find_versions_4.0.0.tgz";
url = "https://registry.yarnpkg.com/find-versions/-/find-versions-4.0.0.tgz";
sha1 = "3c57e573bf97769b8cb8df16934b627915da4965";
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
};
}
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
{
name = "flat_cache___flat_cache_3.0.4.tgz";
path = fetchurl {
name = "flat_cache___flat_cache_3.0.4.tgz";
url = "https://registry.yarnpkg.com/flat-cache/-/flat-cache-3.0.4.tgz";
sha1 = "61b0338302b2fe9f957dcc32fc2a87f1c3048b11";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "flatted___flatted_3.2.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "flatted___flatted_3.2.2.tgz";
url = "https://registry.yarnpkg.com/flatted/-/flatted-3.2.2.tgz";
sha1 = "64bfed5cb68fe3ca78b3eb214ad97b63bedce561";
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
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "fn.name___fn.name_1.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "fn.name___fn.name_1.1.0.tgz";
url = "https://registry.yarnpkg.com/fn.name/-/fn.name-1.1.0.tgz";
sha1 = "26cad8017967aea8731bc42961d04a3d5988accc";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "forwarded___forwarded_0.2.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "forwarded___forwarded_0.2.0.tgz";
url = "https://registry.yarnpkg.com/forwarded/-/forwarded-0.2.0.tgz";
sha1 = "2269936428aad4c15c7ebe9779a84bf0b2a81811";
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 = "fresh___fresh_0.5.2.tgz";
path = fetchurl {
name = "fresh___fresh_0.5.2.tgz";
url = "https://registry.yarnpkg.com/fresh/-/fresh-0.5.2.tgz";
sha1 = "3d8cadd90d976569fa835ab1f8e4b23a105605a7";
};
}
{
name = "from2___from2_2.3.0.tgz";
path = fetchurl {
name = "from2___from2_2.3.0.tgz";
url = "https://registry.yarnpkg.com/from2/-/from2-2.3.0.tgz";
sha1 = "8bfb5502bde4a4d36cfdeea007fcca21d7e382af";
};
}
{
name = "from___from_0.1.7.tgz";
path = fetchurl {
name = "from___from_0.1.7.tgz";
url = "https://registry.yarnpkg.com/from/-/from-0.1.7.tgz";
sha1 = "83c60afc58b9c56997007ed1a768b3ab303a44fe";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "fs_constants___fs_constants_1.0.0.tgz";
path = fetchurl {
name = "fs_constants___fs_constants_1.0.0.tgz";
url = "https://registry.yarnpkg.com/fs-constants/-/fs-constants-1.0.0.tgz";
sha1 = "6be0de9be998ce16af8afc24497b9ee9b7ccd9ad";
};
}
{
name = "fs_extra___fs_extra_9.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "fs_extra___fs_extra_9.1.0.tgz";
url = "https://registry.yarnpkg.com/fs-extra/-/fs-extra-9.1.0.tgz";
sha1 = "5954460c764a8da2094ba3554bf839e6b9a7c86d";
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 = "fs.realpath___fs.realpath_1.0.0.tgz";
path = fetchurl {
name = "fs.realpath___fs.realpath_1.0.0.tgz";
url = "https://registry.yarnpkg.com/fs.realpath/-/fs.realpath-1.0.0.tgz";
sha1 = "1504ad2523158caa40db4a2787cb01411994ea4f";
};
}
grafana-image-renderer: 2.1.0 -> 3.0.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.0
2021-06-07 21:38:04 +00:00
{
name = "fsevents___fsevents_2.3.2.tgz";
path = fetchurl {
name = "fsevents___fsevents_2.3.2.tgz";
url = "https://registry.yarnpkg.com/fsevents/-/fsevents-2.3.2.tgz";
sha1 = "8a526f78b8fdf4623b709e0b975c52c24c02fd1a";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "function_bind___function_bind_1.1.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "function_bind___function_bind_1.1.1.tgz";
url = "https://registry.yarnpkg.com/function-bind/-/function-bind-1.1.1.tgz";
sha1 = "a56899d3ea3c9bab874bb9773b7c5ede92f4895d";
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
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "functional_red_black_tree___functional_red_black_tree_1.0.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "functional_red_black_tree___functional_red_black_tree_1.0.1.tgz";
url = "https://registry.yarnpkg.com/functional-red-black-tree/-/functional-red-black-tree-1.0.1.tgz";
sha1 = "1b0ab3bd553b2a0d6399d29c0e3ea0b252078327";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "gauge___gauge_2.7.4.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "gauge___gauge_2.7.4.tgz";
url = "https://registry.yarnpkg.com/gauge/-/gauge-2.7.4.tgz";
sha1 = "2c03405c7538c39d7eb37b317022e325fb018bf7";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "get_caller_file___get_caller_file_2.0.5.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "get_caller_file___get_caller_file_2.0.5.tgz";
url = "https://registry.yarnpkg.com/get-caller-file/-/get-caller-file-2.0.5.tgz";
sha1 = "4f94412a82db32f36e3b0b9741f8a97feb031f7e";
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
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "get_intrinsic___get_intrinsic_1.1.1.tgz";
path = fetchurl {
name = "get_intrinsic___get_intrinsic_1.1.1.tgz";
url = "https://registry.yarnpkg.com/get-intrinsic/-/get-intrinsic-1.1.1.tgz";
sha1 = "15f59f376f855c446963948f0d24cd3637b4abc6";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "get_own_enumerable_property_symbols___get_own_enumerable_property_symbols_3.0.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "get_own_enumerable_property_symbols___get_own_enumerable_property_symbols_3.0.2.tgz";
url = "https://registry.yarnpkg.com/get-own-enumerable-property-symbols/-/get-own-enumerable-property-symbols-3.0.2.tgz";
sha1 = "b5fde77f22cbe35f390b4e089922c50bce6ef664";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "get_stream___get_stream_5.2.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "get_stream___get_stream_5.2.0.tgz";
url = "https://registry.yarnpkg.com/get-stream/-/get-stream-5.2.0.tgz";
sha1 = "4966a1795ee5ace65e706c4b7beb71257d6e22d3";
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
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "get_stream___get_stream_6.0.1.tgz";
path = fetchurl {
name = "get_stream___get_stream_6.0.1.tgz";
url = "https://registry.yarnpkg.com/get-stream/-/get-stream-6.0.1.tgz";
sha1 = "a262d8eef67aced57c2852ad6167526a43cbf7b7";
};
}
{
name = "get_symbol_description___get_symbol_description_1.0.0.tgz";
path = fetchurl {
name = "get_symbol_description___get_symbol_description_1.0.0.tgz";
url = "https://registry.yarnpkg.com/get-symbol-description/-/get-symbol-description-1.0.0.tgz";
sha1 = "7fdb81c900101fbd564dd5f1a30af5aadc1e58d6";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "github_from_package___github_from_package_0.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "github_from_package___github_from_package_0.0.0.tgz";
url = "https://registry.yarnpkg.com/github-from-package/-/github-from-package-0.0.0.tgz";
sha1 = "97fb5d96bfde8973313f20e8288ef9a167fa64ce";
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
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "glob_parent___glob_parent_5.1.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "glob_parent___glob_parent_5.1.2.tgz";
url = "https://registry.yarnpkg.com/glob-parent/-/glob-parent-5.1.2.tgz";
sha1 = "869832c58034fe68a4093c17dc15e8340d8401c4";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "glob___glob_7.2.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "glob___glob_7.2.0.tgz";
url = "https://registry.yarnpkg.com/glob/-/glob-7.2.0.tgz";
sha1 = "d15535af7732e02e948f4c41628bd910293f6023";
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
};
}
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
{
name = "globals___globals_12.4.0.tgz";
path = fetchurl {
name = "globals___globals_12.4.0.tgz";
url = "https://registry.yarnpkg.com/globals/-/globals-12.4.0.tgz";
sha1 = "a18813576a41b00a24a97e7f815918c2e19925f8";
};
}
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "globals___globals_13.11.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "globals___globals_13.11.0.tgz";
url = "https://registry.yarnpkg.com/globals/-/globals-13.11.0.tgz";
sha1 = "40ef678da117fe7bd2e28f1fab24951bd0255be7";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "globby___globby_11.0.4.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "globby___globby_11.0.4.tgz";
url = "https://registry.yarnpkg.com/globby/-/globby-11.0.4.tgz";
sha1 = "2cbaff77c2f2a62e71e9b2813a67b97a3a3001a5";
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 = "google_protobuf___google_protobuf_3.5.0.tgz";
path = fetchurl {
name = "google_protobuf___google_protobuf_3.5.0.tgz";
url = "https://registry.yarnpkg.com/google-protobuf/-/google-protobuf-3.5.0.tgz";
sha1 = "b8cc63c74d83457bd8a9a904503c8efb26bca339";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "graceful_fs___graceful_fs_4.2.8.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "graceful_fs___graceful_fs_4.2.8.tgz";
url = "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-4.2.8.tgz";
sha1 = "e412b8d33f5e006593cbd3cee6df9f2cebbe802a";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "has_bigints___has_bigints_1.0.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "has_bigints___has_bigints_1.0.1.tgz";
url = "https://registry.yarnpkg.com/has-bigints/-/has-bigints-1.0.1.tgz";
sha1 = "64fe6acb020673e3b78db035a5af69aa9d07b113";
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 = "has_flag___has_flag_3.0.0.tgz";
path = fetchurl {
name = "has_flag___has_flag_3.0.0.tgz";
url = "https://registry.yarnpkg.com/has-flag/-/has-flag-3.0.0.tgz";
sha1 = "b5d454dc2199ae225699f3467e5a07f3b955bafd";
};
}
{
name = "has_flag___has_flag_4.0.0.tgz";
path = fetchurl {
name = "has_flag___has_flag_4.0.0.tgz";
url = "https://registry.yarnpkg.com/has-flag/-/has-flag-4.0.0.tgz";
sha1 = "944771fd9c81c81265c4d6941860da06bb59479b";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "has_symbols___has_symbols_1.0.2.tgz";
path = fetchurl {
name = "has_symbols___has_symbols_1.0.2.tgz";
url = "https://registry.yarnpkg.com/has-symbols/-/has-symbols-1.0.2.tgz";
sha1 = "165d3070c00309752a1236a479331e3ac56f1423";
};
}
{
name = "has_tostringtag___has_tostringtag_1.0.0.tgz";
path = fetchurl {
name = "has_tostringtag___has_tostringtag_1.0.0.tgz";
url = "https://registry.yarnpkg.com/has-tostringtag/-/has-tostringtag-1.0.0.tgz";
sha1 = "7e133818a7d394734f941e73c3d3f9291e658b25";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "has_unicode___has_unicode_2.0.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "has_unicode___has_unicode_2.0.1.tgz";
url = "https://registry.yarnpkg.com/has-unicode/-/has-unicode-2.0.1.tgz";
sha1 = "e0e6fe6a28cf51138855e086d1691e771de2a8b9";
};
}
{
name = "has___has_1.0.3.tgz";
path = fetchurl {
name = "has___has_1.0.3.tgz";
url = "https://registry.yarnpkg.com/has/-/has-1.0.3.tgz";
sha1 = "722d7cbfc1f6aa8241f16dd814e011e1f41e8796";
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 = "http_errors___http_errors_1.7.2.tgz";
path = fetchurl {
name = "http_errors___http_errors_1.7.2.tgz";
url = "https://registry.yarnpkg.com/http-errors/-/http-errors-1.7.2.tgz";
sha1 = "4f5029cf13239f31036e5b2e55292bcfbcc85c8f";
};
}
{
name = "http_errors___http_errors_1.7.3.tgz";
path = fetchurl {
name = "http_errors___http_errors_1.7.3.tgz";
url = "https://registry.yarnpkg.com/http-errors/-/http-errors-1.7.3.tgz";
sha1 = "6c619e4f9c60308c38519498c14fbb10aacebb06";
};
}
{
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
name = "https_proxy_agent___https_proxy_agent_5.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
name = "https_proxy_agent___https_proxy_agent_5.0.0.tgz";
url = "https://registry.yarnpkg.com/https-proxy-agent/-/https-proxy-agent-5.0.0.tgz";
sha1 = "e2a90542abb68a762e0a0850f6c9edadfd8506b2";
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
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "human_signals___human_signals_2.1.0.tgz";
path = fetchurl {
name = "human_signals___human_signals_2.1.0.tgz";
url = "https://registry.yarnpkg.com/human-signals/-/human-signals-2.1.0.tgz";
sha1 = "dc91fcba42e4d06e4abaed33b3e7a3c02f514ea0";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "husky___husky_4.3.8.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "husky___husky_4.3.8.tgz";
url = "https://registry.yarnpkg.com/husky/-/husky-4.3.8.tgz";
sha1 = "31144060be963fd6850e5cc8f019a1dfe194296d";
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 = "iconv_lite___iconv_lite_0.4.24.tgz";
path = fetchurl {
name = "iconv_lite___iconv_lite_0.4.24.tgz";
url = "https://registry.yarnpkg.com/iconv-lite/-/iconv-lite-0.4.24.tgz";
sha1 = "2022b4b25fbddc21d2f524974a474aafe733908b";
};
}
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
{
name = "ieee754___ieee754_1.2.1.tgz";
path = fetchurl {
name = "ieee754___ieee754_1.2.1.tgz";
url = "https://registry.yarnpkg.com/ieee754/-/ieee754-1.2.1.tgz";
sha1 = "8eb7a10a63fff25d15a57b001586d177d1b0d352";
};
}
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
{
name = "ignore___ignore_4.0.6.tgz";
path = fetchurl {
name = "ignore___ignore_4.0.6.tgz";
url = "https://registry.yarnpkg.com/ignore/-/ignore-4.0.6.tgz";
sha1 = "750e3db5862087b4737ebac8207ffd1ef27b25fc";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "ignore___ignore_5.1.8.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "ignore___ignore_5.1.8.tgz";
url = "https://registry.yarnpkg.com/ignore/-/ignore-5.1.8.tgz";
sha1 = "f150a8b50a34289b33e22f5889abd4d8016f0e57";
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
};
}
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
{
name = "import_fresh___import_fresh_3.3.0.tgz";
path = fetchurl {
name = "import_fresh___import_fresh_3.3.0.tgz";
url = "https://registry.yarnpkg.com/import-fresh/-/import-fresh-3.3.0.tgz";
sha1 = "37162c25fcb9ebaa2e6e53d5b4d88ce17d9e0c2b";
};
}
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 = "imurmurhash___imurmurhash_0.1.4.tgz";
path = fetchurl {
name = "imurmurhash___imurmurhash_0.1.4.tgz";
url = "https://registry.yarnpkg.com/imurmurhash/-/imurmurhash-0.1.4.tgz";
sha1 = "9218b9b2b928a238b13dc4fb6b6d576f231453ea";
};
}
{
name = "indent_string___indent_string_4.0.0.tgz";
path = fetchurl {
name = "indent_string___indent_string_4.0.0.tgz";
url = "https://registry.yarnpkg.com/indent-string/-/indent-string-4.0.0.tgz";
sha1 = "624f8f4497d619b2d9768531d58f4122854d7251";
};
}
{
name = "inflight___inflight_1.0.6.tgz";
path = fetchurl {
name = "inflight___inflight_1.0.6.tgz";
url = "https://registry.yarnpkg.com/inflight/-/inflight-1.0.6.tgz";
sha1 = "49bd6331d7d02d0c09bc910a1075ba8165b56df9";
};
}
{
name = "inherits___inherits_2.0.4.tgz";
path = fetchurl {
name = "inherits___inherits_2.0.4.tgz";
url = "https://registry.yarnpkg.com/inherits/-/inherits-2.0.4.tgz";
sha1 = "0fa2c64f932917c3433a0ded55363aae37416b7c";
};
}
{
name = "inherits___inherits_2.0.3.tgz";
path = fetchurl {
name = "inherits___inherits_2.0.3.tgz";
url = "https://registry.yarnpkg.com/inherits/-/inherits-2.0.3.tgz";
sha1 = "633c2c83e3da42a502f52466022480f4208261de";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "ini___ini_1.3.8.tgz";
path = fetchurl {
name = "ini___ini_1.3.8.tgz";
url = "https://registry.yarnpkg.com/ini/-/ini-1.3.8.tgz";
sha1 = "a29da425b48806f34767a4efce397269af28432c";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "internal_slot___internal_slot_1.0.3.tgz";
path = fetchurl {
name = "internal_slot___internal_slot_1.0.3.tgz";
url = "https://registry.yarnpkg.com/internal-slot/-/internal-slot-1.0.3.tgz";
sha1 = "7347e307deeea2faac2ac6205d4bc7d34967f59c";
};
}
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
{
name = "into_stream___into_stream_6.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "into_stream___into_stream_6.0.0.tgz";
url = "https://registry.yarnpkg.com/into-stream/-/into-stream-6.0.0.tgz";
sha1 = "4bfc1244c0128224e18b8870e85b2de8e66c6702";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "ipaddr.js___ipaddr.js_1.9.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "ipaddr.js___ipaddr.js_1.9.1.tgz";
url = "https://registry.yarnpkg.com/ipaddr.js/-/ipaddr.js-1.9.1.tgz";
sha1 = "bff38543eeb8984825079ff3a2a8e6cbd46781b3";
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 = "is_arrayish___is_arrayish_0.2.1.tgz";
path = fetchurl {
name = "is_arrayish___is_arrayish_0.2.1.tgz";
url = "https://registry.yarnpkg.com/is-arrayish/-/is-arrayish-0.2.1.tgz";
sha1 = "77c99840527aa8ecb1a8ba697b80645a7a926a9d";
};
}
{
name = "is_arrayish___is_arrayish_0.3.2.tgz";
path = fetchurl {
name = "is_arrayish___is_arrayish_0.3.2.tgz";
url = "https://registry.yarnpkg.com/is-arrayish/-/is-arrayish-0.3.2.tgz";
sha1 = "4574a2ae56f7ab206896fb431eaeed066fdf8f03";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "is_bigint___is_bigint_1.0.4.tgz";
path = fetchurl {
name = "is_bigint___is_bigint_1.0.4.tgz";
url = "https://registry.yarnpkg.com/is-bigint/-/is-bigint-1.0.4.tgz";
sha1 = "08147a1875bc2b32005d41ccd8291dffc6691df3";
};
}
grafana-image-renderer: 2.1.0 -> 3.0.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.0
2021-06-07 21:38:04 +00:00
{
name = "is_binary_path___is_binary_path_2.1.0.tgz";
path = fetchurl {
name = "is_binary_path___is_binary_path_2.1.0.tgz";
url = "https://registry.yarnpkg.com/is-binary-path/-/is-binary-path-2.1.0.tgz";
sha1 = "ea1f7f3b80f064236e83470f86c09c254fb45b09";
};
}
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_boolean_object___is_boolean_object_1.1.2.tgz";
path = fetchurl {
name = "is_boolean_object___is_boolean_object_1.1.2.tgz";
url = "https://registry.yarnpkg.com/is-boolean-object/-/is-boolean-object-1.1.2.tgz";
sha1 = "5c6dc200246dd9321ae4b885a114bb1f75f63719";
};
}
{
name = "is_callable___is_callable_1.2.4.tgz";
path = fetchurl {
name = "is_callable___is_callable_1.2.4.tgz";
url = "https://registry.yarnpkg.com/is-callable/-/is-callable-1.2.4.tgz";
sha1 = "47301d58dd0259407865547853df6d61fe471945";
};
}
{
name = "is_core_module___is_core_module_2.7.0.tgz";
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_core_module___is_core_module_2.7.0.tgz";
url = "https://registry.yarnpkg.com/is-core-module/-/is-core-module-2.7.0.tgz";
sha1 = "3c0ef7d31b4acfc574f80c58409d568a836848e3";
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
};
}
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
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_date_object___is_date_object_1.0.5.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_date_object___is_date_object_1.0.5.tgz";
url = "https://registry.yarnpkg.com/is-date-object/-/is-date-object-1.0.5.tgz";
sha1 = "0841d5536e724c25597bf6ea62e1bd38298df31f";
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 = "is_extglob___is_extglob_2.1.1.tgz";
path = fetchurl {
name = "is_extglob___is_extglob_2.1.1.tgz";
url = "https://registry.yarnpkg.com/is-extglob/-/is-extglob-2.1.1.tgz";
sha1 = "a88c02535791f02ed37c76a1b9ea9773c833f8c2";
};
}
{
name = "is_fullwidth_code_point___is_fullwidth_code_point_1.0.0.tgz";
path = fetchurl {
name = "is_fullwidth_code_point___is_fullwidth_code_point_1.0.0.tgz";
url = "https://registry.yarnpkg.com/is-fullwidth-code-point/-/is-fullwidth-code-point-1.0.0.tgz";
sha1 = "ef9e31386f031a7f0d643af82fde50c457ef00cb";
};
}
{
name = "is_fullwidth_code_point___is_fullwidth_code_point_2.0.0.tgz";
path = fetchurl {
name = "is_fullwidth_code_point___is_fullwidth_code_point_2.0.0.tgz";
url = "https://registry.yarnpkg.com/is-fullwidth-code-point/-/is-fullwidth-code-point-2.0.0.tgz";
sha1 = "a3b30a5c4f199183167aaab93beefae3ddfb654f";
};
}
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
{
name = "is_fullwidth_code_point___is_fullwidth_code_point_3.0.0.tgz";
path = fetchurl {
name = "is_fullwidth_code_point___is_fullwidth_code_point_3.0.0.tgz";
url = "https://registry.yarnpkg.com/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz";
sha1 = "f116f8064fe90b3f7844a38997c0b75051269f1d";
};
}
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
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_glob___is_glob_4.0.3.tgz";
path = fetchurl {
name = "is_glob___is_glob_4.0.3.tgz";
url = "https://registry.yarnpkg.com/is-glob/-/is-glob-4.0.3.tgz";
sha1 = "64f61e42cbbb2eec2071a9dac0b28ba1e65d5084";
};
}
{
name = "is_negative_zero___is_negative_zero_2.0.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_negative_zero___is_negative_zero_2.0.1.tgz";
url = "https://registry.yarnpkg.com/is-negative-zero/-/is-negative-zero-2.0.1.tgz";
sha1 = "3de746c18dda2319241a53675908d8f766f11c24";
};
}
{
name = "is_number_object___is_number_object_1.0.6.tgz";
path = fetchurl {
name = "is_number_object___is_number_object_1.0.6.tgz";
url = "https://registry.yarnpkg.com/is-number-object/-/is-number-object-1.0.6.tgz";
sha1 = "6a7aaf838c7f0686a50b4553f7e54a96494e89f0";
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 = "is_number___is_number_7.0.0.tgz";
path = fetchurl {
name = "is_number___is_number_7.0.0.tgz";
url = "https://registry.yarnpkg.com/is-number/-/is-number-7.0.0.tgz";
sha1 = "7535345b896734d5f80c4d06c50955527a14f12b";
};
}
{
name = "is_obj___is_obj_1.0.1.tgz";
path = fetchurl {
name = "is_obj___is_obj_1.0.1.tgz";
url = "https://registry.yarnpkg.com/is-obj/-/is-obj-1.0.1.tgz";
sha1 = "3e4729ac1f5fde025cd7d83a896dab9f4f67db0f";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_regex___is_regex_1.1.4.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_regex___is_regex_1.1.4.tgz";
url = "https://registry.yarnpkg.com/is-regex/-/is-regex-1.1.4.tgz";
sha1 = "eef5663cd59fa4c0ae339505323df6854bb15958";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_regexp___is_regexp_1.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_regexp___is_regexp_1.0.0.tgz";
url = "https://registry.yarnpkg.com/is-regexp/-/is-regexp-1.0.0.tgz";
sha1 = "fd2d883545c46bac5a633e7b9a09e87fa2cb5069";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_shared_array_buffer___is_shared_array_buffer_1.0.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_shared_array_buffer___is_shared_array_buffer_1.0.1.tgz";
url = "https://registry.yarnpkg.com/is-shared-array-buffer/-/is-shared-array-buffer-1.0.1.tgz";
sha1 = "97b0c85fbdacb59c9c446fe653b82cf2b5b7cfe6";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_stream___is_stream_2.0.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_stream___is_stream_2.0.1.tgz";
url = "https://registry.yarnpkg.com/is-stream/-/is-stream-2.0.1.tgz";
sha1 = "fac1e3d53b97ad5a9d0ae9cef2389f5810a5c077";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_string___is_string_1.0.7.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_string___is_string_1.0.7.tgz";
url = "https://registry.yarnpkg.com/is-string/-/is-string-1.0.7.tgz";
sha1 = "0dd12bf2006f255bb58f695110eff7491eebc0fd";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_symbol___is_symbol_1.0.4.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_symbol___is_symbol_1.0.4.tgz";
url = "https://registry.yarnpkg.com/is-symbol/-/is-symbol-1.0.4.tgz";
sha1 = "a6dac93b635b063ca6872236de88910a57af139c";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_weakref___is_weakref_1.0.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "is_weakref___is_weakref_1.0.1.tgz";
url = "https://registry.yarnpkg.com/is-weakref/-/is-weakref-1.0.1.tgz";
sha1 = "842dba4ec17fa9ac9850df2d6efbc1737274f2a2";
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 = "isarray___isarray_1.0.0.tgz";
path = fetchurl {
name = "isarray___isarray_1.0.0.tgz";
url = "https://registry.yarnpkg.com/isarray/-/isarray-1.0.0.tgz";
sha1 = "bb935d48582cba168c06834957a54a3e07124f11";
};
}
{
name = "isexe___isexe_2.0.0.tgz";
path = fetchurl {
name = "isexe___isexe_2.0.0.tgz";
url = "https://registry.yarnpkg.com/isexe/-/isexe-2.0.0.tgz";
sha1 = "e8fbf374dc556ff8947a10dcb0572d633f2cfa10";
};
}
{
name = "js_tokens___js_tokens_4.0.0.tgz";
path = fetchurl {
name = "js_tokens___js_tokens_4.0.0.tgz";
url = "https://registry.yarnpkg.com/js-tokens/-/js-tokens-4.0.0.tgz";
sha1 = "19203fb59991df98e3a287050d4647cdeaf32499";
};
}
{
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
name = "js_yaml___js_yaml_3.14.1.tgz";
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
path = fetchurl {
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
name = "js_yaml___js_yaml_3.14.1.tgz";
url = "https://registry.yarnpkg.com/js-yaml/-/js-yaml-3.14.1.tgz";
sha1 = "dae812fdb3825fa306609a8717383c50c36a0537";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "jsdoc_type_pratt_parser___jsdoc_type_pratt_parser_1.1.1.tgz";
path = fetchurl {
name = "jsdoc_type_pratt_parser___jsdoc_type_pratt_parser_1.1.1.tgz";
url = "https://registry.yarnpkg.com/jsdoc-type-pratt-parser/-/jsdoc-type-pratt-parser-1.1.1.tgz";
sha1 = "10fe5e409ba38de22a48b555598955a26ff0160f";
};
}
{
name = "jsdoc_type_pratt_parser___jsdoc_type_pratt_parser_1.2.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "jsdoc_type_pratt_parser___jsdoc_type_pratt_parser_1.2.0.tgz";
url = "https://registry.yarnpkg.com/jsdoc-type-pratt-parser/-/jsdoc-type-pratt-parser-1.2.0.tgz";
sha1 = "3482a3833b74a88c95a6ba7253f0c0de3b77b9f5";
};
}
{
name = "jsdoctypeparser___jsdoctypeparser_9.0.0.tgz";
path = fetchurl {
name = "jsdoctypeparser___jsdoctypeparser_9.0.0.tgz";
url = "https://registry.yarnpkg.com/jsdoctypeparser/-/jsdoctypeparser-9.0.0.tgz";
sha1 = "8c97e2fb69315eb274b0f01377eaa5c940bd7b26";
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
};
}
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
{
name = "json_parse_even_better_errors___json_parse_even_better_errors_2.3.1.tgz";
path = fetchurl {
name = "json_parse_even_better_errors___json_parse_even_better_errors_2.3.1.tgz";
url = "https://registry.yarnpkg.com/json-parse-even-better-errors/-/json-parse-even-better-errors-2.3.1.tgz";
sha1 = "7c47805a94319928e05777405dc12e1f7a4ee02d";
};
}
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 = "json_schema_traverse___json_schema_traverse_0.4.1.tgz";
path = fetchurl {
name = "json_schema_traverse___json_schema_traverse_0.4.1.tgz";
url = "https://registry.yarnpkg.com/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz";
sha1 = "69f6a87d9513ab8bb8fe63bdb0979c448e684660";
};
}
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
{
name = "json_schema_traverse___json_schema_traverse_1.0.0.tgz";
path = fetchurl {
name = "json_schema_traverse___json_schema_traverse_1.0.0.tgz";
url = "https://registry.yarnpkg.com/json-schema-traverse/-/json-schema-traverse-1.0.0.tgz";
sha1 = "ae7bcb3656ab77a73ba5c49bf654f38e6b6860e2";
};
}
{
name = "json_stable_stringify_without_jsonify___json_stable_stringify_without_jsonify_1.0.1.tgz";
path = fetchurl {
name = "json_stable_stringify_without_jsonify___json_stable_stringify_without_jsonify_1.0.1.tgz";
url = "https://registry.yarnpkg.com/json-stable-stringify-without-jsonify/-/json-stable-stringify-without-jsonify-1.0.1.tgz";
sha1 = "9db7b59496ad3f3cfef30a75142d2d930ad72651";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "jsonfile___jsonfile_6.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "jsonfile___jsonfile_6.1.0.tgz";
url = "https://registry.yarnpkg.com/jsonfile/-/jsonfile-6.1.0.tgz";
sha1 = "bc55b2634793c679ec6403094eb13698a6ec0aae";
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
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "jsx_ast_utils___jsx_ast_utils_3.2.1.tgz";
path = fetchurl {
name = "jsx_ast_utils___jsx_ast_utils_3.2.1.tgz";
url = "https://registry.yarnpkg.com/jsx-ast-utils/-/jsx-ast-utils-3.2.1.tgz";
sha1 = "720b97bfe7d901b927d87c3773637ae8ea48781b";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "kuler___kuler_2.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "kuler___kuler_2.0.0.tgz";
url = "https://registry.yarnpkg.com/kuler/-/kuler-2.0.0.tgz";
sha1 = "e2c570a3800388fb44407e851531c1d670b061b3";
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
};
}
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
{
name = "levn___levn_0.4.1.tgz";
path = fetchurl {
name = "levn___levn_0.4.1.tgz";
url = "https://registry.yarnpkg.com/levn/-/levn-0.4.1.tgz";
sha1 = "ae4562c007473b932a6200d403268dd2fffc6ade";
};
}
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 = "levn___levn_0.3.0.tgz";
path = fetchurl {
name = "levn___levn_0.3.0.tgz";
url = "https://registry.yarnpkg.com/levn/-/levn-0.3.0.tgz";
sha1 = "3b09924edf9f083c0490fdd4c0bc4421e04764ee";
};
}
{
name = "lines_and_columns___lines_and_columns_1.1.6.tgz";
path = fetchurl {
name = "lines_and_columns___lines_and_columns_1.1.6.tgz";
url = "https://registry.yarnpkg.com/lines-and-columns/-/lines-and-columns-1.1.6.tgz";
sha1 = "1c00c743b433cd0a4e80758f7b64a57440d9ff00";
};
}
{
grafana-image-renderer: 3.2.1 -> 3.3.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.3.0
2021-11-21 16:18:57 +00:00
name = "lint_staged___lint_staged_11.2.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.1 -> 3.3.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.3.0
2021-11-21 16:18:57 +00:00
name = "lint_staged___lint_staged_11.2.0.tgz";
url = "https://registry.yarnpkg.com/lint-staged/-/lint-staged-11.2.0.tgz";
sha1 = "6b9774a74b3eb4bef5c59fb6475bff84d6853008";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "listr2___listr2_3.12.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "listr2___listr2_3.12.2.tgz";
url = "https://registry.yarnpkg.com/listr2/-/listr2-3.12.2.tgz";
sha1 = "2d55cc627111603ad4768a9e87c9c7bb9b49997e";
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
};
}
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
{
name = "locate_path___locate_path_5.0.0.tgz";
path = fetchurl {
name = "locate_path___locate_path_5.0.0.tgz";
url = "https://registry.yarnpkg.com/locate-path/-/locate-path-5.0.0.tgz";
sha1 = "1afba396afd676a6d42504d0a67a3a7eb9f62aa0";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "locate_path___locate_path_6.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "locate_path___locate_path_6.0.0.tgz";
url = "https://registry.yarnpkg.com/locate-path/-/locate-path-6.0.0.tgz";
sha1 = "55321eb309febbc59c4801d931a72452a681d286";
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 = "lodash.camelcase___lodash.camelcase_4.3.0.tgz";
path = fetchurl {
name = "lodash.camelcase___lodash.camelcase_4.3.0.tgz";
url = "https://registry.yarnpkg.com/lodash.camelcase/-/lodash.camelcase-4.3.0.tgz";
sha1 = "b28aa6288a2b9fc651035c7711f65ab6190331a6";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "lodash.clonedeep___lodash.clonedeep_4.5.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "lodash.clonedeep___lodash.clonedeep_4.5.0.tgz";
url = "https://registry.yarnpkg.com/lodash.clonedeep/-/lodash.clonedeep-4.5.0.tgz";
sha1 = "e23f3f9c4f8fbdde872529c1071857a086e5ccef";
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
};
}
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
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "lodash.merge___lodash.merge_4.6.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "lodash.merge___lodash.merge_4.6.2.tgz";
url = "https://registry.yarnpkg.com/lodash.merge/-/lodash.merge-4.6.2.tgz";
sha1 = "558aa53b43b661e1925a0afdfa36a9a1085fe57a";
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
};
}
{
name = "lodash.truncate___lodash.truncate_4.4.2.tgz";
path = fetchurl {
name = "lodash.truncate___lodash.truncate_4.4.2.tgz";
url = "https://registry.yarnpkg.com/lodash.truncate/-/lodash.truncate-4.4.2.tgz";
sha1 = "5a350da0b1113b837ecfffd5812cbe58d6eae193";
};
}
{
name = "lodash___lodash_4.17.21.tgz";
path = fetchurl {
name = "lodash___lodash_4.17.21.tgz";
url = "https://registry.yarnpkg.com/lodash/-/lodash-4.17.21.tgz";
sha1 = "679591c564c3bffaae8454cf0b3df370c3d6911c";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "log_update___log_update_4.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "log_update___log_update_4.0.0.tgz";
url = "https://registry.yarnpkg.com/log-update/-/log-update-4.0.0.tgz";
sha1 = "589ecd352471f2a1c0c570287543a64dfd20e0a1";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "logform___logform_2.3.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "logform___logform_2.3.0.tgz";
url = "https://registry.yarnpkg.com/logform/-/logform-2.3.0.tgz";
sha1 = "a3997a05985de2ebd325ae0d166dffc9c6fe6b57";
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 = "long___long_4.0.0.tgz";
path = fetchurl {
name = "long___long_4.0.0.tgz";
url = "https://registry.yarnpkg.com/long/-/long-4.0.0.tgz";
sha1 = "9a7b71cfb7d361a194ea555241c92f7468d5bf28";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "loose_envify___loose_envify_1.4.0.tgz";
path = fetchurl {
name = "loose_envify___loose_envify_1.4.0.tgz";
url = "https://registry.yarnpkg.com/loose-envify/-/loose-envify-1.4.0.tgz";
sha1 = "71ee51fa7be4caec1a63839f7e682d8132d30caf";
};
}
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
{
name = "lru_cache___lru_cache_6.0.0.tgz";
path = fetchurl {
name = "lru_cache___lru_cache_6.0.0.tgz";
url = "https://registry.yarnpkg.com/lru-cache/-/lru-cache-6.0.0.tgz";
sha1 = "6d6fe6570ebd96aaf90fcad1dafa3b2566db3a94";
};
}
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 = "map_stream___map_stream_0.1.0.tgz";
path = fetchurl {
name = "map_stream___map_stream_0.1.0.tgz";
url = "https://registry.yarnpkg.com/map-stream/-/map-stream-0.1.0.tgz";
sha1 = "e56aa94c4c8055a16404a0674b78f215f7c8e194";
};
}
{
name = "media_typer___media_typer_0.3.0.tgz";
path = fetchurl {
name = "media_typer___media_typer_0.3.0.tgz";
url = "https://registry.yarnpkg.com/media-typer/-/media-typer-0.3.0.tgz";
sha1 = "8710d7af0aa626f8fffa1ce00168545263255748";
};
}
{
name = "merge_descriptors___merge_descriptors_1.0.1.tgz";
path = fetchurl {
name = "merge_descriptors___merge_descriptors_1.0.1.tgz";
url = "https://registry.yarnpkg.com/merge-descriptors/-/merge-descriptors-1.0.1.tgz";
sha1 = "b00aaa556dd8b44568150ec9d1b953f3f90cbb61";
};
}
{
name = "merge_stream___merge_stream_2.0.0.tgz";
path = fetchurl {
name = "merge_stream___merge_stream_2.0.0.tgz";
url = "https://registry.yarnpkg.com/merge-stream/-/merge-stream-2.0.0.tgz";
sha1 = "52823629a14dd00c9770fb6ad47dc6310f2c1f60";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "merge2___merge2_1.4.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "merge2___merge2_1.4.1.tgz";
url = "https://registry.yarnpkg.com/merge2/-/merge2-1.4.1.tgz";
sha1 = "4368892f885e907455a6fd7dc55c0c9d404990ae";
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 = "methods___methods_1.1.2.tgz";
path = fetchurl {
name = "methods___methods_1.1.2.tgz";
url = "https://registry.yarnpkg.com/methods/-/methods-1.1.2.tgz";
sha1 = "5529a4d67654134edcc5266656835b0f851afcee";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "micromatch___micromatch_4.0.4.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "micromatch___micromatch_4.0.4.tgz";
url = "https://registry.yarnpkg.com/micromatch/-/micromatch-4.0.4.tgz";
sha1 = "896d519dfe9db25fce94ceb7a500919bf881ebf9";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "mime_db___mime_db_1.50.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "mime_db___mime_db_1.50.0.tgz";
url = "https://registry.yarnpkg.com/mime-db/-/mime-db-1.50.0.tgz";
sha1 = "abd4ac94e98d3c0e185016c67ab45d5fde40c11f";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "mime_types___mime_types_2.1.33.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "mime_types___mime_types_2.1.33.tgz";
url = "https://registry.yarnpkg.com/mime-types/-/mime-types-2.1.33.tgz";
sha1 = "1fa12a904472fafd068e48d9e8401f74d3f70edb";
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 = "mime___mime_1.6.0.tgz";
path = fetchurl {
name = "mime___mime_1.6.0.tgz";
url = "https://registry.yarnpkg.com/mime/-/mime-1.6.0.tgz";
sha1 = "32cd9e5c64553bd58d19a568af452acff04981b1";
};
}
{
name = "mimic_fn___mimic_fn_2.1.0.tgz";
path = fetchurl {
name = "mimic_fn___mimic_fn_2.1.0.tgz";
url = "https://registry.yarnpkg.com/mimic-fn/-/mimic-fn-2.1.0.tgz";
sha1 = "7ed2c2ccccaf84d3ffcb7a69b57711fc2083401b";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "mimic_response___mimic_response_2.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "mimic_response___mimic_response_2.1.0.tgz";
url = "https://registry.yarnpkg.com/mimic-response/-/mimic-response-2.1.0.tgz";
sha1 = "d13763d35f613d09ec37ebb30bac0469c0ee8f43";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "minimatch___minimatch_3.0.4.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "minimatch___minimatch_3.0.4.tgz";
url = "https://registry.yarnpkg.com/minimatch/-/minimatch-3.0.4.tgz";
sha1 = "5166e286457f03306064be5497e8dbb0c3d32083";
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 = "minimist___minimist_1.2.5.tgz";
path = fetchurl {
name = "minimist___minimist_1.2.5.tgz";
url = "https://registry.yarnpkg.com/minimist/-/minimist-1.2.5.tgz";
sha1 = "67d66014b66a6a8aaa0c083c5fd58df4e4e97602";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "mkdirp_classic___mkdirp_classic_0.5.3.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "mkdirp_classic___mkdirp_classic_0.5.3.tgz";
url = "https://registry.yarnpkg.com/mkdirp-classic/-/mkdirp-classic-0.5.3.tgz";
sha1 = "fa10c9115cc6d8865be221ba47ee9bed78601113";
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
};
}
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
{
name = "mkdirp___mkdirp_0.5.5.tgz";
path = fetchurl {
name = "mkdirp___mkdirp_0.5.5.tgz";
url = "https://registry.yarnpkg.com/mkdirp/-/mkdirp-0.5.5.tgz";
sha1 = "d91cefd62d1436ca0f41620e251288d420099def";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "morgan___morgan_1.10.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "morgan___morgan_1.10.0.tgz";
url = "https://registry.yarnpkg.com/morgan/-/morgan-1.10.0.tgz";
sha1 = "091778abc1fc47cd3509824653dae1faab6b17d7";
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 = "ms___ms_2.0.0.tgz";
path = fetchurl {
name = "ms___ms_2.0.0.tgz";
url = "https://registry.yarnpkg.com/ms/-/ms-2.0.0.tgz";
sha1 = "5608aeadfc00be6c2901df5f9861788de0d597c8";
};
}
{
name = "ms___ms_2.1.1.tgz";
path = fetchurl {
name = "ms___ms_2.1.1.tgz";
url = "https://registry.yarnpkg.com/ms/-/ms-2.1.1.tgz";
sha1 = "30a5864eb3ebb0a66f2ebe6d727af06a09d86e0a";
};
}
{
name = "ms___ms_2.1.2.tgz";
path = fetchurl {
name = "ms___ms_2.1.2.tgz";
url = "https://registry.yarnpkg.com/ms/-/ms-2.1.2.tgz";
sha1 = "d09d1f357b443f493382a8eb3ccd183872ae6009";
};
}
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
{
name = "ms___ms_2.1.3.tgz";
path = fetchurl {
name = "ms___ms_2.1.3.tgz";
url = "https://registry.yarnpkg.com/ms/-/ms-2.1.3.tgz";
sha1 = "574c8138ce1d2b5861f0b44579dbadd60c6615b2";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "multistream___multistream_4.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "multistream___multistream_4.1.0.tgz";
url = "https://registry.yarnpkg.com/multistream/-/multistream-4.1.0.tgz";
sha1 = "7bf00dfd119556fbc153cff3de4c6d477909f5a8";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "napi_build_utils___napi_build_utils_1.0.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "napi_build_utils___napi_build_utils_1.0.2.tgz";
url = "https://registry.yarnpkg.com/napi-build-utils/-/napi-build-utils-1.0.2.tgz";
sha1 = "b1fddc0b2c46e380a0b7a76f984dd47c41a13806";
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
};
}
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
{
name = "natural_compare___natural_compare_1.4.0.tgz";
path = fetchurl {
name = "natural_compare___natural_compare_1.4.0.tgz";
url = "https://registry.yarnpkg.com/natural-compare/-/natural-compare-1.4.0.tgz";
sha1 = "4abebfeed7541f2c27acfb29bdbbd15c8d5ba4f7";
};
}
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 = "negotiator___negotiator_0.6.2.tgz";
path = fetchurl {
name = "negotiator___negotiator_0.6.2.tgz";
url = "https://registry.yarnpkg.com/negotiator/-/negotiator-0.6.2.tgz";
sha1 = "feacf7ccf525a77ae9634436a64883ffeca346fb";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "node_abi___node_abi_2.30.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "node_abi___node_abi_2.30.1.tgz";
url = "https://registry.yarnpkg.com/node-abi/-/node-abi-2.30.1.tgz";
sha1 = "c437d4b1fe0e285aaf290d45b45d4d7afedac4cf";
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 = "node_cleanup___node_cleanup_2.1.2.tgz";
path = fetchurl {
name = "node_cleanup___node_cleanup_2.1.2.tgz";
url = "https://registry.yarnpkg.com/node-cleanup/-/node-cleanup-2.1.2.tgz";
sha1 = "7ac19abd297e09a7f72a71545d951b517e4dde2c";
};
}
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
{
name = "node_fetch___node_fetch_2.6.1.tgz";
path = fetchurl {
name = "node_fetch___node_fetch_2.6.1.tgz";
url = "https://registry.yarnpkg.com/node-fetch/-/node-fetch-2.6.1.tgz";
sha1 = "045bd323631f76ed2e2b55573394416b639a0052";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "node_fetch___node_fetch_2.6.5.tgz";
path = fetchurl {
name = "node_fetch___node_fetch_2.6.5.tgz";
url = "https://registry.yarnpkg.com/node-fetch/-/node-fetch-2.6.5.tgz";
sha1 = "42735537d7f080a7e5f78b6c549b7146be1742fd";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "noop_logger___noop_logger_0.1.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "noop_logger___noop_logger_0.1.1.tgz";
url = "https://registry.yarnpkg.com/noop-logger/-/noop-logger-0.1.1.tgz";
sha1 = "94a2b1633c4f1317553007d8966fd0e841b6a4c2";
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 = "normalize_path___normalize_path_3.0.0.tgz";
path = fetchurl {
name = "normalize_path___normalize_path_3.0.0.tgz";
url = "https://registry.yarnpkg.com/normalize-path/-/normalize-path-3.0.0.tgz";
sha1 = "0dcd69ff23a1c9b11fd0978316644a0388216a65";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "npm_run_path___npm_run_path_4.0.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "npm_run_path___npm_run_path_4.0.1.tgz";
url = "https://registry.yarnpkg.com/npm-run-path/-/npm-run-path-4.0.1.tgz";
sha1 = "b7ecd1e5ed53da8e37a55e1c2269e0b97ed748ea";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "npmlog___npmlog_4.1.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "npmlog___npmlog_4.1.2.tgz";
url = "https://registry.yarnpkg.com/npmlog/-/npmlog-4.1.2.tgz";
sha1 = "08a7f2a8bf734604779a9efa4ad5cc717abb954b";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "number_is_nan___number_is_nan_1.0.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "number_is_nan___number_is_nan_1.0.1.tgz";
url = "https://registry.yarnpkg.com/number-is-nan/-/number-is-nan-1.0.1.tgz";
sha1 = "097b602b53422a522c1afb8790318336941a011d";
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 = "object_assign___object_assign_4.1.1.tgz";
path = fetchurl {
name = "object_assign___object_assign_4.1.1.tgz";
url = "https://registry.yarnpkg.com/object-assign/-/object-assign-4.1.1.tgz";
sha1 = "2109adc7965887cfc05cbbd442cac8bfbb360863";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "object_inspect___object_inspect_1.11.0.tgz";
path = fetchurl {
name = "object_inspect___object_inspect_1.11.0.tgz";
url = "https://registry.yarnpkg.com/object-inspect/-/object-inspect-1.11.0.tgz";
sha1 = "9dceb146cedd4148a0d9e51ab88d34cf509922b1";
};
}
{
name = "object_keys___object_keys_1.1.1.tgz";
path = fetchurl {
name = "object_keys___object_keys_1.1.1.tgz";
url = "https://registry.yarnpkg.com/object-keys/-/object-keys-1.1.1.tgz";
sha1 = "1c47f272df277f3b1daf061677d9c82e2322c60e";
};
}
{
name = "object.assign___object.assign_4.1.2.tgz";
path = fetchurl {
name = "object.assign___object.assign_4.1.2.tgz";
url = "https://registry.yarnpkg.com/object.assign/-/object.assign-4.1.2.tgz";
sha1 = "0ed54a342eceb37b38ff76eb831a0e788cb63940";
};
}
{
name = "object.entries___object.entries_1.1.5.tgz";
path = fetchurl {
name = "object.entries___object.entries_1.1.5.tgz";
url = "https://registry.yarnpkg.com/object.entries/-/object.entries-1.1.5.tgz";
sha1 = "e1acdd17c4de2cd96d5a08487cfb9db84d881861";
};
}
{
name = "object.fromentries___object.fromentries_2.0.5.tgz";
path = fetchurl {
name = "object.fromentries___object.fromentries_2.0.5.tgz";
url = "https://registry.yarnpkg.com/object.fromentries/-/object.fromentries-2.0.5.tgz";
sha1 = "7b37b205109c21e741e605727fe8b0ad5fa08251";
};
}
{
name = "object.hasown___object.hasown_1.1.0.tgz";
path = fetchurl {
name = "object.hasown___object.hasown_1.1.0.tgz";
url = "https://registry.yarnpkg.com/object.hasown/-/object.hasown-1.1.0.tgz";
sha1 = "7232ed266f34d197d15cac5880232f7a4790afe5";
};
}
{
name = "object.values___object.values_1.1.5.tgz";
path = fetchurl {
name = "object.values___object.values_1.1.5.tgz";
url = "https://registry.yarnpkg.com/object.values/-/object.values-1.1.5.tgz";
sha1 = "959f63e3ce9ef108720333082131e4a459b716ac";
};
}
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 = "on_finished___on_finished_2.3.0.tgz";
path = fetchurl {
name = "on_finished___on_finished_2.3.0.tgz";
url = "https://registry.yarnpkg.com/on-finished/-/on-finished-2.3.0.tgz";
sha1 = "20f1336481b083cd75337992a16971aa2d906947";
};
}
{
name = "on_headers___on_headers_1.0.2.tgz";
path = fetchurl {
name = "on_headers___on_headers_1.0.2.tgz";
url = "https://registry.yarnpkg.com/on-headers/-/on-headers-1.0.2.tgz";
sha1 = "772b0ae6aaa525c399e489adfad90c403eb3c28f";
};
}
{
name = "once___once_1.4.0.tgz";
path = fetchurl {
name = "once___once_1.4.0.tgz";
url = "https://registry.yarnpkg.com/once/-/once-1.4.0.tgz";
sha1 = "583b1aa775961d4b113ac17d9c50baef9dd76bd1";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "one_time___one_time_1.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "one_time___one_time_1.0.0.tgz";
url = "https://registry.yarnpkg.com/one-time/-/one-time-1.0.0.tgz";
sha1 = "e06bc174aed214ed58edede573b433bbf827cb45";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "onetime___onetime_5.1.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "onetime___onetime_5.1.2.tgz";
url = "https://registry.yarnpkg.com/onetime/-/onetime-5.1.2.tgz";
sha1 = "d0e96ebb56b07476df1dd9c4806e5237985ca45e";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "opencollective_postinstall___opencollective_postinstall_2.0.3.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "opencollective_postinstall___opencollective_postinstall_2.0.3.tgz";
url = "https://registry.yarnpkg.com/opencollective-postinstall/-/opencollective-postinstall-2.0.3.tgz";
sha1 = "7a0fff978f6dbfa4d006238fbac98ed4198c3259";
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 = "optionator___optionator_0.8.3.tgz";
path = fetchurl {
name = "optionator___optionator_0.8.3.tgz";
url = "https://registry.yarnpkg.com/optionator/-/optionator-0.8.3.tgz";
sha1 = "84fa1d036fe9d3c7e21d99884b601167ec8fb495";
};
}
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
{
name = "optionator___optionator_0.9.1.tgz";
path = fetchurl {
name = "optionator___optionator_0.9.1.tgz";
url = "https://registry.yarnpkg.com/optionator/-/optionator-0.9.1.tgz";
sha1 = "4f236a6373dae0566a6d43e1326674f50c291499";
};
}
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 = "p_is_promise___p_is_promise_3.0.0.tgz";
path = fetchurl {
name = "p_is_promise___p_is_promise_3.0.0.tgz";
url = "https://registry.yarnpkg.com/p-is-promise/-/p-is-promise-3.0.0.tgz";
sha1 = "58e78c7dfe2e163cf2a04ff869e7c1dba64a5971";
};
}
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
{
name = "p_limit___p_limit_2.3.0.tgz";
path = fetchurl {
name = "p_limit___p_limit_2.3.0.tgz";
url = "https://registry.yarnpkg.com/p-limit/-/p-limit-2.3.0.tgz";
sha1 = "3dd33c647a214fdfffd835933eb086da0dc21db1";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "p_limit___p_limit_3.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "p_limit___p_limit_3.1.0.tgz";
url = "https://registry.yarnpkg.com/p-limit/-/p-limit-3.1.0.tgz";
sha1 = "e1daccbe78d0d1388ca18c64fea38e3e57e3706b";
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
};
}
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
{
name = "p_locate___p_locate_4.1.0.tgz";
path = fetchurl {
name = "p_locate___p_locate_4.1.0.tgz";
url = "https://registry.yarnpkg.com/p-locate/-/p-locate-4.1.0.tgz";
sha1 = "a3428bb7088b3a60292f66919278b7c297ad4f07";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "p_locate___p_locate_5.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "p_locate___p_locate_5.0.0.tgz";
url = "https://registry.yarnpkg.com/p-locate/-/p-locate-5.0.0.tgz";
sha1 = "83c8315c6785005e3bd021839411c9e110e6d834";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "p_map___p_map_4.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "p_map___p_map_4.0.0.tgz";
url = "https://registry.yarnpkg.com/p-map/-/p-map-4.0.0.tgz";
sha1 = "bb2f95a5eda2ec168ec9274e06a747c3e2904d2b";
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
};
}
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
{
name = "p_try___p_try_2.2.0.tgz";
path = fetchurl {
name = "p_try___p_try_2.2.0.tgz";
url = "https://registry.yarnpkg.com/p-try/-/p-try-2.2.0.tgz";
sha1 = "cb2868540e313d61de58fafbe35ce9004d5540e6";
};
}
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
{
name = "parent_module___parent_module_1.0.1.tgz";
path = fetchurl {
name = "parent_module___parent_module_1.0.1.tgz";
url = "https://registry.yarnpkg.com/parent-module/-/parent-module-1.0.1.tgz";
sha1 = "691d2709e78c79fae3a156622452d00762caaaa2";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "parse_json___parse_json_5.2.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "parse_json___parse_json_5.2.0.tgz";
url = "https://registry.yarnpkg.com/parse-json/-/parse-json-5.2.0.tgz";
sha1 = "c76fc66dee54231c962b22bcc8a72cf2f99753cd";
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 = "parseurl___parseurl_1.3.3.tgz";
path = fetchurl {
name = "parseurl___parseurl_1.3.3.tgz";
url = "https://registry.yarnpkg.com/parseurl/-/parseurl-1.3.3.tgz";
sha1 = "9da19e7bee8d12dff0513ed5b76957793bc2e8d4";
};
}
{
name = "path_exists___path_exists_4.0.0.tgz";
path = fetchurl {
name = "path_exists___path_exists_4.0.0.tgz";
url = "https://registry.yarnpkg.com/path-exists/-/path-exists-4.0.0.tgz";
sha1 = "513bdbe2d3b95d7762e8c1137efa195c6c61b5b3";
};
}
{
name = "path_is_absolute___path_is_absolute_1.0.1.tgz";
path = fetchurl {
name = "path_is_absolute___path_is_absolute_1.0.1.tgz";
url = "https://registry.yarnpkg.com/path-is-absolute/-/path-is-absolute-1.0.1.tgz";
sha1 = "174b9268735534ffbc7ace6bf53a5a9e1b5c5f5f";
};
}
{
name = "path_key___path_key_3.1.1.tgz";
path = fetchurl {
name = "path_key___path_key_3.1.1.tgz";
url = "https://registry.yarnpkg.com/path-key/-/path-key-3.1.1.tgz";
sha1 = "581f6ade658cbba65a0d3380de7753295054f375";
};
}
{
grafana-image-renderer: 2.1.0 -> 3.0.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.0
2021-06-07 21:38:04 +00:00
name = "path_parse___path_parse_1.0.7.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.1.0 -> 3.0.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.0
2021-06-07 21:38:04 +00:00
name = "path_parse___path_parse_1.0.7.tgz";
url = "https://registry.yarnpkg.com/path-parse/-/path-parse-1.0.7.tgz";
sha1 = "fbc114b60ca42b30d9daf5858e4bd68bbedb6735";
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 = "path_to_regexp___path_to_regexp_0.1.7.tgz";
path = fetchurl {
name = "path_to_regexp___path_to_regexp_0.1.7.tgz";
url = "https://registry.yarnpkg.com/path-to-regexp/-/path-to-regexp-0.1.7.tgz";
sha1 = "df604178005f522f15eb4490e7247a1bfaa67f8c";
};
}
{
name = "path_type___path_type_4.0.0.tgz";
path = fetchurl {
name = "path_type___path_type_4.0.0.tgz";
url = "https://registry.yarnpkg.com/path-type/-/path-type-4.0.0.tgz";
sha1 = "84ed01c0a7ba380afe09d90a8c180dcd9d03043b";
};
}
{
name = "pause_stream___pause_stream_0.0.11.tgz";
path = fetchurl {
name = "pause_stream___pause_stream_0.0.11.tgz";
url = "https://registry.yarnpkg.com/pause-stream/-/pause-stream-0.0.11.tgz";
sha1 = "fe5a34b0cbce12b5aa6a2b403ee2e73b602f1445";
};
}
{
name = "pend___pend_1.2.0.tgz";
path = fetchurl {
name = "pend___pend_1.2.0.tgz";
url = "https://registry.yarnpkg.com/pend/-/pend-1.2.0.tgz";
sha1 = "7a57eb550a6783f9115331fcf4663d5c8e007a50";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "picomatch___picomatch_2.3.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "picomatch___picomatch_2.3.0.tgz";
url = "https://registry.yarnpkg.com/picomatch/-/picomatch-2.3.0.tgz";
sha1 = "f1f061de8f6a4bf022892e2d128234fb98302972";
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
};
}
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
{
name = "pkg_dir___pkg_dir_4.2.0.tgz";
path = fetchurl {
name = "pkg_dir___pkg_dir_4.2.0.tgz";
url = "https://registry.yarnpkg.com/pkg-dir/-/pkg-dir-4.2.0.tgz";
sha1 = "f099133df7ede422e81d1d8448270eeb3e4261f3";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "pkg_dir___pkg_dir_5.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "pkg_dir___pkg_dir_5.0.0.tgz";
url = "https://registry.yarnpkg.com/pkg-dir/-/pkg-dir-5.0.0.tgz";
sha1 = "a02d6aebe6ba133a928f74aec20bafdfe6b8e760";
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
};
}
{
grafana-image-renderer: 3.2.1 -> 3.3.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.3.0
2021-11-21 16:18:57 +00:00
name = "pkg_fetch___pkg_fetch_3.2.4.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.1 -> 3.3.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.3.0
2021-11-21 16:18:57 +00:00
name = "pkg_fetch___pkg_fetch_3.2.4.tgz";
url = "https://registry.yarnpkg.com/pkg-fetch/-/pkg-fetch-3.2.4.tgz";
sha1 = "5372734b12167d4bacd872be348217461b517390";
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
};
}
{
grafana-image-renderer: 3.2.1 -> 3.3.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.3.0
2021-11-21 16:18:57 +00:00
name = "pkg___pkg_5.4.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.1 -> 3.3.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.3.0
2021-11-21 16:18:57 +00:00
name = "pkg___pkg_5.4.1.tgz";
url = "https://registry.yarnpkg.com/pkg/-/pkg-5.4.1.tgz";
sha1 = "4d824e42c454f32131e471d7cd8d14bfdb3e1c4c";
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 = "please_upgrade_node___please_upgrade_node_3.2.0.tgz";
path = fetchurl {
name = "please_upgrade_node___please_upgrade_node_3.2.0.tgz";
url = "https://registry.yarnpkg.com/please-upgrade-node/-/please-upgrade-node-3.2.0.tgz";
sha1 = "aeddd3f994c933e4ad98b99d9a556efa0e2fe942";
};
}
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
{
name = "prebuild_install___prebuild_install_6.0.1.tgz";
path = fetchurl {
name = "prebuild_install___prebuild_install_6.0.1.tgz";
url = "https://registry.yarnpkg.com/prebuild-install/-/prebuild-install-6.0.1.tgz";
sha1 = "5902172f7a40eb67305b96c2a695db32636ee26d";
};
}
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
{
name = "prelude_ls___prelude_ls_1.2.1.tgz";
path = fetchurl {
name = "prelude_ls___prelude_ls_1.2.1.tgz";
url = "https://registry.yarnpkg.com/prelude-ls/-/prelude-ls-1.2.1.tgz";
sha1 = "debc6489d7a6e6b0e7611888cec880337d316396";
};
}
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 = "prelude_ls___prelude_ls_1.1.2.tgz";
path = fetchurl {
name = "prelude_ls___prelude_ls_1.1.2.tgz";
url = "https://registry.yarnpkg.com/prelude-ls/-/prelude-ls-1.1.2.tgz";
sha1 = "21932a549f5e52ffd9a827f570e04be62a97da54";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "prettier_linter_helpers___prettier_linter_helpers_1.0.0.tgz";
path = fetchurl {
name = "prettier_linter_helpers___prettier_linter_helpers_1.0.0.tgz";
url = "https://registry.yarnpkg.com/prettier-linter-helpers/-/prettier-linter-helpers-1.0.0.tgz";
sha1 = "d23d41fe1375646de2d0104d3454a3008802cf7b";
};
}
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
{
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
name = "prettier___prettier_2.2.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
name = "prettier___prettier_2.2.1.tgz";
url = "https://registry.yarnpkg.com/prettier/-/prettier-2.2.1.tgz";
sha1 = "795a1a78dd52f073da0cd42b21f9c91381923ff5";
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 = "process_nextick_args___process_nextick_args_2.0.1.tgz";
path = fetchurl {
name = "process_nextick_args___process_nextick_args_2.0.1.tgz";
url = "https://registry.yarnpkg.com/process-nextick-args/-/process-nextick-args-2.0.1.tgz";
sha1 = "7820d9b16120cc55ca9ae7792680ae7dba6d7fe2";
};
}
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
{
name = "progress___progress_2.0.1.tgz";
path = fetchurl {
name = "progress___progress_2.0.1.tgz";
url = "https://registry.yarnpkg.com/progress/-/progress-2.0.1.tgz";
sha1 = "c9242169342b1c29d275889c95734621b1952e31";
};
}
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 = "progress___progress_2.0.3.tgz";
path = fetchurl {
name = "progress___progress_2.0.3.tgz";
url = "https://registry.yarnpkg.com/progress/-/progress-2.0.3.tgz";
sha1 = "7e8cf8d8f5b8f239c1bc68beb4eb78567d572ef8";
};
}
{
name = "prom_client___prom_client_11.5.3.tgz";
path = fetchurl {
name = "prom_client___prom_client_11.5.3.tgz";
url = "https://registry.yarnpkg.com/prom-client/-/prom-client-11.5.3.tgz";
sha1 = "5fedfce1083bac6c2b223738e966d0e1643756f8";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "prop_types___prop_types_15.7.2.tgz";
path = fetchurl {
name = "prop_types___prop_types_15.7.2.tgz";
url = "https://registry.yarnpkg.com/prop-types/-/prop-types-15.7.2.tgz";
sha1 = "52c41e75b8c87e72b9d9360e0206b99dcbffa6c5";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "protobufjs___protobufjs_6.11.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "protobufjs___protobufjs_6.11.2.tgz";
url = "https://registry.yarnpkg.com/protobufjs/-/protobufjs-6.11.2.tgz";
sha1 = "de39fabd4ed32beaa08e9bb1e30d08544c1edf8b";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "proxy_addr___proxy_addr_2.0.7.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "proxy_addr___proxy_addr_2.0.7.tgz";
url = "https://registry.yarnpkg.com/proxy-addr/-/proxy-addr-2.0.7.tgz";
sha1 = "f19fe69ceab311eeb94b42e70e8c2070f9ba1025";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "proxy_from_env___proxy_from_env_1.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "proxy_from_env___proxy_from_env_1.1.0.tgz";
url = "https://registry.yarnpkg.com/proxy-from-env/-/proxy-from-env-1.1.0.tgz";
sha1 = "e102f16ca355424865755d2c9e8ea4f24d58c3e2";
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 = "ps_tree___ps_tree_1.2.0.tgz";
path = fetchurl {
name = "ps_tree___ps_tree_1.2.0.tgz";
url = "https://registry.yarnpkg.com/ps-tree/-/ps-tree-1.2.0.tgz";
sha1 = "5e7425b89508736cdd4f2224d028f7bb3f722ebd";
};
}
{
name = "pump___pump_3.0.0.tgz";
path = fetchurl {
name = "pump___pump_3.0.0.tgz";
url = "https://registry.yarnpkg.com/pump/-/pump-3.0.0.tgz";
sha1 = "b4a2116815bde2f4e1ea602354e8c75565107a64";
};
}
{
name = "punycode___punycode_2.1.1.tgz";
path = fetchurl {
name = "punycode___punycode_2.1.1.tgz";
url = "https://registry.yarnpkg.com/punycode/-/punycode-2.1.1.tgz";
sha1 = "b58b010ac40c22c5657616c8d2c2c02c7bf479ec";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "puppeteer_cluster___puppeteer_cluster_0.22.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "puppeteer_cluster___puppeteer_cluster_0.22.0.tgz";
url = "https://registry.yarnpkg.com/puppeteer-cluster/-/puppeteer-cluster-0.22.0.tgz";
sha1 = "4ab214671f414f15ad6a94a4b61ed0b4172e86e6";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "puppeteer___puppeteer_10.4.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "puppeteer___puppeteer_10.4.0.tgz";
url = "https://registry.yarnpkg.com/puppeteer/-/puppeteer-10.4.0.tgz";
sha1 = "a6465ff97fda0576c4ac29601406f67e6fea3dc7";
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 = "qs___qs_6.7.0.tgz";
path = fetchurl {
name = "qs___qs_6.7.0.tgz";
url = "https://registry.yarnpkg.com/qs/-/qs-6.7.0.tgz";
sha1 = "41dc1a015e3d581f1621776be31afb2876a9b1bc";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "queue_microtask___queue_microtask_1.2.3.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "queue_microtask___queue_microtask_1.2.3.tgz";
url = "https://registry.yarnpkg.com/queue-microtask/-/queue-microtask-1.2.3.tgz";
sha1 = "4929228bbc724dfac43e0efb058caf7b6cfb6243";
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 = "range_parser___range_parser_1.2.1.tgz";
path = fetchurl {
name = "range_parser___range_parser_1.2.1.tgz";
url = "https://registry.yarnpkg.com/range-parser/-/range-parser-1.2.1.tgz";
sha1 = "3cf37023d199e1c24d1a55b84800c2f3e6468031";
};
}
{
name = "raw_body___raw_body_2.4.0.tgz";
path = fetchurl {
name = "raw_body___raw_body_2.4.0.tgz";
url = "https://registry.yarnpkg.com/raw-body/-/raw-body-2.4.0.tgz";
sha1 = "a1ce6fb9c9bc356ca52e89256ab59059e13d0332";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "rc___rc_1.2.8.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "rc___rc_1.2.8.tgz";
url = "https://registry.yarnpkg.com/rc/-/rc-1.2.8.tgz";
sha1 = "cd924bf5200a075b83c188cd6b9e211b7fc0d3ed";
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
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "react_is___react_is_16.13.1.tgz";
path = fetchurl {
name = "react_is___react_is_16.13.1.tgz";
url = "https://registry.yarnpkg.com/react-is/-/react-is-16.13.1.tgz";
sha1 = "789729a4dc36de2999dc156dd6c1d9c18cea56a4";
};
}
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 = "readable_stream___readable_stream_2.3.7.tgz";
path = fetchurl {
name = "readable_stream___readable_stream_2.3.7.tgz";
url = "https://registry.yarnpkg.com/readable-stream/-/readable-stream-2.3.7.tgz";
sha1 = "1eca1cf711aef814c04f62252a36a62f6cb23b57";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "readable_stream___readable_stream_3.6.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "readable_stream___readable_stream_3.6.0.tgz";
url = "https://registry.yarnpkg.com/readable-stream/-/readable-stream-3.6.0.tgz";
sha1 = "337bbda3adc0706bd3e024426a286d4b4b2c9198";
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
};
}
grafana-image-renderer: 2.1.0 -> 3.0.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.0
2021-06-07 21:38:04 +00:00
{
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
name = "readdirp___readdirp_3.6.0.tgz";
grafana-image-renderer: 2.1.0 -> 3.0.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.0
2021-06-07 21:38:04 +00:00
path = fetchurl {
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
name = "readdirp___readdirp_3.6.0.tgz";
url = "https://registry.yarnpkg.com/readdirp/-/readdirp-3.6.0.tgz";
sha1 = "74a370bd857116e245b29cc97340cd431a02a6c7";
grafana-image-renderer: 2.1.0 -> 3.0.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.0
2021-06-07 21:38:04 +00:00
};
}
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
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "regexp.prototype.flags___regexp.prototype.flags_1.3.1.tgz";
path = fetchurl {
name = "regexp.prototype.flags___regexp.prototype.flags_1.3.1.tgz";
url = "https://registry.yarnpkg.com/regexp.prototype.flags/-/regexp.prototype.flags-1.3.1.tgz";
sha1 = "7ef352ae8d159e758c0eadca6f8fcb4eef07be26";
};
}
{
name = "regexpp___regexpp_3.2.0.tgz";
path = fetchurl {
name = "regexpp___regexpp_3.2.0.tgz";
url = "https://registry.yarnpkg.com/regexpp/-/regexpp-3.2.0.tgz";
sha1 = "0425a2768d8f23bad70ca4b90461fa2f1213e1b2";
};
}
{
name = "regextras___regextras_0.7.1.tgz";
path = fetchurl {
name = "regextras___regextras_0.7.1.tgz";
url = "https://registry.yarnpkg.com/regextras/-/regextras-0.7.1.tgz";
sha1 = "be95719d5f43f9ef0b9fa07ad89b7c606995a3b2";
};
}
{
name = "regextras___regextras_0.8.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "regextras___regextras_0.8.0.tgz";
url = "https://registry.yarnpkg.com/regextras/-/regextras-0.8.0.tgz";
sha1 = "ec0f99853d4912839321172f608b544814b02217";
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
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "require_directory___require_directory_2.1.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "require_directory___require_directory_2.1.1.tgz";
url = "https://registry.yarnpkg.com/require-directory/-/require-directory-2.1.1.tgz";
sha1 = "8c64ad5fd30dab1c976e2344ffe7f792a6a6df42";
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
};
}
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
{
name = "require_from_string___require_from_string_2.0.2.tgz";
path = fetchurl {
name = "require_from_string___require_from_string_2.0.2.tgz";
url = "https://registry.yarnpkg.com/require-from-string/-/require-from-string-2.0.2.tgz";
sha1 = "89a7fdd938261267318eafe14f9c32e598c36909";
};
}
{
name = "resolve_from___resolve_from_4.0.0.tgz";
path = fetchurl {
name = "resolve_from___resolve_from_4.0.0.tgz";
url = "https://registry.yarnpkg.com/resolve-from/-/resolve-from-4.0.0.tgz";
sha1 = "4abcd852ad32dd7baabfe9b40e00a36db5f392e6";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "resolve___resolve_1.20.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "resolve___resolve_1.20.0.tgz";
url = "https://registry.yarnpkg.com/resolve/-/resolve-1.20.0.tgz";
sha1 = "629a013fb3f70755d6f0b7935cc1c2c5378b1975";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "resolve___resolve_2.0.0_next.3.tgz";
path = fetchurl {
name = "resolve___resolve_2.0.0_next.3.tgz";
url = "https://registry.yarnpkg.com/resolve/-/resolve-2.0.0-next.3.tgz";
sha1 = "d41016293d4a8586a39ca5d9b5f15cbea1f55e46";
};
}
{
name = "restore_cursor___restore_cursor_3.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "restore_cursor___restore_cursor_3.1.0.tgz";
url = "https://registry.yarnpkg.com/restore-cursor/-/restore-cursor-3.1.0.tgz";
sha1 = "39f67c54b3a7a58cea5236d95cf0034239631f7e";
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 = "reusify___reusify_1.0.4.tgz";
path = fetchurl {
name = "reusify___reusify_1.0.4.tgz";
url = "https://registry.yarnpkg.com/reusify/-/reusify-1.0.4.tgz";
sha1 = "90da382b1e126efc02146e90845a88db12925d76";
};
}
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
{
name = "rimraf___rimraf_3.0.2.tgz";
path = fetchurl {
name = "rimraf___rimraf_3.0.2.tgz";
url = "https://registry.yarnpkg.com/rimraf/-/rimraf-3.0.2.tgz";
sha1 = "f1a5402ba6220ad52cc1282bac1ae3aa49fd061a";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "run_parallel___run_parallel_1.2.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "run_parallel___run_parallel_1.2.0.tgz";
url = "https://registry.yarnpkg.com/run-parallel/-/run-parallel-1.2.0.tgz";
sha1 = "66d1368da7bdf921eb9d95bd1a9229e7f21a43ee";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "rxjs___rxjs_6.6.7.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "rxjs___rxjs_6.6.7.tgz";
url = "https://registry.yarnpkg.com/rxjs/-/rxjs-6.6.7.tgz";
sha1 = "90ac018acabf491bf65044235d5863c4dab804c9";
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 = "safe_buffer___safe_buffer_5.1.2.tgz";
path = fetchurl {
name = "safe_buffer___safe_buffer_5.1.2.tgz";
url = "https://registry.yarnpkg.com/safe-buffer/-/safe-buffer-5.1.2.tgz";
sha1 = "991ec69d296e0313747d59bdfd2b745c35f8828d";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "safe_buffer___safe_buffer_5.2.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "safe_buffer___safe_buffer_5.2.1.tgz";
url = "https://registry.yarnpkg.com/safe-buffer/-/safe-buffer-5.2.1.tgz";
sha1 = "1eaf9fa9bdb1fdd4ec75f58f9cdb4e6b7827eec6";
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
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "safe_stable_stringify___safe_stable_stringify_1.1.1.tgz";
path = fetchurl {
name = "safe_stable_stringify___safe_stable_stringify_1.1.1.tgz";
url = "https://registry.yarnpkg.com/safe-stable-stringify/-/safe-stable-stringify-1.1.1.tgz";
sha1 = "c8a220ab525cd94e60ebf47ddc404d610dc5d84a";
};
}
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 = "safer_buffer___safer_buffer_2.1.2.tgz";
path = fetchurl {
name = "safer_buffer___safer_buffer_2.1.2.tgz";
url = "https://registry.yarnpkg.com/safer-buffer/-/safer-buffer-2.1.2.tgz";
sha1 = "44fa161b0187b9549dd84bb91802f9bd8385cd6a";
};
}
{
name = "semver_compare___semver_compare_1.0.0.tgz";
path = fetchurl {
name = "semver_compare___semver_compare_1.0.0.tgz";
url = "https://registry.yarnpkg.com/semver-compare/-/semver-compare-1.0.0.tgz";
sha1 = "0dee216a1c941ab37e9efb1788f6afc5ff5537fc";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "semver_regex___semver_regex_3.1.3.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "semver_regex___semver_regex_3.1.3.tgz";
url = "https://registry.yarnpkg.com/semver-regex/-/semver-regex-3.1.3.tgz";
sha1 = "b2bcc6f97f63269f286994e297e229b6245d0dc3";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "semver___semver_5.7.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "semver___semver_5.7.1.tgz";
url = "https://registry.yarnpkg.com/semver/-/semver-5.7.1.tgz";
sha1 = "a954f931aeba508d307bbf069eff0c01c96116f7";
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
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "semver___semver_6.3.0.tgz";
path = fetchurl {
name = "semver___semver_6.3.0.tgz";
url = "https://registry.yarnpkg.com/semver/-/semver-6.3.0.tgz";
sha1 = "ee0a64c8af5e8ceea67687b133761e1becbd1d3d";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "semver___semver_7.3.5.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "semver___semver_7.3.5.tgz";
url = "https://registry.yarnpkg.com/semver/-/semver-7.3.5.tgz";
sha1 = "0b621c879348d8998e4b0e4be94b3f12e6018ef7";
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
};
}
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 = "send___send_0.17.1.tgz";
path = fetchurl {
name = "send___send_0.17.1.tgz";
url = "https://registry.yarnpkg.com/send/-/send-0.17.1.tgz";
sha1 = "c1d8b059f7900f7466dd4938bdc44e11ddb376c8";
};
}
{
name = "serve_static___serve_static_1.14.1.tgz";
path = fetchurl {
name = "serve_static___serve_static_1.14.1.tgz";
url = "https://registry.yarnpkg.com/serve-static/-/serve-static-1.14.1.tgz";
sha1 = "666e636dc4f010f7ef29970a88a674320898b2f9";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "set_blocking___set_blocking_2.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "set_blocking___set_blocking_2.0.0.tgz";
url = "https://registry.yarnpkg.com/set-blocking/-/set-blocking-2.0.0.tgz";
sha1 = "045f9782d011ae9a6803ddd382b24392b3d890f7";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "setprototypeof___setprototypeof_1.1.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "setprototypeof___setprototypeof_1.1.1.tgz";
url = "https://registry.yarnpkg.com/setprototypeof/-/setprototypeof-1.1.1.tgz";
sha1 = "7e95acb24aa92f5885e0abef5ba131330d4ae683";
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 = "shebang_command___shebang_command_2.0.0.tgz";
path = fetchurl {
name = "shebang_command___shebang_command_2.0.0.tgz";
url = "https://registry.yarnpkg.com/shebang-command/-/shebang-command-2.0.0.tgz";
sha1 = "ccd0af4f8835fbdc265b82461aaf0c36663f34ea";
};
}
{
name = "shebang_regex___shebang_regex_3.0.0.tgz";
path = fetchurl {
name = "shebang_regex___shebang_regex_3.0.0.tgz";
url = "https://registry.yarnpkg.com/shebang-regex/-/shebang-regex-3.0.0.tgz";
sha1 = "ae16f1644d873ecad843b0307b143362d4c42172";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "side_channel___side_channel_1.0.4.tgz";
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "side_channel___side_channel_1.0.4.tgz";
url = "https://registry.yarnpkg.com/side-channel/-/side-channel-1.0.4.tgz";
sha1 = "efce5c8fdc104ee751b25c58d4290011fa5ea2cf";
};
}
{
name = "signal_exit___signal_exit_3.0.5.tgz";
path = fetchurl {
name = "signal_exit___signal_exit_3.0.5.tgz";
url = "https://registry.yarnpkg.com/signal-exit/-/signal-exit-3.0.5.tgz";
sha1 = "9e3e8cc0c75a99472b44321033a7702e7738252f";
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
};
}
{
name = "simple_concat___simple_concat_1.0.1.tgz";
path = fetchurl {
name = "simple_concat___simple_concat_1.0.1.tgz";
url = "https://registry.yarnpkg.com/simple-concat/-/simple-concat-1.0.1.tgz";
sha1 = "f46976082ba35c2263f1c8ab5edfe26c41c9552f";
};
}
{
name = "simple_get___simple_get_3.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "simple_get___simple_get_3.1.0.tgz";
url = "https://registry.yarnpkg.com/simple-get/-/simple-get-3.1.0.tgz";
sha1 = "b45be062435e50d159540b576202ceec40b9c6b3";
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 = "simple_swizzle___simple_swizzle_0.2.2.tgz";
path = fetchurl {
name = "simple_swizzle___simple_swizzle_0.2.2.tgz";
url = "https://registry.yarnpkg.com/simple-swizzle/-/simple-swizzle-0.2.2.tgz";
sha1 = "a4da6b635ffcccca33f70d17cb92592de95e557a";
};
}
{
name = "slash___slash_3.0.0.tgz";
path = fetchurl {
name = "slash___slash_3.0.0.tgz";
url = "https://registry.yarnpkg.com/slash/-/slash-3.0.0.tgz";
sha1 = "6539be870c165adbd5240220dbe361f1bc4d4634";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "slice_ansi___slice_ansi_3.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "slice_ansi___slice_ansi_3.0.0.tgz";
url = "https://registry.yarnpkg.com/slice-ansi/-/slice-ansi-3.0.0.tgz";
sha1 = "31ddc10930a1b7e0b67b08c96c2f49b77a789787";
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
};
}
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
{
name = "slice_ansi___slice_ansi_4.0.0.tgz";
path = fetchurl {
name = "slice_ansi___slice_ansi_4.0.0.tgz";
url = "https://registry.yarnpkg.com/slice-ansi/-/slice-ansi-4.0.0.tgz";
sha1 = "500e8dd0fd55b05815086255b3195adf2a45fe6b";
};
}
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 = "source_map___source_map_0.6.1.tgz";
path = fetchurl {
name = "source_map___source_map_0.6.1.tgz";
url = "https://registry.yarnpkg.com/source-map/-/source-map-0.6.1.tgz";
sha1 = "74722af32e9614e9c287a8d0bbde48b5e2f1a263";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "spdx_exceptions___spdx_exceptions_2.3.0.tgz";
path = fetchurl {
name = "spdx_exceptions___spdx_exceptions_2.3.0.tgz";
url = "https://registry.yarnpkg.com/spdx-exceptions/-/spdx-exceptions-2.3.0.tgz";
sha1 = "3f28ce1a77a00372683eade4a433183527a2163d";
};
}
{
name = "spdx_expression_parse___spdx_expression_parse_3.0.1.tgz";
path = fetchurl {
name = "spdx_expression_parse___spdx_expression_parse_3.0.1.tgz";
url = "https://registry.yarnpkg.com/spdx-expression-parse/-/spdx-expression-parse-3.0.1.tgz";
sha1 = "cf70f50482eefdc98e3ce0a6833e4a53ceeba679";
};
}
{
name = "spdx_license_ids___spdx_license_ids_3.0.10.tgz";
path = fetchurl {
name = "spdx_license_ids___spdx_license_ids_3.0.10.tgz";
url = "https://registry.yarnpkg.com/spdx-license-ids/-/spdx-license-ids-3.0.10.tgz";
sha1 = "0d9becccde7003d6c658d487dd48a32f0bf3014b";
};
}
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 = "split___split_0.3.3.tgz";
path = fetchurl {
name = "split___split_0.3.3.tgz";
url = "https://registry.yarnpkg.com/split/-/split-0.3.3.tgz";
sha1 = "cd0eea5e63a211dfff7eb0f091c4133e2d0dd28f";
};
}
{
name = "sprintf_js___sprintf_js_1.0.3.tgz";
path = fetchurl {
name = "sprintf_js___sprintf_js_1.0.3.tgz";
url = "https://registry.yarnpkg.com/sprintf-js/-/sprintf-js-1.0.3.tgz";
sha1 = "04e6926f662895354f3dd015203633b857297e2c";
};
}
{
name = "stack_trace___stack_trace_0.0.10.tgz";
path = fetchurl {
name = "stack_trace___stack_trace_0.0.10.tgz";
url = "https://registry.yarnpkg.com/stack-trace/-/stack-trace-0.0.10.tgz";
sha1 = "547c70b347e8d32b4e108ea1a2a159e5fdde19c0";
};
}
{
name = "statuses___statuses_1.5.0.tgz";
path = fetchurl {
name = "statuses___statuses_1.5.0.tgz";
url = "https://registry.yarnpkg.com/statuses/-/statuses-1.5.0.tgz";
sha1 = "161c7dac177659fd9811f43771fa99381478628c";
};
}
{
name = "stream_combiner___stream_combiner_0.0.4.tgz";
path = fetchurl {
name = "stream_combiner___stream_combiner_0.0.4.tgz";
url = "https://registry.yarnpkg.com/stream-combiner/-/stream-combiner-0.0.4.tgz";
sha1 = "4d5e433c185261dde623ca3f44c586bcf5c4ad14";
};
}
{
name = "stream_meter___stream_meter_1.0.4.tgz";
path = fetchurl {
name = "stream_meter___stream_meter_1.0.4.tgz";
url = "https://registry.yarnpkg.com/stream-meter/-/stream-meter-1.0.4.tgz";
sha1 = "52af95aa5ea760a2491716704dbff90f73afdd1d";
};
}
{
name = "string_argv___string_argv_0.3.1.tgz";
path = fetchurl {
name = "string_argv___string_argv_0.3.1.tgz";
url = "https://registry.yarnpkg.com/string-argv/-/string-argv-0.3.1.tgz";
sha1 = "95e2fbec0427ae19184935f816d74aaa4c5c19da";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "string_argv___string_argv_0.1.2.tgz";
path = fetchurl {
name = "string_argv___string_argv_0.1.2.tgz";
url = "https://registry.yarnpkg.com/string-argv/-/string-argv-0.1.2.tgz";
sha1 = "c5b7bc03fb2b11983ba3a72333dd0559e77e4738";
};
}
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 = "string_width___string_width_1.0.2.tgz";
path = fetchurl {
name = "string_width___string_width_1.0.2.tgz";
url = "https://registry.yarnpkg.com/string-width/-/string-width-1.0.2.tgz";
sha1 = "118bdf5b8cdc51a2a7e70d211e07e2b0b9b107d3";
};
}
{
name = "string_width___string_width_2.1.1.tgz";
path = fetchurl {
name = "string_width___string_width_2.1.1.tgz";
url = "https://registry.yarnpkg.com/string-width/-/string-width-2.1.1.tgz";
sha1 = "ab93f27a8dc13d28cac815c462143a6d9012ae9e";
};
}
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
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "string_width___string_width_4.2.3.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "string_width___string_width_4.2.3.tgz";
url = "https://registry.yarnpkg.com/string-width/-/string-width-4.2.3.tgz";
sha1 = "269c7117d27b05ad2e536830a8ec895ef9c6d010";
};
}
{
name = "string.prototype.matchall___string.prototype.matchall_4.0.6.tgz";
path = fetchurl {
name = "string.prototype.matchall___string.prototype.matchall_4.0.6.tgz";
url = "https://registry.yarnpkg.com/string.prototype.matchall/-/string.prototype.matchall-4.0.6.tgz";
sha1 = "5abb5dabc94c7b0ea2380f65ba610b3a544b15fa";
};
}
{
name = "string.prototype.trimend___string.prototype.trimend_1.0.4.tgz";
path = fetchurl {
name = "string.prototype.trimend___string.prototype.trimend_1.0.4.tgz";
url = "https://registry.yarnpkg.com/string.prototype.trimend/-/string.prototype.trimend-1.0.4.tgz";
sha1 = "e75ae90c2942c63504686c18b287b4a0b1a45f80";
};
}
{
name = "string.prototype.trimstart___string.prototype.trimstart_1.0.4.tgz";
path = fetchurl {
name = "string.prototype.trimstart___string.prototype.trimstart_1.0.4.tgz";
url = "https://registry.yarnpkg.com/string.prototype.trimstart/-/string.prototype.trimstart-1.0.4.tgz";
sha1 = "b36399af4ab2999b4c9c648bd7a3fb2bb26feeed";
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
};
}
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 = "string_decoder___string_decoder_1.3.0.tgz";
path = fetchurl {
name = "string_decoder___string_decoder_1.3.0.tgz";
url = "https://registry.yarnpkg.com/string_decoder/-/string_decoder-1.3.0.tgz";
sha1 = "42f114594a46cf1a8e30b0a84f56c78c3edac21e";
};
}
{
name = "string_decoder___string_decoder_1.1.1.tgz";
path = fetchurl {
name = "string_decoder___string_decoder_1.1.1.tgz";
url = "https://registry.yarnpkg.com/string_decoder/-/string_decoder-1.1.1.tgz";
sha1 = "9cf1611ba62685d7030ae9e4ba34149c3af03fc8";
};
}
{
name = "stringify_object___stringify_object_3.3.0.tgz";
path = fetchurl {
name = "stringify_object___stringify_object_3.3.0.tgz";
url = "https://registry.yarnpkg.com/stringify-object/-/stringify-object-3.3.0.tgz";
sha1 = "703065aefca19300d3ce88af4f5b3956d7556629";
};
}
{
name = "strip_ansi___strip_ansi_3.0.1.tgz";
path = fetchurl {
name = "strip_ansi___strip_ansi_3.0.1.tgz";
url = "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-3.0.1.tgz";
sha1 = "6a385fb8853d952d5ff05d0e8aaf94278dc63dcf";
};
}
{
name = "strip_ansi___strip_ansi_4.0.0.tgz";
path = fetchurl {
name = "strip_ansi___strip_ansi_4.0.0.tgz";
url = "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-4.0.0.tgz";
sha1 = "a8479022eb1ac368a871389b635262c505ee368f";
};
}
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
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "strip_ansi___strip_ansi_6.0.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "strip_ansi___strip_ansi_6.0.1.tgz";
url = "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-6.0.1.tgz";
sha1 = "9e26c63d30f53443e9489495b2105d37b67a85d9";
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
};
}
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 = "strip_final_newline___strip_final_newline_2.0.0.tgz";
path = fetchurl {
name = "strip_final_newline___strip_final_newline_2.0.0.tgz";
url = "https://registry.yarnpkg.com/strip-final-newline/-/strip-final-newline-2.0.0.tgz";
sha1 = "89b852fb2fcbe936f6f4b3187afb0a12c1ab58ad";
};
}
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
{
name = "strip_json_comments___strip_json_comments_3.1.1.tgz";
path = fetchurl {
name = "strip_json_comments___strip_json_comments_3.1.1.tgz";
url = "https://registry.yarnpkg.com/strip-json-comments/-/strip-json-comments-3.1.1.tgz";
sha1 = "31f1281b3832630434831c310c01cccda8cbe006";
};
}
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
{
name = "strip_json_comments___strip_json_comments_2.0.1.tgz";
path = fetchurl {
name = "strip_json_comments___strip_json_comments_2.0.1.tgz";
url = "https://registry.yarnpkg.com/strip-json-comments/-/strip-json-comments-2.0.1.tgz";
sha1 = "3c531942e908c2697c0ec344858c286c7ca0a60a";
};
}
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
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "supports_color___supports_color_8.1.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "supports_color___supports_color_8.1.1.tgz";
url = "https://registry.yarnpkg.com/supports-color/-/supports-color-8.1.1.tgz";
sha1 = "cd6fc17e28500cff56c1b86c0a7fd4a54a73005c";
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 = "supports_color___supports_color_5.5.0.tgz";
path = fetchurl {
name = "supports_color___supports_color_5.5.0.tgz";
url = "https://registry.yarnpkg.com/supports-color/-/supports-color-5.5.0.tgz";
sha1 = "e2e69a44ac8772f78a1ec0b35b689df6530efc8f";
};
}
{
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
name = "supports_color___supports_color_7.2.0.tgz";
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
path = fetchurl {
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
name = "supports_color___supports_color_7.2.0.tgz";
url = "https://registry.yarnpkg.com/supports-color/-/supports-color-7.2.0.tgz";
sha1 = "1b7dcdcb32b8138801b3e478ba6a51caa89648da";
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
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "table___table_6.7.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "table___table_6.7.2.tgz";
url = "https://registry.yarnpkg.com/table/-/table-6.7.2.tgz";
sha1 = "a8d39b9f5966693ca8b0feba270a78722cbaf3b0";
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
};
}
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
{
name = "tar_fs___tar_fs_2.0.0.tgz";
path = fetchurl {
name = "tar_fs___tar_fs_2.0.0.tgz";
url = "https://registry.yarnpkg.com/tar-fs/-/tar-fs-2.0.0.tgz";
sha1 = "677700fc0c8b337a78bee3623fdc235f21d7afad";
};
}
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
{
name = "tar_fs___tar_fs_2.1.1.tgz";
path = fetchurl {
name = "tar_fs___tar_fs_2.1.1.tgz";
url = "https://registry.yarnpkg.com/tar-fs/-/tar-fs-2.1.1.tgz";
sha1 = "489a15ab85f1f0befabb370b7de4f9eb5cbe8784";
};
}
{
name = "tar_stream___tar_stream_2.2.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "tar_stream___tar_stream_2.2.0.tgz";
url = "https://registry.yarnpkg.com/tar-stream/-/tar-stream-2.2.0.tgz";
sha1 = "acad84c284136b060dc3faa64474aa9aebd77287";
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
};
}
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 = "tdigest___tdigest_0.1.1.tgz";
path = fetchurl {
name = "tdigest___tdigest_0.1.1.tgz";
url = "https://registry.yarnpkg.com/tdigest/-/tdigest-0.1.1.tgz";
sha1 = "2e3cb2c39ea449e55d1e6cd91117accca4588021";
};
}
{
name = "text_hex___text_hex_1.0.0.tgz";
path = fetchurl {
name = "text_hex___text_hex_1.0.0.tgz";
url = "https://registry.yarnpkg.com/text-hex/-/text-hex-1.0.0.tgz";
sha1 = "69dc9c1b17446ee79a92bf5b884bb4b9127506f5";
};
}
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
{
name = "text_table___text_table_0.2.0.tgz";
path = fetchurl {
name = "text_table___text_table_0.2.0.tgz";
url = "https://registry.yarnpkg.com/text-table/-/text-table-0.2.0.tgz";
sha1 = "7f5ee823ae805207c00af2df4a84ec3fcfa570b4";
};
}
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 = "through___through_2.3.8.tgz";
path = fetchurl {
name = "through___through_2.3.8.tgz";
url = "https://registry.yarnpkg.com/through/-/through-2.3.8.tgz";
sha1 = "0dd4c9ffaabc357960b1b724115d7e0e86a2e1f5";
};
}
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
{
name = "to_fast_properties___to_fast_properties_2.0.0.tgz";
path = fetchurl {
name = "to_fast_properties___to_fast_properties_2.0.0.tgz";
url = "https://registry.yarnpkg.com/to-fast-properties/-/to-fast-properties-2.0.0.tgz";
sha1 = "dc5e698cbd079265bc73e0377681a4e4e83f616e";
};
}
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 = "to_regex_range___to_regex_range_5.0.1.tgz";
path = fetchurl {
name = "to_regex_range___to_regex_range_5.0.1.tgz";
url = "https://registry.yarnpkg.com/to-regex-range/-/to-regex-range-5.0.1.tgz";
sha1 = "1648c44aae7c8d988a326018ed72f5b4dd0392e4";
};
}
{
name = "toidentifier___toidentifier_1.0.0.tgz";
path = fetchurl {
name = "toidentifier___toidentifier_1.0.0.tgz";
url = "https://registry.yarnpkg.com/toidentifier/-/toidentifier-1.0.0.tgz";
sha1 = "7e1be3470f1e77948bc43d94a3c8f4d7752ba553";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "tr46___tr46_0.0.3.tgz";
path = fetchurl {
name = "tr46___tr46_0.0.3.tgz";
url = "https://registry.yarnpkg.com/tr46/-/tr46-0.0.3.tgz";
sha1 = "8184fd347dac9cdc185992f3a6622e14b9d9ab6a";
};
}
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 = "triple_beam___triple_beam_1.3.0.tgz";
path = fetchurl {
name = "triple_beam___triple_beam_1.3.0.tgz";
url = "https://registry.yarnpkg.com/triple-beam/-/triple-beam-1.3.0.tgz";
sha1 = "a595214c7298db8339eeeee083e4d10bd8cb8dd9";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "tsc_watch___tsc_watch_4.5.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "tsc_watch___tsc_watch_4.5.0.tgz";
url = "https://registry.yarnpkg.com/tsc-watch/-/tsc-watch-4.5.0.tgz";
sha1 = "d6884b932822b2c2ccd37f1c1f3748304566a474";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "tslib___tslib_2.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "tslib___tslib_2.1.0.tgz";
url = "https://registry.yarnpkg.com/tslib/-/tslib-2.1.0.tgz";
sha1 = "da60860f1c2ecaa5703ab7d39bc05b6bf988b97a";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "tslib___tslib_1.14.1.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "tslib___tslib_1.14.1.tgz";
url = "https://registry.yarnpkg.com/tslib/-/tslib-1.14.1.tgz";
sha1 = "cf2d38bdc34a134bcaf1091c41f6619e2f672d00";
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
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "tsutils___tsutils_3.21.0.tgz";
path = fetchurl {
name = "tsutils___tsutils_3.21.0.tgz";
url = "https://registry.yarnpkg.com/tsutils/-/tsutils-3.21.0.tgz";
sha1 = "b48717d394cea6c1e096983eed58e9d61715b623";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "tunnel_agent___tunnel_agent_0.6.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "tunnel_agent___tunnel_agent_0.6.0.tgz";
url = "https://registry.yarnpkg.com/tunnel-agent/-/tunnel-agent-0.6.0.tgz";
sha1 = "27a5dea06b36b04a0a9966774b290868f0fc40fd";
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
};
}
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
{
name = "type_check___type_check_0.4.0.tgz";
path = fetchurl {
name = "type_check___type_check_0.4.0.tgz";
url = "https://registry.yarnpkg.com/type-check/-/type-check-0.4.0.tgz";
sha1 = "07b8203bfa7056c0657050e3ccd2c37730bab8f1";
};
}
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 = "type_check___type_check_0.3.2.tgz";
path = fetchurl {
name = "type_check___type_check_0.3.2.tgz";
url = "https://registry.yarnpkg.com/type-check/-/type-check-0.3.2.tgz";
sha1 = "5884cab512cf1d355e3fb784f30804b2b520db72";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "type_fest___type_fest_0.20.2.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "type_fest___type_fest_0.20.2.tgz";
url = "https://registry.yarnpkg.com/type-fest/-/type-fest-0.20.2.tgz";
sha1 = "1bf207f4b28f91583666cb5fbd327887301cd5f4";
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
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "type_fest___type_fest_0.21.3.tgz";
path = fetchurl {
name = "type_fest___type_fest_0.21.3.tgz";
url = "https://registry.yarnpkg.com/type-fest/-/type-fest-0.21.3.tgz";
sha1 = "d260a24b0198436e133fa26a524a6d65fa3b2e37";
};
}
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
{
name = "type_fest___type_fest_0.8.1.tgz";
path = fetchurl {
name = "type_fest___type_fest_0.8.1.tgz";
url = "https://registry.yarnpkg.com/type-fest/-/type-fest-0.8.1.tgz";
sha1 = "09e249ebde851d3b1e48d27c105444667f17b83d";
};
}
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 = "type_is___type_is_1.6.18.tgz";
path = fetchurl {
name = "type_is___type_is_1.6.18.tgz";
url = "https://registry.yarnpkg.com/type-is/-/type-is-1.6.18.tgz";
sha1 = "4e552cd05df09467dcbc4ef739de89f2cf37c131";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "typescript___typescript_4.3.4.tgz";
path = fetchurl {
name = "typescript___typescript_4.3.4.tgz";
url = "https://registry.yarnpkg.com/typescript/-/typescript-4.3.4.tgz";
sha1 = "3f85b986945bcf31071decdd96cf8bfa65f9dcbc";
};
}
{
name = "typescript___typescript_4.4.3.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "typescript___typescript_4.4.3.tgz";
url = "https://registry.yarnpkg.com/typescript/-/typescript-4.4.3.tgz";
sha1 = "bdc5407caa2b109efd4f82fe130656f977a29324";
};
}
{
name = "unbox_primitive___unbox_primitive_1.0.1.tgz";
path = fetchurl {
name = "unbox_primitive___unbox_primitive_1.0.1.tgz";
url = "https://registry.yarnpkg.com/unbox-primitive/-/unbox-primitive-1.0.1.tgz";
sha1 = "085e215625ec3162574dc8859abee78a59b14471";
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
};
}
{
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
name = "unbzip2_stream___unbzip2_stream_1.3.3.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.0.0 -> 3.2.0 ChangeLogs: * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.1 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.1.0 * https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.0
2021-09-18 23:02:58 +00:00
name = "unbzip2_stream___unbzip2_stream_1.3.3.tgz";
url = "https://registry.yarnpkg.com/unbzip2-stream/-/unbzip2-stream-1.3.3.tgz";
sha1 = "d156d205e670d8d8c393e1c02ebd506422873f6a";
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 = "unique_filename___unique_filename_1.1.1.tgz";
path = fetchurl {
name = "unique_filename___unique_filename_1.1.1.tgz";
url = "https://registry.yarnpkg.com/unique-filename/-/unique-filename-1.1.1.tgz";
sha1 = "1d69769369ada0583103a1e6ae87681b56573230";
};
}
{
name = "unique_slug___unique_slug_2.0.2.tgz";
path = fetchurl {
name = "unique_slug___unique_slug_2.0.2.tgz";
url = "https://registry.yarnpkg.com/unique-slug/-/unique-slug-2.0.2.tgz";
sha1 = "baabce91083fc64e945b0f3ad613e264f7cd4e6c";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "universalify___universalify_2.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "universalify___universalify_2.0.0.tgz";
url = "https://registry.yarnpkg.com/universalify/-/universalify-2.0.0.tgz";
sha1 = "75a4984efedc4b08975c5aeb73f530d02df25717";
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 = "unpipe___unpipe_1.0.0.tgz";
path = fetchurl {
name = "unpipe___unpipe_1.0.0.tgz";
url = "https://registry.yarnpkg.com/unpipe/-/unpipe-1.0.0.tgz";
sha1 = "b2bf4ee8514aae6165b4817829d21b2ef49904ec";
};
}
{
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
name = "uri_js___uri_js_4.4.1.tgz";
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
path = fetchurl {
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
name = "uri_js___uri_js_4.4.1.tgz";
url = "https://registry.yarnpkg.com/uri-js/-/uri-js-4.4.1.tgz";
sha1 = "9b1a52595225859e55f669d928f88c6c57f2a77e";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "url_value_parser___url_value_parser_2.0.3.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "url_value_parser___url_value_parser_2.0.3.tgz";
url = "https://registry.yarnpkg.com/url-value-parser/-/url-value-parser-2.0.3.tgz";
sha1 = "cd4b8d6754e458d65e8125260c09718d926e6e21";
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 = "util_deprecate___util_deprecate_1.0.2.tgz";
path = fetchurl {
name = "util_deprecate___util_deprecate_1.0.2.tgz";
url = "https://registry.yarnpkg.com/util-deprecate/-/util-deprecate-1.0.2.tgz";
sha1 = "450d4dc9fa70de732762fbd2d4a28981419a0ccf";
};
}
{
name = "utils_merge___utils_merge_1.0.1.tgz";
path = fetchurl {
name = "utils_merge___utils_merge_1.0.1.tgz";
url = "https://registry.yarnpkg.com/utils-merge/-/utils-merge-1.0.1.tgz";
sha1 = "9f95710f50a267947b2ccc124741c1028427e713";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "v8_compile_cache___v8_compile_cache_2.3.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "v8_compile_cache___v8_compile_cache_2.3.0.tgz";
url = "https://registry.yarnpkg.com/v8-compile-cache/-/v8-compile-cache-2.3.0.tgz";
sha1 = "2de19618c66dc247dcfb6f99338035d8245a2cee";
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 = "vary___vary_1.1.2.tgz";
path = fetchurl {
name = "vary___vary_1.1.2.tgz";
url = "https://registry.yarnpkg.com/vary/-/vary-1.1.2.tgz";
sha1 = "2299f02c6ded30d4a5961b0b9f74524a18f634fc";
};
}
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
{
name = "webidl_conversions___webidl_conversions_3.0.1.tgz";
path = fetchurl {
name = "webidl_conversions___webidl_conversions_3.0.1.tgz";
url = "https://registry.yarnpkg.com/webidl-conversions/-/webidl-conversions-3.0.1.tgz";
sha1 = "24534275e2a7bc6be7bc86611cc16ae0a5654871";
};
}
{
name = "whatwg_url___whatwg_url_5.0.0.tgz";
path = fetchurl {
name = "whatwg_url___whatwg_url_5.0.0.tgz";
url = "https://registry.yarnpkg.com/whatwg-url/-/whatwg-url-5.0.0.tgz";
sha1 = "966454e8765462e37644d3626f6742ce8b70965d";
};
}
{
name = "which_boxed_primitive___which_boxed_primitive_1.0.2.tgz";
path = fetchurl {
name = "which_boxed_primitive___which_boxed_primitive_1.0.2.tgz";
url = "https://registry.yarnpkg.com/which-boxed-primitive/-/which-boxed-primitive-1.0.2.tgz";
sha1 = "13757bc89b209b049fe5d86430e21cf40a89a8e6";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "which_pm_runs___which_pm_runs_1.0.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "which_pm_runs___which_pm_runs_1.0.0.tgz";
url = "https://registry.yarnpkg.com/which-pm-runs/-/which-pm-runs-1.0.0.tgz";
sha1 = "670b3afbc552e0b55df6b7780ca74615f23ad1cb";
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 = "which___which_2.0.2.tgz";
path = fetchurl {
name = "which___which_2.0.2.tgz";
url = "https://registry.yarnpkg.com/which/-/which-2.0.2.tgz";
sha1 = "7c6a8dd0a636a0327e10b59c9286eee93f3f51b1";
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "wide_align___wide_align_1.1.3.tgz";
path = fetchurl {
name = "wide_align___wide_align_1.1.3.tgz";
url = "https://registry.yarnpkg.com/wide-align/-/wide-align-1.1.3.tgz";
sha1 = "ae074e6bdc0c14a431e804e624549c633b000457";
};
}
{
name = "winston_transport___winston_transport_4.4.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "winston_transport___winston_transport_4.4.0.tgz";
url = "https://registry.yarnpkg.com/winston-transport/-/winston-transport-4.4.0.tgz";
sha1 = "17af518daa690d5b2ecccaa7acf7b20ca7925e59";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "winston___winston_3.3.3.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "winston___winston_3.3.3.tgz";
url = "https://registry.yarnpkg.com/winston/-/winston-3.3.3.tgz";
sha1 = "ae6172042cafb29786afa3d09c8ff833ab7c9170";
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 = "word_wrap___word_wrap_1.2.3.tgz";
path = fetchurl {
name = "word_wrap___word_wrap_1.2.3.tgz";
url = "https://registry.yarnpkg.com/word-wrap/-/word-wrap-1.2.3.tgz";
sha1 = "610636f6b1f703891bd34771ccb17fb93b47079c";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "wrap_ansi___wrap_ansi_6.2.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "wrap_ansi___wrap_ansi_6.2.0.tgz";
url = "https://registry.yarnpkg.com/wrap-ansi/-/wrap-ansi-6.2.0.tgz";
sha1 = "e9393ba07102e6c91a3b221478f0257cd2856e53";
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
};
}
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
{
name = "wrap_ansi___wrap_ansi_7.0.0.tgz";
path = fetchurl {
name = "wrap_ansi___wrap_ansi_7.0.0.tgz";
url = "https://registry.yarnpkg.com/wrap-ansi/-/wrap-ansi-7.0.0.tgz";
sha1 = "67e145cff510a6a6984bdf1152911d69d2eb9e43";
};
}
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 = "wrappy___wrappy_1.0.2.tgz";
path = fetchurl {
name = "wrappy___wrappy_1.0.2.tgz";
url = "https://registry.yarnpkg.com/wrappy/-/wrappy-1.0.2.tgz";
sha1 = "b5243d8f3ec1aa35f1364605bc0d1036e30ab69f";
};
}
{
grafana-image-renderer: 2.1.0 -> 3.0.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.0
2021-06-07 21:38:04 +00:00
name = "ws___ws_7.4.6.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.1.0 -> 3.0.0 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.0.0
2021-06-07 21:38:04 +00:00
name = "ws___ws_7.4.6.tgz";
url = "https://registry.yarnpkg.com/ws/-/ws-7.4.6.tgz";
sha1 = "5654ca8ecdeee47c33a9a4bf6d28e2be2980377c";
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
};
}
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "y18n___y18n_5.0.8.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "y18n___y18n_5.0.8.tgz";
url = "https://registry.yarnpkg.com/y18n/-/y18n-5.0.8.tgz";
sha1 = "7f4934d0f7ca8c56f95314939ddcd2dd91ce1d55";
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
};
}
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
{
name = "yallist___yallist_4.0.0.tgz";
path = fetchurl {
name = "yallist___yallist_4.0.0.tgz";
url = "https://registry.yarnpkg.com/yallist/-/yallist-4.0.0.tgz";
sha1 = "9bb92790d9c0effec63be73519e11a35019a3a72";
};
}
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
{
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "yaml___yaml_1.10.2.tgz";
path = fetchurl {
name = "yaml___yaml_1.10.2.tgz";
url = "https://registry.yarnpkg.com/yaml/-/yaml-1.10.2.tgz";
sha1 = "2301c5ffbf12b467de8da2333a459e29e7920e4b";
};
}
{
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "yargs_parser___yargs_parser_20.2.9.tgz";
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
path = fetchurl {
grafana-image-renderer: 3.2.0 -> 3.2.1 ChangeLog: https://github.com/grafana/grafana-image-renderer/releases/tag/v3.2.1
2021-10-09 18:51:00 +00:00
name = "yargs_parser___yargs_parser_20.2.9.tgz";
url = "https://registry.yarnpkg.com/yargs-parser/-/yargs-parser-20.2.9.tgz";
sha1 = "2eb7dc3b0289718fc295f362753845c41a0c94ee";
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
};
}
{
name = "yargs___yargs_16.2.0.tgz";
path = fetchurl {
name = "yargs___yargs_16.2.0.tgz";
url = "https://registry.yarnpkg.com/yargs/-/yargs-16.2.0.tgz";
sha1 = "1c82bf0f6b6a66eafce7ef30e376f49a12477f66";
};
}
{
name = "yauzl___yauzl_2.10.0.tgz";
path = fetchurl {
name = "yauzl___yauzl_2.10.0.tgz";
url = "https://registry.yarnpkg.com/yauzl/-/yauzl-2.10.0.tgz";
sha1 = "c7eb17c93e112cb1086fa6d8e51fb0667b79a5f9";
};
}
{
name = "yocto_queue___yocto_queue_0.1.0.tgz";
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
path = fetchurl {
grafana-image-renderer: 2.0.1 -> 2.1.0
2021-05-11 21:40:44 +00:00
name = "yocto_queue___yocto_queue_0.1.0.tgz";
url = "https://registry.yarnpkg.com/yocto-queue/-/yocto-queue-0.1.0.tgz";
sha1 = "0294eb3dee05028d31ee1a5fa2c556a6aaf10a1b";
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
};
}
];
}
Reference in New Issue Copy Permalink