Sakurai/pdf.js
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
5242c38af5
pdf.js/package-lock.json

33199 lines
1.1 MiB
JSON
Raw Normal View History

Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
{
"name": "pdf.js",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"lockfileVersion": 2,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"requires": true,
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"packages": {
"": {
"name": "pdf.js",
"hasInstallScript": true,
"license": "Apache-2.0",
"devDependencies": {
Update npm packages
2022-02-20 18:08:23 +09:00
"@babel/core": "^7.17.5",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/plugin-transform-modules-commonjs": "^7.16.8",
Update npm packages
2022-02-06 19:24:14 +09:00
"@babel/plugin-transform-runtime": "^7.17.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/preset-env": "^7.16.11",
Update npm packages
2022-02-20 18:08:23 +09:00
"@babel/runtime": "^7.17.2",
Update the `@javascript-obfuscator/escodegen` package to the latest version The only changes are support for [Class static initialization blocks](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Class_static_initialization_blocks), and the diff for the `node_modules\@javascript-obfuscator\escodegen\escodegen.js` file contains only: ```diff @@ -1506,6 +1506,13 @@ return result; }, + StaticBlock: function (stmt, flags) { + return [ + 'static' + space, + this.BlockStatement(stmt, flags) + ]; + }, + ThrowStatement: function (stmt, flags) { return [join( 'throw', ```
2022-02-06 19:26:07 +09:00
"@javascript-obfuscator/escodegen": "2.3.0",
Update npm packages
2022-01-09 18:05:52 +09:00
"acorn": "^8.7.0",
"autoprefixer": "^10.4.2",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"babel-loader": "^8.2.3",
Add the `caniuse-lite` package Since the Autoprefixer plugin indirectly depends on this, it seems like a good idea to add this as a direct dependency in the PDF.js project to hopefully avoid having to manually update `caniuse-lite` in the future; see https://github.com/browserslist/browserslist#browsers-data-updating Also, slightly tweaks the Autoprefixer config for GENERIC-builds of the PDF.js library; note that this change doesn't affect the contents of the *built* `web/viewer.js` file.
2022-02-27 19:32:23 +09:00
"caniuse-lite": "^1.0.30001312",
Update npm packages
2022-01-23 18:58:15 +09:00
"canvas": "^2.9.0",
Update npm packages
2022-02-20 18:08:23 +09:00
"core-js": "^3.21.1",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"cross-env": "^7.0.3",
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"dommatrix": "^0.0.24",
Update npm packages
2022-02-20 18:08:23 +09:00
"es-module-shims": "^1.4.6",
"eslint": "^8.9.0",
"eslint-config-prettier": "^8.4.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"eslint-plugin-fetch-options": "^0.0.5",
"eslint-plugin-html": "^6.2.0",
Update npm packages
2022-01-09 18:05:52 +09:00
"eslint-plugin-import": "^2.25.4",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"eslint-plugin-json": "^3.1.0",
"eslint-plugin-mozilla": "^2.11.1",
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"eslint-plugin-no-unsanitized": "^4.0.1",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"eslint-plugin-prettier": "^4.0.0",
"eslint-plugin-sort-exports": "^0.6.0",
Update npm packages
2022-02-20 18:08:23 +09:00
"eslint-plugin-unicorn": "^41.0.0",
Update npm packages
2022-02-06 19:24:14 +09:00
"globals": "^13.12.1",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"gulp": "^4.0.2",
"gulp-postcss": "^9.0.1",
"gulp-rename": "^2.0.0",
"gulp-replace": "^1.1.3",
"gulp-zip": "^5.1.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"jasmine": "^4.0.2",
Update npm packages
2022-02-06 19:24:14 +09:00
"jsdoc": "^3.6.10",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"jstransformer-markdown-it": "^2.1.0",
"merge-stream": "^2.0.0",
"mkdirp": "^1.0.4",
"needle": "^3.0.0",
Update npm packages
2022-02-06 19:24:14 +09:00
"postcss": "^8.4.6",
Update npm packages
2022-02-20 18:08:23 +09:00
"postcss-calc": "^8.2.4",
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"prettier": "^2.5.1",
Update npm packages
2022-02-20 18:08:23 +09:00
"puppeteer": "^13.3.2",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"rimraf": "^3.0.2",
"streamqueue": "^1.1.2",
Update npm packages
2022-02-20 18:08:23 +09:00
"stylelint": "^14.5.1",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"stylelint-config-prettier": "^9.0.3",
"stylelint-prettier": "^2.0.0",
"systemjs": "^0.21.6",
"systemjs-plugin-babel": "^0.0.25",
"terser": "^5.10.0",
"through2": "^4.0.2",
"ttest": "^3.0.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"typescript": "^4.5.5",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"typogr": "^0.6.8",
"vinyl": "^2.2.1",
"vinyl-fs": "^3.0.3",
"web-streams-polyfill": "^3.2.0",
Update npm packages
2022-02-20 18:08:23 +09:00
"webpack": "^5.69.1",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"webpack-stream": "^7.0.0",
"wintersmith": "^2.5.0",
Update npm packages
2021-12-26 19:09:29 +09:00
"yargs": "^17.3.1"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
Update npm packages
2022-02-06 19:24:14 +09:00
"node_modules/@ampproject/remapping": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/@ampproject/remapping/-/remapping-2.1.2.tgz",
"integrity": "sha512-hoyByceqwKirw7w3Z7gnIIZC3Wx3J484Y3L/cMpXFbr7d9ZQj2mODrirNzcJa+SM3UlpWXYvKV4RlRpFXlWgXg==",
Update npm packages
2022-02-06 19:24:14 +09:00
"dev": true,
"dependencies": {
"@jridgewell/trace-mapping": "^0.3.0"
},
"engines": {
"node": ">=6.0.0"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/@babel/code-frame": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.16.7.tgz",
"integrity": "sha512-iAXqUn8IIeBTNd72xsFlgaXHkMBMt6y4HJp1tIaK465CWLT/fG1aqB7ykr95gHHmlBdGbFeWWfyB4NJJ0nmeIg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/highlight": "^7.16.7"
},
"engines": {
"node": ">=6.9.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/@babel/compat-data": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.8",
"resolved": "https://registry.npmjs.org/@babel/compat-data/-/compat-data-7.16.8.tgz",
"integrity": "sha512-m7OkX0IdKLKPpBlJtF561YJal5y/jyI5fNfWbPxh2D/nbzzGI4qRyrD8xO2jB24u7l+5I2a43scCG2IrfjC50Q==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/core": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "7.17.5",
"resolved": "https://registry.npmjs.org/@babel/core/-/core-7.17.5.tgz",
"integrity": "sha512-/BBMw4EvjmyquN5O+t5eh0+YqB3XXJkYD2cjKpYtWOfFy4lQ4UozNSmxAcWT8r2XtZs0ewG+zrfsqeR15i1ajA==",
Update npm packages
2022-01-09 18:05:52 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-02-20 18:08:23 +09:00
"@ampproject/remapping": "^2.1.0",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/code-frame": "^7.16.7",
Update npm packages
2022-02-20 18:08:23 +09:00
"@babel/generator": "^7.17.3",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-compilation-targets": "^7.16.7",
"@babel/helper-module-transforms": "^7.16.7",
Update npm packages
2022-02-20 18:08:23 +09:00
"@babel/helpers": "^7.17.2",
"@babel/parser": "^7.17.3",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/template": "^7.16.7",
Update npm packages
2022-02-20 18:08:23 +09:00
"@babel/traverse": "^7.17.3",
Update npm packages
2022-02-06 19:24:14 +09:00
"@babel/types": "^7.17.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"convert-source-map": "^1.7.0",
"debug": "^4.1.0",
"gensync": "^1.0.0-beta.2",
"json5": "^2.1.2",
Update npm packages
2022-02-06 19:24:14 +09:00
"semver": "^6.3.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/babel"
}
},
"node_modules/@babel/core/node_modules/convert-source-map": {
"version": "1.8.0",
"resolved": "https://registry.npmjs.org/convert-source-map/-/convert-source-map-1.8.0.tgz",
"integrity": "sha512-+OQdjP49zViI/6i7nIJpA8rAl4sV/JdPfU9nZs3VqOwGIgizICvuN2ru6fMd+4llL0tar18UYJXfZ/TWtmhUjA==",
"dev": true,
"dependencies": {
"safe-buffer": "~5.1.1"
}
},
"node_modules/@babel/core/node_modules/debug": {
"version": "4.3.2",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.2.tgz",
"integrity": "sha512-mOp8wKcvj7XxC78zLgw/ZA+6TSgkoE2C/ienthhRD298T7UNwAg9diBpLRxC0mOezLl4B0xV7M0cCO6P/O0Xhw==",
"dev": true,
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/@babel/core/node_modules/ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
},
"node_modules/@babel/core/node_modules/semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
"dev": true,
"bin": {
"semver": "bin/semver.js"
}
},
"node_modules/@babel/eslint-parser": {
"version": "7.16.3",
"resolved": "https://registry.npmjs.org/@babel/eslint-parser/-/eslint-parser-7.16.3.tgz",
"integrity": "sha512-iB4ElZT0jAt7PKVaeVulOECdGe6UnmA/O0P9jlF5g5GBOwDVbna8AXhHRu4s27xQf6OkveyA8iTDv1jHdDejgQ==",
"dev": true,
"dependencies": {
"eslint-scope": "^5.1.1",
"eslint-visitor-keys": "^2.1.0",
"semver": "^6.3.0"
},
"engines": {
"node": "^10.13.0 || ^12.13.0 || >=14.0.0"
},
"peerDependencies": {
"@babel/core": ">=7.11.0",
"eslint": "^7.5.0 || ^8.0.0"
}
},
"node_modules/@babel/eslint-parser/node_modules/semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
"dev": true,
"bin": {
"semver": "bin/semver.js"
}
},
"node_modules/@babel/generator": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "7.17.3",
"resolved": "https://registry.npmjs.org/@babel/generator/-/generator-7.17.3.tgz",
"integrity": "sha512-+R6Dctil/MgUsZsZAkYgK+ADNSZzJRRy0TvY65T71z/CR854xHQ1EweBYXdfT+HNeN7w0cSJJEzgxZMv40pxsg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-02-06 19:24:14 +09:00
"@babel/types": "^7.17.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"jsesc": "^2.5.1",
"source-map": "^0.5.0"
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/generator/node_modules/source-map": {
"version": "0.5.7",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.7.tgz",
"integrity": "sha1-igOdLRAh0i0eoUyA2OpGi6LvP8w=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/@babel/helper-annotate-as-pure": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-annotate-as-pure/-/helper-annotate-as-pure-7.16.7.tgz",
"integrity": "sha512-s6t2w/IPQVTAET1HitoowRGXooX8mCgtuP5195wD/QJPV6wYjpujCGF7JuMODVX2ZAJOf1GT6DT9MHEZvLOFSw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-builder-binary-assignment-operator-visitor": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-builder-binary-assignment-operator-visitor/-/helper-builder-binary-assignment-operator-visitor-7.16.7.tgz",
"integrity": "sha512-C6FdbRaxYjwVu/geKW4ZeQ0Q31AftgRcdSnZ5/jsH6BzCJbtvXvhpfkbkThYSuutZA7nCXpPR6AD9zd1dprMkA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-explode-assignable-expression": "^7.16.7",
"@babel/types": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-compilation-targets": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-compilation-targets/-/helper-compilation-targets-7.16.7.tgz",
"integrity": "sha512-mGojBwIWcwGD6rfqgRXVlVYmPAv7eOpIemUG3dGnDdCY4Pae70ROij3XmfrH6Fa1h1aiDylpglbZyktfzyo/hA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/compat-data": "^7.16.4",
"@babel/helper-validator-option": "^7.16.7",
Update npm packages
2021-12-26 19:09:29 +09:00
"browserslist": "^4.17.5",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"semver": "^6.3.0"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0"
}
},
"node_modules/@babel/helper-compilation-targets/node_modules/semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
"dev": true,
"bin": {
"semver": "bin/semver.js"
}
},
"node_modules/@babel/helper-create-class-features-plugin": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.10",
"resolved": "https://registry.npmjs.org/@babel/helper-create-class-features-plugin/-/helper-create-class-features-plugin-7.16.10.tgz",
"integrity": "sha512-wDeej0pu3WN/ffTxMNCPW5UCiOav8IcLRxSIyp/9+IF2xJUM9h/OYjg0IJLHaL6F8oU8kqMz9nc1vryXhMsgXg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-annotate-as-pure": "^7.16.7",
"@babel/helper-environment-visitor": "^7.16.7",
"@babel/helper-function-name": "^7.16.7",
"@babel/helper-member-expression-to-functions": "^7.16.7",
"@babel/helper-optimise-call-expression": "^7.16.7",
"@babel/helper-replace-supers": "^7.16.7",
"@babel/helper-split-export-declaration": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0"
}
},
"node_modules/@babel/helper-create-regexp-features-plugin": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-create-regexp-features-plugin/-/helper-create-regexp-features-plugin-7.16.7.tgz",
"integrity": "sha512-fk5A6ymfp+O5+p2yCkXAu5Kyj6v0xh0RBeNcAkYUMDvvAAoxvSKXn+Jb37t/yWFiQVDFK1ELpUTD8/aLhCPu+g==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-annotate-as-pure": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"regexpu-core": "^4.7.1"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0"
}
},
"node_modules/@babel/helper-define-polyfill-provider": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "0.3.1",
"resolved": "https://registry.npmjs.org/@babel/helper-define-polyfill-provider/-/helper-define-polyfill-provider-0.3.1.tgz",
"integrity": "sha512-J9hGMpJQmtWmj46B3kBHmL38UhJGhYX7eqkcq+2gsstyYt341HmPeWspihX43yVRA0mS+8GGk2Gckc7bY/HCmA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"@babel/helper-compilation-targets": "^7.13.0",
"@babel/helper-module-imports": "^7.12.13",
"@babel/helper-plugin-utils": "^7.13.0",
"@babel/traverse": "^7.13.0",
"debug": "^4.1.1",
"lodash.debounce": "^4.0.8",
"resolve": "^1.14.2",
"semver": "^6.1.2"
},
"peerDependencies": {
"@babel/core": "^7.4.0-0"
}
},
"node_modules/@babel/helper-define-polyfill-provider/node_modules/debug": {
"version": "4.3.3",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.3.tgz",
"integrity": "sha512-/zxw5+vh1Tfv+4Qn7a5nsbcJKPaSvCDhojn6FEl9vupwK2VCSDtEiEtqr8DFtzYFOdz63LBkxec7DYuc2jon6Q==",
"dev": true,
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/@babel/helper-define-polyfill-provider/node_modules/ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
},
"node_modules/@babel/helper-define-polyfill-provider/node_modules/resolve": {
"version": "1.20.0",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.20.0.tgz",
"integrity": "sha512-wENBPt4ySzg4ybFQW2TT1zMQucPK95HSh/nq2CFTZVOGut2+pQvSsgtda4d26YrYcr067wjbmzOG8byDPBX63A==",
"dev": true,
"dependencies": {
"is-core-module": "^2.2.0",
"path-parse": "^1.0.6"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/@babel/helper-define-polyfill-provider/node_modules/semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
"dev": true,
"bin": {
"semver": "bin/semver.js"
}
},
Update npm packages
2021-12-26 19:09:29 +09:00
"node_modules/@babel/helper-environment-visitor": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-environment-visitor/-/helper-environment-visitor-7.16.7.tgz",
"integrity": "sha512-SLLb0AAn6PkUeAfKJCCOl9e1R53pQlGAfc4y4XuMRZfqeMYLE0dM1LMhqbGAlGQY0lfw5/ohoYWAe9V1yibRag==",
Update npm packages
2021-12-26 19:09:29 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Update npm packages
2021-12-26 19:09:29 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/@babel/helper-explode-assignable-expression": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-explode-assignable-expression/-/helper-explode-assignable-expression-7.16.7.tgz",
"integrity": "sha512-KyUenhWMC8VrxzkGP0Jizjo4/Zx+1nNZhgocs+gLzyZyB8SHidhoq9KK/8Ato4anhwsivfkBLftky7gvzbZMtQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-function-name": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-function-name/-/helper-function-name-7.16.7.tgz",
"integrity": "sha512-QfDfEnIUyyBSR3HtrtGECuZ6DAyCkYFp7GHl75vFtTnn6pjKeK0T1DB5lLkFvBea8MdaiUABx3osbgLyInoejA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-get-function-arity": "^7.16.7",
"@babel/template": "^7.16.7",
"@babel/types": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-get-function-arity": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-get-function-arity/-/helper-get-function-arity-7.16.7.tgz",
"integrity": "sha512-flc+RLSOBXzNzVhcLu6ujeHUrD6tANAOU5ojrRx/as+tbzf8+stUCj7+IfRRoAbEZqj/ahXEMsjhOhgeZsrnTw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-hoist-variables": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-hoist-variables/-/helper-hoist-variables-7.16.7.tgz",
"integrity": "sha512-m04d/0Op34H5v7pbZw6pSKP7weA6lsMvfiIAMeIvkY/R4xQtBSMFEigu9QTZ2qB/9l22vsxtM8a+Q8CzD255fg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-member-expression-to-functions": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-member-expression-to-functions/-/helper-member-expression-to-functions-7.16.7.tgz",
"integrity": "sha512-VtJ/65tYiU/6AbMTDwyoXGPKHgTsfRarivm+YbB5uAzKUyuPjgZSgAFeG87FCigc7KNHu2Pegh1XIT3lXjvz3Q==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-module-imports": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-module-imports/-/helper-module-imports-7.16.7.tgz",
"integrity": "sha512-LVtS6TqjJHFc+nYeITRo6VLXve70xmq7wPhWTqDJusJEgGmkAACWwMiTNrvfoQo6hEhFwAIixNkvB0jPXDL8Wg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-module-transforms": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-module-transforms/-/helper-module-transforms-7.16.7.tgz",
"integrity": "sha512-gaqtLDxJEFCeQbYp9aLAefjhkKdjKcdh6DB7jniIGU3Pz52WAmP268zK0VgPz9hUNkMSYeH976K2/Y6yPadpng==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-environment-visitor": "^7.16.7",
"@babel/helper-module-imports": "^7.16.7",
"@babel/helper-simple-access": "^7.16.7",
"@babel/helper-split-export-declaration": "^7.16.7",
"@babel/helper-validator-identifier": "^7.16.7",
"@babel/template": "^7.16.7",
"@babel/traverse": "^7.16.7",
"@babel/types": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-optimise-call-expression": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-optimise-call-expression/-/helper-optimise-call-expression-7.16.7.tgz",
"integrity": "sha512-EtgBhg7rd/JcnpZFXpBy0ze1YRfdm7BnBX4uKMBd3ixa3RGAE002JZB66FJyNH7g0F38U05pXmA5P8cBh7z+1w==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-plugin-utils": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-plugin-utils/-/helper-plugin-utils-7.16.7.tgz",
"integrity": "sha512-Qg3Nk7ZxpgMrsox6HreY1ZNKdBq7K72tDSliA6dCl5f007jR4ne8iD5UzuNnCJH2xBf2BEEVGr+/OL6Gdp7RxA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-remap-async-to-generator": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.8",
"resolved": "https://registry.npmjs.org/@babel/helper-remap-async-to-generator/-/helper-remap-async-to-generator-7.16.8.tgz",
"integrity": "sha512-fm0gH7Flb8H51LqJHy3HJ3wnE1+qtYR2A99K06ahwrawLdOFsCEWjZOrYricXJHoPSudNKxrMBUPEIPxiIIvBw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-annotate-as-pure": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/helper-wrap-function": "^7.16.8",
"@babel/types": "^7.16.8"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-replace-supers": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-replace-supers/-/helper-replace-supers-7.16.7.tgz",
"integrity": "sha512-y9vsWilTNaVnVh6xiJfABzsNpgDPKev9HnAgz6Gb1p6UUwf9NepdlsV7VXGCftJM+jqD5f7JIEubcpLjZj5dBw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-environment-visitor": "^7.16.7",
"@babel/helper-member-expression-to-functions": "^7.16.7",
"@babel/helper-optimise-call-expression": "^7.16.7",
"@babel/traverse": "^7.16.7",
"@babel/types": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-simple-access": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-simple-access/-/helper-simple-access-7.16.7.tgz",
"integrity": "sha512-ZIzHVyoeLMvXMN/vok/a4LWRy8G2v205mNP0XOuf9XRLyX5/u9CnVulUtDgUTama3lT+bf/UqucuZjqiGuTS1g==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-skip-transparent-expression-wrappers": {
"version": "7.16.0",
"resolved": "https://registry.npmjs.org/@babel/helper-skip-transparent-expression-wrappers/-/helper-skip-transparent-expression-wrappers-7.16.0.tgz",
"integrity": "sha512-+il1gTy0oHwUsBQZyJvukbB4vPMdcYBrFHa0Uc4AizLxbq6BOYC51Rv4tWocX9BLBDLZ4kc6qUFpQ6HRgL+3zw==",
"dev": true,
"dependencies": {
"@babel/types": "^7.16.0"
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-split-export-declaration": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-split-export-declaration/-/helper-split-export-declaration-7.16.7.tgz",
"integrity": "sha512-xbWoy/PFoxSWazIToT9Sif+jJTlrMcndIsaOKvTA6u7QEo7ilkRZpjew18/W3c7nm8fXdUDXh02VXTbZ0pGDNw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-validator-identifier": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-validator-identifier/-/helper-validator-identifier-7.16.7.tgz",
"integrity": "sha512-hsEnFemeiW4D08A5gUAZxLBTXpZ39P+a+DGDsHw1yxqyQ/jzFEnxf5uTEGp+3bzAbNOxU1paTgYS4ECU/IgfDw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-validator-option": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-validator-option/-/helper-validator-option-7.16.7.tgz",
"integrity": "sha512-TRtenOuRUVo9oIQGPC5G9DgK4743cdxvtOw0weQNpZXaS16SCBi5MNjZF8vba3ETURjZpTbVn7Vvcf2eAwFozQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-wrap-function": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.8",
"resolved": "https://registry.npmjs.org/@babel/helper-wrap-function/-/helper-wrap-function-7.16.8.tgz",
"integrity": "sha512-8RpyRVIAW1RcDDGTA+GpPAwV22wXCfKOoM9bet6TLkGIFTkRQSkH1nMQ5Yet4MpoXe1ZwHPVtNasc2w0uZMqnw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-function-name": "^7.16.7",
"@babel/template": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/traverse": "^7.16.8",
"@babel/types": "^7.16.8"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helpers": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "7.17.2",
"resolved": "https://registry.npmjs.org/@babel/helpers/-/helpers-7.17.2.tgz",
"integrity": "sha512-0Qu7RLR1dILozr/6M0xgj+DFPmi6Bnulgm9M8BVa9ZCWxDqlSnqt3cf8IDPB5m45sVXUZ0kuQAgUrdSFFH79fQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/template": "^7.16.7",
Update npm packages
2022-02-06 19:24:14 +09:00
"@babel/traverse": "^7.17.0",
"@babel/types": "^7.17.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/highlight": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/highlight/-/highlight-7.16.7.tgz",
"integrity": "sha512-aKpPMfLvGO3Q97V0qhw/V2SWNWlwfJknuwAunU7wZLSfrM4xTBvg7E5opUVi1kJTBKihE38CPg4nBiqX83PWYw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-validator-identifier": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"chalk": "^2.0.0",
"js-tokens": "^4.0.0"
Update npm packages
2022-01-09 18:05:52 +09:00
},
"engines": {
"node": ">=6.9.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/@babel/parser": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "7.17.3",
"resolved": "https://registry.npmjs.org/@babel/parser/-/parser-7.17.3.tgz",
"integrity": "sha512-7yJPvPV+ESz2IUTPbOL+YkIGyCqOyNIzdguKQuJGnH7bg1WTIifuM21YqokFt/THWh1AkCRn9IgoykTRCBVpzA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"bin": {
"parser": "bin/babel-parser.js"
},
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression/-/plugin-bugfix-safari-id-destructuring-collision-in-function-expression-7.16.7.tgz",
"integrity": "sha512-anv/DObl7waiGEnC24O9zqL0pSuI9hljihqiDuFHC8d7/bjr/4RLGPWuc8rYOff/QPzbEPSkzG8wGG9aDuhHRg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0"
}
},
"node_modules/@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining/-/plugin-bugfix-v8-spread-parameters-in-optional-chaining-7.16.7.tgz",
"integrity": "sha512-di8vUHRdf+4aJ7ltXhaDbPoszdkh59AQtJM5soLsuHpQJdFQZOA4uGj0V2u/CZ8bJ/u8ULDL5yq6FO/bCXnKHw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@babel/helper-skip-transparent-expression-wrappers": "^7.16.0",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/plugin-proposal-optional-chaining": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.13.0"
}
},
"node_modules/@babel/plugin-proposal-async-generator-functions": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.8",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-async-generator-functions/-/plugin-proposal-async-generator-functions-7.16.8.tgz",
"integrity": "sha512-71YHIvMuiuqWJQkebWJtdhQTfd4Q4mF76q2IX37uZPkG9+olBxsX+rH1vkhFto4UeJZ9dPY2s+mDvhDm1u2BGQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/helper-remap-async-to-generator": "^7.16.8",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@babel/plugin-syntax-async-generators": "^7.8.4"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-proposal-class-properties": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-class-properties/-/plugin-proposal-class-properties-7.16.7.tgz",
"integrity": "sha512-IobU0Xme31ewjYOShSIqd/ZGM/r/cuOz2z0MDbNrhF5FW+ZVgi0f2lyeoj9KFPDOAqsYxmLWZte1WOwlvY9aww==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-create-class-features-plugin": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-proposal-class-static-block": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-class-static-block/-/plugin-proposal-class-static-block-7.16.7.tgz",
"integrity": "sha512-dgqJJrcZoG/4CkMopzhPJjGxsIe9A8RlkQLnL/Vhhx8AA9ZuaRwGSlscSh42hazc7WSrya/IK7mTeoF0DP9tEw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-create-class-features-plugin": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@babel/plugin-syntax-class-static-block": "^7.14.5"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.12.0"
}
},
"node_modules/@babel/plugin-proposal-dynamic-import": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-dynamic-import/-/plugin-proposal-dynamic-import-7.16.7.tgz",
"integrity": "sha512-I8SW9Ho3/8DRSdmDdH3gORdyUuYnk1m4cMxUAdu5oy4n3OfN8flDEH+d60iG7dUfi0KkYwSvoalHzzdRzpWHTg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@babel/plugin-syntax-dynamic-import": "^7.8.3"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-proposal-export-namespace-from": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-export-namespace-from/-/plugin-proposal-export-namespace-from-7.16.7.tgz",
"integrity": "sha512-ZxdtqDXLRGBL64ocZcs7ovt71L3jhC1RGSyR996svrCi3PYqHNkb3SwPJCs8RIzD86s+WPpt2S73+EHCGO+NUA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@babel/plugin-syntax-export-namespace-from": "^7.8.3"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-proposal-json-strings": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-json-strings/-/plugin-proposal-json-strings-7.16.7.tgz",
"integrity": "sha512-lNZ3EEggsGY78JavgbHsK9u5P3pQaW7k4axlgFLYkMd7UBsiNahCITShLjNQschPyjtO6dADrL24757IdhBrsQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@babel/plugin-syntax-json-strings": "^7.8.3"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-proposal-logical-assignment-operators": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-logical-assignment-operators/-/plugin-proposal-logical-assignment-operators-7.16.7.tgz",
"integrity": "sha512-K3XzyZJGQCr00+EtYtrDjmwX7o7PLK6U9bi1nCwkQioRFVUv6dJoxbQjtWVtP+bCPy82bONBKG8NPyQ4+i6yjg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@babel/plugin-syntax-logical-assignment-operators": "^7.10.4"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-proposal-nullish-coalescing-operator": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-nullish-coalescing-operator/-/plugin-proposal-nullish-coalescing-operator-7.16.7.tgz",
"integrity": "sha512-aUOrYU3EVtjf62jQrCj63pYZ7k6vns2h/DQvHPWGmsJRYzWXZ6/AsfgpiRy6XiuIDADhJzP2Q9MwSMKauBQ+UQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@babel/plugin-syntax-nullish-coalescing-operator": "^7.8.3"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-proposal-numeric-separator": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-numeric-separator/-/plugin-proposal-numeric-separator-7.16.7.tgz",
"integrity": "sha512-vQgPMknOIgiuVqbokToyXbkY/OmmjAzr/0lhSIbG/KmnzXPGwW/AdhdKpi+O4X/VkWiWjnkKOBiqJrTaC98VKw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@babel/plugin-syntax-numeric-separator": "^7.10.4"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-proposal-object-rest-spread": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-object-rest-spread/-/plugin-proposal-object-rest-spread-7.16.7.tgz",
"integrity": "sha512-3O0Y4+dw94HA86qSg9IHfyPktgR7q3gpNVAeiKQd+8jBKFaU5NQS1Yatgo4wY+UFNuLjvxcSmzcsHqrhgTyBUA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2021-12-26 19:09:29 +09:00
"@babel/compat-data": "^7.16.4",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-compilation-targets": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@babel/plugin-syntax-object-rest-spread": "^7.8.3",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/plugin-transform-parameters": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-proposal-optional-catch-binding": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-optional-catch-binding/-/plugin-proposal-optional-catch-binding-7.16.7.tgz",
"integrity": "sha512-eMOH/L4OvWSZAE1VkHbr1vckLG1WUcHGJSLqqQwl2GaUqG6QjddvrOaTUMNYiv77H5IKPMZ9U9P7EaHwvAShfA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@babel/plugin-syntax-optional-catch-binding": "^7.8.3"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-proposal-optional-chaining": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-optional-chaining/-/plugin-proposal-optional-chaining-7.16.7.tgz",
"integrity": "sha512-eC3xy+ZrUcBtP7x+sq62Q/HYd674pPTb/77XZMb5wbDPGWIdUbSr4Agr052+zaUPSb+gGRnjxXfKFvx5iMJ+DA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@babel/helper-skip-transparent-expression-wrappers": "^7.16.0",
"@babel/plugin-syntax-optional-chaining": "^7.8.3"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-proposal-private-methods": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.11",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-private-methods/-/plugin-proposal-private-methods-7.16.11.tgz",
"integrity": "sha512-F/2uAkPlXDr8+BHpZvo19w3hLFKge+k75XUprE6jaqKxjGkSYcK+4c+bup5PdW/7W/Rpjwql7FTVEDW+fRAQsw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/helper-create-class-features-plugin": "^7.16.10",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-proposal-private-property-in-object": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-private-property-in-object/-/plugin-proposal-private-property-in-object-7.16.7.tgz",
"integrity": "sha512-rMQkjcOFbm+ufe3bTZLyOfsOUOxyvLXZJCTARhJr+8UMSoZmqTe1K1BgkFcrW37rAchWg57yI69ORxiWvUINuQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-annotate-as-pure": "^7.16.7",
"@babel/helper-create-class-features-plugin": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@babel/plugin-syntax-private-property-in-object": "^7.14.5"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-proposal-unicode-property-regex": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-unicode-property-regex/-/plugin-proposal-unicode-property-regex-7.16.7.tgz",
"integrity": "sha512-QRK0YI/40VLhNVGIjRNAAQkEHws0cswSdFFjpFyt943YmJIU1da9uW63Iu6NFV6CxTZW5eTDCrwZUstBWgp/Rg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-create-regexp-features-plugin": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=4"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-syntax-async-generators": {
"version": "7.8.4",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-async-generators/-/plugin-syntax-async-generators-7.8.4.tgz",
"integrity": "sha512-tycmZxkGfZaxhMRbXlPXuVFpdWlXpir2W4AMhSJgRKzk/eDlIXOhb2LHWoLpDF7TEHylV5zNhykX6KAgHJmTNw==",
"dev": true,
"dependencies": {
"@babel/helper-plugin-utils": "^7.8.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-syntax-class-properties": {
"version": "7.12.13",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-class-properties/-/plugin-syntax-class-properties-7.12.13.tgz",
"integrity": "sha512-fm4idjKla0YahUNgFNLCB0qySdsoPiZP3iQE3rky0mBUtMZ23yDJ9SJdg6dXTSDnulOVqiF3Hgr9nbXvXTQZYA==",
"dev": true,
"dependencies": {
"@babel/helper-plugin-utils": "^7.12.13"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-syntax-class-static-block": {
"version": "7.14.5",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-class-static-block/-/plugin-syntax-class-static-block-7.14.5.tgz",
"integrity": "sha512-b+YyPmr6ldyNnM6sqYeMWE+bgJcJpO6yS4QD7ymxgH34GBPNDM/THBh8iunyvKIZztiwLH4CJZ0RxTk9emgpjw==",
"dev": true,
"dependencies": {
"@babel/helper-plugin-utils": "^7.14.5"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-syntax-dynamic-import": {
"version": "7.8.3",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-dynamic-import/-/plugin-syntax-dynamic-import-7.8.3.tgz",
"integrity": "sha512-5gdGbFon+PszYzqs83S3E5mpi7/y/8M9eC90MRTZfduQOYW76ig6SOSPNe41IG5LoP3FGBn2N0RjVDSQiS94kQ==",
"dev": true,
"dependencies": {
"@babel/helper-plugin-utils": "^7.8.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-syntax-export-namespace-from": {
"version": "7.8.3",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-export-namespace-from/-/plugin-syntax-export-namespace-from-7.8.3.tgz",
"integrity": "sha512-MXf5laXo6c1IbEbegDmzGPwGNTsHZmEy6QGznu5Sh2UCWvueywb2ee+CCE4zQiZstxU9BMoQO9i6zUFSY0Kj0Q==",
"dev": true,
"dependencies": {
"@babel/helper-plugin-utils": "^7.8.3"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-syntax-json-strings": {
"version": "7.8.3",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-json-strings/-/plugin-syntax-json-strings-7.8.3.tgz",
"integrity": "sha512-lY6kdGpWHvjoe2vk4WrAapEuBR69EMxZl+RoGRhrFGNYVK8mOPAW8VfbT/ZgrFbXlDNiiaxQnAtgVCZ6jv30EA==",
"dev": true,
"dependencies": {
"@babel/helper-plugin-utils": "^7.8.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-syntax-logical-assignment-operators": {
"version": "7.10.4",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-logical-assignment-operators/-/plugin-syntax-logical-assignment-operators-7.10.4.tgz",
"integrity": "sha512-d8waShlpFDinQ5MtvGU9xDAOzKH47+FFoney2baFIoMr952hKOLp1HR7VszoZvOsV/4+RRszNY7D17ba0te0ig==",
"dev": true,
"dependencies": {
"@babel/helper-plugin-utils": "^7.10.4"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-syntax-nullish-coalescing-operator": {
"version": "7.8.3",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-nullish-coalescing-operator/-/plugin-syntax-nullish-coalescing-operator-7.8.3.tgz",
"integrity": "sha512-aSff4zPII1u2QD7y+F8oDsz19ew4IGEJg9SVW+bqwpwtfFleiQDMdzA/R+UlWDzfnHFCxxleFT0PMIrR36XLNQ==",
"dev": true,
"dependencies": {
"@babel/helper-plugin-utils": "^7.8.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-syntax-numeric-separator": {
"version": "7.10.4",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-numeric-separator/-/plugin-syntax-numeric-separator-7.10.4.tgz",
"integrity": "sha512-9H6YdfkcK/uOnY/K7/aA2xpzaAgkQn37yzWUMRK7OaPOqOpGS1+n0H5hxT9AUw9EsSjPW8SVyMJwYRtWs3X3ug==",
"dev": true,
"dependencies": {
"@babel/helper-plugin-utils": "^7.10.4"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-syntax-object-rest-spread": {
"version": "7.8.3",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-object-rest-spread/-/plugin-syntax-object-rest-spread-7.8.3.tgz",
"integrity": "sha512-XoqMijGZb9y3y2XskN+P1wUGiVwWZ5JmoDRwx5+3GmEplNyVM2s2Dg8ILFQm8rWM48orGy5YpI5Bl8U1y7ydlA==",
"dev": true,
"dependencies": {
"@babel/helper-plugin-utils": "^7.8.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-syntax-optional-catch-binding": {
"version": "7.8.3",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-optional-catch-binding/-/plugin-syntax-optional-catch-binding-7.8.3.tgz",
"integrity": "sha512-6VPD0Pc1lpTqw0aKoeRTMiB+kWhAoT24PA+ksWSBrFtl5SIRVpZlwN3NNPQjehA2E/91FV3RjLWoVTglWcSV3Q==",
"dev": true,
"dependencies": {
"@babel/helper-plugin-utils": "^7.8.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-syntax-optional-chaining": {
"version": "7.8.3",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-optional-chaining/-/plugin-syntax-optional-chaining-7.8.3.tgz",
"integrity": "sha512-KoK9ErH1MBlCPxV0VANkXW2/dw4vlbGDrFgz8bmUsBGYkFRcbRwMh6cIJubdPrkxRwuGdtCk0v/wPTKbQgBjkg==",
"dev": true,
"dependencies": {
"@babel/helper-plugin-utils": "^7.8.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-syntax-private-property-in-object": {
"version": "7.14.5",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-private-property-in-object/-/plugin-syntax-private-property-in-object-7.14.5.tgz",
"integrity": "sha512-0wVnp9dxJ72ZUJDV27ZfbSj6iHLoytYZmh3rFcxNnvsJF3ktkzLDZPy/mA17HGsaQT3/DQsWYX1f1QGWkCoVUg==",
"dev": true,
"dependencies": {
"@babel/helper-plugin-utils": "^7.14.5"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-syntax-top-level-await": {
"version": "7.14.5",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-top-level-await/-/plugin-syntax-top-level-await-7.14.5.tgz",
"integrity": "sha512-hx++upLv5U1rgYfwe1xBQUhRmU41NEvpUvrp8jkrSCdvGSnM5/qdRMtylJ6PG5OFkBaHkbTAKTnd3/YyESRHFw==",
"dev": true,
"dependencies": {
"@babel/helper-plugin-utils": "^7.14.5"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-arrow-functions": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-arrow-functions/-/plugin-transform-arrow-functions-7.16.7.tgz",
"integrity": "sha512-9ffkFFMbvzTvv+7dTp/66xvZAWASuPD5Tl9LK3Z9vhOmANo6j94rik+5YMBt4CwHVMWLWpMsriIc2zsa3WW3xQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-async-to-generator": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.8",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-async-to-generator/-/plugin-transform-async-to-generator-7.16.8.tgz",
"integrity": "sha512-MtmUmTJQHCnyJVrScNzNlofQJ3dLFuobYn3mwOTKHnSCMtbNsqvF71GQmJfFjdrXSsAA7iysFmYWw4bXZ20hOg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-module-imports": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/helper-remap-async-to-generator": "^7.16.8"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-block-scoped-functions": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-block-scoped-functions/-/plugin-transform-block-scoped-functions-7.16.7.tgz",
"integrity": "sha512-JUuzlzmF40Z9cXyytcbZEZKckgrQzChbQJw/5PuEHYeqzCsvebDx0K0jWnIIVcmmDOAVctCgnYs0pMcrYj2zJg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-block-scoping": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-block-scoping/-/plugin-transform-block-scoping-7.16.7.tgz",
"integrity": "sha512-ObZev2nxVAYA4bhyusELdo9hb3H+A56bxH3FZMbEImZFiEDYVHXQSJ1hQKFlDnlt8G9bBrCZ5ZpURZUrV4G5qQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-classes": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-classes/-/plugin-transform-classes-7.16.7.tgz",
"integrity": "sha512-WY7og38SFAGYRe64BrjKf8OrE6ulEHtr5jEYaZMwox9KebgqPi67Zqz8K53EKk1fFEJgm96r32rkKZ3qA2nCWQ==",
"dev": true,
"dependencies": {
"@babel/helper-annotate-as-pure": "^7.16.7",
"@babel/helper-environment-visitor": "^7.16.7",
"@babel/helper-function-name": "^7.16.7",
"@babel/helper-optimise-call-expression": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
"@babel/helper-replace-supers": "^7.16.7",
"@babel/helper-split-export-declaration": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"globals": "^11.1.0"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-classes/node_modules/globals": {
"version": "11.12.0",
"resolved": "https://registry.npmjs.org/globals/-/globals-11.12.0.tgz",
"integrity": "sha512-WOBp/EEGUiIsJSp7wcv/y6MO+lV9UoncWqxuFfm8eBwzWNgyfBd6Gz+IeKQ9jCmyhoH99g15M3T+QaVHFjizVA==",
"dev": true,
"engines": {
"node": ">=4"
}
},
"node_modules/@babel/plugin-transform-computed-properties": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-computed-properties/-/plugin-transform-computed-properties-7.16.7.tgz",
"integrity": "sha512-gN72G9bcmenVILj//sv1zLNaPyYcOzUho2lIJBMh/iakJ9ygCo/hEF9cpGb61SCMEDxbbyBoVQxrt+bWKu5KGw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-destructuring": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-destructuring/-/plugin-transform-destructuring-7.16.7.tgz",
"integrity": "sha512-VqAwhTHBnu5xBVDCvrvqJbtLUa++qZaWC0Fgr2mqokBlulZARGyIvZDoqbPlPaKImQ9dKAcCzbv+ul//uqu70A==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-dotall-regex": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-dotall-regex/-/plugin-transform-dotall-regex-7.16.7.tgz",
"integrity": "sha512-Lyttaao2SjZF6Pf4vk1dVKv8YypMpomAbygW+mU5cYP3S5cWTfCJjG8xV6CFdzGFlfWK81IjL9viiTvpb6G7gQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-create-regexp-features-plugin": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-duplicate-keys": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-duplicate-keys/-/plugin-transform-duplicate-keys-7.16.7.tgz",
"integrity": "sha512-03DvpbRfvWIXyK0/6QiR1KMTWeT6OcQ7tbhjrXyFS02kjuX/mu5Bvnh5SDSWHxyawit2g5aWhKwI86EE7GUnTw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-exponentiation-operator": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-exponentiation-operator/-/plugin-transform-exponentiation-operator-7.16.7.tgz",
"integrity": "sha512-8UYLSlyLgRixQvlYH3J2ekXFHDFLQutdy7FfFAMm3CPZ6q9wHCwnUyiXpQCe3gVVnQlHc5nsuiEVziteRNTXEA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-builder-binary-assignment-operator-visitor": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-for-of": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-for-of/-/plugin-transform-for-of-7.16.7.tgz",
"integrity": "sha512-/QZm9W92Ptpw7sjI9Nx1mbcsWz33+l8kuMIQnDwgQBG5s3fAfQvkRjQ7NqXhtNcKOnPkdICmUHyCaWW06HCsqg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-function-name": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-function-name/-/plugin-transform-function-name-7.16.7.tgz",
"integrity": "sha512-SU/C68YVwTRxqWj5kgsbKINakGag0KTgq9f2iZEXdStoAbOzLHEBRYzImmA6yFo8YZhJVflvXmIHUO7GWHmxxA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-compilation-targets": "^7.16.7",
"@babel/helper-function-name": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-literals": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-literals/-/plugin-transform-literals-7.16.7.tgz",
"integrity": "sha512-6tH8RTpTWI0s2sV6uq3e/C9wPo4PTqqZps4uF0kzQ9/xPLFQtipynvmT1g/dOfEJ+0EQsHhkQ/zyRId8J2b8zQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-member-expression-literals": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-member-expression-literals/-/plugin-transform-member-expression-literals-7.16.7.tgz",
"integrity": "sha512-mBruRMbktKQwbxaJof32LT9KLy2f3gH+27a5XSuXo6h7R3vqltl0PgZ80C8ZMKw98Bf8bqt6BEVi3svOh2PzMw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-modules-amd": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-modules-amd/-/plugin-transform-modules-amd-7.16.7.tgz",
"integrity": "sha512-KaaEtgBL7FKYwjJ/teH63oAmE3lP34N3kshz8mm4VMAw7U3PxjVwwUmxEFksbgsNUaO3wId9R2AVQYSEGRa2+g==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-module-transforms": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"babel-plugin-dynamic-import-node": "^2.3.3"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-modules-commonjs": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.8",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-modules-commonjs/-/plugin-transform-modules-commonjs-7.16.8.tgz",
"integrity": "sha512-oflKPvsLT2+uKQopesJt3ApiaIS2HW+hzHFcwRNtyDGieAeC/dIHZX8buJQ2J2X1rxGPy4eRcUijm3qcSPjYcA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-module-transforms": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
"@babel/helper-simple-access": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"babel-plugin-dynamic-import-node": "^2.3.3"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-modules-systemjs": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-modules-systemjs/-/plugin-transform-modules-systemjs-7.16.7.tgz",
"integrity": "sha512-DuK5E3k+QQmnOqBR9UkusByy5WZWGRxfzV529s9nPra1GE7olmxfqO2FHobEOYSPIjPBTr4p66YDcjQnt8cBmw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-hoist-variables": "^7.16.7",
"@babel/helper-module-transforms": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
"@babel/helper-validator-identifier": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"babel-plugin-dynamic-import-node": "^2.3.3"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-modules-umd": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-modules-umd/-/plugin-transform-modules-umd-7.16.7.tgz",
"integrity": "sha512-EMh7uolsC8O4xhudF2F6wedbSHm1HHZ0C6aJ7K67zcDNidMzVcxWdGr+htW9n21klm+bOn+Rx4CBsAntZd3rEQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-module-transforms": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-named-capturing-groups-regex": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.8",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-named-capturing-groups-regex/-/plugin-transform-named-capturing-groups-regex-7.16.8.tgz",
"integrity": "sha512-j3Jw+n5PvpmhRR+mrgIh04puSANCk/T/UA3m3P1MjJkhlK906+ApHhDIqBQDdOgL/r1UYpz4GNclTXxyZrYGSw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-create-regexp-features-plugin": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0"
}
},
"node_modules/@babel/plugin-transform-new-target": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-new-target/-/plugin-transform-new-target-7.16.7.tgz",
"integrity": "sha512-xiLDzWNMfKoGOpc6t3U+etCE2yRnn3SM09BXqWPIZOBpL2gvVrBWUKnsJx0K/ADi5F5YC5f8APFfWrz25TdlGg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-object-super": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-object-super/-/plugin-transform-object-super-7.16.7.tgz",
"integrity": "sha512-14J1feiQVWaGvRxj2WjyMuXS2jsBkgB3MdSN5HuC2G5nRspa5RK9COcs82Pwy5BuGcjb+fYaUj94mYcOj7rCvw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
"@babel/helper-replace-supers": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-parameters": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-parameters/-/plugin-transform-parameters-7.16.7.tgz",
"integrity": "sha512-AT3MufQ7zZEhU2hwOA11axBnExW0Lszu4RL/tAlUJBuNoRak+wehQW8h6KcXOcgjY42fHtDxswuMhMjFEuv/aw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-property-literals": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-property-literals/-/plugin-transform-property-literals-7.16.7.tgz",
"integrity": "sha512-z4FGr9NMGdoIl1RqavCqGG+ZuYjfZ/hkCIeuH6Do7tXmSm0ls11nYVSJqFEUOSJbDab5wC6lRE/w6YjVcr6Hqw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-regenerator": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-regenerator/-/plugin-transform-regenerator-7.16.7.tgz",
"integrity": "sha512-mF7jOgGYCkSJagJ6XCujSQg+6xC1M77/03K2oBmVJWoFGNUtnVJO4WHKJk3dnPC8HCcj4xBQP1Egm8DWh3Pb3Q==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"regenerator-transform": "^0.14.2"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-reserved-words": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-reserved-words/-/plugin-transform-reserved-words-7.16.7.tgz",
"integrity": "sha512-KQzzDnZ9hWQBjwi5lpY5v9shmm6IVG0U9pB18zvMu2i4H90xpT4gmqwPYsn8rObiadYe2M0gmgsiOIF5A/2rtg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-runtime": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "7.17.0",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-runtime/-/plugin-transform-runtime-7.17.0.tgz",
"integrity": "sha512-fr7zPWnKXNc1xoHfrIU9mN/4XKX4VLZ45Q+oMhfsYIaHvg7mHgmhfOy/ckRWqDK7XF3QDigRpkh5DKq6+clE8A==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-module-imports": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"babel-plugin-polyfill-corejs2": "^0.3.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"babel-plugin-polyfill-corejs3": "^0.5.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"babel-plugin-polyfill-regenerator": "^0.3.0",
"semver": "^6.3.0"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-runtime/node_modules/semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
"dev": true,
"bin": {
"semver": "bin/semver.js"
}
},
"node_modules/@babel/plugin-transform-shorthand-properties": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-shorthand-properties/-/plugin-transform-shorthand-properties-7.16.7.tgz",
"integrity": "sha512-hah2+FEnoRoATdIb05IOXf+4GzXYTq75TVhIn1PewihbpyrNWUt2JbudKQOETWw6QpLe+AIUpJ5MVLYTQbeeUg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-spread": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-spread/-/plugin-transform-spread-7.16.7.tgz",
"integrity": "sha512-+pjJpgAngb53L0iaA5gU/1MLXJIfXcYepLgXB3esVRf4fqmj8f2cxM3/FKaHsZms08hFQJkFccEWuIpm429TXg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@babel/helper-skip-transparent-expression-wrappers": "^7.16.0"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-sticky-regex": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-sticky-regex/-/plugin-transform-sticky-regex-7.16.7.tgz",
"integrity": "sha512-NJa0Bd/87QV5NZZzTuZG5BPJjLYadeSZ9fO6oOUoL4iQx+9EEuw/eEM92SrsT19Yc2jgB1u1hsjqDtH02c3Drw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-template-literals": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-template-literals/-/plugin-transform-template-literals-7.16.7.tgz",
"integrity": "sha512-VwbkDDUeenlIjmfNeDX/V0aWrQH2QiVyJtwymVQSzItFDTpxfyJh3EVaQiS0rIN/CqbLGr0VcGmuwyTdZtdIsA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-typeof-symbol": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-typeof-symbol/-/plugin-transform-typeof-symbol-7.16.7.tgz",
"integrity": "sha512-p2rOixCKRJzpg9JB4gjnG4gjWkWa89ZoYUnl9snJ1cWIcTH/hvxZqfO+WjG6T8DRBpctEol5jw1O5rA8gkCokQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-unicode-escapes": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-unicode-escapes/-/plugin-transform-unicode-escapes-7.16.7.tgz",
"integrity": "sha512-TAV5IGahIz3yZ9/Hfv35TV2xEm+kaBDaZQCn2S/hG9/CZ0DktxJv9eKfPc7yYCvOYR4JGx1h8C+jcSOvgaaI/Q==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-unicode-regex": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-unicode-regex/-/plugin-transform-unicode-regex-7.16.7.tgz",
"integrity": "sha512-oC5tYYKw56HO75KZVLQ+R/Nl3Hro9kf8iG0hXoaHP7tjAyCpvqBiSNe6vGrZni1Z6MggmUOC6A7VP7AVmw225Q==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-create-regexp-features-plugin": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/preset-env": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.11",
"resolved": "https://registry.npmjs.org/@babel/preset-env/-/preset-env-7.16.11.tgz",
"integrity": "sha512-qcmWG8R7ZW6WBRPZK//y+E3Cli151B20W1Rv7ln27vuPaXU/8TKms6jFdiJtF7UDTxcrb7mZd88tAeK9LjdT8g==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/compat-data": "^7.16.8",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-compilation-targets": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
"@babel/helper-validator-option": "^7.16.7",
"@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression": "^7.16.7",
"@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/plugin-proposal-async-generator-functions": "^7.16.8",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/plugin-proposal-class-properties": "^7.16.7",
"@babel/plugin-proposal-class-static-block": "^7.16.7",
"@babel/plugin-proposal-dynamic-import": "^7.16.7",
"@babel/plugin-proposal-export-namespace-from": "^7.16.7",
"@babel/plugin-proposal-json-strings": "^7.16.7",
"@babel/plugin-proposal-logical-assignment-operators": "^7.16.7",
"@babel/plugin-proposal-nullish-coalescing-operator": "^7.16.7",
"@babel/plugin-proposal-numeric-separator": "^7.16.7",
"@babel/plugin-proposal-object-rest-spread": "^7.16.7",
"@babel/plugin-proposal-optional-catch-binding": "^7.16.7",
"@babel/plugin-proposal-optional-chaining": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/plugin-proposal-private-methods": "^7.16.11",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/plugin-proposal-private-property-in-object": "^7.16.7",
"@babel/plugin-proposal-unicode-property-regex": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@babel/plugin-syntax-async-generators": "^7.8.4",
"@babel/plugin-syntax-class-properties": "^7.12.13",
"@babel/plugin-syntax-class-static-block": "^7.14.5",
"@babel/plugin-syntax-dynamic-import": "^7.8.3",
"@babel/plugin-syntax-export-namespace-from": "^7.8.3",
"@babel/plugin-syntax-json-strings": "^7.8.3",
"@babel/plugin-syntax-logical-assignment-operators": "^7.10.4",
"@babel/plugin-syntax-nullish-coalescing-operator": "^7.8.3",
"@babel/plugin-syntax-numeric-separator": "^7.10.4",
"@babel/plugin-syntax-object-rest-spread": "^7.8.3",
"@babel/plugin-syntax-optional-catch-binding": "^7.8.3",
"@babel/plugin-syntax-optional-chaining": "^7.8.3",
"@babel/plugin-syntax-private-property-in-object": "^7.14.5",
"@babel/plugin-syntax-top-level-await": "^7.14.5",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/plugin-transform-arrow-functions": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/plugin-transform-async-to-generator": "^7.16.8",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/plugin-transform-block-scoped-functions": "^7.16.7",
"@babel/plugin-transform-block-scoping": "^7.16.7",
"@babel/plugin-transform-classes": "^7.16.7",
"@babel/plugin-transform-computed-properties": "^7.16.7",
"@babel/plugin-transform-destructuring": "^7.16.7",
"@babel/plugin-transform-dotall-regex": "^7.16.7",
"@babel/plugin-transform-duplicate-keys": "^7.16.7",
"@babel/plugin-transform-exponentiation-operator": "^7.16.7",
"@babel/plugin-transform-for-of": "^7.16.7",
"@babel/plugin-transform-function-name": "^7.16.7",
"@babel/plugin-transform-literals": "^7.16.7",
"@babel/plugin-transform-member-expression-literals": "^7.16.7",
"@babel/plugin-transform-modules-amd": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/plugin-transform-modules-commonjs": "^7.16.8",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/plugin-transform-modules-systemjs": "^7.16.7",
"@babel/plugin-transform-modules-umd": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/plugin-transform-named-capturing-groups-regex": "^7.16.8",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/plugin-transform-new-target": "^7.16.7",
"@babel/plugin-transform-object-super": "^7.16.7",
"@babel/plugin-transform-parameters": "^7.16.7",
"@babel/plugin-transform-property-literals": "^7.16.7",
"@babel/plugin-transform-regenerator": "^7.16.7",
"@babel/plugin-transform-reserved-words": "^7.16.7",
"@babel/plugin-transform-shorthand-properties": "^7.16.7",
"@babel/plugin-transform-spread": "^7.16.7",
"@babel/plugin-transform-sticky-regex": "^7.16.7",
"@babel/plugin-transform-template-literals": "^7.16.7",
"@babel/plugin-transform-typeof-symbol": "^7.16.7",
"@babel/plugin-transform-unicode-escapes": "^7.16.7",
"@babel/plugin-transform-unicode-regex": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@babel/preset-modules": "^0.1.5",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/types": "^7.16.8",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"babel-plugin-polyfill-corejs2": "^0.3.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"babel-plugin-polyfill-corejs3": "^0.5.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"babel-plugin-polyfill-regenerator": "^0.3.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"core-js-compat": "^3.20.2",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"semver": "^6.3.0"
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/preset-env/node_modules/semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
"dev": true,
"bin": {
"semver": "bin/semver.js"
}
},
"node_modules/@babel/preset-modules": {
"version": "0.1.5",
"resolved": "https://registry.npmjs.org/@babel/preset-modules/-/preset-modules-0.1.5.tgz",
"integrity": "sha512-A57th6YRG7oR3cq/yt/Y84MvGgE0eJG2F1JLhKuyG+jFxEgrd/HAMJatiFtmOiZurz+0DkrvbheCLaV5f2JfjA==",
"dev": true,
"dependencies": {
"@babel/helper-plugin-utils": "^7.0.0",
"@babel/plugin-proposal-unicode-property-regex": "^7.4.4",
"@babel/plugin-transform-dotall-regex": "^7.4.4",
"@babel/types": "^7.4.4",
"esutils": "^2.0.2"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/runtime": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "7.17.2",
"resolved": "https://registry.npmjs.org/@babel/runtime/-/runtime-7.17.2.tgz",
"integrity": "sha512-hzeyJyMA1YGdJTuWU0e/j4wKXrU4OMFvY2MSlaI9B7VQb0r5cxTE3EAIS2Q7Tn2RIcDkRvTA/v2JsAEhxe99uw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"regenerator-runtime": "^0.13.4"
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/runtime/node_modules/regenerator-runtime": {
"version": "0.13.9",
"resolved": "https://registry.npmjs.org/regenerator-runtime/-/regenerator-runtime-0.13.9.tgz",
"integrity": "sha512-p3VT+cOEgxFsRRA9X4lkI1E+k2/CtnKtU4gcxyaCUreilL/vqI6CdZ3wxVUx3UOUg+gnUOQQcRI7BmSI656MYA==",
"dev": true
},
"node_modules/@babel/template": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/template/-/template-7.16.7.tgz",
"integrity": "sha512-I8j/x8kHUrbYRTUxXrrMbfCa7jxkE7tZre39x3kjr9hvI82cK1FfqLygotcWN5kdPGWcLdWMHpSBavse5tWw3w==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/code-frame": "^7.16.7",
"@babel/parser": "^7.16.7",
"@babel/types": "^7.16.7"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/traverse": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "7.17.3",
"resolved": "https://registry.npmjs.org/@babel/traverse/-/traverse-7.17.3.tgz",
"integrity": "sha512-5irClVky7TxRWIRtxlh2WPUUOLhcPN06AGgaQSB8AEwuyEBgJVuJ5imdHm5zxk8w0QS5T+tDfnDxAlhWjpb7cw==",
Update npm packages
2022-01-09 18:05:52 +09:00
"dev": true,
"dependencies": {
"@babel/code-frame": "^7.16.7",
Update npm packages
2022-02-20 18:08:23 +09:00
"@babel/generator": "^7.17.3",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-environment-visitor": "^7.16.7",
"@babel/helper-function-name": "^7.16.7",
"@babel/helper-hoist-variables": "^7.16.7",
"@babel/helper-split-export-declaration": "^7.16.7",
Update npm packages
2022-02-20 18:08:23 +09:00
"@babel/parser": "^7.17.3",
Update npm packages
2022-02-06 19:24:14 +09:00
"@babel/types": "^7.17.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"debug": "^4.1.0",
"globals": "^11.1.0"
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/traverse/node_modules/debug": {
"version": "4.3.2",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.2.tgz",
"integrity": "sha512-mOp8wKcvj7XxC78zLgw/ZA+6TSgkoE2C/ienthhRD298T7UNwAg9diBpLRxC0mOezLl4B0xV7M0cCO6P/O0Xhw==",
"dev": true,
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/@babel/traverse/node_modules/globals": {
"version": "11.12.0",
"resolved": "https://registry.npmjs.org/globals/-/globals-11.12.0.tgz",
"integrity": "sha512-WOBp/EEGUiIsJSp7wcv/y6MO+lV9UoncWqxuFfm8eBwzWNgyfBd6Gz+IeKQ9jCmyhoH99g15M3T+QaVHFjizVA==",
"dev": true,
"engines": {
"node": ">=4"
}
},
"node_modules/@babel/traverse/node_modules/ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
},
"node_modules/@babel/types": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "7.17.0",
"resolved": "https://registry.npmjs.org/@babel/types/-/types-7.17.0.tgz",
"integrity": "sha512-TmKSNO4D5rzhL5bjWFcVHHLETzfQ/AmbKpKPOSjlP0WoHZ6L911fgoOKY4Alp/emzG4cHJdyN49zpgkbXFEHHw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-validator-identifier": "^7.16.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"to-fast-properties": "^2.0.0"
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/types/node_modules/to-fast-properties": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/to-fast-properties/-/to-fast-properties-2.0.0.tgz",
"integrity": "sha1-3F5pjL0HkmW8c+A3doGk5Og/YW4=",
"dev": true,
"engines": {
"node": ">=4"
}
},
"node_modules/@eslint/eslintrc": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/@eslint/eslintrc/-/eslintrc-1.1.0.tgz",
"integrity": "sha512-C1DfL7XX4nPqGd6jcP01W9pVM1HYCuUkFk1432D7F0v3JSlUIeOYn9oCoi3eoLZ+iwBSb29BMFxxny0YrrEZqg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"ajv": "^6.12.4",
"debug": "^4.3.2",
Update npm packages
2022-02-20 18:08:23 +09:00
"espree": "^9.3.1",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"globals": "^13.9.0",
"ignore": "^4.0.6",
"import-fresh": "^3.2.1",
"js-yaml": "^4.1.0",
"minimatch": "^3.0.4",
"strip-json-comments": "^3.1.1"
},
"engines": {
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
}
},
"node_modules/@eslint/eslintrc/node_modules/argparse": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/argparse/-/argparse-2.0.1.tgz",
"integrity": "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==",
"dev": true
},
"node_modules/@eslint/eslintrc/node_modules/debug": {
"version": "4.3.3",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.3.tgz",
"integrity": "sha512-/zxw5+vh1Tfv+4Qn7a5nsbcJKPaSvCDhojn6FEl9vupwK2VCSDtEiEtqr8DFtzYFOdz63LBkxec7DYuc2jon6Q==",
"dev": true,
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/@eslint/eslintrc/node_modules/js-yaml": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.0.tgz",
"integrity": "sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==",
"dev": true,
"dependencies": {
"argparse": "^2.0.1"
},
"bin": {
"js-yaml": "bin/js-yaml.js"
}
},
"node_modules/@eslint/eslintrc/node_modules/ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
},
"node_modules/@humanwhocodes/config-array": {
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"version": "0.9.2",
"resolved": "https://registry.npmjs.org/@humanwhocodes/config-array/-/config-array-0.9.2.tgz",
"integrity": "sha512-UXOuFCGcwciWckOpmfKDq/GyhlTf9pN/BzG//x8p8zTOFEcGuA68ANXheFS0AGvy3qgZqLBUkMs7hqzqCKOVwA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"@humanwhocodes/object-schema": "^1.2.1",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"debug": "^4.1.1",
"minimatch": "^3.0.4"
},
"engines": {
"node": ">=10.10.0"
}
},
"node_modules/@humanwhocodes/config-array/node_modules/debug": {
"version": "4.3.3",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.3.tgz",
"integrity": "sha512-/zxw5+vh1Tfv+4Qn7a5nsbcJKPaSvCDhojn6FEl9vupwK2VCSDtEiEtqr8DFtzYFOdz63LBkxec7DYuc2jon6Q==",
"dev": true,
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/@humanwhocodes/config-array/node_modules/ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
},
"node_modules/@humanwhocodes/object-schema": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/@humanwhocodes/object-schema/-/object-schema-1.2.1.tgz",
"integrity": "sha512-ZnQMnLV4e7hDlUvw8H+U8ASL02SS2Gn6+9Ac3wGGLIe7+je2AeAOxPY+izIPJDfFDb7eDjev0Us8MO1iFRN8hA==",
"dev": true
},
"node_modules/@javascript-obfuscator/escodegen": {
Update the `@javascript-obfuscator/escodegen` package to the latest version The only changes are support for [Class static initialization blocks](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Class_static_initialization_blocks), and the diff for the `node_modules\@javascript-obfuscator\escodegen\escodegen.js` file contains only: ```diff @@ -1506,6 +1506,13 @@ return result; }, + StaticBlock: function (stmt, flags) { + return [ + 'static' + space, + this.BlockStatement(stmt, flags) + ]; + }, + ThrowStatement: function (stmt, flags) { return [join( 'throw', ```
2022-02-06 19:26:07 +09:00
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/@javascript-obfuscator/escodegen/-/escodegen-2.3.0.tgz",
"integrity": "sha512-QVXwMIKqYMl3KwtTirYIA6gOCiJ0ZDtptXqAv/8KWLG9uQU2fZqTVy7a/A5RvcoZhbDoFfveTxuGxJ5ibzQtkw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"@javascript-obfuscator/estraverse": "^5.3.0",
"esprima": "^4.0.1",
"esutils": "^2.0.2",
"optionator": "^0.8.1"
},
"engines": {
"node": ">=6.0"
},
"optionalDependencies": {
"source-map": "~0.6.1"
}
},
"node_modules/@javascript-obfuscator/estraverse": {
"version": "5.3.0",
"resolved": "https://registry.npmjs.org/@javascript-obfuscator/estraverse/-/estraverse-5.3.0.tgz",
"integrity": "sha512-SxIFtV5/wlXYS7G3zLVj7CddLolX8Bm/hr68fiyNL3MyG2k4FwF9B5Z5GTpVLhw2EELYNwyoYBvFlR4gGnQPdw==",
"dev": true,
"engines": {
"node": ">=4.0"
}
},
Update npm packages
2022-02-06 19:24:14 +09:00
"node_modules/@jridgewell/resolve-uri": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "3.0.5",
"resolved": "https://registry.npmjs.org/@jridgewell/resolve-uri/-/resolve-uri-3.0.5.tgz",
"integrity": "sha512-VPeQ7+wH0itvQxnG+lIzWgkysKIr3L9sslimFW55rHMdGu/qCQ5z5h9zq4gI8uBtqkpHhsF4Z/OwExufUCThew==",
Update npm packages
2022-02-06 19:24:14 +09:00
"dev": true,
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/@jridgewell/sourcemap-codec": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "1.4.11",
"resolved": "https://registry.npmjs.org/@jridgewell/sourcemap-codec/-/sourcemap-codec-1.4.11.tgz",
"integrity": "sha512-Fg32GrJo61m+VqYSdRSjRXMjQ06j8YIYfcTqndLYVAaHmroZHLJZCydsWBOTDqXS2v+mjxohBWEMfg97GXmYQg==",
Update npm packages
2022-02-06 19:24:14 +09:00
"dev": true
},
"node_modules/@jridgewell/trace-mapping": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "0.3.4",
"resolved": "https://registry.npmjs.org/@jridgewell/trace-mapping/-/trace-mapping-0.3.4.tgz",
"integrity": "sha512-vFv9ttIedivx0ux3QSjhgtCVjPZd5l46ZOMDSCwnH1yUO2e964gO8LZGyv2QkqcgR6TnBU1v+1IFqmeoG+0UJQ==",
Update npm packages
2022-02-06 19:24:14 +09:00
"dev": true,
"dependencies": {
"@jridgewell/resolve-uri": "^3.0.3",
"@jridgewell/sourcemap-codec": "^1.4.10"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/@mapbox/node-pre-gyp": {
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/@mapbox/node-pre-gyp/-/node-pre-gyp-1.0.5.tgz",
"integrity": "sha512-4srsKPXWlIxp5Vbqz5uLfBN+du2fJChBoYn/f2h991WLdk7jUvcSk/McVLSv/X+xQIPI8eGD5GjrnygdyHnhPA==",
"dev": true,
"dependencies": {
"detect-libc": "^1.0.3",
"https-proxy-agent": "^5.0.0",
"make-dir": "^3.1.0",
"node-fetch": "^2.6.1",
"nopt": "^5.0.0",
"npmlog": "^4.1.2",
"rimraf": "^3.0.2",
"semver": "^7.3.4",
"tar": "^6.1.0"
},
"bin": {
"node-pre-gyp": "bin/node-pre-gyp"
}
},
"node_modules/@mapbox/node-pre-gyp/node_modules/semver": {
"version": "7.3.5",
"resolved": "https://registry.npmjs.org/semver/-/semver-7.3.5.tgz",
"integrity": "sha512-PoeGJYh8HK4BTO/a9Tf6ZG3veo/A7ZVsYrSA6J8ny9nb3B1VrpkuN+z9OE5wfE5p6H4LchYZsegiQgbJD94ZFQ==",
"dev": true,
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
"engines": {
"node": ">=10"
}
},
"node_modules/@nodelib/fs.scandir": {
"version": "2.1.5",
"resolved": "https://registry.npmjs.org/@nodelib/fs.scandir/-/fs.scandir-2.1.5.tgz",
"integrity": "sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==",
"dev": true,
"dependencies": {
"@nodelib/fs.stat": "2.0.5",
"run-parallel": "^1.1.9"
},
"engines": {
"node": ">= 8"
}
},
"node_modules/@nodelib/fs.stat": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/@nodelib/fs.stat/-/fs.stat-2.0.5.tgz",
"integrity": "sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==",
"dev": true,
"engines": {
"node": ">= 8"
}
},
"node_modules/@nodelib/fs.walk": {
"version": "1.2.8",
"resolved": "https://registry.npmjs.org/@nodelib/fs.walk/-/fs.walk-1.2.8.tgz",
"integrity": "sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==",
"dev": true,
"dependencies": {
"@nodelib/fs.scandir": "2.1.5",
"fastq": "^1.6.0"
},
"engines": {
"node": ">= 8"
}
},
"node_modules/@types/babel-types": {
"version": "7.0.4",
"resolved": "https://registry.npmjs.org/@types/babel-types/-/babel-types-7.0.4.tgz",
"integrity": "sha512-WiZhq3SVJHFRgRYLXvpf65XnV6ipVHhnNaNvE8yCimejrGglkg38kEj0JcizqwSHxmPSjcTlig/6JouxLGEhGw==",
"dev": true
},
"node_modules/@types/babylon": {
"version": "6.16.4",
"resolved": "https://registry.npmjs.org/@types/babylon/-/babylon-6.16.4.tgz",
"integrity": "sha512-8dZMcGPno3g7pJ/d0AyJERo+lXh9i1JhDuCUs+4lNIN9eUe5Yh6UCLrpgSEi05Ve2JMLauL2aozdvKwNL0px1Q==",
"dev": true,
"dependencies": {
"@types/babel-types": "*"
}
},
"node_modules/@types/eslint": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "8.4.1",
"resolved": "https://registry.npmjs.org/@types/eslint/-/eslint-8.4.1.tgz",
"integrity": "sha512-GE44+DNEyxxh2Kc6ro/VkIj+9ma0pO0bwv9+uHSyBrikYOHr8zYcdPvnBOp1aw8s+CjRvuSx7CyWqRrNFQ59mA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"@types/estree": "*",
"@types/json-schema": "*"
}
},
"node_modules/@types/eslint-scope": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "3.7.3",
"resolved": "https://registry.npmjs.org/@types/eslint-scope/-/eslint-scope-3.7.3.tgz",
"integrity": "sha512-PB3ldyrcnAicT35TWPs5IcwKD8S333HMaa2VVv4+wdvebJkjWuW/xESoB8IwRcog8HYVYamb1g/R31Qv5Bx03g==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"@types/eslint": "*",
"@types/estree": "*"
}
},
"node_modules/@types/estree": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "0.0.51",
"resolved": "https://registry.npmjs.org/@types/estree/-/estree-0.0.51.tgz",
"integrity": "sha512-CuPgU6f3eT/XgKKPqKd/gLZV1Xmvf1a2R5POBOGQa6uv82xpls89HU5zKeVoyR8XzHd1RGNOlQlvUe3CFkjWNQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/@types/expect": {
"version": "1.20.4",
"resolved": "https://registry.npmjs.org/@types/expect/-/expect-1.20.4.tgz",
"integrity": "sha512-Q5Vn3yjTDyCMV50TB6VRIbQNxSE4OmZR86VSbGaNpfUolm0iePBB4KdEEHmxoY5sT2+2DIvXW0rvMDP2nHZ4Mg==",
"dev": true
},
"node_modules/@types/json-schema": {
"version": "7.0.9",
"resolved": "https://registry.npmjs.org/@types/json-schema/-/json-schema-7.0.9.tgz",
"integrity": "sha512-qcUXuemtEu+E5wZSJHNxUXeCZhAfXKQ41D+duX+VYPde7xyEVZci+/oXKJL13tnRs9lR2pr4fod59GT6/X1/yQ==",
"dev": true
},
"node_modules/@types/json5": {
"version": "0.0.29",
"resolved": "https://registry.npmjs.org/@types/json5/-/json5-0.0.29.tgz",
"integrity": "sha1-7ihweulOEdK4J7y+UnC86n8+ce4=",
"dev": true
},
Update npm packages
2022-01-23 18:58:15 +09:00
"node_modules/@types/linkify-it": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/@types/linkify-it/-/linkify-it-3.0.2.tgz",
"integrity": "sha512-HZQYqbiFVWufzCwexrvh694SOim8z2d+xJl5UNamcvQFejLY/2YUtzXHYi3cHdI7PMlS8ejH2slRAOJQ32aNbA==",
"dev": true
},
"node_modules/@types/markdown-it": {
"version": "12.2.3",
"resolved": "https://registry.npmjs.org/@types/markdown-it/-/markdown-it-12.2.3.tgz",
"integrity": "sha512-GKMHFfv3458yYy+v/N8gjufHO6MSZKCOXpZc5GXIWWy8uldwfmPn98vp81gZ5f9SVw8YYBctgfJ22a2d7AOMeQ==",
"dev": true,
"dependencies": {
"@types/linkify-it": "*",
"@types/mdurl": "*"
}
},
"node_modules/@types/mdurl": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/@types/mdurl/-/mdurl-1.0.2.tgz",
"integrity": "sha512-eC4U9MlIcu2q0KQmXszyn5Akca/0jrQmwDRgpAMJai7qBWq4amIQhZyNau4VYGtCeALvW1/NtjzJJ567aZxfKA==",
"dev": true
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/@types/minimist": {
"version": "1.2.2",
"resolved": "https://registry.npmjs.org/@types/minimist/-/minimist-1.2.2.tgz",
"integrity": "sha512-jhuKLIRrhvCPLqwPcx6INqmKeiA5EWrsCOPhrlFSrbrmU4ZMPjj5Ul/oLCMDO98XRUIwVm78xICz4EPCektzeQ==",
"dev": true
},
"node_modules/@types/node": {
"version": "14.14.45",
"resolved": "https://registry.npmjs.org/@types/node/-/node-14.14.45.tgz",
"integrity": "sha512-DssMqTV9UnnoxDWu959sDLZzfvqCF0qDNRjaWeYSui9xkFe61kKo4l1TWNTQONpuXEm+gLMRvdlzvNHBamzmEw==",
"dev": true
},
"node_modules/@types/normalize-package-data": {
"version": "2.4.0",
"resolved": "https://registry.npmjs.org/@types/normalize-package-data/-/normalize-package-data-2.4.0.tgz",
"integrity": "sha512-f5j5b/Gf71L+dbqxIpQ4Z2WlmI/mPJ0fOkGGmFgtb6sAu97EPczzbS3/tJKxmcYDj55OX6ssqwDAWOHIYDRDGA==",
"dev": true
},
"node_modules/@types/parse-json": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/@types/parse-json/-/parse-json-4.0.0.tgz",
"integrity": "sha512-//oorEZjL6sbPcKUaCdIGlIUeH26mgzimjBB77G6XRgnDl/L5wOnpyBGRe/Mmf5CVW3PwEBE1NjiMZ/ssFh4wA==",
"dev": true
},
"node_modules/@types/vinyl": {
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/@types/vinyl/-/vinyl-2.0.4.tgz",
"integrity": "sha512-2o6a2ixaVI2EbwBPg1QYLGQoHK56p/8X/sGfKbFC8N6sY9lfjsMf/GprtkQkSya0D4uRiutRZ2BWj7k3JvLsAQ==",
"dev": true,
"dependencies": {
"@types/expect": "^1.20.4",
"@types/node": "*"
}
},
"node_modules/@types/yauzl": {
"version": "2.9.2",
"resolved": "https://registry.npmjs.org/@types/yauzl/-/yauzl-2.9.2.tgz",
"integrity": "sha512-8uALY5LTvSuHgloDVUvWP3pIauILm+8/0pDMokuDYIoNsOkSwd5AiHBTSEJjKTDcZr5z8UpgOWZkxBF4iJftoA==",
"dev": true,
"optional": true,
"dependencies": {
"@types/node": "*"
}
},
"node_modules/@webassemblyjs/ast": {
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/ast/-/ast-1.11.1.tgz",
"integrity": "sha512-ukBh14qFLjxTQNTXocdyksN5QdM28S1CxHt2rdskFyL+xFV7VremuBLVbmCePj+URalXBENx/9Lm7lnhihtCSw==",
"dev": true,
"dependencies": {
"@webassemblyjs/helper-numbers": "1.11.1",
"@webassemblyjs/helper-wasm-bytecode": "1.11.1"
}
},
"node_modules/@webassemblyjs/floating-point-hex-parser": {
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/floating-point-hex-parser/-/floating-point-hex-parser-1.11.1.tgz",
"integrity": "sha512-iGRfyc5Bq+NnNuX8b5hwBrRjzf0ocrJPI6GWFodBFzmFnyvrQ83SHKhmilCU/8Jv67i4GJZBMhEzltxzcNagtQ==",
"dev": true
},
"node_modules/@webassemblyjs/helper-api-error": {
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/helper-api-error/-/helper-api-error-1.11.1.tgz",
"integrity": "sha512-RlhS8CBCXfRUR/cwo2ho9bkheSXG0+NwooXcc3PAILALf2QLdFyj7KGsKRbVc95hZnhnERon4kW/D3SZpp6Tcg==",
"dev": true
},
"node_modules/@webassemblyjs/helper-buffer": {
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/helper-buffer/-/helper-buffer-1.11.1.tgz",
"integrity": "sha512-gwikF65aDNeeXa8JxXa2BAk+REjSyhrNC9ZwdT0f8jc4dQQeDQ7G4m0f2QCLPJiMTTO6wfDmRmj/pW0PsUvIcA==",
"dev": true
},
"node_modules/@webassemblyjs/helper-numbers": {
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/helper-numbers/-/helper-numbers-1.11.1.tgz",
"integrity": "sha512-vDkbxiB8zfnPdNK9Rajcey5C0w+QJugEglN0of+kmO8l7lDb77AnlKYQF7aarZuCrv+l0UvqL+68gSDr3k9LPQ==",
"dev": true,
"dependencies": {
"@webassemblyjs/floating-point-hex-parser": "1.11.1",
"@webassemblyjs/helper-api-error": "1.11.1",
"@xtuc/long": "4.2.2"
}
},
"node_modules/@webassemblyjs/helper-wasm-bytecode": {
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/helper-wasm-bytecode/-/helper-wasm-bytecode-1.11.1.tgz",
"integrity": "sha512-PvpoOGiJwXeTrSf/qfudJhwlvDQxFgelbMqtq52WWiXC6Xgg1IREdngmPN3bs4RoO83PnL/nFrxucXj1+BX62Q==",
"dev": true
},
"node_modules/@webassemblyjs/helper-wasm-section": {
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/helper-wasm-section/-/helper-wasm-section-1.11.1.tgz",
"integrity": "sha512-10P9No29rYX1j7F3EVPX3JvGPQPae+AomuSTPiF9eBQeChHI6iqjMIwR9JmOJXwpnn/oVGDk7I5IlskuMwU/pg==",
"dev": true,
"dependencies": {
"@webassemblyjs/ast": "1.11.1",
"@webassemblyjs/helper-buffer": "1.11.1",
"@webassemblyjs/helper-wasm-bytecode": "1.11.1",
"@webassemblyjs/wasm-gen": "1.11.1"
}
},
"node_modules/@webassemblyjs/ieee754": {
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/ieee754/-/ieee754-1.11.1.tgz",
"integrity": "sha512-hJ87QIPtAMKbFq6CGTkZYJivEwZDbQUgYd3qKSadTNOhVY7p+gfP6Sr0lLRVTaG1JjFj+r3YchoqRYxNH3M0GQ==",
"dev": true,
"dependencies": {
"@xtuc/ieee754": "^1.2.0"
}
},
"node_modules/@webassemblyjs/leb128": {
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/leb128/-/leb128-1.11.1.tgz",
"integrity": "sha512-BJ2P0hNZ0u+Th1YZXJpzW6miwqQUGcIHT1G/sf72gLVD9DZ5AdYTqPNbHZh6K1M5VmKvFXwGSWZADz+qBWxeRw==",
"dev": true,
"dependencies": {
"@xtuc/long": "4.2.2"
}
},
"node_modules/@webassemblyjs/utf8": {
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/utf8/-/utf8-1.11.1.tgz",
"integrity": "sha512-9kqcxAEdMhiwQkHpkNiorZzqpGrodQQ2IGrHHxCy+Ozng0ofyMA0lTqiLkVs1uzTRejX+/O0EOT7KxqVPuXosQ==",
"dev": true
},
"node_modules/@webassemblyjs/wasm-edit": {
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/wasm-edit/-/wasm-edit-1.11.1.tgz",
"integrity": "sha512-g+RsupUC1aTHfR8CDgnsVRVZFJqdkFHpsHMfJuWQzWU3tvnLC07UqHICfP+4XyL2tnr1amvl1Sdp06TnYCmVkA==",
"dev": true,
"dependencies": {
"@webassemblyjs/ast": "1.11.1",
"@webassemblyjs/helper-buffer": "1.11.1",
"@webassemblyjs/helper-wasm-bytecode": "1.11.1",
"@webassemblyjs/helper-wasm-section": "1.11.1",
"@webassemblyjs/wasm-gen": "1.11.1",
"@webassemblyjs/wasm-opt": "1.11.1",
"@webassemblyjs/wasm-parser": "1.11.1",
"@webassemblyjs/wast-printer": "1.11.1"
}
},
"node_modules/@webassemblyjs/wasm-gen": {
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/wasm-gen/-/wasm-gen-1.11.1.tgz",
"integrity": "sha512-F7QqKXwwNlMmsulj6+O7r4mmtAlCWfO/0HdgOxSklZfQcDu0TpLiD1mRt/zF25Bk59FIjEuGAIyn5ei4yMfLhA==",
"dev": true,
"dependencies": {
"@webassemblyjs/ast": "1.11.1",
"@webassemblyjs/helper-wasm-bytecode": "1.11.1",
"@webassemblyjs/ieee754": "1.11.1",
"@webassemblyjs/leb128": "1.11.1",
"@webassemblyjs/utf8": "1.11.1"
}
},
"node_modules/@webassemblyjs/wasm-opt": {
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/wasm-opt/-/wasm-opt-1.11.1.tgz",
"integrity": "sha512-VqnkNqnZlU5EB64pp1l7hdm3hmQw7Vgqa0KF/KCNO9sIpI6Fk6brDEiX+iCOYrvMuBWDws0NkTOxYEb85XQHHw==",
"dev": true,
"dependencies": {
"@webassemblyjs/ast": "1.11.1",
"@webassemblyjs/helper-buffer": "1.11.1",
"@webassemblyjs/wasm-gen": "1.11.1",
"@webassemblyjs/wasm-parser": "1.11.1"
}
},
"node_modules/@webassemblyjs/wasm-parser": {
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/wasm-parser/-/wasm-parser-1.11.1.tgz",
"integrity": "sha512-rrBujw+dJu32gYB7/Lup6UhdkPx9S9SnobZzRVL7VcBH9Bt9bCBLEuX/YXOOtBsOZ4NQrRykKhffRWHvigQvOA==",
"dev": true,
"dependencies": {
"@webassemblyjs/ast": "1.11.1",
"@webassemblyjs/helper-api-error": "1.11.1",
"@webassemblyjs/helper-wasm-bytecode": "1.11.1",
"@webassemblyjs/ieee754": "1.11.1",
"@webassemblyjs/leb128": "1.11.1",
"@webassemblyjs/utf8": "1.11.1"
}
},
"node_modules/@webassemblyjs/wast-printer": {
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/wast-printer/-/wast-printer-1.11.1.tgz",
"integrity": "sha512-IQboUWM4eKzWW+N/jij2sRatKMh99QEelo3Eb2q0qXkvPRISAj8Qxtmw5itwqK+TTkBuUIE45AxYPToqPtL5gg==",
"dev": true,
"dependencies": {
"@webassemblyjs/ast": "1.11.1",
"@xtuc/long": "4.2.2"
}
},
"node_modules/@xtuc/ieee754": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/@xtuc/ieee754/-/ieee754-1.2.0.tgz",
"integrity": "sha512-DX8nKgqcGwsc0eJSqYt5lwP4DH5FlHnmuWWBRy7X0NcaGR0ZtuyeESgMwTYVEtxmsNGY+qit4QYT/MIYTOTPeA==",
"dev": true
},
"node_modules/@xtuc/long": {
"version": "4.2.2",
"resolved": "https://registry.npmjs.org/@xtuc/long/-/long-4.2.2.tgz",
"integrity": "sha512-NuHqBY1PB/D8xU6s/thBgOAiAP7HOYDQ32+BFZILJ8ivkUkAHQnWfn6WhL79Owj1qmUnoN/YPhktdIoucipkAQ==",
"dev": true
},
"node_modules/abbrev": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/abbrev/-/abbrev-1.1.1.tgz",
"integrity": "sha512-nne9/IiQ/hzIhY6pdDnbBtz7DjPTKrY00P/zvPSm5pOFkl6xuGrGnXn/VtTNNfNtAfZ9/1RtehkszU9qcTii0Q==",
"dev": true
},
"node_modules/acorn": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "8.7.0",
"resolved": "https://registry.npmjs.org/acorn/-/acorn-8.7.0.tgz",
"integrity": "sha512-V/LGr1APy+PXIwKebEWrkZPwoeoF+w1jiOBUmuxuiUIaOHtob8Qc9BTrYo7VuI5fR8tqsy+buA2WFooR5olqvQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"bin": {
"acorn": "bin/acorn"
},
"engines": {
"node": ">=0.4.0"
}
},
"node_modules/acorn-globals": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/acorn-globals/-/acorn-globals-3.1.0.tgz",
"integrity": "sha1-/YJw9x+7SZawBPqIDuXUZXOnMb8=",
"dev": true,
"dependencies": {
"acorn": "^4.0.4"
}
},
"node_modules/acorn-globals/node_modules/acorn": {
"version": "4.0.13",
"resolved": "https://registry.npmjs.org/acorn/-/acorn-4.0.13.tgz",
"integrity": "sha1-EFSVrlNh1pe9GVyCUZLhrX8lN4c=",
"dev": true,
"bin": {
"acorn": "bin/acorn"
},
"engines": {
"node": ">=0.4.0"
}
},
"node_modules/acorn-import-assertions": {
"version": "1.8.0",
"resolved": "https://registry.npmjs.org/acorn-import-assertions/-/acorn-import-assertions-1.8.0.tgz",
"integrity": "sha512-m7VZ3jwz4eK6A4Vtt8Ew1/mNbP24u0FhdyfA7fSvnJR6LMdfOYnmuIrrJAgrYfYJ10F/otaHTtrtrtmHdMNzEw==",
"dev": true,
"peerDependencies": {
"acorn": "^8"
}
},
"node_modules/acorn-jsx": {
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"version": "5.3.2",
"resolved": "https://registry.npmjs.org/acorn-jsx/-/acorn-jsx-5.3.2.tgz",
"integrity": "sha512-rq9s+JNhf0IChjtDXxllJ7g41oZk5SlXtp0LHwyA5cejwn7vKmKp4pPri6YEePv2PU65sAsegbXtIinmDFDXgQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"peerDependencies": {
"acorn": "^6.0.0 || ^7.0.0 || ^8.0.0"
}
},
"node_modules/agent-base": {
"version": "6.0.2",
"resolved": "https://registry.npmjs.org/agent-base/-/agent-base-6.0.2.tgz",
"integrity": "sha512-RZNwNclF7+MS/8bDg70amg32dyeZGZxiDuQmZxKLAlQjr3jGyLx+4Kkk58UO7D2QdgFIQCovuSuZESne6RG6XQ==",
"dev": true,
"dependencies": {
"debug": "4"
},
"engines": {
"node": ">= 6.0.0"
}
},
"node_modules/agent-base/node_modules/debug": {
"version": "4.3.1",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.1.tgz",
"integrity": "sha512-doEwdvm4PCeK4K3RQN2ZC2BYUBaxwLARCqZmMjtF8a51J2Rb0xpVloFRnCODwqjpwnAoao4pelN8l3RJdv3gRQ==",
"dev": true,
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/agent-base/node_modules/ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
},
"node_modules/ajv": {
"version": "6.12.6",
"resolved": "https://registry.npmjs.org/ajv/-/ajv-6.12.6.tgz",
"integrity": "sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==",
"dev": true,
"dependencies": {
"fast-deep-equal": "^3.1.1",
"fast-json-stable-stringify": "^2.0.0",
"json-schema-traverse": "^0.4.1",
"uri-js": "^4.2.2"
},
"funding": {
"type": "github",
"url": "https://github.com/sponsors/epoberezkin"
}
},
"node_modules/ajv-keywords": {
"version": "3.5.2",
"resolved": "https://registry.npmjs.org/ajv-keywords/-/ajv-keywords-3.5.2.tgz",
"integrity": "sha512-5p6WTN0DdTGVQk6VjcEju19IgaHudalcfabD7yhDGeA6bcQnmL+CpveLJq/3hvfwd1aof6L386Ougkx6RfyMIQ==",
"dev": true,
"peerDependencies": {
"ajv": "^6.9.1"
}
},
"node_modules/align-text": {
"version": "0.1.4",
"resolved": "https://registry.npmjs.org/align-text/-/align-text-0.1.4.tgz",
"integrity": "sha1-DNkKVhCT810KmSVsIrcGlDP60Rc=",
"dev": true,
"dependencies": {
"kind-of": "^3.0.2",
"longest": "^1.0.1",
"repeat-string": "^1.5.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/align-text/node_modules/kind-of": {
"version": "3.2.2",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz",
"integrity": "sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=",
"dev": true,
"dependencies": {
"is-buffer": "^1.1.5"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/ansi-colors": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/ansi-colors/-/ansi-colors-1.1.0.tgz",
"integrity": "sha512-SFKX67auSNoVR38N3L+nvsPjOE0bybKTYbkf5tRvushrAPQ9V75huw0ZxBkKVeRU9kqH3d6HA4xTckbwZ4ixmA==",
"dev": true,
"dependencies": {
"ansi-wrap": "^0.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/ansi-gray": {
"version": "0.1.1",
"resolved": "https://registry.npmjs.org/ansi-gray/-/ansi-gray-0.1.1.tgz",
"integrity": "sha1-KWLPVOyXksSFEKPetSRDaGHvclE=",
"dev": true,
"dependencies": {
"ansi-wrap": "0.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/ansi-regex": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.1.1.tgz",
"integrity": "sha1-w7M6te42DYbg5ijwRorn7yfWVN8=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/ansi-styles": {
"version": "3.2.1",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-3.2.1.tgz",
"integrity": "sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA==",
"dev": true,
"dependencies": {
"color-convert": "^1.9.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/ansi-wrap": {
"version": "0.1.0",
"resolved": "https://registry.npmjs.org/ansi-wrap/-/ansi-wrap-0.1.0.tgz",
"integrity": "sha1-qCJQ3bABXponyoLoLqYDu/pF768=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/anymatch": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/anymatch/-/anymatch-2.0.0.tgz",
"integrity": "sha512-5teOsQWABXHHBFP9y3skS5P3d/WfWXpv3FUpy+LorMrNYaT9pI4oLMQX7jzQ2KklNpGpWHzdCXTDT2Y3XGlZBw==",
"dev": true,
"dependencies": {
"micromatch": "^3.1.4",
"normalize-path": "^2.1.1"
}
},
"node_modules/append-buffer": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/append-buffer/-/append-buffer-1.0.2.tgz",
"integrity": "sha1-2CIM9GYIFSXv6lBhTz3mUU36WPE=",
"dev": true,
"dependencies": {
"buffer-equal": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/aproba": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/aproba/-/aproba-1.2.0.tgz",
"integrity": "sha512-Y9J6ZjXtoYh8RnXVCMOU/ttDmk1aBjunq9vO0ta5x85WDQiQfUF9sIPBITdbiiIVcBo03Hi3jMxigBtsddlXRw==",
"dev": true
},
"node_modules/archy": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/archy/-/archy-1.0.0.tgz",
"integrity": "sha1-+cjBN1fMHde8N5rHeyxipcKGjEA=",
"dev": true
},
"node_modules/are-we-there-yet": {
"version": "1.1.5",
"resolved": "https://registry.npmjs.org/are-we-there-yet/-/are-we-there-yet-1.1.5.tgz",
"integrity": "sha512-5hYdAkZlcG8tOLujVDTgCT+uPX0VnpAH28gWsLfzpXYm7wP6mp5Q/gYyR7YQ0cKVJcXJnl3j2kpBan13PtQf6w==",
"dev": true,
"dependencies": {
"delegates": "^1.0.0",
"readable-stream": "^2.0.6"
}
},
"node_modules/argparse": {
"version": "1.0.10",
"resolved": "https://registry.npmjs.org/argparse/-/argparse-1.0.10.tgz",
"integrity": "sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==",
"dev": true,
"dependencies": {
"sprintf-js": "~1.0.2"
}
},
"node_modules/arr-diff": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/arr-diff/-/arr-diff-4.0.0.tgz",
"integrity": "sha1-1kYQdP6/7HHn4VI1dhoyml3HxSA=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/arr-filter": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/arr-filter/-/arr-filter-1.1.2.tgz",
"integrity": "sha1-Q/3d0JHo7xGqTEXZzcGOLf8XEe4=",
"dev": true,
"dependencies": {
"make-iterator": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/arr-flatten": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/arr-flatten/-/arr-flatten-1.1.0.tgz",
"integrity": "sha512-L3hKV5R/p5o81R7O02IGnwpDmkp6E982XhtbuwSe3O4qOtMMMtodicASA1Cny2U+aCXcNpml+m4dPsvsJ3jatg==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/arr-map": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/arr-map/-/arr-map-2.0.2.tgz",
"integrity": "sha1-Onc0X/wc814qkYJWAfnljy4kysQ=",
"dev": true,
"dependencies": {
"make-iterator": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/arr-union": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/arr-union/-/arr-union-3.1.0.tgz",
"integrity": "sha1-45sJrqne+Gao8gbiiK9jkZuuOcQ=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/array-each": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/array-each/-/array-each-1.0.1.tgz",
"integrity": "sha1-p5SvDAWrF1KEbudTofIRoFugxE8=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/array-includes": {
"version": "3.1.4",
"resolved": "https://registry.npmjs.org/array-includes/-/array-includes-3.1.4.tgz",
"integrity": "sha512-ZTNSQkmWumEbiHO2GF4GmWxYVTiQyJy2XOTa15sdQSrvKn7l+180egQMqlrMOUMCyLMD7pmyQe4mMDUT6Behrw==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.2",
"define-properties": "^1.1.3",
"es-abstract": "^1.19.1",
"get-intrinsic": "^1.1.1",
"is-string": "^1.0.7"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/array-includes/node_modules/define-properties": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.1.3.tgz",
"integrity": "sha512-3MqfYKj2lLzdMSf8ZIZE/V+Zuy+BgD6f164e8K2w7dgnpKArBDerGYpM46IYYcjnkdPNMjPk9A6VFB8+3SKlXQ==",
"dev": true,
"dependencies": {
"object-keys": "^1.0.12"
},
"engines": {
"node": ">= 0.4"
}
},
"node_modules/array-includes/node_modules/object-keys": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz",
"integrity": "sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==",
"dev": true,
"engines": {
"node": ">= 0.4"
}
},
"node_modules/array-initial": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/array-initial/-/array-initial-1.1.0.tgz",
"integrity": "sha1-L6dLJnOTccOUe9enrcc74zSz15U=",
"dev": true,
"dependencies": {
"array-slice": "^1.0.0",
"is-number": "^4.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/array-initial/node_modules/is-number": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/is-number/-/is-number-4.0.0.tgz",
"integrity": "sha512-rSklcAIlf1OmFdyAqbnWTLVelsQ58uvZ66S/ZyawjWqIviTWCjg2PzVGw8WUA+nNuPTqb4wgA+NszrJ+08LlgQ==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/array-last": {
"version": "1.3.0",
"resolved": "https://registry.npmjs.org/array-last/-/array-last-1.3.0.tgz",
"integrity": "sha512-eOCut5rXlI6aCOS7Z7kCplKRKyiFQ6dHFBem4PwlwKeNFk2/XxTrhRh5T9PyaEWGy/NHTZWbY+nsZlNFJu9rYg==",
"dev": true,
"dependencies": {
"is-number": "^4.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/array-last/node_modules/is-number": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/is-number/-/is-number-4.0.0.tgz",
"integrity": "sha512-rSklcAIlf1OmFdyAqbnWTLVelsQ58uvZ66S/ZyawjWqIviTWCjg2PzVGw8WUA+nNuPTqb4wgA+NszrJ+08LlgQ==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/array-slice": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/array-slice/-/array-slice-1.1.0.tgz",
"integrity": "sha512-B1qMD3RBP7O8o0H2KbrXDyB0IccejMF15+87Lvlor12ONPRHP6gTjXMNkt/d3ZuOGbAe66hFmaCfECI24Ufp6w==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/array-sort": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/array-sort/-/array-sort-1.0.0.tgz",
"integrity": "sha512-ihLeJkonmdiAsD7vpgN3CRcx2J2S0TiYW+IS/5zHBI7mKUq3ySvBdzzBfD236ubDBQFiiyG3SWCPc+msQ9KoYg==",
"dev": true,
"dependencies": {
"default-compare": "^1.0.0",
"get-value": "^2.0.6",
"kind-of": "^5.0.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/array-sort/node_modules/kind-of": {
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-5.1.0.tgz",
"integrity": "sha512-NGEErnH6F2vUuXDh+OlbcKW7/wOcfdRHaZ7VWtqCztfHri/++YKmP51OdWeGPuqCOba6kk2OTe5d02VmTB80Pw==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/array-union": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/array-union/-/array-union-2.1.0.tgz",
"integrity": "sha512-HGyxoOTYUyCM6stUe6EJgnd4EoewAI7zMdfqO+kGjnlZmBDz/cR5pf8r/cR4Wq60sL/p0IkcjUEEPwS3GFrIyw==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/array-unique": {
"version": "0.3.2",
"resolved": "https://registry.npmjs.org/array-unique/-/array-unique-0.3.2.tgz",
"integrity": "sha1-qJS3XUvE9s1nnvMkSp/Y9Gri1Cg=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/array.prototype.flat": {
"version": "1.2.5",
"resolved": "https://registry.npmjs.org/array.prototype.flat/-/array.prototype.flat-1.2.5.tgz",
"integrity": "sha512-KaYU+S+ndVqyUnignHftkwc58o3uVU1jzczILJ1tN2YaIZpFIKBiP/x/j97E5MVPsaCloPbqWLB/8qCTVvT2qg==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.2",
"define-properties": "^1.1.3",
"es-abstract": "^1.19.0"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/array.prototype.flat/node_modules/define-properties": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.1.3.tgz",
"integrity": "sha512-3MqfYKj2lLzdMSf8ZIZE/V+Zuy+BgD6f164e8K2w7dgnpKArBDerGYpM46IYYcjnkdPNMjPk9A6VFB8+3SKlXQ==",
"dev": true,
"dependencies": {
"object-keys": "^1.0.12"
},
"engines": {
"node": ">= 0.4"
}
},
"node_modules/array.prototype.flat/node_modules/object-keys": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz",
"integrity": "sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==",
"dev": true,
"engines": {
"node": ">= 0.4"
}
},
"node_modules/arrify": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/arrify/-/arrify-1.0.1.tgz",
"integrity": "sha1-iYUI2iIm84DfkEcoRWhJwVAaSw0=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/asap": {
"version": "2.0.6",
"resolved": "https://registry.npmjs.org/asap/-/asap-2.0.6.tgz",
"integrity": "sha1-5QNHYR1+aQlDIIu9r+vLwvuGbUY=",
"dev": true
},
"node_modules/assign-symbols": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/assign-symbols/-/assign-symbols-1.0.0.tgz",
"integrity": "sha1-WWZ/QfrdTyDMvCu5a41Pf3jsA2c=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/astral-regex": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/astral-regex/-/astral-regex-2.0.0.tgz",
"integrity": "sha512-Z7tMw1ytTXt5jqMcOP+OQteU1VuNK9Y02uuJtKQ1Sv69jXQKKg5cibLwGJow8yzZP+eAc18EmLGPal0bp36rvQ==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/async": {
"version": "0.2.10",
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz",
"integrity": "sha1-trvgsGdLnXGXCMo43owjfLUmw9E=",
"dev": true
},
"node_modules/async-done": {
"version": "1.3.1",
"resolved": "https://registry.npmjs.org/async-done/-/async-done-1.3.1.tgz",
"integrity": "sha512-R1BaUeJ4PMoLNJuk+0tLJgjmEqVsdN118+Z8O+alhnQDQgy0kmD5Mqi0DNEmMx2LM0Ed5yekKu+ZXYvIHceicg==",
"dev": true,
"dependencies": {
"end-of-stream": "^1.1.0",
"once": "^1.3.2",
"process-nextick-args": "^1.0.7",
"stream-exhaust": "^1.0.1"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/async-done/node_modules/process-nextick-args": {
"version": "1.0.7",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.7.tgz",
"integrity": "sha1-FQ4gt1ZZCtP5EJPyWk8q2L/zC6M=",
"dev": true
},
"node_modules/async-each": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/async-each/-/async-each-1.0.1.tgz",
"integrity": "sha1-GdOGodntxufByF04iu28xW0zYC0=",
"dev": true
},
"node_modules/async-settle": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/async-settle/-/async-settle-1.0.0.tgz",
"integrity": "sha1-HQqRS7Aldb7IqPOnTlCA9yssDGs=",
"dev": true,
"dependencies": {
"async-done": "^1.2.2"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/atob": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/atob/-/atob-2.1.1.tgz",
"integrity": "sha1-ri1acpR38onWDdf5amMUoi3Wwio=",
"dev": true,
"bin": {
"atob": "bin/atob.js"
},
"engines": {
"node": ">= 4.5.0"
}
},
"node_modules/autoprefixer": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "10.4.2",
"resolved": "https://registry.npmjs.org/autoprefixer/-/autoprefixer-10.4.2.tgz",
"integrity": "sha512-9fOPpHKuDW1w/0EKfRmVnxTDt8166MAnLI3mgZ1JCnhNtYWxcJ6Ud5CO/AVOZi/AvFa8DY9RTy3h3+tFBlrrdQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"browserslist": "^4.19.1",
"caniuse-lite": "^1.0.30001297",
"fraction.js": "^4.1.2",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"normalize-range": "^0.1.2",
"picocolors": "^1.0.0",
Update npm packages
2022-01-09 18:05:52 +09:00
"postcss-value-parser": "^4.2.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"bin": {
"autoprefixer": "bin/autoprefixer"
},
"engines": {
"node": "^10 || ^12 || >=14"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/postcss/"
},
"peerDependencies": {
"postcss": "^8.1.0"
}
},
"node_modules/babel-loader": {
"version": "8.2.3",
"resolved": "https://registry.npmjs.org/babel-loader/-/babel-loader-8.2.3.tgz",
"integrity": "sha512-n4Zeta8NC3QAsuyiizu0GkmRcQ6clkV9WFUnUf1iXP//IeSKbWjofW3UHyZVwlOB4y039YQKefawyTn64Zwbuw==",
"dev": true,
"dependencies": {
"find-cache-dir": "^3.3.1",
"loader-utils": "^1.4.0",
"make-dir": "^3.1.0",
"schema-utils": "^2.6.5"
},
"engines": {
"node": ">= 8.9"
},
"peerDependencies": {
"@babel/core": "^7.0.0",
"webpack": ">=2"
}
},
"node_modules/babel-plugin-dynamic-import-node": {
"version": "2.3.3",
"resolved": "https://registry.npmjs.org/babel-plugin-dynamic-import-node/-/babel-plugin-dynamic-import-node-2.3.3.tgz",
"integrity": "sha512-jZVI+s9Zg3IqA/kdi0i6UDCybUI3aSBLnglhYbSSjKlV7yF1F/5LWv8MakQmvYpnbJDS6fcBL2KzHSxNCMtWSQ==",
"dev": true,
"dependencies": {
"object.assign": "^4.1.0"
}
},
"node_modules/babel-plugin-polyfill-corejs2": {
"version": "0.3.0",
"resolved": "https://registry.npmjs.org/babel-plugin-polyfill-corejs2/-/babel-plugin-polyfill-corejs2-0.3.0.tgz",
"integrity": "sha512-wMDoBJ6uG4u4PNFh72Ty6t3EgfA91puCuAwKIazbQlci+ENb/UU9A3xG5lutjUIiXCIn1CY5L15r9LimiJyrSA==",
"dev": true,
"dependencies": {
"@babel/compat-data": "^7.13.11",
"@babel/helper-define-polyfill-provider": "^0.3.0",
"semver": "^6.1.1"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/babel-plugin-polyfill-corejs2/node_modules/semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
"dev": true,
"bin": {
"semver": "bin/semver.js"
}
},
"node_modules/babel-plugin-polyfill-corejs3": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "0.5.1",
"resolved": "https://registry.npmjs.org/babel-plugin-polyfill-corejs3/-/babel-plugin-polyfill-corejs3-0.5.1.tgz",
"integrity": "sha512-TihqEe4sQcb/QcPJvxe94/9RZuLQuF1+To4WqQcRvc+3J3gLCPIPgDKzGLG6zmQLfH3nn25heRuDNkS2KR4I8A==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/helper-define-polyfill-provider": "^0.3.1",
"core-js-compat": "^3.20.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/babel-plugin-polyfill-regenerator": {
"version": "0.3.0",
"resolved": "https://registry.npmjs.org/babel-plugin-polyfill-regenerator/-/babel-plugin-polyfill-regenerator-0.3.0.tgz",
"integrity": "sha512-dhAPTDLGoMW5/84wkgwiLRwMnio2i1fUe53EuvtKMv0pn2p3S8OCoV1xAzfJPl0KOX7IB89s2ib85vbYiea3jg==",
"dev": true,
"dependencies": {
"@babel/helper-define-polyfill-provider": "^0.3.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/babel-runtime": {
"version": "6.26.0",
"resolved": "https://registry.npmjs.org/babel-runtime/-/babel-runtime-6.26.0.tgz",
"integrity": "sha1-llxwWGaOgrVde/4E/yM3vItWR/4=",
"dev": true,
"dependencies": {
"core-js": "^2.4.0",
"regenerator-runtime": "^0.11.0"
}
},
"node_modules/babel-runtime/node_modules/core-js": {
"version": "2.6.9",
"resolved": "https://registry.npmjs.org/core-js/-/core-js-2.6.9.tgz",
"integrity": "sha512-HOpZf6eXmnl7la+cUdMnLvUxKNqLUzJvgIziQ0DiF3JwSImNphIqdGqzj6hIKyX04MmV0poclQ7+wjWvxQyR2A==",
"deprecated": "core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.",
"dev": true,
"hasInstallScript": true
},
"node_modules/babel-types": {
"version": "6.26.0",
"resolved": "https://registry.npmjs.org/babel-types/-/babel-types-6.26.0.tgz",
"integrity": "sha1-o7Bz+Uq0nrb6Vc1lInozQ4BjJJc=",
"dev": true,
"dependencies": {
"babel-runtime": "^6.26.0",
"esutils": "^2.0.2",
"lodash": "^4.17.4",
"to-fast-properties": "^1.0.3"
}
},
"node_modules/babylon": {
"version": "6.18.0",
"resolved": "https://registry.npmjs.org/babylon/-/babylon-6.18.0.tgz",
"integrity": "sha512-q/UEjfGJ2Cm3oKV71DJz9d25TPnq5rhBVL2Q4fA5wcC3jcrdn7+SssEybFIxwAvvP+YCsCYNKughoF33GxgycQ==",
"dev": true,
"bin": {
"babylon": "bin/babylon.js"
}
},
"node_modules/bach": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/bach/-/bach-1.2.0.tgz",
"integrity": "sha1-Szzpa/JxNPeaG0FKUcFONMO9mIA=",
"dev": true,
"dependencies": {
"arr-filter": "^1.1.1",
"arr-flatten": "^1.0.1",
"arr-map": "^2.0.0",
"array-each": "^1.0.0",
"array-initial": "^1.0.0",
"array-last": "^1.1.1",
"async-done": "^1.2.2",
"async-settle": "^1.0.0",
"now-and-later": "^2.0.0"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/balanced-match": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-1.0.0.tgz",
"integrity": "sha1-ibTRmasr7kneFk6gK4nORi1xt2c=",
"dev": true
},
"node_modules/base": {
"version": "0.11.2",
"resolved": "https://registry.npmjs.org/base/-/base-0.11.2.tgz",
"integrity": "sha512-5T6P4xPgpp0YDFvSWwEZ4NoE3aM4QBQXDzmVbraCkFj8zHM+mba8SyqB5DbZWyR7mYHo6Y7BdQo3MoA4m0TeQg==",
"dev": true,
"dependencies": {
"cache-base": "^1.0.1",
"class-utils": "^0.3.5",
"component-emitter": "^1.2.1",
"define-property": "^1.0.0",
"isobject": "^3.0.1",
"mixin-deep": "^1.2.0",
"pascalcase": "^0.1.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/base/node_modules/define-property": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-1.0.0.tgz",
"integrity": "sha1-dp66rz9KY6rTr56NMEybvnm/sOY=",
"dev": true,
"dependencies": {
"is-descriptor": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/base/node_modules/is-accessor-descriptor": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-accessor-descriptor/-/is-accessor-descriptor-1.0.0.tgz",
"integrity": "sha512-m5hnHTkcVsPfqx3AKlyttIPb7J+XykHvJP2B9bZDjlhLIoEq4XoK64Vg7boZlVWYK6LUY94dYPEE7Lh0ZkZKcQ==",
"dev": true,
"dependencies": {
"kind-of": "^6.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/base/node_modules/is-data-descriptor": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-data-descriptor/-/is-data-descriptor-1.0.0.tgz",
"integrity": "sha512-jbRXy1FmtAoCjQkVmIVYwuuqDFUbaOeDjmed1tOGPrsMhtJA4rD9tkgA0F1qJ3gRFRXcHYVkdeaP50Q5rE/jLQ==",
"dev": true,
"dependencies": {
"kind-of": "^6.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/base/node_modules/is-descriptor": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/is-descriptor/-/is-descriptor-1.0.2.tgz",
"integrity": "sha512-2eis5WqQGV7peooDyLmNEPUrps9+SXX5c9pL3xEB+4e9HnGuDa7mB7kHxHw4CbqS9k1T2hOH3miL8n8WtiYVtg==",
"dev": true,
"dependencies": {
"is-accessor-descriptor": "^1.0.0",
"is-data-descriptor": "^1.0.0",
"kind-of": "^6.0.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/base64-js": {
"version": "1.5.1",
"resolved": "https://registry.npmjs.org/base64-js/-/base64-js-1.5.1.tgz",
"integrity": "sha512-AKpaYlHn8t4SVbOHCy+b5+KKgvR4vrsD8vbvrbiQJps7fKDTkjkDry6ji0rUJjC0kzbNePLwzxq8iypo41qeWA==",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
]
},
"node_modules/big.js": {
"version": "5.2.2",
"resolved": "https://registry.npmjs.org/big.js/-/big.js-5.2.2.tgz",
"integrity": "sha512-vyL2OymJxmarO8gxMr0mhChsO9QGwhynfuu4+MHTAW6czfq9humCB7rKpUjDd9YUiDPU4mzpyupFSvOClAwbmQ==",
"dev": true,
"engines": {
"node": "*"
}
},
"node_modules/binary-extensions": {
"version": "1.11.0",
"resolved": "https://registry.npmjs.org/binary-extensions/-/binary-extensions-1.11.0.tgz",
"integrity": "sha1-RqoXUftqL5PuXmibsQh9SxTGwgU=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/binaryextensions": {
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/binaryextensions/-/binaryextensions-2.3.0.tgz",
"integrity": "sha512-nAihlQsYGyc5Bwq6+EsubvANYGExeJKHDO3RjnvwU042fawQTQfM3Kxn7IHUXQOz4bzfwsGYYHGSvXyW4zOGLg==",
"dev": true,
"engines": {
"node": ">=0.8"
},
"funding": {
"url": "https://bevry.me/fund"
}
},
"node_modules/bl": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/bl/-/bl-4.1.0.tgz",
"integrity": "sha512-1W07cM9gS6DcLperZfFSj+bWLtaPGSOHWhPiGzXmvVJbRLdG82sH/Kn8EtW1VqWVA54AKf2h5k5BbnIbwF3h6w==",
"dev": true,
"dependencies": {
"buffer": "^5.5.0",
"inherits": "^2.0.4",
"readable-stream": "^3.4.0"
}
},
"node_modules/bl/node_modules/readable-stream": {
"version": "3.6.0",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-3.6.0.tgz",
"integrity": "sha512-BViHy7LKeTz4oNnkcLJ+lVSL6vpiFeX6/d3oSH8zCW7UxP2onchk+vTGB143xuFjHS3deTgkKoXXymXqymiIdA==",
"dev": true,
"dependencies": {
"inherits": "^2.0.3",
"string_decoder": "^1.1.1",
"util-deprecate": "^1.0.1"
},
"engines": {
"node": ">= 6"
}
},
"node_modules/bluebird": {
"version": "3.7.2",
"resolved": "https://registry.npmjs.org/bluebird/-/bluebird-3.7.2.tgz",
"integrity": "sha512-XpNj6GDQzdfW+r2Wnn7xiSAd7TM3jzkxGXBGTtWKuSXv1xUV+azxAm8jdWZN06QTQk+2N2XB9jRDkvbmQmcRtg==",
"dev": true
},
"node_modules/brace-expansion": {
"version": "1.1.11",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz",
"integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==",
"dev": true,
"dependencies": {
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
}
},
"node_modules/braces": {
"version": "2.3.2",
"resolved": "https://registry.npmjs.org/braces/-/braces-2.3.2.tgz",
"integrity": "sha512-aNdbnj9P8PjdXU4ybaWLK2IF3jc/EoDYbC7AazW6to3TRsfXxscC9UXOB5iDiEQrkyIbWp2SLQda4+QAa7nc3w==",
"dev": true,
"dependencies": {
"arr-flatten": "^1.1.0",
"array-unique": "^0.3.2",
"extend-shallow": "^2.0.1",
"fill-range": "^4.0.0",
"isobject": "^3.0.1",
"repeat-element": "^1.1.2",
"snapdragon": "^0.8.1",
"snapdragon-node": "^2.0.1",
"split-string": "^3.0.2",
"to-regex": "^3.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/braces/node_modules/extend-shallow": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/extend-shallow/-/extend-shallow-2.0.1.tgz",
"integrity": "sha1-Ua99YUrZqfYQ6huvu5idaxxWiQ8=",
"dev": true,
"dependencies": {
"is-extendable": "^0.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/browserslist": {
Update npm packages
2021-12-26 19:09:29 +09:00
"version": "4.19.1",
"resolved": "https://registry.npmjs.org/browserslist/-/browserslist-4.19.1.tgz",
"integrity": "sha512-u2tbbG5PdKRTUoctO3NBD8FQ5HdPh1ZXPHzp1rwaa5jTc+RV9/+RlWiAIKmjRPQF+xbGM9Kklj5bZQFa2s/38A==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2021-12-26 19:09:29 +09:00
"caniuse-lite": "^1.0.30001286",
"electron-to-chromium": "^1.4.17",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"escalade": "^3.1.1",
Update npm packages
2021-12-26 19:09:29 +09:00
"node-releases": "^2.0.1",
"picocolors": "^1.0.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"bin": {
"browserslist": "cli.js"
},
"engines": {
"node": "^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/browserslist"
}
},
"node_modules/buffer": {
"version": "5.7.1",
"resolved": "https://registry.npmjs.org/buffer/-/buffer-5.7.1.tgz",
"integrity": "sha512-EHcyIPBQ4BSGlvjB16k5KgAJ27CIsHY/2JBmCRReo48y9rQ3MaUzWX3KVlBa4U7MyX02HdVj0K7C3WaB3ju7FQ==",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
],
"dependencies": {
"base64-js": "^1.3.1",
"ieee754": "^1.1.13"
}
},
"node_modules/buffer-crc32": {
"version": "0.2.13",
"resolved": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.13.tgz",
"integrity": "sha1-DTM+PwDqxQqhRUq9MO+MKl2ackI=",
"dev": true,
"engines": {
"node": "*"
}
},
"node_modules/buffer-equal": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/buffer-equal/-/buffer-equal-1.0.0.tgz",
"integrity": "sha1-WWFrSYME1Var1GaWayLu2j7KX74=",
"dev": true,
"engines": {
"node": ">=0.4.0"
}
},
"node_modules/buffer-from": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/buffer-from/-/buffer-from-1.1.1.tgz",
"integrity": "sha512-MQcXEUbCKtEo7bhqEs6560Hyd4XaovZlO/k9V3hjVUF/zwW7KBVdSK4gIt/bzwS9MbR5qob+F5jusZsb0YQK2A==",
"dev": true
},
"node_modules/builtin-modules": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.1.tgz",
"integrity": "sha1-Jw8HbFpywC9bZaR9+Uxf46J4iS8=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/cache-base": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/cache-base/-/cache-base-1.0.1.tgz",
"integrity": "sha512-AKcdTnFSWATd5/GCPRxr2ChwIJ85CeyrEyjRHlKxQ56d4XJMGym0uAiKn0xbLOGOl3+yRpOTi484dVCEc5AUzQ==",
"dev": true,
"dependencies": {
"collection-visit": "^1.0.0",
"component-emitter": "^1.2.1",
"get-value": "^2.0.6",
"has-value": "^1.0.0",
"isobject": "^3.0.1",
"set-value": "^2.0.0",
"to-object-path": "^0.3.0",
"union-value": "^1.0.0",
"unset-value": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/call-bind": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/call-bind/-/call-bind-1.0.2.tgz",
"integrity": "sha512-7O+FbCihrB5WGbFYesctwmTKae6rOiIzmz1icreWJ+0aA7LJfuqhEso2T9ncpcFtzMQtzXf2QGGueWJGTYsqrA==",
"dev": true,
"dependencies": {
"function-bind": "^1.1.1",
"get-intrinsic": "^1.0.2"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/callsites": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/callsites/-/callsites-3.1.0.tgz",
"integrity": "sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==",
"dev": true,
"engines": {
"node": ">=6"
}
},
"node_modules/camelcase": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"integrity": "sha1-m7UwTS4LVmmLLHWLCKPqqdqlijk=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/camelcase-keys": {
"version": "6.2.2",
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-6.2.2.tgz",
"integrity": "sha512-YrwaA0vEKazPBkn0ipTiMpSajYDSe+KjQfrjhcBMxJt/znbvlHd8Pw/Vamaz5EB4Wfhs3SUR3Z9mwRu/P3s3Yg==",
"dev": true,
"dependencies": {
"camelcase": "^5.3.1",
"map-obj": "^4.0.0",
"quick-lru": "^4.0.1"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/camelcase-keys/node_modules/camelcase": {
"version": "5.3.1",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-5.3.1.tgz",
"integrity": "sha512-L28STB170nwWS63UjtlEOE3dldQApaJXZkOI1uMFfzf3rRuPegHaHesyee+YxQ+W6SvRDQV6UrdOdRiR153wJg==",
"dev": true,
"engines": {
"node": ">=6"
}
},
"node_modules/caniuse-lite": {
Add the `caniuse-lite` package Since the Autoprefixer plugin indirectly depends on this, it seems like a good idea to add this as a direct dependency in the PDF.js project to hopefully avoid having to manually update `caniuse-lite` in the future; see https://github.com/browserslist/browserslist#browsers-data-updating Also, slightly tweaks the Autoprefixer config for GENERIC-builds of the PDF.js library; note that this change doesn't affect the contents of the *built* `web/viewer.js` file.
2022-02-27 19:32:23 +09:00
"version": "1.0.30001312",
"resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001312.tgz",
"integrity": "sha512-Wiz1Psk2MEK0pX3rUzWaunLTZzqS2JYZFzNKqAiJGiuxIjRPLgV6+VDPOg6lQOUxmDwhTlh198JsTTi8Hzw6aQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/browserslist"
}
},
"node_modules/canvas": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "2.9.0",
"resolved": "https://registry.npmjs.org/canvas/-/canvas-2.9.0.tgz",
"integrity": "sha512-0l93g7uxp7rMyr7H+XRQ28A3ud0dKIUTIEkUe1Dxh4rjUYN7B93+SjC3r1PDKA18xcQN87OFGgUnyw7LSgNLSQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"hasInstallScript": true,
"dependencies": {
"@mapbox/node-pre-gyp": "^1.0.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"nan": "^2.15.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"simple-get": "^3.0.3"
},
"engines": {
"node": ">=6"
}
},
"node_modules/catharsis": {
"version": "0.9.0",
"resolved": "https://registry.npmjs.org/catharsis/-/catharsis-0.9.0.tgz",
"integrity": "sha512-prMTQVpcns/tzFgFVkVp6ak6RykZyWb3gu8ckUpd6YkTlacOd3DXGJjIpD4Q6zJirizvaiAjSSHlOsA+6sNh2A==",
"dev": true,
"dependencies": {
"lodash": "^4.17.15"
},
"engines": {
"node": ">= 10"
}
},
"node_modules/center-align": {
"version": "0.1.3",
"resolved": "https://registry.npmjs.org/center-align/-/center-align-0.1.3.tgz",
"integrity": "sha1-qg0yYptu6XIgBBHL1EYckHvCt60=",
"dev": true,
"dependencies": {
"align-text": "^0.1.3",
"lazy-cache": "^1.0.3"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/cephes": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/cephes/-/cephes-1.2.0.tgz",
"integrity": "sha512-twuUuJRrIrsELHz6foJtZlqrz6FC36zoHZJvvThsrM1UWPKxyoilw1Rka6Hk0AmPFKHKUoGwGfAtvNZNtNZu0g==",
"dev": true
},
"node_modules/chalk": {
"version": "2.4.1",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-2.4.1.tgz",
"integrity": "sha512-ObN6h1v2fTJSmUXoS3nMQ92LbDK9be4TV+6G+omQlGJFdcUX5heKi1LZ1YnRMIgwTLEj3E24bT6tYni50rlCfQ==",
"dev": true,
"dependencies": {
"ansi-styles": "^3.2.1",
"escape-string-regexp": "^1.0.5",
"supports-color": "^5.3.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/character-parser": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/character-parser/-/character-parser-2.2.0.tgz",
"integrity": "sha1-x84o821LzZdE5f/CxfzeHHMmH8A=",
"dev": true,
"dependencies": {
"is-regex": "^1.0.3"
}
},
"node_modules/chokidar": {
"version": "2.1.8",
"resolved": "https://registry.npmjs.org/chokidar/-/chokidar-2.1.8.tgz",
"integrity": "sha512-ZmZUazfOzf0Nve7duiCKD23PFSCs4JPoYyccjUFF3aQkQadqBhfzhjkwBH2mNOG9cTBwhamM37EIsIkZw3nRgg==",
"deprecated": "Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.",
"dev": true,
"dependencies": {
"anymatch": "^2.0.0",
"async-each": "^1.0.1",
"braces": "^2.3.2",
"glob-parent": "^3.1.0",
"inherits": "^2.0.3",
"is-binary-path": "^1.0.0",
"is-glob": "^4.0.0",
"normalize-path": "^3.0.0",
"path-is-absolute": "^1.0.0",
"readdirp": "^2.2.1",
"upath": "^1.1.1"
},
"optionalDependencies": {
"fsevents": "^1.2.7"
}
},
"node_modules/chokidar/node_modules/is-glob": {
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.1.tgz",
"integrity": "sha512-5G0tKtBTFImOqDnLB2hG6Bp2qcKEFduo4tZu9MT/H6NQv/ghhy30o55ufafxJ/LdH79LLs2Kfrn85TLKyA7BUg==",
"dev": true,
"dependencies": {
"is-extglob": "^2.1.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/chokidar/node_modules/normalize-path": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/normalize-path/-/normalize-path-3.0.0.tgz",
"integrity": "sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/chownr": {
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/chownr/-/chownr-1.1.4.tgz",
"integrity": "sha512-jJ0bqzaylmJtVnNgzTeSOs8DPavpbYgEr/b0YL8/2GO3xJEhInFmhKMUnEJQjZumK7KXGFhUy89PrsJWlakBVg==",
"dev": true
},
"node_modules/chrome-trace-event": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/chrome-trace-event/-/chrome-trace-event-1.0.3.tgz",
"integrity": "sha512-p3KULyQg4S7NIHixdwbGX+nFHkoBiA4YQmyWtjb8XngSKV124nJmRysgAeujbUVb15vh+RvFUfCPqU7rXk+hZg==",
"dev": true,
"engines": {
"node": ">=6.0"
}
},
"node_modules/ci-info": {
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/ci-info/-/ci-info-3.3.0.tgz",
"integrity": "sha512-riT/3vI5YpVH6/qomlDnJow6TBee2PBKSEpx3O32EGPYbWGIRsIlGRms3Sm74wYE1JMo8RnO04Hb12+v1J5ICw==",
"dev": true
},
"node_modules/class-utils": {
"version": "0.3.6",
"resolved": "https://registry.npmjs.org/class-utils/-/class-utils-0.3.6.tgz",
"integrity": "sha512-qOhPa/Fj7s6TY8H8esGu5QNpMMQxz79h+urzrNYN6mn+9BnxlDGf5QZ+XeCDsxSjPqsSR56XOZOJmpeurnLMeg==",
"dev": true,
"dependencies": {
"arr-union": "^3.1.0",
"define-property": "^0.2.5",
"isobject": "^3.0.0",
"static-extend": "^0.1.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/class-utils/node_modules/define-property": {
"version": "0.2.5",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-0.2.5.tgz",
"integrity": "sha1-w1se+RjsPJkPmlvFe+BKrOxcgRY=",
"dev": true,
"dependencies": {
"is-descriptor": "^0.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/clean-css": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "4.2.4",
"resolved": "https://registry.npmjs.org/clean-css/-/clean-css-4.2.4.tgz",
"integrity": "sha512-EJUDT7nDVFDvaQgAo2G/PJvxmp1o/c6iXLbswsBbUFXi1Nr+AjA2cKmfbKDMjMvzEe75g3P6JkaDDAKk96A85A==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"source-map": "~0.6.0"
},
"engines": {
"node": ">= 4.0"
}
},
"node_modules/clean-regexp": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/clean-regexp/-/clean-regexp-1.0.0.tgz",
"integrity": "sha1-jffHquUf02h06PjQW5GAvBGj/tc=",
"dev": true,
"dependencies": {
"escape-string-regexp": "^1.0.5"
},
"engines": {
"node": ">=4"
}
},
"node_modules/cliui": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/cliui/-/cliui-2.1.0.tgz",
"integrity": "sha1-S0dXYP+AJkx2LDoXGQMukcf+oNE=",
"dev": true,
"dependencies": {
"center-align": "^0.1.1",
"right-align": "^0.1.1",
"wordwrap": "0.0.2"
}
},
"node_modules/clone": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/clone/-/clone-2.1.2.tgz",
"integrity": "sha1-G39Ln1kfHo+DZwQBYANFoCiHQ18=",
"dev": true,
"engines": {
"node": ">=0.8"
}
},
"node_modules/clone-buffer": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/clone-buffer/-/clone-buffer-1.0.0.tgz",
"integrity": "sha1-4+JbIHrE5wGvch4staFnksrD3Fg=",
"dev": true,
"engines": {
"node": ">= 0.10"
}
},
"node_modules/clone-regexp": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/clone-regexp/-/clone-regexp-2.2.0.tgz",
"integrity": "sha512-beMpP7BOtTipFuW8hrJvREQ2DrRu3BE7by0ZpibtfBA+qfHYvMGTc2Yb1JMYPKg/JUw0CHYvpg796aNTSW9z7Q==",
"dev": true,
"dependencies": {
"is-regexp": "^2.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/clone-stats": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-1.0.0.tgz",
"integrity": "sha1-s3gt/4u1R04Yuba/D9/ngvh3doA=",
"dev": true
},
"node_modules/cloneable-readable": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/cloneable-readable/-/cloneable-readable-1.1.3.tgz",
"integrity": "sha512-2EF8zTQOxYq70Y4XKtorQupqF0m49MBz2/yf5Bj+MHjvpG3Hy7sImifnqD6UA+TKYxeSV+u6qqQPawN5UvnpKQ==",
"dev": true,
"dependencies": {
"inherits": "^2.0.1",
"process-nextick-args": "^2.0.0",
"readable-stream": "^2.3.5"
}
},
"node_modules/code-point-at": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/code-point-at/-/code-point-at-1.1.0.tgz",
"integrity": "sha1-DQcLTQQ6W+ozovGkDi7bPZpMz3c=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/coffee-script": {
"version": "1.12.7",
"resolved": "https://registry.npmjs.org/coffee-script/-/coffee-script-1.12.7.tgz",
"integrity": "sha512-fLeEhqwymYat/MpTPUjSKHVYYl0ec2mOyALEMLmzr5i1isuG+6jfI2j2d5oBO3VIzgUXgBVIcOT9uH1TFxBckw==",
"deprecated": "CoffeeScript on NPM has moved to \"coffeescript\" (no hyphen)",
"dev": true,
"bin": {
"cake": "bin/cake",
"coffee": "bin/coffee"
},
"engines": {
"node": ">=0.8.0"
}
},
"node_modules/collection-map": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/collection-map/-/collection-map-1.0.0.tgz",
"integrity": "sha1-rqDwb40mx4DCt1SUOFVEsiVa8Yw=",
"dev": true,
"dependencies": {
"arr-map": "^2.0.2",
"for-own": "^1.0.0",
"make-iterator": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/collection-visit": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/collection-visit/-/collection-visit-1.0.0.tgz",
"integrity": "sha1-S8A3PBZLwykbTTaMgpzxqApZ3KA=",
"dev": true,
"dependencies": {
"map-visit": "^1.0.0",
"object-visit": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/color": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/color/-/color-3.0.0.tgz",
"integrity": "sha512-jCpd5+s0s0t7p3pHQKpnJ0TpQKKdleP71LWcA0aqiljpiuAkOSUFN/dyH8ZwF0hRmFlrIuRhufds1QyEP9EB+w==",
"dev": true,
"dependencies": {
"color-convert": "^1.9.1",
"color-string": "^1.5.2"
}
},
"node_modules/color-convert": {
"version": "1.9.1",
"resolved": "https://registry.npmjs.org/color-convert/-/color-convert-1.9.1.tgz",
"integrity": "sha512-mjGanIiwQJskCC18rPR6OmrZ6fm2Lc7PeGFYwCmy5J34wC6F1PzdGL6xeMfmgicfYcNLGuVFA3WzXtIDCQSZxQ==",
"dev": true,
"dependencies": {
"color-name": "^1.1.1"
}
},
"node_modules/color-name": {
Update npm packages
2021-12-26 19:09:29 +09:00
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz",
"integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/color-string": {
"version": "1.5.5",
"resolved": "https://registry.npmjs.org/color-string/-/color-string-1.5.5.tgz",
"integrity": "sha512-jgIoum0OfQfq9Whcfc2z/VhCNcmQjWbey6qBX0vqt7YICflUmBCh9E9CiQD5GSJ+Uehixm3NUwHVhqUAWRivZg==",
"dev": true,
"dependencies": {
"color-name": "^1.0.0",
"simple-swizzle": "^0.2.2"
}
},
"node_modules/color-support": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/color-support/-/color-support-1.1.3.tgz",
"integrity": "sha512-qiBjkpbMLO/HL68y+lh4q0/O1MZFj2RX6X/KmMa3+gJD3z+WwI1ZzDHysvqHGS3mP6mznPckpXmw1nI9cJjyRg==",
"dev": true,
"bin": {
"color-support": "bin.js"
}
},
Update npm packages
2021-12-26 19:09:29 +09:00
"node_modules/colord": {
"version": "2.9.2",
"resolved": "https://registry.npmjs.org/colord/-/colord-2.9.2.tgz",
"integrity": "sha512-Uqbg+J445nc1TKn4FoDPS6ZZqAvEDnwrH42yo8B40JSOgSLxMZ/gt3h4nmCtPLQeXhjJJkqBx7SCY35WnIixaQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/colornames": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/colornames/-/colornames-1.1.1.tgz",
"integrity": "sha1-+IiQMGhcfE/54qVZ9Qd+t2qBb5Y=",
"dev": true
},
"node_modules/colors": {
"version": "1.3.2",
"resolved": "https://registry.npmjs.org/colors/-/colors-1.3.2.tgz",
"integrity": "sha512-rhP0JSBGYvpcNQj4s5AdShMeE5ahMop96cTeDl/v9qQQm2fYClE2QXZRi8wLzc+GmXSxdIqqbOIAhyObEXDbfQ==",
"dev": true,
"engines": {
"node": ">=0.1.90"
}
},
"node_modules/colorspace": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/colorspace/-/colorspace-1.1.1.tgz",
"integrity": "sha512-pI3btWyiuz7Ken0BWh9Elzsmv2bM9AhA7psXib4anUXy/orfZ/E0MbQwhSOG/9L8hLlalqrU0UhOuqxW1YjmVw==",
"dev": true,
"dependencies": {
"color": "3.0.x",
"text-hex": "1.0.x"
}
},
"node_modules/commander": {
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/commander/-/commander-1.0.5.tgz",
"integrity": "sha1-RXKVu5duOI6d0NtS3kMz4knz2Iw=",
"dev": true,
"dependencies": {
"keypress": "0.1.x"
},
"engines": {
"node": ">= 0.6.x"
}
},
"node_modules/commondir": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/commondir/-/commondir-1.0.1.tgz",
"integrity": "sha1-3dgA2gxmEnOTzKWVDqloo6rxJTs=",
"dev": true
},
"node_modules/component-emitter": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/component-emitter/-/component-emitter-1.2.1.tgz",
"integrity": "sha1-E3kY1teCg/ffemt8WmPhQOaUJeY=",
"dev": true
},
"node_modules/concat-map": {
"version": "0.0.1",
"resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz",
"integrity": "sha1-2Klr13/Wjfd5OnMDajug1UBdR3s=",
"dev": true
},
"node_modules/concat-stream": {
"version": "1.6.2",
"resolved": "https://registry.npmjs.org/concat-stream/-/concat-stream-1.6.2.tgz",
"integrity": "sha512-27HBghJxjiZtIk3Ycvn/4kbJk/1uZuJFfuPEns6LaEvpvG1f0hTea8lilrouyo9mVc2GWdcEZ8OLoGmSADlrCw==",
"dev": true,
"engines": [
"node >= 0.8"
],
"dependencies": {
"buffer-from": "^1.0.0",
"inherits": "^2.0.3",
"readable-stream": "^2.2.2",
"typedarray": "^0.0.6"
}
},
"node_modules/console-control-strings": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/console-control-strings/-/console-control-strings-1.1.0.tgz",
"integrity": "sha1-PXz0Rk22RG6mRL9LOVB/mFEAjo4=",
"dev": true
},
"node_modules/constantinople": {
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/constantinople/-/constantinople-3.1.2.tgz",
"integrity": "sha512-yePcBqEFhLOqSBtwYOGGS1exHo/s1xjekXiinh4itpNQGCu4KA1euPh1fg07N2wMITZXQkBz75Ntdt1ctGZouw==",
"dev": true,
"dependencies": {
"@types/babel-types": "^7.0.0",
"@types/babylon": "^6.16.2",
"babel-types": "^6.26.0",
"babylon": "^6.18.0"
}
},
"node_modules/convert-source-map": {
"version": "1.5.1",
"resolved": "https://registry.npmjs.org/convert-source-map/-/convert-source-map-1.5.1.tgz",
"integrity": "sha1-uCeAl7m8IpNl3lxiz1/K7YtVmeU=",
"dev": true
},
"node_modules/copy-descriptor": {
"version": "0.1.1",
"resolved": "https://registry.npmjs.org/copy-descriptor/-/copy-descriptor-0.1.1.tgz",
"integrity": "sha1-Z29us8OZl8LuGsOpJP1hJHSPV40=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/copy-props": {
Bump copy-props from 2.0.4 to 2.0.5 Bumps [copy-props](https://github.com/gulpjs/copy-props) from 2.0.4 to 2.0.5. - [Release notes](https://github.com/gulpjs/copy-props/releases) - [Changelog](https://github.com/gulpjs/copy-props/blob/master/CHANGELOG.md) - [Commits](https://github.com/gulpjs/copy-props/compare/2.0.4...2.0.5) --- updated-dependencies: - dependency-name: copy-props dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-28 06:37:54 +09:00
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/copy-props/-/copy-props-2.0.5.tgz",
"integrity": "sha512-XBlx8HSqrT0ObQwmSzM7WE5k8FxTV75h1DX1Z3n6NhQ/UYYAvInWYmG06vFt7hQZArE2fuO62aihiWIVQwh1sw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Bump copy-props from 2.0.4 to 2.0.5 Bumps [copy-props](https://github.com/gulpjs/copy-props) from 2.0.4 to 2.0.5. - [Release notes](https://github.com/gulpjs/copy-props/releases) - [Changelog](https://github.com/gulpjs/copy-props/blob/master/CHANGELOG.md) - [Commits](https://github.com/gulpjs/copy-props/compare/2.0.4...2.0.5) --- updated-dependencies: - dependency-name: copy-props dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-28 06:37:54 +09:00
"each-props": "^1.3.2",
"is-plain-object": "^5.0.0"
}
},
"node_modules/copy-props/node_modules/is-plain-object": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/is-plain-object/-/is-plain-object-5.0.0.tgz",
"integrity": "sha512-VRSzKkbMm5jMDoKLbltAkFQ5Qr7VDiTFGXxYFXXowVj387GeGNOCsOH6Msy00SGZ3Fp84b1Naa1psqgcCIEP5Q==",
"dev": true,
"engines": {
"node": ">=0.10.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/core-js": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "3.21.1",
"resolved": "https://registry.npmjs.org/core-js/-/core-js-3.21.1.tgz",
"integrity": "sha512-FRq5b/VMrWlrmCzwRrpDYNxyHP9BcAZC+xHJaqTgIE5091ZV1NTmyh0sGOg5XqpnHvR0svdy0sv1gWA1zmhxig==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"hasInstallScript": true,
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/core-js"
}
},
"node_modules/core-js-compat": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "3.20.3",
"resolved": "https://registry.npmjs.org/core-js-compat/-/core-js-compat-3.20.3.tgz",
"integrity": "sha512-c8M5h0IkNZ+I92QhIpuSijOxGAcj3lgpsWdkCqmUTZNwidujF4r3pi6x1DCN+Vcs5qTS2XWWMfWSuCqyupX8gw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-23 18:58:15 +09:00
"browserslist": "^4.19.1",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"semver": "7.0.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/core-js"
}
},
"node_modules/core-js-compat/node_modules/semver": {
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-7.0.0.tgz",
"integrity": "sha512-+GB6zVA9LWh6zovYQLALHwv5rb2PHGlJi3lfiqIHxR0uuwCgefcOJc59v9fv1w8GbStwxuuqqAjI9NMAOOgq1A==",
"dev": true,
"bin": {
"semver": "bin/semver.js"
}
},
"node_modules/core-util-is": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.2.tgz",
"integrity": "sha1-tf1UIgqivFq1eqtxQMlAdUUDwac=",
"dev": true
},
"node_modules/cosmiconfig": {
"version": "7.0.1",
"resolved": "https://registry.npmjs.org/cosmiconfig/-/cosmiconfig-7.0.1.tgz",
"integrity": "sha512-a1YWNUV2HwGimB7dU2s1wUMurNKjpx60HxBB6xUM8Re+2s1g1IIfJvFR0/iCF+XHdE0GMTKTuLR32UQff4TEyQ==",
"dev": true,
"dependencies": {
"@types/parse-json": "^4.0.0",
"import-fresh": "^3.2.1",
"parse-json": "^5.0.0",
"path-type": "^4.0.0",
"yaml": "^1.10.0"
},
"engines": {
"node": ">=10"
}
},
"node_modules/cosmiconfig/node_modules/parse-json": {
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-5.2.0.tgz",
"integrity": "sha512-ayCKvm/phCGxOkYRSCM82iDwct8/EonSEgCSxWxD7ve6jHggsFl4fZVQBPRNgQoKiuV/odhFrGzQXZwbifC8Rg==",
"dev": true,
"dependencies": {
"@babel/code-frame": "^7.0.0",
"error-ex": "^1.3.1",
"json-parse-even-better-errors": "^2.3.0",
"lines-and-columns": "^1.1.6"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/cross-env": {
"version": "7.0.3",
"resolved": "https://registry.npmjs.org/cross-env/-/cross-env-7.0.3.tgz",
"integrity": "sha512-+/HKd6EgcQCJGh2PSjZuUitQBQynKor4wrFbRg4DtAgS1aWO+gU52xpH7M9ScGgXSYmAVS9bIJ8EzuaGw0oNAw==",
"dev": true,
"dependencies": {
"cross-spawn": "^7.0.1"
},
"bin": {
"cross-env": "src/bin/cross-env.js",
"cross-env-shell": "src/bin/cross-env-shell.js"
},
"engines": {
"node": ">=10.14",
"npm": ">=6",
"yarn": ">=1"
}
},
Update npm packages
2022-02-20 18:08:23 +09:00
"node_modules/cross-fetch": {
"version": "3.1.5",
"resolved": "https://registry.npmjs.org/cross-fetch/-/cross-fetch-3.1.5.tgz",
"integrity": "sha512-lvb1SBsI0Z7GDwmuid+mU3kWVBwTVUbe7S0H52yaaAdQOXq2YktTCZdlAcNKFzE6QtRz0snpw9bNiPeOIkkQvw==",
"dev": true,
"dependencies": {
"node-fetch": "2.6.7"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/cross-spawn": {
"version": "7.0.3",
"resolved": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.3.tgz",
"integrity": "sha512-iRDPJKUPVEND7dHPO8rkbOnPpyDygcDFtWjpeWNCgy8WP2rXcxXL8TskReQl6OrB2G7+UJrags1q15Fudc7G6w==",
"dev": true,
"dependencies": {
"path-key": "^3.1.0",
"shebang-command": "^2.0.0",
"which": "^2.0.1"
},
"engines": {
"node": ">= 8"
}
},
"node_modules/cross-spawn/node_modules/path-key": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/path-key/-/path-key-3.1.1.tgz",
"integrity": "sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/cross-spawn/node_modules/shebang-command": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/shebang-command/-/shebang-command-2.0.0.tgz",
"integrity": "sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==",
"dev": true,
"dependencies": {
"shebang-regex": "^3.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/cross-spawn/node_modules/shebang-regex": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/shebang-regex/-/shebang-regex-3.0.0.tgz",
"integrity": "sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/cross-spawn/node_modules/which": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/which/-/which-2.0.2.tgz",
"integrity": "sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==",
"dev": true,
"dependencies": {
"isexe": "^2.0.0"
},
"bin": {
"node-which": "bin/node-which"
},
"engines": {
"node": ">= 8"
}
},
Update npm packages
2022-02-20 18:08:23 +09:00
"node_modules/css-functions-list": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/css-functions-list/-/css-functions-list-3.0.1.tgz",
"integrity": "sha512-PriDuifDt4u4rkDgnqRCLnjfMatufLmWNfQnGCq34xZwpY3oabwhB9SqRBmuvWUgndbemCFlKqg+nO7C2q0SBw==",
"dev": true,
"engines": {
"node": ">=12.22"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/cssesc": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/cssesc/-/cssesc-3.0.0.tgz",
"integrity": "sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==",
"dev": true,
"bin": {
"cssesc": "bin/cssesc"
},
"engines": {
"node": ">=4"
}
},
"node_modules/d": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/d/-/d-1.0.0.tgz",
"integrity": "sha1-dUu1v+VUUdpppYuU1F9MWwRi1Y8=",
"dev": true,
"dependencies": {
"es5-ext": "^0.10.9"
}
},
"node_modules/debug": {
"version": "2.6.9",
"resolved": "https://registry.npmjs.org/debug/-/debug-2.6.9.tgz",
"integrity": "sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==",
"dev": true,
"dependencies": {
"ms": "2.0.0"
}
},
"node_modules/decamelize": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/decamelize/-/decamelize-1.2.0.tgz",
"integrity": "sha1-9lNNFRSCabIDUue+4m9QH5oZEpA=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/decamelize-keys": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/decamelize-keys/-/decamelize-keys-1.1.0.tgz",
"integrity": "sha1-0XGoeTMlKAfrPLYdwcFEXQeN8tk=",
"dev": true,
"dependencies": {
"decamelize": "^1.1.0",
"map-obj": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/decamelize-keys/node_modules/map-obj": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
"integrity": "sha1-2TPOuSBdgr3PSIb2dCvcK03qFG0=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/decode-uri-component": {
"version": "0.2.0",
"resolved": "https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz",
"integrity": "sha1-6zkTMzRYd1y4TNGh+uBiEGu4dUU=",
"dev": true,
"engines": {
"node": ">=0.10"
}
},
"node_modules/decompress-response": {
"version": "4.2.1",
"resolved": "https://registry.npmjs.org/decompress-response/-/decompress-response-4.2.1.tgz",
"integrity": "sha512-jOSne2qbyE+/r8G1VU+G/82LBs2Fs4LAsTiLSHOCOMZQl2OKZ6i8i4IyHemTe+/yIXOtTcRQMzPcgyhoFlqPkw==",
"dev": true,
"dependencies": {
"mimic-response": "^2.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/deep-is": {
"version": "0.1.3",
"resolved": "https://registry.npmjs.org/deep-is/-/deep-is-0.1.3.tgz",
"integrity": "sha1-s2nW+128E+7PUk+RsHD+7cNXzzQ=",
"dev": true
},
"node_modules/default-compare": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/default-compare/-/default-compare-1.0.0.tgz",
"integrity": "sha512-QWfXlM0EkAbqOCbD/6HjdwT19j7WCkMyiRhWilc4H9/5h/RzTF9gv5LYh1+CmDV5d1rki6KAWLtQale0xt20eQ==",
"dev": true,
"dependencies": {
"kind-of": "^5.0.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/default-compare/node_modules/kind-of": {
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-5.1.0.tgz",
"integrity": "sha512-NGEErnH6F2vUuXDh+OlbcKW7/wOcfdRHaZ7VWtqCztfHri/++YKmP51OdWeGPuqCOba6kk2OTe5d02VmTB80Pw==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/default-resolution": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/default-resolution/-/default-resolution-2.0.0.tgz",
"integrity": "sha1-vLgrqnKtebQmp2cy8aga1t8m1oQ=",
"dev": true,
"engines": {
"node": ">= 0.10"
}
},
"node_modules/define-properties": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.1.2.tgz",
"integrity": "sha1-g6c/L+pWmJj7c3GTyPhzyvbUXJQ=",
"dev": true,
"dependencies": {
"foreach": "^2.0.5",
"object-keys": "^1.0.8"
},
"engines": {
"node": ">= 0.4"
}
},
"node_modules/define-property": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-2.0.2.tgz",
"integrity": "sha512-jwK2UV4cnPpbcG7+VRARKTZPUWowwXA8bzH5NP6ud0oeAxyYPuGZUAC7hMugpCdz4BeSZl2Dl9k66CHJ/46ZYQ==",
"dev": true,
"dependencies": {
"is-descriptor": "^1.0.2",
"isobject": "^3.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/define-property/node_modules/is-accessor-descriptor": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-accessor-descriptor/-/is-accessor-descriptor-1.0.0.tgz",
"integrity": "sha512-m5hnHTkcVsPfqx3AKlyttIPb7J+XykHvJP2B9bZDjlhLIoEq4XoK64Vg7boZlVWYK6LUY94dYPEE7Lh0ZkZKcQ==",
"dev": true,
"dependencies": {
"kind-of": "^6.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/define-property/node_modules/is-data-descriptor": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-data-descriptor/-/is-data-descriptor-1.0.0.tgz",
"integrity": "sha512-jbRXy1FmtAoCjQkVmIVYwuuqDFUbaOeDjmed1tOGPrsMhtJA4rD9tkgA0F1qJ3gRFRXcHYVkdeaP50Q5rE/jLQ==",
"dev": true,
"dependencies": {
"kind-of": "^6.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/define-property/node_modules/is-descriptor": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/is-descriptor/-/is-descriptor-1.0.2.tgz",
"integrity": "sha512-2eis5WqQGV7peooDyLmNEPUrps9+SXX5c9pL3xEB+4e9HnGuDa7mB7kHxHw4CbqS9k1T2hOH3miL8n8WtiYVtg==",
"dev": true,
"dependencies": {
"is-accessor-descriptor": "^1.0.0",
"is-data-descriptor": "^1.0.0",
"kind-of": "^6.0.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/delegates": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/delegates/-/delegates-1.0.0.tgz",
"integrity": "sha1-hMbhWbgZBP3KWaDvRM2HDTElD5o=",
"dev": true
},
"node_modules/detect-file": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/detect-file/-/detect-file-1.0.0.tgz",
"integrity": "sha1-8NZtA2cqglyxtzvbP+YjEMjlUrc=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/detect-libc": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/detect-libc/-/detect-libc-1.0.3.tgz",
"integrity": "sha1-+hN8S9aY7fVc1c0CrFWfkaTEups=",
"dev": true,
"bin": {
"detect-libc": "bin/detect-libc.js"
},
"engines": {
"node": ">=0.10"
}
},
"node_modules/devtools-protocol": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "0.0.960912",
"resolved": "https://registry.npmjs.org/devtools-protocol/-/devtools-protocol-0.0.960912.tgz",
"integrity": "sha512-I3hWmV9rWHbdnUdmMKHF2NuYutIM2kXz2mdXW8ha7TbRlGTVs+PF+PsB5QWvpCek4Fy9B+msiispCfwlhG5Sqg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/diagnostics": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/diagnostics/-/diagnostics-1.1.1.tgz",
"integrity": "sha512-8wn1PmdunLJ9Tqbx+Fx/ZEuHfJf4NKSN2ZBj7SJC/OWRWha843+WsTjqMe1B5E3p28jqBlp+mJ2fPVxPyNgYKQ==",
"dev": true,
"dependencies": {
"colorspace": "1.1.x",
"enabled": "1.0.x",
"kuler": "1.0.x"
}
},
"node_modules/dir-glob": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/dir-glob/-/dir-glob-3.0.1.tgz",
"integrity": "sha512-WkrWp9GR4KXfKGYzOLmTuGVi1UWFfws377n9cc55/tb6DuqyF6pcQ5AbiHEshaDpY9v6oaSr2XCDidGmMwdzIA==",
"dev": true,
"dependencies": {
"path-type": "^4.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/distributions": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/distributions/-/distributions-2.1.0.tgz",
"integrity": "sha512-4eov7WXRip5Tu0K7Y51W1oVt+DcvkoE0EzsvbLzgedC/n4PUpYXHqk6vo/OH1HteBHp5Vm6cmfnInf9NAXM4qQ==",
"dev": true,
"dependencies": {
"cephes": "^1.1.2"
}
},
"node_modules/doctrine": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/doctrine/-/doctrine-3.0.0.tgz",
"integrity": "sha512-yS+Q5i3hBf7GBkd4KG8a7eBNNWNGLTaEwwYWUijIYM7zrlYDM0BFXHjjPWlWZ1Rg7UaddZeIDmi9jF3HmqiQ2w==",
"dev": true,
"dependencies": {
"esutils": "^2.0.2"
},
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/doctypes": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/doctypes/-/doctypes-1.1.0.tgz",
"integrity": "sha1-6oCxBqh1OHdOijpKWv4pPeSJ4Kk=",
"dev": true
},
"node_modules/domelementtype": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-2.0.1.tgz",
"integrity": "sha512-5HOHUDsYZWV8FGWN0Njbr/Rn7f/eWSQi1v7+HsUVwXgn8nWWlL64zKDkS0n8ZmQ3mlWOMuXOnR+7Nx/5tMO5AQ==",
"dev": true
},
"node_modules/domhandler": {
"version": "4.2.2",
"resolved": "https://registry.npmjs.org/domhandler/-/domhandler-4.2.2.tgz",
"integrity": "sha512-PzE9aBMsdZO8TK4BnuJwH0QT41wgMbRzuZrHUcpYncEjmQazq8QEaBWgLG7ZyC/DAZKEgglpIA6j4Qn/HmxS3w==",
"dev": true,
"dependencies": {
"domelementtype": "^2.2.0"
},
"engines": {
"node": ">= 4"
},
"funding": {
"url": "https://github.com/fb55/domhandler?sponsor=1"
}
},
"node_modules/domhandler/node_modules/domelementtype": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-2.2.0.tgz",
"integrity": "sha512-DtBMo82pv1dFtUmHyr48beiuq792Sxohr+8Hm9zoxklYPfa6n0Z3Byjj2IV7bmr2IyqClnqEQhfgHJJ5QF0R5A==",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/fb55"
}
]
},
"node_modules/dommatrix": {
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"version": "0.0.24",
"resolved": "https://registry.npmjs.org/dommatrix/-/dommatrix-0.0.24.tgz",
"integrity": "sha512-PatEhAW5pIHr28MvFQGV5iiHNloqvecQZlxs7/8s/eulLqZI3uVqPkrO7YDuqsebovr/9mmcWDSWzVG4amEZgQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/domutils": {
"version": "2.8.0",
"resolved": "https://registry.npmjs.org/domutils/-/domutils-2.8.0.tgz",
"integrity": "sha512-w96Cjofp72M5IIhpjgobBimYEfoPjx1Vx0BSX9P30WBdZW2WIKU0T1Bd0kz2eNZ9ikjKgHbEyKx8BB6H1L3h3A==",
"dev": true,
"dependencies": {
"dom-serializer": "^1.0.1",
"domelementtype": "^2.2.0",
"domhandler": "^4.2.0"
},
"funding": {
"url": "https://github.com/fb55/domutils?sponsor=1"
}
},
"node_modules/domutils/node_modules/dom-serializer": {
"version": "1.3.2",
"resolved": "https://registry.npmjs.org/dom-serializer/-/dom-serializer-1.3.2.tgz",
"integrity": "sha512-5c54Bk5Dw4qAxNOI1pFEizPSjVsx5+bpJKmL2kPn8JhBUq2q09tTCa3mjijun2NfK78NMouDYNMBkOrPZiS+ig==",
"dev": true,
"dependencies": {
"domelementtype": "^2.0.1",
"domhandler": "^4.2.0",
"entities": "^2.0.0"
},
"funding": {
"url": "https://github.com/cheeriojs/dom-serializer?sponsor=1"
}
},
"node_modules/domutils/node_modules/domelementtype": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-2.2.0.tgz",
"integrity": "sha512-DtBMo82pv1dFtUmHyr48beiuq792Sxohr+8Hm9zoxklYPfa6n0Z3Byjj2IV7bmr2IyqClnqEQhfgHJJ5QF0R5A==",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/fb55"
}
]
},
"node_modules/domutils/node_modules/entities": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/entities/-/entities-2.2.0.tgz",
"integrity": "sha512-p92if5Nz619I0w+akJrLZH0MX0Pb5DX39XOwQTtXSdQQOaYH03S1uIQp4mhOZtAXrxq4ViO67YTiLBo2638o9A==",
"dev": true,
"funding": {
"url": "https://github.com/fb55/entities?sponsor=1"
}
},
"node_modules/duplexify": {
"version": "3.6.0",
"resolved": "https://registry.npmjs.org/duplexify/-/duplexify-3.6.0.tgz",
"integrity": "sha512-fO3Di4tBKJpYTFHAxTU00BcfWMY9w24r/x21a6rZRbsD/ToUgGxsMbiGRmB7uVAXeGKXD9MwiLZa5E97EVgIRQ==",
"dev": true,
"dependencies": {
"end-of-stream": "^1.0.0",
"inherits": "^2.0.1",
"readable-stream": "^2.0.0",
"stream-shift": "^1.0.0"
}
},
"node_modules/each-props": {
"version": "1.3.2",
"resolved": "https://registry.npmjs.org/each-props/-/each-props-1.3.2.tgz",
"integrity": "sha512-vV0Hem3zAGkJAyU7JSjixeU66rwdynTAa1vofCrSA5fEln+m67Az9CcnkVD776/fsN/UjIWmBDoNRS6t6G9RfA==",
"dev": true,
"dependencies": {
"is-plain-object": "^2.0.1",
"object.defaults": "^1.1.0"
}
},
"node_modules/electron-to-chromium": {
Update npm packages
2021-12-26 19:09:29 +09:00
"version": "1.4.28",
"resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.4.28.tgz",
"integrity": "sha512-Gzbf0wUtKfyPaqf0Plz+Ctinf9eQIzxEqBHwSvbGfeOm9GMNdLxyu1dNiCUfM+x6r4BE0xUJNh3Nmg9gfAtTmg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/emoji-regex": {
"version": "8.0.0",
"resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-8.0.0.tgz",
"integrity": "sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==",
"dev": true
},
"node_modules/emojis-list": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/emojis-list/-/emojis-list-3.0.0.tgz",
"integrity": "sha512-/kyM18EfinwXZbno9FyUGeFh87KC8HRQBQGildHZbEuRyWFOmv1U10o9BBp8XVZDVNNuQKyIGIu5ZYAAXJ0V2Q==",
"dev": true,
"engines": {
"node": ">= 4"
}
},
"node_modules/enabled": {
"version": "1.0.2",
"resolved": "http://registry.npmjs.org/enabled/-/enabled-1.0.2.tgz",
"integrity": "sha1-ll9lE9LC0cX0ZStkouM5ZGf8L5M=",
"dev": true,
"dependencies": {
"env-variable": "0.0.x"
}
},
"node_modules/end-of-stream": {
"version": "1.4.1",
"resolved": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.4.1.tgz",
"integrity": "sha512-1MkrZNvWTKCaigbn+W15elq2BB/L22nqrSY5DKlo3X6+vclJm8Bb5djXJBmEX6fS3+zCh/F4VBK5Z2KxJt4s2Q==",
"dev": true,
"dependencies": {
"once": "^1.4.0"
}
},
"node_modules/enhanced-resolve": {
"version": "5.8.3",
"resolved": "https://registry.npmjs.org/enhanced-resolve/-/enhanced-resolve-5.8.3.tgz",
"integrity": "sha512-EGAbGvH7j7Xt2nc0E7D99La1OiEs8LnyimkRgwExpUMScN6O+3x9tIWs7PLQZVNx4YD+00skHXPXi1yQHpAmZA==",
"dev": true,
"dependencies": {
"graceful-fs": "^4.2.4",
"tapable": "^2.2.0"
},
"engines": {
"node": ">=10.13.0"
}
},
"node_modules/entities": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/entities/-/entities-1.1.2.tgz",
"integrity": "sha512-f2LZMYl1Fzu7YSBKg+RoROelpOaNrcGmE9AZubeDfrCEia483oW4MI4VyFd5VNHIgQ/7qm1I0wUHK1eJnn2y2w==",
"dev": true
},
"node_modules/env-variable": {
"version": "0.0.5",
"resolved": "https://registry.npmjs.org/env-variable/-/env-variable-0.0.5.tgz",
"integrity": "sha512-zoB603vQReOFvTg5xMl9I1P2PnHsHQQKTEowsKKD7nseUfJq6UWzK+4YtlWUO1nhiQUxe6XMkk+JleSZD1NZFA==",
"dev": true
},
"node_modules/errno": {
"version": "0.1.8",
"resolved": "https://registry.npmjs.org/errno/-/errno-0.1.8.tgz",
"integrity": "sha512-dJ6oBr5SQ1VSd9qkk7ByRgb/1SH4JZjCHSW/mr63/QcXO9zLVxvJ6Oy13nio03rxpSnVDDjFor75SjVeZWPW/A==",
"dev": true,
"dependencies": {
"prr": "~1.0.1"
},
"bin": {
"errno": "cli.js"
}
},
"node_modules/error-ex": {
"version": "1.3.1",
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.3.1.tgz",
"integrity": "sha1-+FWobOYa3E6GIcPNoh56dhLDqNw=",
"dev": true,
"dependencies": {
"is-arrayish": "^0.2.1"
}
},
"node_modules/es-abstract": {
"version": "1.19.1",
"resolved": "https://registry.npmjs.org/es-abstract/-/es-abstract-1.19.1.tgz",
"integrity": "sha512-2vJ6tjA/UfqLm2MPs7jxVybLoB8i1t1Jd9R3kISld20sIxPcTbLuggQOUxeWeAvIUkduv/CfMjuh4WmiXr2v9w==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.2",
"es-to-primitive": "^1.2.1",
"function-bind": "^1.1.1",
"get-intrinsic": "^1.1.1",
"get-symbol-description": "^1.0.0",
"has": "^1.0.3",
"has-symbols": "^1.0.2",
"internal-slot": "^1.0.3",
"is-callable": "^1.2.4",
"is-negative-zero": "^2.0.1",
"is-regex": "^1.1.4",
"is-shared-array-buffer": "^1.0.1",
"is-string": "^1.0.7",
"is-weakref": "^1.0.1",
"object-inspect": "^1.11.0",
"object-keys": "^1.1.1",
"object.assign": "^4.1.2",
"string.prototype.trimend": "^1.0.4",
"string.prototype.trimstart": "^1.0.4",
"unbox-primitive": "^1.0.1"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/es-abstract/node_modules/define-properties": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.1.3.tgz",
"integrity": "sha512-3MqfYKj2lLzdMSf8ZIZE/V+Zuy+BgD6f164e8K2w7dgnpKArBDerGYpM46IYYcjnkdPNMjPk9A6VFB8+3SKlXQ==",
"dev": true,
"dependencies": {
"object-keys": "^1.0.12"
},
"engines": {
"node": ">= 0.4"
}
},
"node_modules/es-abstract/node_modules/has-symbols": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.2.tgz",
"integrity": "sha512-chXa79rL/UC2KlX17jo3vRGz0azaWEx5tGqZg5pO3NUyEJVB17dMruQlzCCOfUvElghKcm5194+BCRvi2Rv/Gw==",
"dev": true,
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/es-abstract/node_modules/object-keys": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz",
"integrity": "sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==",
"dev": true,
"engines": {
"node": ">= 0.4"
}
},
"node_modules/es-abstract/node_modules/object.assign": {
"version": "4.1.2",
"resolved": "https://registry.npmjs.org/object.assign/-/object.assign-4.1.2.tgz",
"integrity": "sha512-ixT2L5THXsApyiUPYKmW+2EHpXXe5Ii3M+f4e+aJFAHao5amFRW6J0OO6c/LU8Be47utCx2GL89hxGB6XSmKuQ==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.0",
"define-properties": "^1.1.3",
"has-symbols": "^1.0.1",
"object-keys": "^1.1.1"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/es-module-lexer": {
"version": "0.9.3",
"resolved": "https://registry.npmjs.org/es-module-lexer/-/es-module-lexer-0.9.3.tgz",
"integrity": "sha512-1HQ2M2sPtxwnvOvT1ZClHyQDiggdNjURWpY2we6aMKCQiUVxTmVs2UYPLIrD84sS+kMdUwfBSylbJPwNnBrnHQ==",
"dev": true
},
"node_modules/es-module-shims": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "1.4.6",
"resolved": "https://registry.npmjs.org/es-module-shims/-/es-module-shims-1.4.6.tgz",
"integrity": "sha512-uXuuv+98O227v1pD8HPAeG0ggqyDj6JnRcMBp+A6K7/pTgbdwyNGH4eOk9L9xifZoNbsXZ8Z2y1J9fKjr1v4KQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/es-to-primitive": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/es-to-primitive/-/es-to-primitive-1.2.1.tgz",
"integrity": "sha512-QCOllgZJtaUo9miYBcLChTUaHNjJF3PYs1VidD7AwiEj1kYxKeQTctLAezAOH5ZKRH0g2IgPn6KwB4IT8iRpvA==",
"dev": true,
"dependencies": {
"is-callable": "^1.1.4",
"is-date-object": "^1.0.1",
"is-symbol": "^1.0.2"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/es5-ext": {
"version": "0.10.44",
"resolved": "https://registry.npmjs.org/es5-ext/-/es5-ext-0.10.44.tgz",
"integrity": "sha512-TO4Vt9IhW3FzDKLDOpoA8VS9BCV4b9WTf6BqvMOgfoa8wX73F3Kh3y2J7yTstTaXlQ0k1vq4DH2vw6RSs42z+g==",
"dev": true,
"dependencies": {
"es6-iterator": "~2.0.3",
"es6-symbol": "~3.1.1",
"next-tick": "1"
}
},
"node_modules/es6-iterator": {
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/es6-iterator/-/es6-iterator-2.0.3.tgz",
"integrity": "sha1-p96IkUGgWpSwhUQDstCg+/qY87c=",
"dev": true,
"dependencies": {
"d": "1",
"es5-ext": "^0.10.35",
"es6-symbol": "^3.1.1"
}
},
"node_modules/es6-symbol": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/es6-symbol/-/es6-symbol-3.1.1.tgz",
"integrity": "sha1-vwDvT9q2uhtG7Le2KbTH7VcVzHc=",
"dev": true,
"dependencies": {
"d": "1",
"es5-ext": "~0.10.14"
}
},
"node_modules/es6-weak-map": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/es6-weak-map/-/es6-weak-map-2.0.2.tgz",
"integrity": "sha1-XjqzIlH/0VOKH45f+hNXdy+S2W8=",
"dev": true,
"dependencies": {
"d": "1",
"es5-ext": "^0.10.14",
"es6-iterator": "^2.0.1",
"es6-symbol": "^3.1.1"
}
},
"node_modules/escalade": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/escalade/-/escalade-3.1.1.tgz",
"integrity": "sha512-k0er2gUkLf8O0zKJiAhmkTnJlTvINGv7ygDNPbeIsX/TJjGJZHuh9B2UxbsaEkmlEo9MfhrSzmhIlhRlI2GXnw==",
"dev": true,
"engines": {
"node": ">=6"
}
},
"node_modules/escape-string-regexp": {
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz",
"integrity": "sha1-G2HAViGQqN/2rjuyzwIAyhMLhtQ=",
"dev": true,
"engines": {
"node": ">=0.8.0"
}
},
"node_modules/eslint": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "8.9.0",
"resolved": "https://registry.npmjs.org/eslint/-/eslint-8.9.0.tgz",
"integrity": "sha512-PB09IGwv4F4b0/atrbcMFboF/giawbBLVC7fyDamk5Wtey4Jh2K+rYaBhCAbUyEI4QzB1ly09Uglc9iCtFaG2Q==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-02-20 18:08:23 +09:00
"@eslint/eslintrc": "^1.1.0",
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"@humanwhocodes/config-array": "^0.9.2",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"ajv": "^6.10.0",
"chalk": "^4.0.0",
"cross-spawn": "^7.0.2",
"debug": "^4.3.2",
"doctrine": "^3.0.0",
"escape-string-regexp": "^4.0.0",
Update npm packages
2022-02-20 18:08:23 +09:00
"eslint-scope": "^7.1.1",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"eslint-utils": "^3.0.0",
Update npm packages
2022-02-20 18:08:23 +09:00
"eslint-visitor-keys": "^3.3.0",
"espree": "^9.3.1",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"esquery": "^1.4.0",
"esutils": "^2.0.2",
"fast-deep-equal": "^3.1.3",
"file-entry-cache": "^6.0.1",
"functional-red-black-tree": "^1.0.1",
"glob-parent": "^6.0.1",
"globals": "^13.6.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"ignore": "^5.2.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"import-fresh": "^3.0.0",
"imurmurhash": "^0.1.4",
"is-glob": "^4.0.0",
"js-yaml": "^4.1.0",
"json-stable-stringify-without-jsonify": "^1.0.1",
"levn": "^0.4.1",
"lodash.merge": "^4.6.2",
"minimatch": "^3.0.4",
"natural-compare": "^1.4.0",
"optionator": "^0.9.1",
"regexpp": "^3.2.0",
"strip-ansi": "^6.0.1",
"strip-json-comments": "^3.1.0",
"text-table": "^0.2.0",
"v8-compile-cache": "^2.0.3"
},
"bin": {
"eslint": "bin/eslint.js"
},
"engines": {
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
},
"funding": {
"url": "https://opencollective.com/eslint"
}
},
"node_modules/eslint-config-prettier": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "8.4.0",
"resolved": "https://registry.npmjs.org/eslint-config-prettier/-/eslint-config-prettier-8.4.0.tgz",
"integrity": "sha512-CFotdUcMY18nGRo5KGsnNxpznzhkopOcOo0InID+sgQssPrzjvsyKZPvOgymTFeHrFuC3Tzdf2YndhXtULK9Iw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"bin": {
"eslint-config-prettier": "bin/cli.js"
},
"peerDependencies": {
"eslint": ">=7.0.0"
}
},
"node_modules/eslint-import-resolver-node": {
"version": "0.3.6",
"resolved": "https://registry.npmjs.org/eslint-import-resolver-node/-/eslint-import-resolver-node-0.3.6.tgz",
"integrity": "sha512-0En0w03NRVMn9Uiyn8YRPDKvWjxCWkslUEhGNTdGx15RvPJYQ+lbOlqrlNI2vEAs4pDYK4f/HN2TbDmk5TP0iw==",
"dev": true,
"dependencies": {
"debug": "^3.2.7",
"resolve": "^1.20.0"
}
},
"node_modules/eslint-import-resolver-node/node_modules/debug": {
"version": "3.2.7",
"resolved": "https://registry.npmjs.org/debug/-/debug-3.2.7.tgz",
"integrity": "sha512-CFjzYYAi4ThfiQvizrFQevTTXHtnCqWfe7x1AhgEscTz6ZbLbfoLRLPugTQyBth6f8ZERVUSyWHFD/7Wu4t1XQ==",
"dev": true,
"dependencies": {
"ms": "^2.1.1"
}
},
"node_modules/eslint-import-resolver-node/node_modules/ms": {
"version": "2.1.3",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.3.tgz",
"integrity": "sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==",
"dev": true
},
"node_modules/eslint-import-resolver-node/node_modules/resolve": {
"version": "1.20.0",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.20.0.tgz",
"integrity": "sha512-wENBPt4ySzg4ybFQW2TT1zMQucPK95HSh/nq2CFTZVOGut2+pQvSsgtda4d26YrYcr067wjbmzOG8byDPBX63A==",
"dev": true,
"dependencies": {
"is-core-module": "^2.2.0",
"path-parse": "^1.0.6"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/eslint-module-utils": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "2.7.2",
"resolved": "https://registry.npmjs.org/eslint-module-utils/-/eslint-module-utils-2.7.2.tgz",
"integrity": "sha512-zquepFnWCY2ISMFwD/DqzaM++H+7PDzOpUvotJWm/y1BAFt5R4oeULgdrTejKqLkz7MA/tgstsUMNYc7wNdTrg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"debug": "^3.2.7",
Update npm packages
2022-01-09 18:05:52 +09:00
"find-up": "^2.1.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=4"
}
},
"node_modules/eslint-module-utils/node_modules/debug": {
"version": "3.2.7",
"resolved": "https://registry.npmjs.org/debug/-/debug-3.2.7.tgz",
"integrity": "sha512-CFjzYYAi4ThfiQvizrFQevTTXHtnCqWfe7x1AhgEscTz6ZbLbfoLRLPugTQyBth6f8ZERVUSyWHFD/7Wu4t1XQ==",
"dev": true,
"dependencies": {
"ms": "^2.1.1"
}
},
"node_modules/eslint-module-utils/node_modules/ms": {
"version": "2.1.3",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.3.tgz",
"integrity": "sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==",
"dev": true
},
"node_modules/eslint-plugin-fetch-options": {
"version": "0.0.5",
"resolved": "https://registry.npmjs.org/eslint-plugin-fetch-options/-/eslint-plugin-fetch-options-0.0.5.tgz",
"integrity": "sha512-ZMxrccsOAZ7uMQ4nMvPJLqLg6oyLF96YOEwTKWAIbDHpwWUp1raXALZom8ikKucaEnhqWSRuBWI8jBXveFwkJg==",
"dev": true,
"engines": {
"node": ">=0.9.0"
}
},
"node_modules/eslint-plugin-html": {
"version": "6.2.0",
"resolved": "https://registry.npmjs.org/eslint-plugin-html/-/eslint-plugin-html-6.2.0.tgz",
"integrity": "sha512-vi3NW0E8AJombTvt8beMwkL1R/fdRWl4QSNRNMhVQKWm36/X0KF0unGNAY4mqUF06mnwVWZcIcerrCnfn9025g==",
"dev": true,
"dependencies": {
"htmlparser2": "^7.1.2"
}
},
"node_modules/eslint-plugin-import": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "2.25.4",
"resolved": "https://registry.npmjs.org/eslint-plugin-import/-/eslint-plugin-import-2.25.4.tgz",
"integrity": "sha512-/KJBASVFxpu0xg1kIBn9AUa8hQVnszpwgE7Ld0lKAlx7Ie87yzEzCgSkekt+le/YVhiaosO4Y14GDAOc41nfxA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"array-includes": "^3.1.4",
"array.prototype.flat": "^1.2.5",
"debug": "^2.6.9",
"doctrine": "^2.1.0",
"eslint-import-resolver-node": "^0.3.6",
Update npm packages
2022-01-09 18:05:52 +09:00
"eslint-module-utils": "^2.7.2",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"has": "^1.0.3",
"is-core-module": "^2.8.0",
"is-glob": "^4.0.3",
"minimatch": "^3.0.4",
"object.values": "^1.1.5",
"resolve": "^1.20.0",
Update npm packages
2022-01-09 18:05:52 +09:00
"tsconfig-paths": "^3.12.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=4"
},
"peerDependencies": {
"eslint": "^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8"
}
},
"node_modules/eslint-plugin-import/node_modules/doctrine": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/doctrine/-/doctrine-2.1.0.tgz",
"integrity": "sha512-35mSku4ZXK0vfCuHEDAwt55dg2jNajHZ1odvF+8SSr82EsZY4QmXfuWso8oEd8zRhVObSN18aM0CjSdoBX7zIw==",
"dev": true,
"dependencies": {
"esutils": "^2.0.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/eslint-plugin-import/node_modules/is-core-module": {
"version": "2.8.0",
"resolved": "https://registry.npmjs.org/is-core-module/-/is-core-module-2.8.0.tgz",
"integrity": "sha512-vd15qHsaqrRL7dtH6QNuy0ndJmRDrS9HAM1CAiSifNUFv4x1a0CCVsj18hJ1mShxIG6T2i1sO78MkP56r0nYRw==",
"dev": true,
"dependencies": {
"has": "^1.0.3"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/eslint-plugin-import/node_modules/is-glob": {
"version": "4.0.3",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz",
"integrity": "sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==",
"dev": true,
"dependencies": {
"is-extglob": "^2.1.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/eslint-plugin-import/node_modules/resolve": {
"version": "1.20.0",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.20.0.tgz",
"integrity": "sha512-wENBPt4ySzg4ybFQW2TT1zMQucPK95HSh/nq2CFTZVOGut2+pQvSsgtda4d26YrYcr067wjbmzOG8byDPBX63A==",
"dev": true,
"dependencies": {
"is-core-module": "^2.2.0",
"path-parse": "^1.0.6"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/eslint-plugin-json": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/eslint-plugin-json/-/eslint-plugin-json-3.1.0.tgz",
"integrity": "sha512-MrlG2ynFEHe7wDGwbUuFPsaT2b1uhuEFhJ+W1f1u+1C2EkXmTYJp4B1aAdQQ8M+CC3t//N/oRKiIVw14L2HR1g==",
"dev": true,
"dependencies": {
"lodash": "^4.17.21",
"vscode-json-languageservice": "^4.1.6"
},
"engines": {
"node": ">=12.0"
}
},
"node_modules/eslint-plugin-mozilla": {
"version": "2.11.1",
"resolved": "https://registry.npmjs.org/eslint-plugin-mozilla/-/eslint-plugin-mozilla-2.11.1.tgz",
"integrity": "sha512-4kd2+ABYvnUzYwCHJVwhwRGUPlJLXG7DKlOjA/wGeQF3A1j7KA/Oal6+tuFh4yhL7XiHcBsn8pvla0CuB3253g==",
"dev": true,
"dependencies": {
"@babel/core": "^7.15.0",
"@babel/eslint-parser": "^7.15.0",
"eslint-scope": "^5.1.1",
"eslint-visitor-keys": "^2.1.0",
"estraverse": "^4.3.0",
"htmlparser2": "^6.0.1",
"multi-ini": "^2.1.2",
"sax": "^1.2.4"
},
"engines": {
"node": ">=6.9.1"
},
"peerDependencies": {
"eslint": "^7.23.0",
"eslint-config-prettier": "^8.0.0",
"eslint-plugin-fetch-options": "^0.0.5",
"eslint-plugin-html": "^6.0.0",
"eslint-plugin-no-unsanitized": "^3.0.0",
"eslint-plugin-prettier": "^3.0.0",
"prettier": "^1.19.1"
}
},
"node_modules/eslint-plugin-mozilla/node_modules/entities": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/entities/-/entities-2.2.0.tgz",
"integrity": "sha512-p92if5Nz619I0w+akJrLZH0MX0Pb5DX39XOwQTtXSdQQOaYH03S1uIQp4mhOZtAXrxq4ViO67YTiLBo2638o9A==",
"dev": true,
"funding": {
"url": "https://github.com/fb55/entities?sponsor=1"
}
},
"node_modules/eslint-plugin-mozilla/node_modules/estraverse": {
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-4.3.0.tgz",
"integrity": "sha512-39nnKffWz8xN1BU/2c79n9nB9HDzo0niYUqx6xyqUnyoAnQyyWpOTdZEeiCch8BBu515t4wp9ZmgVfVhn9EBpw==",
"dev": true,
"engines": {
"node": ">=4.0"
}
},
"node_modules/eslint-plugin-mozilla/node_modules/htmlparser2": {
"version": "6.1.0",
"resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-6.1.0.tgz",
"integrity": "sha512-gyyPk6rgonLFEDGoeRgQNaEUvdJ4ktTmmUh/h2t7s+M8oPpIPxgNACWa+6ESR57kXstwqPiCut0V8NRpcwgU7A==",
"dev": true,
"funding": [
"https://github.com/fb55/htmlparser2?sponsor=1",
{
"type": "github",
"url": "https://github.com/sponsors/fb55"
}
],
"dependencies": {
"domelementtype": "^2.0.1",
"domhandler": "^4.0.0",
"domutils": "^2.5.2",
"entities": "^2.0.0"
}
},
"node_modules/eslint-plugin-no-unsanitized": {
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/eslint-plugin-no-unsanitized/-/eslint-plugin-no-unsanitized-4.0.1.tgz",
"integrity": "sha512-y/lAMWnPPC7RYuUdxlEL/XiCL8FehN9h9s3Kjqbp/Kv0i9NZs+IXSC2kS546Fa4Bumwy31HlVS/OdWX0Kxb5Xg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"peerDependencies": {
"eslint": "^6 || ^7 || ^8"
}
},
"node_modules/eslint-plugin-prettier": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/eslint-plugin-prettier/-/eslint-plugin-prettier-4.0.0.tgz",
"integrity": "sha512-98MqmCJ7vJodoQK359bqQWaxOE0CS8paAz/GgjaZLyex4TTk3g9HugoO89EqWCrFiOqn9EVvcoo7gZzONCWVwQ==",
"dev": true,
"dependencies": {
"prettier-linter-helpers": "^1.0.0"
},
"engines": {
"node": ">=6.0.0"
},
"peerDependencies": {
"eslint": ">=7.28.0",
"prettier": ">=2.0.0"
},
"peerDependenciesMeta": {
"eslint-config-prettier": {
"optional": true
}
}
},
"node_modules/eslint-plugin-sort-exports": {
"version": "0.6.0",
"resolved": "https://registry.npmjs.org/eslint-plugin-sort-exports/-/eslint-plugin-sort-exports-0.6.0.tgz",
"integrity": "sha512-NMFUDPL6jVkTiGR698sv6nNEM/cA7CzSJaeIDdBnzkyj8ZYe7eFvcaxLSSSSouikQaxZQukVd74CIQ2sggbrtg==",
"dev": true,
"peerDependencies": {
"eslint": ">=5.0.0"
}
},
"node_modules/eslint-plugin-unicorn": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "41.0.0",
"resolved": "https://registry.npmjs.org/eslint-plugin-unicorn/-/eslint-plugin-unicorn-41.0.0.tgz",
"integrity": "sha512-xoJCaRc1uy5REg9DkVga1BkZV57jJxoqOcrU28QHZB89Lk5LdSqdVyTIt9JQVfHNKaiyJ7X+3iLlIn+VEHWEzA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-validator-identifier": "^7.15.7",
"ci-info": "^3.3.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"clean-regexp": "^1.0.0",
"eslint-utils": "^3.0.0",
"esquery": "^1.4.0",
Update npm packages
2022-01-09 18:05:52 +09:00
"indent-string": "^4.0.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"is-builtin-module": "^3.1.0",
"lodash": "^4.17.21",
"pluralize": "^8.0.0",
"read-pkg-up": "^7.0.1",
Update npm packages
2022-01-09 18:05:52 +09:00
"regexp-tree": "^0.1.24",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"safe-regex": "^2.1.1",
"semver": "^7.3.5",
"strip-indent": "^3.0.0"
},
"engines": {
"node": ">=12"
},
"funding": {
"url": "https://github.com/sindresorhus/eslint-plugin-unicorn?sponsor=1"
},
"peerDependencies": {
Update npm packages
2022-02-20 18:08:23 +09:00
"eslint": ">=8.8.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/eslint-plugin-unicorn/node_modules/builtin-modules": {
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-3.2.0.tgz",
"integrity": "sha512-lGzLKcioL90C7wMczpkY0n/oART3MbBa8R9OFGE1rJxoVI86u4WAGfEk8Wjv10eKSyTHVGkSo3bvBylCEtk7LA==",
"dev": true,
"engines": {
"node": ">=6"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/eslint-plugin-unicorn/node_modules/is-builtin-module": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-3.1.0.tgz",
"integrity": "sha512-OV7JjAgOTfAFJmHZLvpSTb4qi0nIILDV1gWPYDnDJUTNFM5aGlRAhk4QcT8i7TuAleeEV5Fdkqn3t4mS+Q11fg==",
"dev": true,
"dependencies": {
"builtin-modules": "^3.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/eslint-plugin-unicorn/node_modules/safe-regex": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/safe-regex/-/safe-regex-2.1.1.tgz",
"integrity": "sha512-rx+x8AMzKb5Q5lQ95Zoi6ZbJqwCLkqi3XuJXp5P3rT8OEc6sZCJG5AE5dU3lsgRr/F4Bs31jSlVN+j5KrsGu9A==",
"dev": true,
"dependencies": {
"regexp-tree": "~0.1.1"
}
},
"node_modules/eslint-plugin-unicorn/node_modules/semver": {
"version": "7.3.5",
"resolved": "https://registry.npmjs.org/semver/-/semver-7.3.5.tgz",
"integrity": "sha512-PoeGJYh8HK4BTO/a9Tf6ZG3veo/A7ZVsYrSA6J8ny9nb3B1VrpkuN+z9OE5wfE5p6H4LchYZsegiQgbJD94ZFQ==",
"dev": true,
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
"engines": {
"node": ">=10"
}
},
"node_modules/eslint-scope": {
"version": "5.1.1",
"resolved": "https://registry.npmjs.org/eslint-scope/-/eslint-scope-5.1.1.tgz",
"integrity": "sha512-2NxwbF/hZ0KpepYN0cNbo+FN6XoK7GaHlQhgx/hIZl6Va0bF45RQOOwhLIy8lQDbuCiadSLCBnH2CFYquit5bw==",
"dev": true,
"dependencies": {
"esrecurse": "^4.3.0",
"estraverse": "^4.1.1"
},
"engines": {
"node": ">=8.0.0"
}
},
"node_modules/eslint-utils": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/eslint-utils/-/eslint-utils-3.0.0.tgz",
"integrity": "sha512-uuQC43IGctw68pJA1RgbQS8/NP7rch6Cwd4j3ZBtgo4/8Flj4eGE7ZYSZRN3iq5pVUv6GPdW5Z1RFleo84uLDA==",
"dev": true,
"dependencies": {
"eslint-visitor-keys": "^2.0.0"
},
"engines": {
"node": "^10.0.0 || ^12.0.0 || >= 14.0.0"
},
"funding": {
"url": "https://github.com/sponsors/mysticatea"
},
"peerDependencies": {
"eslint": ">=5"
}
},
"node_modules/eslint-visitor-keys": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-2.1.0.tgz",
"integrity": "sha512-0rSmRBzXgDzIsD6mGdJgevzgezI534Cer5L/vyMX0kHzT/jiB43jRhd9YUlMGYLQy2zprNmoT8qasCGtY+QaKw==",
"dev": true,
"engines": {
"node": ">=10"
}
},
"node_modules/eslint/node_modules/ansi-regex": {
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
"integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/eslint/node_modules/ansi-styles": {
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz",
"integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==",
"dev": true,
"dependencies": {
"color-convert": "^2.0.1"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/chalk/ansi-styles?sponsor=1"
}
},
"node_modules/eslint/node_modules/argparse": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/argparse/-/argparse-2.0.1.tgz",
"integrity": "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==",
"dev": true
},
"node_modules/eslint/node_modules/chalk": {
"version": "4.1.2",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz",
"integrity": "sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==",
"dev": true,
"dependencies": {
"ansi-styles": "^4.1.0",
"supports-color": "^7.1.0"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/chalk/chalk?sponsor=1"
}
},
"node_modules/eslint/node_modules/color-convert": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz",
"integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==",
"dev": true,
"dependencies": {
"color-name": "~1.1.4"
},
"engines": {
Update npm packages
2021-12-26 19:09:29 +09:00
"node": ">=7.0.0"
}
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"node_modules/eslint/node_modules/debug": {
"version": "4.3.3",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.3.tgz",
"integrity": "sha512-/zxw5+vh1Tfv+4Qn7a5nsbcJKPaSvCDhojn6FEl9vupwK2VCSDtEiEtqr8DFtzYFOdz63LBkxec7DYuc2jon6Q==",
"dev": true,
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/eslint/node_modules/escape-string-regexp": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-4.0.0.tgz",
"integrity": "sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA==",
"dev": true,
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/eslint/node_modules/eslint-scope": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "7.1.1",
"resolved": "https://registry.npmjs.org/eslint-scope/-/eslint-scope-7.1.1.tgz",
"integrity": "sha512-QKQM/UXpIiHcLqJ5AOyIW7XZmzjkzQXYE54n1++wb0u9V/abW3l9uQnxX8Z5Xd18xyKIMTUAyQ0k1e8pz6LUrw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"esrecurse": "^4.3.0",
"estraverse": "^5.2.0"
},
"engines": {
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
}
},
"node_modules/eslint/node_modules/eslint-visitor-keys": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-3.3.0.tgz",
"integrity": "sha512-mQ+suqKJVyeuwGYHAdjMFqjCyfl8+Ldnxuyp3ldiMBFKkvytrXUZWaiPCEav8qDHKty44bD+qV1IP4T+w+xXRA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"engines": {
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
}
},
"node_modules/eslint/node_modules/estraverse": {
"version": "5.3.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz",
"integrity": "sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==",
"dev": true,
"engines": {
"node": ">=4.0"
}
},
"node_modules/eslint/node_modules/glob-parent": {
"version": "6.0.2",
"resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-6.0.2.tgz",
"integrity": "sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==",
"dev": true,
"dependencies": {
"is-glob": "^4.0.3"
},
"engines": {
"node": ">=10.13.0"
}
},
"node_modules/eslint/node_modules/has-flag": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz",
"integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==",
"dev": true,
"engines": {
"node": ">=8"
}
},
Update npm packages
2022-01-23 18:58:15 +09:00
"node_modules/eslint/node_modules/ignore": {
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/ignore/-/ignore-5.2.0.tgz",
"integrity": "sha512-CmxgYGiEPCLhfLnpPp1MoRmifwEIOgjcHXxOBjv7mY96c+eWScsOP9c112ZyLdWHi0FxHjI+4uVhKYp/gcdRmQ==",
"dev": true,
"engines": {
"node": ">= 4"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/eslint/node_modules/is-glob": {
"version": "4.0.3",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz",
"integrity": "sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==",
"dev": true,
"dependencies": {
"is-extglob": "^2.1.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/eslint/node_modules/js-yaml": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.0.tgz",
"integrity": "sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==",
"dev": true,
"dependencies": {
"argparse": "^2.0.1"
},
"bin": {
"js-yaml": "bin/js-yaml.js"
}
},
"node_modules/eslint/node_modules/levn": {
"version": "0.4.1",
"resolved": "https://registry.npmjs.org/levn/-/levn-0.4.1.tgz",
"integrity": "sha512-+bT2uH4E5LGE7h/n3evcS/sQlJXCpIp6ym8OWJ5eV6+67Dsql/LaaT7qJBAt2rzfoa/5QBGBhxDix1dMt2kQKQ==",
"dev": true,
"dependencies": {
"prelude-ls": "^1.2.1",
"type-check": "~0.4.0"
},
"engines": {
"node": ">= 0.8.0"
}
},
"node_modules/eslint/node_modules/ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
},
"node_modules/eslint/node_modules/optionator": {
"version": "0.9.1",
"resolved": "https://registry.npmjs.org/optionator/-/optionator-0.9.1.tgz",
"integrity": "sha512-74RlY5FCnhq4jRxVUPKDaRwrVNXMqsGsiW6AJw4XK8hmtm10wC0ypZBLw5IIp85NZMr91+qd1RvvENwg7jjRFw==",
"dev": true,
"dependencies": {
"deep-is": "^0.1.3",
"fast-levenshtein": "^2.0.6",
"levn": "^0.4.1",
"prelude-ls": "^1.2.1",
"type-check": "^0.4.0",
"word-wrap": "^1.2.3"
},
"engines": {
"node": ">= 0.8.0"
}
},
"node_modules/eslint/node_modules/prelude-ls": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.2.1.tgz",
"integrity": "sha512-vkcDPrRZo1QZLbn5RLGPpg/WmIQ65qoWWhcGKf/b5eplkkarX0m9z8ppCat4mlOqUsWpyNuYgO3VRyrYHSzX5g==",
"dev": true,
"engines": {
"node": ">= 0.8.0"
}
},
"node_modules/eslint/node_modules/strip-ansi": {
"version": "6.0.1",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
"integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
"dev": true,
"dependencies": {
"ansi-regex": "^5.0.1"
},
"engines": {
"node": ">=8"
}
},
"node_modules/eslint/node_modules/supports-color": {
"version": "7.2.0",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-7.2.0.tgz",
"integrity": "sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==",
"dev": true,
"dependencies": {
"has-flag": "^4.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/eslint/node_modules/type-check": {
"version": "0.4.0",
"resolved": "https://registry.npmjs.org/type-check/-/type-check-0.4.0.tgz",
"integrity": "sha512-XleUoc9uwGXqjWwXaUTZAmzMcFZ5858QA2vvx1Ur5xIcixXIP+8LnFDgRplU30us6teqdlskFfu+ae4K79Ooew==",
"dev": true,
"dependencies": {
"prelude-ls": "^1.2.1"
},
"engines": {
"node": ">= 0.8.0"
}
},
"node_modules/espree": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "9.3.1",
"resolved": "https://registry.npmjs.org/espree/-/espree-9.3.1.tgz",
"integrity": "sha512-bvdyLmJMfwkV3NCRl5ZhJf22zBFo1y8bYh3VYb+bfzqNB4Je68P2sSuXyuFquzWLebHpNd2/d5uv7yoP9ISnGQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-09 18:05:52 +09:00
"acorn": "^8.7.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"acorn-jsx": "^5.3.1",
Update npm packages
2022-02-20 18:08:23 +09:00
"eslint-visitor-keys": "^3.3.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
}
},
"node_modules/espree/node_modules/eslint-visitor-keys": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-3.3.0.tgz",
"integrity": "sha512-mQ+suqKJVyeuwGYHAdjMFqjCyfl8+Ldnxuyp3ldiMBFKkvytrXUZWaiPCEav8qDHKty44bD+qV1IP4T+w+xXRA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"engines": {
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
}
},
"node_modules/esprima": {
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/esprima/-/esprima-4.0.1.tgz",
"integrity": "sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==",
"dev": true,
"bin": {
"esparse": "bin/esparse.js",
"esvalidate": "bin/esvalidate.js"
},
"engines": {
"node": ">=4"
}
},
"node_modules/esquery": {
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/esquery/-/esquery-1.4.0.tgz",
"integrity": "sha512-cCDispWt5vHHtwMY2YrAQ4ibFkAL8RbH5YGBnZBc90MolvvfkkQcJro/aZiAQUlQ3qgrYS6D6v8Gc5G5CQsc9w==",
"dev": true,
"dependencies": {
"estraverse": "^5.1.0"
},
"engines": {
"node": ">=0.10"
}
},
"node_modules/esquery/node_modules/estraverse": {
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-5.2.0.tgz",
"integrity": "sha512-BxbNGGNm0RyRYvUdHpIwv9IWzeM9XClbOxwoATuFdOE7ZE6wHL+HQ5T8hoPM+zHvmKzzsEqhgy0GrQ5X13afiQ==",
"dev": true,
"engines": {
"node": ">=4.0"
}
},
"node_modules/esrecurse": {
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/esrecurse/-/esrecurse-4.3.0.tgz",
"integrity": "sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag==",
"dev": true,
"dependencies": {
"estraverse": "^5.2.0"
},
"engines": {
"node": ">=4.0"
}
},
"node_modules/esrecurse/node_modules/estraverse": {
"version": "5.3.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz",
"integrity": "sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==",
"dev": true,
"engines": {
"node": ">=4.0"
}
},
"node_modules/estraverse": {
"version": "4.2.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-4.2.0.tgz",
"integrity": "sha1-De4/7TH81GlhjOc0IJn8GvoL2xM=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/esutils": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/esutils/-/esutils-2.0.2.tgz",
"integrity": "sha1-Cr9PHKpbyx96nYrMbepPqqBLrJs=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/events": {
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/events/-/events-3.3.0.tgz",
"integrity": "sha512-mQw+2fkQbALzQ7V0MY0IqdnXNOeTtP4r0lN9z7AAawCXgqea7bDii20AYrIBrFd/Hx0M2Ocz6S111CaFkUcb0Q==",
"dev": true,
"engines": {
"node": ">=0.8.x"
}
},
"node_modules/execall": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/execall/-/execall-2.0.0.tgz",
"integrity": "sha512-0FU2hZ5Hh6iQnarpRtQurM/aAvp3RIbfvgLHrcqJYzhXyV2KFruhuChf9NC6waAhiUR7FFtlugkI4p7f2Fqlow==",
"dev": true,
"dependencies": {
"clone-regexp": "^2.1.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/expand-brackets": {
"version": "2.1.4",
"resolved": "https://registry.npmjs.org/expand-brackets/-/expand-brackets-2.1.4.tgz",
"integrity": "sha1-t3c14xXOMPa27/D4OwQVGiJEliI=",
"dev": true,
"dependencies": {
"debug": "^2.3.3",
"define-property": "^0.2.5",
"extend-shallow": "^2.0.1",
"posix-character-classes": "^0.1.0",
"regex-not": "^1.0.0",
"snapdragon": "^0.8.1",
"to-regex": "^3.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/expand-brackets/node_modules/define-property": {
"version": "0.2.5",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-0.2.5.tgz",
"integrity": "sha1-w1se+RjsPJkPmlvFe+BKrOxcgRY=",
"dev": true,
"dependencies": {
"is-descriptor": "^0.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/expand-brackets/node_modules/extend-shallow": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/extend-shallow/-/extend-shallow-2.0.1.tgz",
"integrity": "sha1-Ua99YUrZqfYQ6huvu5idaxxWiQ8=",
"dev": true,
"dependencies": {
"is-extendable": "^0.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/expand-tilde": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/expand-tilde/-/expand-tilde-2.0.2.tgz",
"integrity": "sha1-l+gBqgUt8CRU3kawK/YhZCzchQI=",
"dev": true,
"dependencies": {
"homedir-polyfill": "^1.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/extend": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/extend/-/extend-3.0.2.tgz",
"integrity": "sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==",
"dev": true
},
"node_modules/extend-shallow": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/extend-shallow/-/extend-shallow-3.0.2.tgz",
"integrity": "sha1-Jqcarwc7OfshJxcnRhMcJwQCjbg=",
"dev": true,
"dependencies": {
"assign-symbols": "^1.0.0",
"is-extendable": "^1.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/extend-shallow/node_modules/is-extendable": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/is-extendable/-/is-extendable-1.0.1.tgz",
"integrity": "sha512-arnXMxT1hhoKo9k1LZdmlNyJdDDfy2v0fXjFlmok4+i8ul/6WlbVge9bhM74OpNPQPMGUToDtz+KXa1PneJxOA==",
"dev": true,
"dependencies": {
"is-plain-object": "^2.0.4"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/extglob": {
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/extglob/-/extglob-2.0.4.tgz",
"integrity": "sha512-Nmb6QXkELsuBr24CJSkilo6UHHgbekK5UiZgfE6UHD3Eb27YC6oD+bhcT+tJ6cl8dmsgdQxnWlcry8ksBIBLpw==",
"dev": true,
"dependencies": {
"array-unique": "^0.3.2",
"define-property": "^1.0.0",
"expand-brackets": "^2.1.4",
"extend-shallow": "^2.0.1",
"fragment-cache": "^0.2.1",
"regex-not": "^1.0.0",
"snapdragon": "^0.8.1",
"to-regex": "^3.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/extglob/node_modules/define-property": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-1.0.0.tgz",
"integrity": "sha1-dp66rz9KY6rTr56NMEybvnm/sOY=",
"dev": true,
"dependencies": {
"is-descriptor": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/extglob/node_modules/extend-shallow": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/extend-shallow/-/extend-shallow-2.0.1.tgz",
"integrity": "sha1-Ua99YUrZqfYQ6huvu5idaxxWiQ8=",
"dev": true,
"dependencies": {
"is-extendable": "^0.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/extglob/node_modules/is-accessor-descriptor": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-accessor-descriptor/-/is-accessor-descriptor-1.0.0.tgz",
"integrity": "sha512-m5hnHTkcVsPfqx3AKlyttIPb7J+XykHvJP2B9bZDjlhLIoEq4XoK64Vg7boZlVWYK6LUY94dYPEE7Lh0ZkZKcQ==",
"dev": true,
"dependencies": {
"kind-of": "^6.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/extglob/node_modules/is-data-descriptor": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-data-descriptor/-/is-data-descriptor-1.0.0.tgz",
"integrity": "sha512-jbRXy1FmtAoCjQkVmIVYwuuqDFUbaOeDjmed1tOGPrsMhtJA4rD9tkgA0F1qJ3gRFRXcHYVkdeaP50Q5rE/jLQ==",
"dev": true,
"dependencies": {
"kind-of": "^6.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/extglob/node_modules/is-descriptor": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/is-descriptor/-/is-descriptor-1.0.2.tgz",
"integrity": "sha512-2eis5WqQGV7peooDyLmNEPUrps9+SXX5c9pL3xEB+4e9HnGuDa7mB7kHxHw4CbqS9k1T2hOH3miL8n8WtiYVtg==",
"dev": true,
"dependencies": {
"is-accessor-descriptor": "^1.0.0",
"is-data-descriptor": "^1.0.0",
"kind-of": "^6.0.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/extract-zip": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/extract-zip/-/extract-zip-2.0.1.tgz",
"integrity": "sha512-GDhU9ntwuKyGXdZBUgTIe+vXnWj0fppUEtMDL0+idd5Sta8TGpHssn/eusA9mrPr9qNDym6SxAYZjNvCn/9RBg==",
"dev": true,
"dependencies": {
"debug": "^4.1.1",
"get-stream": "^5.1.0",
"yauzl": "^2.10.0"
},
"bin": {
"extract-zip": "cli.js"
},
"engines": {
"node": ">= 10.17.0"
},
"optionalDependencies": {
"@types/yauzl": "^2.9.1"
}
},
"node_modules/extract-zip/node_modules/debug": {
"version": "4.3.2",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.2.tgz",
"integrity": "sha512-mOp8wKcvj7XxC78zLgw/ZA+6TSgkoE2C/ienthhRD298T7UNwAg9diBpLRxC0mOezLl4B0xV7M0cCO6P/O0Xhw==",
"dev": true,
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/extract-zip/node_modules/ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
},
"node_modules/fancy-log": {
"version": "1.3.3",
"resolved": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.3.3.tgz",
"integrity": "sha512-k9oEhlyc0FrVh25qYuSELjr8oxsCoc4/LEZfg2iJJrfEk/tZL9bCoJE47gqAvI2m/AUjluCS4+3I0eTx8n3AEw==",
"dev": true,
"dependencies": {
"ansi-gray": "^0.1.1",
"color-support": "^1.1.3",
"parse-node-version": "^1.0.0",
"time-stamp": "^1.0.0"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/fast-deep-equal": {
"version": "3.1.3",
"resolved": "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz",
"integrity": "sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==",
"dev": true
},
"node_modules/fast-diff": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/fast-diff/-/fast-diff-1.2.0.tgz",
"integrity": "sha512-xJuoT5+L99XlZ8twedaRf6Ax2TgQVxvgZOYoPKqZufmJib0tL2tegPBOZb1pVNgIhlqDlA0eO0c3wBvQcmzx4w==",
"dev": true
},
"node_modules/fast-glob": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "3.2.11",
"resolved": "https://registry.npmjs.org/fast-glob/-/fast-glob-3.2.11.tgz",
"integrity": "sha512-xrO3+1bxSo3ZVHAnqzyuewYT6aMFHRAd4Kcs92MAonjwQZLsK9d0SF1IyQ3k5PoirxTW0Oe/RqFgMQ6TcNE5Ew==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"@nodelib/fs.stat": "^2.0.2",
"@nodelib/fs.walk": "^1.2.3",
"glob-parent": "^5.1.2",
"merge2": "^1.3.0",
"micromatch": "^4.0.4"
},
"engines": {
Update npm packages
2022-02-06 19:24:14 +09:00
"node": ">=8.6.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/fast-glob/node_modules/braces": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/braces/-/braces-3.0.2.tgz",
"integrity": "sha512-b8um+L1RzM3WDSzvhm6gIz1yfTbBt6YTlcEKAvsmqCZZFw46z626lVj9j1yEPW33H5H+lBQpZMP1k8l+78Ha0A==",
"dev": true,
"dependencies": {
"fill-range": "^7.0.1"
},
"engines": {
"node": ">=8"
}
},
"node_modules/fast-glob/node_modules/fill-range": {
"version": "7.0.1",
"resolved": "https://registry.npmjs.org/fill-range/-/fill-range-7.0.1.tgz",
"integrity": "sha512-qOo9F+dMUmC2Lcb4BbVvnKJxTPjCm+RRpe4gDuGrzkL7mEVl/djYSu2OdQ2Pa302N4oqkSg9ir6jaLWJ2USVpQ==",
"dev": true,
"dependencies": {
"to-regex-range": "^5.0.1"
},
"engines": {
"node": ">=8"
}
},
"node_modules/fast-glob/node_modules/glob-parent": {
"version": "5.1.2",
"resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz",
"integrity": "sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==",
"dev": true,
"dependencies": {
"is-glob": "^4.0.1"
},
"engines": {
"node": ">= 6"
}
},
"node_modules/fast-glob/node_modules/is-glob": {
"version": "4.0.3",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz",
"integrity": "sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==",
"dev": true,
"dependencies": {
"is-extglob": "^2.1.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/fast-glob/node_modules/is-number": {
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/is-number/-/is-number-7.0.0.tgz",
"integrity": "sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==",
"dev": true,
"engines": {
"node": ">=0.12.0"
}
},
"node_modules/fast-glob/node_modules/micromatch": {
"version": "4.0.4",
"resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.4.tgz",
"integrity": "sha512-pRmzw/XUcwXGpD9aI9q/0XOwLNygjETJ8y0ao0wdqprrzDa4YnxLcz7fQRZr8voh8V10kGhABbNcHVk5wHgWwg==",
"dev": true,
"dependencies": {
"braces": "^3.0.1",
"picomatch": "^2.2.3"
},
"engines": {
"node": ">=8.6"
}
},
"node_modules/fast-glob/node_modules/to-regex-range": {
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/to-regex-range/-/to-regex-range-5.0.1.tgz",
"integrity": "sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==",
"dev": true,
"dependencies": {
"is-number": "^7.0.0"
},
"engines": {
"node": ">=8.0"
}
},
"node_modules/fast-json-stable-stringify": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/fast-json-stable-stringify/-/fast-json-stable-stringify-2.1.0.tgz",
"integrity": "sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==",
"dev": true
},
"node_modules/fast-levenshtein": {
"version": "2.0.6",
"resolved": "https://registry.npmjs.org/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz",
"integrity": "sha1-PYpcZog6FqMMqGQ+hR8Zuqd5eRc=",
"dev": true
},
"node_modules/fast-safe-stringify": {
"version": "2.0.6",
"resolved": "https://registry.npmjs.org/fast-safe-stringify/-/fast-safe-stringify-2.0.6.tgz",
"integrity": "sha512-q8BZ89jjc+mz08rSxROs8VsrBBcn1SIw1kq9NjolL509tkABRk9io01RAjSaEv1Xb2uFLt8VtRiZbGp5H8iDtg==",
"dev": true
},
"node_modules/fastest-levenshtein": {
"version": "1.0.12",
"resolved": "https://registry.npmjs.org/fastest-levenshtein/-/fastest-levenshtein-1.0.12.tgz",
"integrity": "sha512-On2N+BpYJ15xIC974QNVuYGMOlEVt4s0EOI3wwMqOmK1fdDY+FN/zltPV8vosq4ad4c/gJ1KHScUn/6AWIgiow==",
"dev": true
},
"node_modules/fastq": {
"version": "1.13.0",
"resolved": "https://registry.npmjs.org/fastq/-/fastq-1.13.0.tgz",
"integrity": "sha512-YpkpUnK8od0o1hmeSc7UUs/eB/vIPWJYjKck2QKIzAf71Vm1AAQ3EbuZB3g2JIy+pg+ERD0vqI79KyZiB2e2Nw==",
"dev": true,
"dependencies": {
"reusify": "^1.0.4"
}
},
"node_modules/fd-slicer": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/fd-slicer/-/fd-slicer-1.1.0.tgz",
"integrity": "sha1-JcfInLH5B3+IkbvmHY85Dq4lbx4=",
"dev": true,
"dependencies": {
"pend": "~1.2.0"
}
},
"node_modules/fecha": {
"version": "2.3.3",
"resolved": "http://registry.npmjs.org/fecha/-/fecha-2.3.3.tgz",
"integrity": "sha512-lUGBnIamTAwk4znq5BcqsDaxSmZ9nDVJaij6NvRt/Tg4R69gERA+otPKbS86ROw9nxVMw2/mp1fnaiWqbs6Sdg==",
"dev": true
},
"node_modules/file-entry-cache": {
"version": "6.0.1",
"resolved": "https://registry.npmjs.org/file-entry-cache/-/file-entry-cache-6.0.1.tgz",
"integrity": "sha512-7Gps/XWymbLk2QLYK4NzpMOrYjMhdIxXuIvy2QBsLE6ljuodKvdkWs/cpyJJ3CVIVpH0Oi1Hvg1ovbMzLdFBBg==",
"dev": true,
"dependencies": {
"flat-cache": "^3.0.4"
},
"engines": {
"node": "^10.12.0 || >=12.0.0"
}
},
"node_modules/fill-range": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/fill-range/-/fill-range-4.0.0.tgz",
"integrity": "sha1-1USBHUKPmOsGpj3EAtJAPDKMOPc=",
"dev": true,
"dependencies": {
"extend-shallow": "^2.0.1",
"is-number": "^3.0.0",
"repeat-string": "^1.6.1",
"to-regex-range": "^2.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/fill-range/node_modules/extend-shallow": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/extend-shallow/-/extend-shallow-2.0.1.tgz",
"integrity": "sha1-Ua99YUrZqfYQ6huvu5idaxxWiQ8=",
"dev": true,
"dependencies": {
"is-extendable": "^0.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/find-cache-dir": {
"version": "3.3.2",
"resolved": "https://registry.npmjs.org/find-cache-dir/-/find-cache-dir-3.3.2.tgz",
"integrity": "sha512-wXZV5emFEjrridIgED11OoUKLxiYjAcqot/NJdAkOhlJ+vGzwhOAfcG5OX1jP+S0PcjEn8bdMJv+g2jwQ3Onig==",
"dev": true,
"dependencies": {
"commondir": "^1.0.1",
"make-dir": "^3.0.2",
"pkg-dir": "^4.1.0"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/avajs/find-cache-dir?sponsor=1"
}
},
"node_modules/find-up": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-2.1.0.tgz",
"integrity": "sha1-RdG35QbHF93UgndaK3eSCjwMV6c=",
"dev": true,
"dependencies": {
"locate-path": "^2.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/findup-sync": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/findup-sync/-/findup-sync-3.0.0.tgz",
"integrity": "sha512-YbffarhcicEhOrm4CtrwdKBdCuz576RLdhJDsIfvNtxUuhdRet1qZcsMjqbePtAseKdAnDyM/IyXbu7PRPRLYg==",
"dev": true,
"dependencies": {
"detect-file": "^1.0.0",
"is-glob": "^4.0.0",
"micromatch": "^3.0.4",
"resolve-dir": "^1.0.1"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/findup-sync/node_modules/is-glob": {
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.1.tgz",
"integrity": "sha512-5G0tKtBTFImOqDnLB2hG6Bp2qcKEFduo4tZu9MT/H6NQv/ghhy30o55ufafxJ/LdH79LLs2Kfrn85TLKyA7BUg==",
"dev": true,
"dependencies": {
"is-extglob": "^2.1.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/fined": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/fined/-/fined-1.2.0.tgz",
"integrity": "sha512-ZYDqPLGxDkDhDZBjZBb+oD1+j0rA4E0pXY50eplAAOPg2N/gUBSSk5IM1/QhPfyVo19lJ+CvXpqfvk+b2p/8Ng==",
"dev": true,
"dependencies": {
"expand-tilde": "^2.0.2",
"is-plain-object": "^2.0.3",
"object.defaults": "^1.1.0",
"object.pick": "^1.2.0",
"parse-filepath": "^1.0.1"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/flagged-respawn": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/flagged-respawn/-/flagged-respawn-1.0.1.tgz",
"integrity": "sha512-lNaHNVymajmk0OJMBn8fVUAU1BtDeKIqKoVhk4xAALB57aALg6b4W0MfJ/cUE0g9YBXy5XhSlPIpYIJ7HaY/3Q==",
"dev": true,
"engines": {
"node": ">= 0.10"
}
},
"node_modules/flat-cache": {
"version": "3.0.4",
"resolved": "https://registry.npmjs.org/flat-cache/-/flat-cache-3.0.4.tgz",
"integrity": "sha512-dm9s5Pw7Jc0GvMYbshN6zchCA9RgQlzzEZX3vylR9IqFfS8XciblUXOKfW6SiuJ0e13eDYZoZV5wdrev7P3Nwg==",
"dev": true,
"dependencies": {
"flatted": "^3.1.0",
"rimraf": "^3.0.2"
},
"engines": {
"node": "^10.12.0 || >=12.0.0"
}
},
"node_modules/flatted": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/flatted/-/flatted-3.1.1.tgz",
"integrity": "sha512-zAoAQiudy+r5SvnSw3KJy5os/oRJYHzrzja/tBDqrZtNhUw8bt6y8OBzMWcjWr+8liV8Eb6yOhw8WZ7VFZ5ZzA==",
"dev": true
},
"node_modules/flush-write-stream": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/flush-write-stream/-/flush-write-stream-1.0.3.tgz",
"integrity": "sha512-calZMC10u0FMUqoiunI2AiGIIUtUIvifNwkHhNupZH4cbNnW1Itkoh/Nf5HFYmDrwWPjrUxpkZT0KhuCq0jmGw==",
"dev": true,
"dependencies": {
"inherits": "^2.0.1",
"readable-stream": "^2.0.4"
}
},
"node_modules/for-in": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/for-in/-/for-in-1.0.2.tgz",
"integrity": "sha1-gQaNKVqBQuwKxybG4iAMMPttXoA=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/for-own": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/for-own/-/for-own-1.0.0.tgz",
"integrity": "sha1-xjMy9BXO3EsE2/5wz4NklMU8tEs=",
"dev": true,
"dependencies": {
"for-in": "^1.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/foreach": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/foreach/-/foreach-2.0.5.tgz",
"integrity": "sha1-C+4AUBiusmDQo6865ljdATbsG5k=",
"dev": true
},
"node_modules/fraction.js": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "4.1.2",
"resolved": "https://registry.npmjs.org/fraction.js/-/fraction.js-4.1.2.tgz",
"integrity": "sha512-o2RiJQ6DZaR/5+Si0qJUIy637QMRudSi9kU/FFzx9EZazrIdnBgpU+3sEWCxAVhH2RtxW2Oz+T4p2o8uOPVcgA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"engines": {
"node": "*"
},
"funding": {
"type": "patreon",
"url": "https://www.patreon.com/infusion"
}
},
"node_modules/fragment-cache": {
"version": "0.2.1",
"resolved": "https://registry.npmjs.org/fragment-cache/-/fragment-cache-0.2.1.tgz",
"integrity": "sha1-QpD60n8T6Jvn8zeZxrxaCr//DRk=",
"dev": true,
"dependencies": {
"map-cache": "^0.2.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/fs-constants": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/fs-constants/-/fs-constants-1.0.0.tgz",
"integrity": "sha512-y6OAwoSIf7FyjMIv94u+b5rdheZEjzR63GTyZJm5qh4Bi+2YgwLCcI/fPFZkL5PSixOt6ZNKm+w+Hfp/Bciwow==",
"dev": true
},
"node_modules/fs-minipass": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/fs-minipass/-/fs-minipass-2.1.0.tgz",
"integrity": "sha512-V/JgOLFCS+R6Vcq0slCuaeWEdNC3ouDlJMNIsacH2VtALiu9mV4LPrHc5cDl8k5aw6J8jwgWWpiTo5RYhmIzvg==",
"dev": true,
"dependencies": {
"minipass": "^3.0.0"
},
"engines": {
"node": ">= 8"
}
},
"node_modules/fs-mkdirp-stream": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/fs-mkdirp-stream/-/fs-mkdirp-stream-1.0.0.tgz",
"integrity": "sha1-C3gV/DIBxqaeFNuYzgmMFpNSWes=",
"dev": true,
"dependencies": {
"graceful-fs": "^4.1.11",
"through2": "^2.0.3"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/fs-mkdirp-stream/node_modules/through2": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.5.tgz",
"integrity": "sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==",
"dev": true,
"dependencies": {
"readable-stream": "~2.3.6",
"xtend": "~4.0.1"
}
},
"node_modules/fs.realpath": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/fs.realpath/-/fs.realpath-1.0.0.tgz",
"integrity": "sha1-FQStJSMVjKpA20onh8sBQRmU6k8=",
"dev": true
},
"node_modules/fsevents": {
"version": "1.2.9",
"resolved": "https://registry.npmjs.org/fsevents/-/fsevents-1.2.9.tgz",
"integrity": "sha512-oeyj2H3EjjonWcFjD5NvZNE9Rqe4UW+nQBU2HNeKw0koVLEFIhtyETyAakeAM3de7Z/SW5kcA+fZUait9EApnw==",
"bundleDependencies": [
"node-pre-gyp"
],
"deprecated": "fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.",
"dev": true,
"hasInstallScript": true,
"optional": true,
"os": [
"darwin"
],
"dependencies": {
"nan": "^2.12.1",
"node-pre-gyp": "^0.12.0"
},
"engines": {
"node": ">=4.0"
}
},
"node_modules/fsevents/node_modules/abbrev": {
"version": "1.1.1",
"integrity": "sha512-nne9/IiQ/hzIhY6pdDnbBtz7DjPTKrY00P/zvPSm5pOFkl6xuGrGnXn/VtTNNfNtAfZ9/1RtehkszU9qcTii0Q==",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/ansi-regex": {
"version": "2.1.1",
"integrity": "sha1-w7M6te42DYbg5ijwRorn7yfWVN8=",
"dev": true,
"inBundle": true,
"optional": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/fsevents/node_modules/aproba": {
"version": "1.2.0",
"integrity": "sha512-Y9J6ZjXtoYh8RnXVCMOU/ttDmk1aBjunq9vO0ta5x85WDQiQfUF9sIPBITdbiiIVcBo03Hi3jMxigBtsddlXRw==",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/are-we-there-yet": {
"version": "1.1.5",
"integrity": "sha512-5hYdAkZlcG8tOLujVDTgCT+uPX0VnpAH28gWsLfzpXYm7wP6mp5Q/gYyR7YQ0cKVJcXJnl3j2kpBan13PtQf6w==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"delegates": "^1.0.0",
"readable-stream": "^2.0.6"
}
},
"node_modules/fsevents/node_modules/balanced-match": {
"version": "1.0.0",
"integrity": "sha1-ibTRmasr7kneFk6gK4nORi1xt2c=",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/brace-expansion": {
"version": "1.1.11",
"integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
}
},
"node_modules/fsevents/node_modules/code-point-at": {
"version": "1.1.0",
"integrity": "sha1-DQcLTQQ6W+ozovGkDi7bPZpMz3c=",
"dev": true,
"inBundle": true,
"optional": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/fsevents/node_modules/concat-map": {
"version": "0.0.1",
"integrity": "sha1-2Klr13/Wjfd5OnMDajug1UBdR3s=",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/console-control-strings": {
"version": "1.1.0",
"integrity": "sha1-PXz0Rk22RG6mRL9LOVB/mFEAjo4=",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/core-util-is": {
"version": "1.0.2",
"integrity": "sha1-tf1UIgqivFq1eqtxQMlAdUUDwac=",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/debug": {
"version": "4.1.1",
"integrity": "sha512-pYAIzeRo8J6KPEaJ0VWOh5Pzkbw/RetuzehGM7QRRX5he4fPHx2rdKMB256ehJCkX+XRQm16eZLqLNS8RSZXZw==",
"deprecated": "Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"ms": "^2.1.1"
}
},
"node_modules/fsevents/node_modules/deep-extend": {
"version": "0.6.0",
"integrity": "sha512-LOHxIOaPYdHlJRtCQfDIVZtfw/ufM8+rVj649RIHzcm/vGwQRXFt6OPqIFWsm2XEMrNIEtWR64sY1LEKD2vAOA==",
"dev": true,
"inBundle": true,
"optional": true,
"engines": {
"node": ">=4.0.0"
}
},
"node_modules/fsevents/node_modules/delegates": {
"version": "1.0.0",
"integrity": "sha1-hMbhWbgZBP3KWaDvRM2HDTElD5o=",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/detect-libc": {
"version": "1.0.3",
"integrity": "sha1-+hN8S9aY7fVc1c0CrFWfkaTEups=",
"dev": true,
"inBundle": true,
"optional": true,
"bin": {
"detect-libc": "bin/detect-libc.js"
},
"engines": {
"node": ">=0.10"
}
},
"node_modules/fsevents/node_modules/fs.realpath": {
"version": "1.0.0",
"integrity": "sha1-FQStJSMVjKpA20onh8sBQRmU6k8=",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/gauge": {
"version": "2.7.4",
"integrity": "sha1-LANAXHU4w51+s3sxcCLjJfsBi/c=",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"aproba": "^1.0.3",
"console-control-strings": "^1.0.0",
"has-unicode": "^2.0.0",
"object-assign": "^4.1.0",
"signal-exit": "^3.0.0",
"string-width": "^1.0.1",
"strip-ansi": "^3.0.1",
"wide-align": "^1.1.0"
}
},
"node_modules/fsevents/node_modules/glob": {
"version": "7.1.3",
"integrity": "sha512-vcfuiIxogLV4DlGBHIUOwI0IbrJ8HWPc4MU7HzviGeNho/UJDfi6B5p3sHeWIQ0KGIU0Jpxi5ZHxemQfLkkAwQ==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
"minimatch": "^3.0.4",
"once": "^1.3.0",
"path-is-absolute": "^1.0.0"
},
"engines": {
"node": "*"
}
},
"node_modules/fsevents/node_modules/has-unicode": {
"version": "2.0.1",
"integrity": "sha1-4Ob+aijPUROIVeCG0Wkedx3iqLk=",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/iconv-lite": {
"version": "0.4.24",
"integrity": "sha512-v3MXnZAcvnywkTUEZomIActle7RXXeedOR31wwl7VlyoXO4Qi9arvSenNQWne1TcRwhCL1HwLI21bEqdpj8/rA==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"safer-buffer": ">= 2.1.2 < 3"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/fsevents/node_modules/ignore-walk": {
"version": "3.0.1",
"integrity": "sha512-DTVlMx3IYPe0/JJcYP7Gxg7ttZZu3IInhuEhbchuqneY9wWe5Ojy2mXLBaQFUQmo0AW2r3qG7m1mg86js+gnlQ==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"minimatch": "^3.0.4"
}
},
"node_modules/fsevents/node_modules/inflight": {
"version": "1.0.6",
"integrity": "sha1-Sb1jMdfQLQwJvJEKEHW6gWW1bfk=",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"once": "^1.3.0",
"wrappy": "1"
}
},
"node_modules/fsevents/node_modules/inherits": {
"version": "2.0.3",
"integrity": "sha1-Yzwsg+PaQqUC9SRmAiSA9CCCYd4=",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/is-fullwidth-code-point": {
"version": "1.0.0",
"integrity": "sha1-754xOG8DGn8NZDr4L95QxFfvAMs=",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"number-is-nan": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/fsevents/node_modules/isarray": {
"version": "1.0.0",
"integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/minimatch": {
"version": "3.0.4",
"integrity": "sha512-yJHVQEhyqPLUTgt9B83PXu6W3rx4MvvHvSUvToogpwoGDOUQ+yDrR0HRot+yOCdCO7u4hX3pWft6kWBBcqh0UA==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"brace-expansion": "^1.1.7"
},
"engines": {
"node": "*"
}
},
"node_modules/fsevents/node_modules/minimist": {
"version": "0.0.8",
"integrity": "sha1-hX/Kv8M5fSYluCKCYuhqp6ARsF0=",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/mkdirp": {
"version": "0.5.1",
"integrity": "sha1-MAV0OOrGz3+MR2fzhkjWaX11yQM=",
"deprecated": "Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"minimist": "0.0.8"
},
"bin": {
"mkdirp": "bin/cmd.js"
}
},
"node_modules/fsevents/node_modules/ms": {
"version": "2.1.1",
"integrity": "sha512-tgp+dl5cGk28utYktBsrFqA7HKgrhgPsg6Z/EfhWI4gl1Hwq8B/GmY/0oXZ6nF8hDVesS/FpnYaD/kOWhYQvyg==",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/needle": {
"version": "2.3.0",
"integrity": "sha512-QBZu7aAFR0522EyaXZM0FZ9GLpq6lvQ3uq8gteiDUp7wKdy0lSd2hPlgFwVuW1CBkfEs9PfDQsQzZghLs/psdg==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"debug": "^4.1.0",
"iconv-lite": "^0.4.4",
"sax": "^1.2.4"
},
"bin": {
"needle": "bin/needle"
},
"engines": {
"node": ">= 4.4.x"
}
},
"node_modules/fsevents/node_modules/node-pre-gyp": {
"version": "0.12.0",
"integrity": "sha512-4KghwV8vH5k+g2ylT+sLTjy5wmUOb9vPhnM8NHvRf9dHmnW/CndrFXy2aRPaPST6dugXSdHXfeaHQm77PIz/1A==",
"deprecated": "Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"detect-libc": "^1.0.2",
"mkdirp": "^0.5.1",
"needle": "^2.2.1",
"nopt": "^4.0.1",
"npm-packlist": "^1.1.6",
"npmlog": "^4.0.2",
"rc": "^1.2.7",
"rimraf": "^2.6.1",
"semver": "^5.3.0",
"tar": "^4"
},
"bin": {
"node-pre-gyp": "bin/node-pre-gyp"
}
},
"node_modules/fsevents/node_modules/nopt": {
"version": "4.0.1",
"integrity": "sha1-0NRoWv1UFRk8jHUFYC0NF81kR00=",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"abbrev": "1",
"osenv": "^0.1.4"
},
"bin": {
"nopt": "bin/nopt.js"
}
},
"node_modules/fsevents/node_modules/npm-bundled": {
"version": "1.0.6",
"integrity": "sha512-8/JCaftHwbd//k6y2rEWp6k1wxVfpFzB6t1p825+cUb7Ym2XQfhwIC5KwhrvzZRJu+LtDE585zVaS32+CGtf0g==",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/npm-packlist": {
"version": "1.4.1",
"integrity": "sha512-+TcdO7HJJ8peiiYhvPxsEDhF3PJFGUGRcFsGve3vxvxdcpO2Z4Z7rkosRM0kWj6LfbK/P0gu3dzk5RU1ffvFcw==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"ignore-walk": "^3.0.1",
"npm-bundled": "^1.0.1"
}
},
"node_modules/fsevents/node_modules/npmlog": {
"version": "4.1.2",
"integrity": "sha512-2uUqazuKlTaSI/dC8AzicUck7+IrEaOnN/e0jd3Xtt1KcGpwx30v50mL7oPyr/h9bL3E4aZccVwpwP+5W9Vjkg==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"are-we-there-yet": "~1.1.2",
"console-control-strings": "~1.1.0",
"gauge": "~2.7.3",
"set-blocking": "~2.0.0"
}
},
"node_modules/fsevents/node_modules/number-is-nan": {
"version": "1.0.1",
"integrity": "sha1-CXtgK1NCKlIsGvuHkDGDNpQaAR0=",
"dev": true,
"inBundle": true,
"optional": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/fsevents/node_modules/object-assign": {
"version": "4.1.1",
"integrity": "sha1-IQmtx5ZYh8/AXLvUQsrIv7s2CGM=",
"dev": true,
"inBundle": true,
"optional": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/fsevents/node_modules/once": {
"version": "1.4.0",
"integrity": "sha1-WDsap3WWHUsROsF9nFC6753Xa9E=",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"wrappy": "1"
}
},
"node_modules/fsevents/node_modules/os-homedir": {
"version": "1.0.2",
"integrity": "sha1-/7xJiDNuDoM94MFox+8VISGqf7M=",
"dev": true,
"inBundle": true,
"optional": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/fsevents/node_modules/os-tmpdir": {
"version": "1.0.2",
"integrity": "sha1-u+Z0BseaqFxc/sdm/lc0VV36EnQ=",
"dev": true,
"inBundle": true,
"optional": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/fsevents/node_modules/osenv": {
"version": "0.1.5",
"integrity": "sha512-0CWcCECdMVc2Rw3U5w9ZjqX6ga6ubk1xDVKxtBQPK7wis/0F2r9T6k4ydGYhecl7YUBxBVxhL5oisPsNxAPe2g==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"os-homedir": "^1.0.0",
"os-tmpdir": "^1.0.0"
}
},
"node_modules/fsevents/node_modules/path-is-absolute": {
"version": "1.0.1",
"integrity": "sha1-F0uSaHNVNP+8es5r9TpanhtcX18=",
"dev": true,
"inBundle": true,
"optional": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/fsevents/node_modules/process-nextick-args": {
"version": "2.0.0",
"integrity": "sha512-MtEC1TqN0EU5nephaJ4rAtThHtC86dNN9qCuEhtshvpVBkAW5ZO7BASN9REnF9eoXGcRub+pFuKEpOHE+HbEMw==",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/rc": {
"version": "1.2.8",
"integrity": "sha512-y3bGgqKj3QBdxLbLkomlohkvsA8gdAiUQlSBJnBhfn+BPxg4bc62d8TcBW15wavDfgexCgccckhcZvywyQYPOw==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"deep-extend": "^0.6.0",
"ini": "~1.3.0",
"minimist": "^1.2.0",
"strip-json-comments": "~2.0.1"
},
"bin": {
"rc": "cli.js"
}
},
"node_modules/fsevents/node_modules/rc/node_modules/minimist": {
"version": "1.2.0",
"integrity": "sha1-o1AIsg9BOD7sH7kU9M1d95omQoQ=",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/readable-stream": {
"version": "2.3.6",
"integrity": "sha512-tQtKA9WIAhBF3+VLAseyMqZeBjW0AHJoxOtYqSUZNJxauErmLbVm2FW1y+J/YA9dUrAC39ITejlZWhVIwawkKw==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"node_modules/fsevents/node_modules/rimraf": {
"version": "2.6.3",
"integrity": "sha512-mwqeW5XsA2qAejG46gYdENaxXjx9onRNCfn7L0duuP4hCuTIi/QO7PDK07KJfp1d+izWPrzEJDcSqBa0OZQriA==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"glob": "^7.1.3"
},
"bin": {
"rimraf": "bin.js"
}
},
"node_modules/fsevents/node_modules/safe-buffer": {
"version": "5.1.2",
"integrity": "sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/safer-buffer": {
"version": "2.1.2",
"integrity": "sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/sax": {
"version": "1.2.4",
"integrity": "sha512-NqVDv9TpANUjFm0N8uM5GxL36UgKi9/atZw+x7YFnQ8ckwFGKrl4xX4yWtrey3UJm5nP1kUbnYgLopqWNSRhWw==",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/semver": {
"version": "5.7.0",
"integrity": "sha512-Ya52jSX2u7QKghxeoFGpLwCtGlt7j0oY9DYb5apt9nPlJ42ID+ulTXESnt/qAQcoSERyZ5sl3LDIOw0nAn/5DA==",
"dev": true,
"inBundle": true,
"optional": true,
"bin": {
"semver": "bin/semver"
}
},
"node_modules/fsevents/node_modules/set-blocking": {
"version": "2.0.0",
"integrity": "sha1-BF+XgtARrppoA93TgrJDkrPYkPc=",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/signal-exit": {
"version": "3.0.2",
"integrity": "sha1-tf3AjxKH6hF4Yo5BXiUTK3NkbG0=",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/string_decoder": {
"version": "1.1.1",
"integrity": "sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"safe-buffer": "~5.1.0"
}
},
"node_modules/fsevents/node_modules/string-width": {
"version": "1.0.2",
"integrity": "sha1-EYvfW4zcUaKn5w0hHgfisLmxB9M=",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"code-point-at": "^1.0.0",
"is-fullwidth-code-point": "^1.0.0",
"strip-ansi": "^3.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/fsevents/node_modules/strip-ansi": {
"version": "3.0.1",
"integrity": "sha1-ajhfuIU9lS1f8F0Oiq+UJ43GPc8=",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"ansi-regex": "^2.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/fsevents/node_modules/strip-json-comments": {
"version": "2.0.1",
"integrity": "sha1-PFMZQukIwml8DsNEhYwobHygpgo=",
"dev": true,
"inBundle": true,
"optional": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/fsevents/node_modules/tar": {
"version": "4.4.19",
"resolved": "https://registry.npmjs.org/tar/-/tar-4.4.19.tgz",
"integrity": "sha512-a20gEsvHnWe0ygBY8JbxoM4w3SJdhc7ZAuxkLqh+nvNQN2IOt0B5lLgM490X5Hl8FF0dl0tOf2ewFYAlIFgzVA==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"chownr": "^1.1.4",
"fs-minipass": "^1.2.7",
"minipass": "^2.9.0",
"minizlib": "^1.3.3",
"mkdirp": "^0.5.5",
"safe-buffer": "^5.2.1",
"yallist": "^3.1.1"
},
"engines": {
"node": ">=4.5"
}
},
"node_modules/fsevents/node_modules/tar/node_modules/chownr": {
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/chownr/-/chownr-1.1.4.tgz",
"integrity": "sha512-jJ0bqzaylmJtVnNgzTeSOs8DPavpbYgEr/b0YL8/2GO3xJEhInFmhKMUnEJQjZumK7KXGFhUy89PrsJWlakBVg==",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/tar/node_modules/fs-minipass": {
"version": "1.2.7",
"resolved": "https://registry.npmjs.org/fs-minipass/-/fs-minipass-1.2.7.tgz",
"integrity": "sha512-GWSSJGFy4e9GUeCcbIkED+bgAoFyj7XF1mV8rma3QW4NIqX9Kyx79N/PF61H5udOV3aY1IaMLs6pGbH71nlCTA==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"minipass": "^2.6.0"
}
},
"node_modules/fsevents/node_modules/tar/node_modules/minimist": {
"version": "1.2.5",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz",
"integrity": "sha512-FM9nNUYrRBAELZQT3xeZQ7fmMOBg6nWNmJKTcgsJeaLstP/UODVpGsr5OhXhhXg6f+qtJ8uiZ+PUxkDWcgIXLw==",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/tar/node_modules/minipass": {
"version": "2.9.0",
"resolved": "https://registry.npmjs.org/minipass/-/minipass-2.9.0.tgz",
"integrity": "sha512-wxfUjg9WebH+CUDX/CdbRlh5SmfZiy/hpkxaRI16Y9W56Pa75sWgd/rvFilSgrauD9NyFymP/+JFV3KwzIsJeg==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"safe-buffer": "^5.1.2",
"yallist": "^3.0.0"
}
},
"node_modules/fsevents/node_modules/tar/node_modules/minizlib": {
"version": "1.3.3",
"resolved": "https://registry.npmjs.org/minizlib/-/minizlib-1.3.3.tgz",
"integrity": "sha512-6ZYMOEnmVsdCeTJVE0W9ZD+pVnE8h9Hma/iOwwRDsdQoePpoX56/8B6z3P9VNwppJuBKNRuFDRNRqRWexT9G9Q==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"minipass": "^2.9.0"
}
},
"node_modules/fsevents/node_modules/tar/node_modules/mkdirp": {
"version": "0.5.5",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.5.tgz",
"integrity": "sha512-NKmAlESf6jMGym1++R0Ra7wvhV+wFW63FaSOFPwRahvea0gMUcGUhVeAg/0BC0wiv9ih5NYPB1Wn1UEI1/L+xQ==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"minimist": "^1.2.5"
},
"bin": {
"mkdirp": "bin/cmd.js"
}
},
"node_modules/fsevents/node_modules/tar/node_modules/safe-buffer": {
"version": "5.2.1",
"resolved": "https://registry.npmjs.org/safe-buffer/-/safe-buffer-5.2.1.tgz",
"integrity": "sha512-rp3So07KcdmmKbGvgaNxQSJr7bGVSVk5S9Eq1F+ppbRo70+YeaDxkw5Dd8NPN+GD6bjnYm2VuPuCXmpuYvmCXQ==",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
],
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/tar/node_modules/yallist": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/yallist/-/yallist-3.1.1.tgz",
"integrity": "sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g==",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/util-deprecate": {
"version": "1.0.2",
"integrity": "sha1-RQ1Nyfpw3nMnYvvS1KKJgUGaDM8=",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/fsevents/node_modules/wide-align": {
"version": "1.1.3",
"integrity": "sha512-QGkOQc8XL6Bt5PwnsExKBPuMKBxnGxWWW3fU55Xt4feHozMUhdUMaBCk290qpm/wG5u/RSKzwdAC4i51YigihA==",
"dev": true,
"inBundle": true,
"optional": true,
"dependencies": {
"string-width": "^1.0.2 || 2"
}
},
"node_modules/fsevents/node_modules/wrappy": {
"version": "1.0.2",
"integrity": "sha1-tSQ9jz7BqjXxNkYFvA0QNuMKtp8=",
"dev": true,
"inBundle": true,
"optional": true
},
"node_modules/function-bind": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/function-bind/-/function-bind-1.1.1.tgz",
"integrity": "sha512-yIovAzMX49sF8Yl58fSCWJ5svSLuaibPxXQJFLmBObTuCr0Mf1KiPopGM9NiFjiYBCbfaa2Fh6breQ6ANVTI0A==",
"dev": true
},
"node_modules/functional-red-black-tree": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/functional-red-black-tree/-/functional-red-black-tree-1.0.1.tgz",
"integrity": "sha1-GwqzvVU7Kg1jmdKcDj6gslIHgyc=",
"dev": true
},
"node_modules/gauge": {
"version": "2.7.4",
"resolved": "https://registry.npmjs.org/gauge/-/gauge-2.7.4.tgz",
"integrity": "sha1-LANAXHU4w51+s3sxcCLjJfsBi/c=",
"dev": true,
"dependencies": {
"aproba": "^1.0.3",
"console-control-strings": "^1.0.0",
"has-unicode": "^2.0.0",
"object-assign": "^4.1.0",
"signal-exit": "^3.0.0",
"string-width": "^1.0.1",
"strip-ansi": "^3.0.1",
"wide-align": "^1.1.0"
}
},
"node_modules/gensync": {
"version": "1.0.0-beta.2",
"resolved": "https://registry.npmjs.org/gensync/-/gensync-1.0.0-beta.2.tgz",
"integrity": "sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg==",
"dev": true,
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/get-caller-file": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/get-caller-file/-/get-caller-file-1.0.2.tgz",
"integrity": "sha1-9wLmMSfn4jHBYKgMFVSstw1QR+U=",
"dev": true
},
"node_modules/get-intrinsic": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/get-intrinsic/-/get-intrinsic-1.1.1.tgz",
"integrity": "sha512-kWZrnVM42QCiEA2Ig1bG8zjoIMOgxWwYCEeNdwY6Tv/cOSeGpcoX4pXHfKUxNKVoArnrEr2e9srnAxxGIraS9Q==",
"dev": true,
"dependencies": {
"function-bind": "^1.1.1",
"has": "^1.0.3",
"has-symbols": "^1.0.1"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/get-intrinsic/node_modules/has-symbols": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.2.tgz",
"integrity": "sha512-chXa79rL/UC2KlX17jo3vRGz0azaWEx5tGqZg5pO3NUyEJVB17dMruQlzCCOfUvElghKcm5194+BCRvi2Rv/Gw==",
"dev": true,
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/get-stdin": {
"version": "8.0.0",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-8.0.0.tgz",
"integrity": "sha512-sY22aA6xchAzprjyqmSEQv4UbAAzRN0L2dQB0NlN5acTTK9Don6nhoc3eAbUnpZiCANAMfd/+40kVdKfFygohg==",
"dev": true,
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/get-stream": {
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/get-stream/-/get-stream-5.2.0.tgz",
"integrity": "sha512-nBF+F1rAZVCu/p7rjzgA+Yb4lfYXrpl7a6VmJrU8wF9I1CKvP/QwPNZHnOlwbTkY6dvtFIzFMSyQXbLoTQPRpA==",
"dev": true,
"dependencies": {
"pump": "^3.0.0"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/get-stream/node_modules/pump": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/pump/-/pump-3.0.0.tgz",
"integrity": "sha512-LwZy+p3SFs1Pytd/jYct4wpv49HiYCqd9Rlc5ZVdk0V+8Yzv6jR5Blk3TRmPL1ft69TxP0IMZGJ+WPFU2BFhww==",
"dev": true,
"dependencies": {
"end-of-stream": "^1.1.0",
"once": "^1.3.1"
}
},
"node_modules/get-symbol-description": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/get-symbol-description/-/get-symbol-description-1.0.0.tgz",
"integrity": "sha512-2EmdH1YvIQiZpltCNgkuiUnyukzxM/R6NDJX31Ke3BG1Nq5b0S2PhX59UKi9vZpPDQVdqn+1IcaAwnzTT5vCjw==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.2",
"get-intrinsic": "^1.1.1"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/get-value": {
"version": "2.0.6",
"resolved": "https://registry.npmjs.org/get-value/-/get-value-2.0.6.tgz",
"integrity": "sha1-3BXKHGcjh8p2vTesCjlbogQqLCg=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/glob": {
"version": "7.1.2",
"resolved": "https://registry.npmjs.org/glob/-/glob-7.1.2.tgz",
"integrity": "sha512-MJTUg1kjuLeQCJ+ccE4Vpa6kKVXkPYJ2mOCQyUuKLcLQsdrMCpBPUi8qVE6+YuaJkozeA9NusTAw3hLr8Xe5EQ==",
"dev": true,
"dependencies": {
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
"minimatch": "^3.0.4",
"once": "^1.3.0",
"path-is-absolute": "^1.0.0"
},
"engines": {
"node": "*"
}
},
"node_modules/glob-parent": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz",
"integrity": "sha1-nmr2KZ2NO9K9QEMIMr0RPfkGxa4=",
"dev": true,
"dependencies": {
"is-glob": "^3.1.0",
"path-dirname": "^1.0.0"
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/glob-stream": {
"version": "6.1.0",
"resolved": "https://registry.npmjs.org/glob-stream/-/glob-stream-6.1.0.tgz",
"integrity": "sha1-cEXJlBOz65SIjYOrRtC0BMx73eQ=",
"dev": true,
"dependencies": {
"extend": "^3.0.0",
"glob": "^7.1.1",
"glob-parent": "^3.1.0",
"is-negated-glob": "^1.0.0",
"ordered-read-streams": "^1.0.0",
"pumpify": "^1.3.5",
"readable-stream": "^2.1.5",
"remove-trailing-separator": "^1.0.1",
"to-absolute-glob": "^2.0.0",
"unique-stream": "^2.0.2"
},
"engines": {
"node": ">= 0.10"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/glob-to-regexp": {
"version": "0.4.1",
"resolved": "https://registry.npmjs.org/glob-to-regexp/-/glob-to-regexp-0.4.1.tgz",
"integrity": "sha512-lkX1HJXwyMcprw/5YUZc2s7DrpAiHB21/V+E1rHUrVNokkvB6bqMzT0VfV6/86ZNabt1k14YOIaT7nDvOX3Iiw==",
"dev": true
},
"node_modules/glob-watcher": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "5.0.5",
"resolved": "https://registry.npmjs.org/glob-watcher/-/glob-watcher-5.0.5.tgz",
"integrity": "sha512-zOZgGGEHPklZNjZQaZ9f41i7F2YwE+tS5ZHrDhbBCk3stwahn5vQxnFmBJZHoYdusR6R1bLSXeGUy/BhctwKzw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"anymatch": "^2.0.0",
"async-done": "^1.2.0",
"chokidar": "^2.0.0",
"is-negated-glob": "^1.0.0",
"just-debounce": "^1.0.0",
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"normalize-path": "^3.0.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"object.defaults": "^1.1.0"
},
"engines": {
"node": ">= 0.10"
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/glob-watcher/node_modules/normalize-path": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/normalize-path/-/normalize-path-3.0.0.tgz",
"integrity": "sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/global-modules": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/global-modules/-/global-modules-1.0.0.tgz",
"integrity": "sha512-sKzpEkf11GpOFuw0Zzjzmt4B4UZwjOcG757PPvrfhxcLFbq0wpsgpOqxpxtxFiCG4DtG93M6XRVbF2oGdev7bg==",
"dev": true,
"dependencies": {
"global-prefix": "^1.0.1",
"is-windows": "^1.0.1",
"resolve-dir": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/global-prefix": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/global-prefix/-/global-prefix-1.0.2.tgz",
"integrity": "sha1-2/dDxsFJklk8ZVVoy2btMsASLr4=",
"dev": true,
"dependencies": {
"expand-tilde": "^2.0.2",
"homedir-polyfill": "^1.0.1",
"ini": "^1.3.4",
"is-windows": "^1.0.1",
"which": "^1.2.14"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/globals": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "13.12.1",
"resolved": "https://registry.npmjs.org/globals/-/globals-13.12.1.tgz",
"integrity": "sha512-317dFlgY2pdJZ9rspXDks7073GpDmXdfbM3vYYp0HAMKGDh1FfWPleI2ljVNLQX5M5lXcAslTcPTrOrMEFOjyw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"type-fest": "^0.20.2"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/globals/node_modules/type-fest": {
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.20.2.tgz",
"integrity": "sha512-Ne+eE4r0/iWnpAxD852z3A+N0Bt5RN//NjJwRd2VFHEmrywxf5vsZlh4R6lixl6B+wz/8d+maTSAkN1FIkI3LQ==",
"dev": true,
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/globby": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "11.1.0",
"resolved": "https://registry.npmjs.org/globby/-/globby-11.1.0.tgz",
"integrity": "sha512-jhIXaOzy1sb8IyocaruWSn1TjmnBVs8Ayhcy83rmxNJ8q2uWKCAj3CnJY+KpGSXCueAPc0i05kVvVKtP1t9S3g==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"array-union": "^2.1.0",
"dir-glob": "^3.0.1",
Update npm packages
2022-02-06 19:24:14 +09:00
"fast-glob": "^3.2.9",
"ignore": "^5.2.0",
"merge2": "^1.4.1",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"slash": "^3.0.0"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/globby/node_modules/ignore": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/ignore/-/ignore-5.2.0.tgz",
"integrity": "sha512-CmxgYGiEPCLhfLnpPp1MoRmifwEIOgjcHXxOBjv7mY96c+eWScsOP9c112ZyLdWHi0FxHjI+4uVhKYp/gcdRmQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"engines": {
"node": ">= 4"
}
},
"node_modules/globjoin": {
"version": "0.1.4",
"resolved": "https://registry.npmjs.org/globjoin/-/globjoin-0.1.4.tgz",
"integrity": "sha1-L0SUrIkZ43Z8XLtpHp9GMyQoXUM=",
"dev": true
},
"node_modules/glogg": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/glogg/-/glogg-1.0.1.tgz",
"integrity": "sha512-ynYqXLoluBKf9XGR1gA59yEJisIL7YHEH4xr3ZziHB5/yl4qWfaK8Js9jGe6gBGCSCKVqiyO30WnRZADvemUNw==",
"dev": true,
"dependencies": {
"sparkles": "^1.0.0"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/graceful-fs": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "4.2.9",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.9.tgz",
"integrity": "sha512-NtNxqUcXgpW2iMrfqSfR73Glt39K+BLwWsPs94yR63v45T0Wbej7eRmL5cWfwEgqXnmjQp3zaJTshdRW/qC2ZQ==",
"dev": true
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"node_modules/gulp": {
"version": "4.0.2",
"resolved": "https://registry.npmjs.org/gulp/-/gulp-4.0.2.tgz",
"integrity": "sha512-dvEs27SCZt2ibF29xYgmnwwCYZxdxhQ/+LFWlbAW8y7jt68L/65402Lz3+CKy0Ov4rOs+NERmDq7YlZaDqUIfA==",
"dev": true,
"dependencies": {
"glob-watcher": "^5.0.3",
"gulp-cli": "^2.2.0",
"undertaker": "^1.2.1",
"vinyl-fs": "^3.0.0"
},
"bin": {
"gulp": "bin/gulp.js"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/gulp-postcss": {
"version": "9.0.1",
"resolved": "https://registry.npmjs.org/gulp-postcss/-/gulp-postcss-9.0.1.tgz",
"integrity": "sha512-9QUHam5JyXwGUxaaMvoFQVT44tohpEFpM8xBdPfdwTYGM0AItS1iTQz0MpsF8Jroh7GF5Jt2GVPaYgvy8qD2Fw==",
"dev": true,
"dependencies": {
"fancy-log": "^1.3.3",
"plugin-error": "^1.0.1",
"postcss-load-config": "^3.0.0",
"vinyl-sourcemaps-apply": "^0.2.1"
},
"engines": {
"node": "^10 || ^12 || >=14"
},
"peerDependencies": {
"postcss": "^8.0.0"
}
},
"node_modules/gulp-rename": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/gulp-rename/-/gulp-rename-2.0.0.tgz",
"integrity": "sha512-97Vba4KBzbYmR5VBs9mWmK+HwIf5mj+/zioxfZhOKeXtx5ZjBk57KFlePf5nxq9QsTtFl0ejnHE3zTC9MHXqyQ==",
"dev": true,
"engines": {
"node": ">=4"
}
},
"node_modules/gulp-replace": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/gulp-replace/-/gulp-replace-1.1.3.tgz",
"integrity": "sha512-HcPHpWY4XdF8zxYkDODHnG2+7a3nD/Y8Mfu3aBgMiCFDW3X2GiOKXllsAmILcxe3KZT2BXoN18WrpEFm48KfLQ==",
"dev": true,
"dependencies": {
"@types/node": "^14.14.41",
"@types/vinyl": "^2.0.4",
"istextorbinary": "^3.0.0",
"replacestream": "^4.0.3",
"yargs-parser": ">=5.0.0-security.0"
},
"engines": {
"node": ">=10"
}
},
"node_modules/gulp-zip": {
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/gulp-zip/-/gulp-zip-5.1.0.tgz",
"integrity": "sha512-XZr/y91IliK/SpR74g3TkZejGkGEmK7CSDjSghT1jXshgO+dFvpLIz9w9fpuwkew6i7k4F+G24TubNgq1ISzEw==",
"dev": true,
"dependencies": {
"get-stream": "^5.2.0",
"plugin-error": "^1.0.1",
"through2": "^3.0.1",
"vinyl": "^2.1.0",
"yazl": "^2.5.1"
},
"engines": {
"node": ">=8"
},
"peerDependencies": {
"gulp": ">=4"
},
"peerDependenciesMeta": {
"gulp": {
"optional": true
}
}
},
"node_modules/gulp-zip/node_modules/through2": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/through2/-/through2-3.0.2.tgz",
"integrity": "sha512-enaDQ4MUyP2W6ZyT6EsMzqBPZaM/avg8iuo+l2d3QCs0J+6RaqkHV/2/lOwDTueBHeJ/2LG9lrLW3d5rWPucuQ==",
"dev": true,
"dependencies": {
"inherits": "^2.0.4",
"readable-stream": "2 || 3"
}
},
"node_modules/gulp/node_modules/camelcase": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-3.0.0.tgz",
"integrity": "sha1-MvxLn82vhF/N9+c7uXysImHwqwo=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/gulp/node_modules/cliui": {
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/cliui/-/cliui-3.2.0.tgz",
"integrity": "sha1-EgYBU3qRbSmUD5NNo7SNWFo5IT0=",
"dev": true,
"dependencies": {
"string-width": "^1.0.1",
"strip-ansi": "^3.0.1",
"wrap-ansi": "^2.0.0"
}
},
"node_modules/gulp/node_modules/find-up": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.1.2.tgz",
"integrity": "sha1-ay6YIrGizgpgq2TWEOzK1TyyTQ8=",
"dev": true,
"dependencies": {
"path-exists": "^2.0.0",
"pinkie-promise": "^2.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/gulp/node_modules/gulp-cli": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/gulp-cli/-/gulp-cli-2.2.0.tgz",
"integrity": "sha512-rGs3bVYHdyJpLqR0TUBnlcZ1O5O++Zs4bA0ajm+zr3WFCfiSLjGwoCBqFs18wzN+ZxahT9DkOK5nDf26iDsWjA==",
"dev": true,
"dependencies": {
"ansi-colors": "^1.0.1",
"archy": "^1.0.0",
"array-sort": "^1.0.0",
"color-support": "^1.1.3",
"concat-stream": "^1.6.0",
"copy-props": "^2.0.1",
"fancy-log": "^1.3.2",
"gulplog": "^1.0.0",
"interpret": "^1.1.0",
"isobject": "^3.0.1",
"liftoff": "^3.1.0",
"matchdep": "^2.0.0",
"mute-stdout": "^1.0.0",
"pretty-hrtime": "^1.0.0",
"replace-homedir": "^1.0.0",
"semver-greatest-satisfied-range": "^1.1.0",
"v8flags": "^3.0.1",
"yargs": "^7.1.0"
},
"bin": {
"gulp": "bin/gulp.js"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/gulp/node_modules/load-json-file": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.1.0.tgz",
"integrity": "sha1-lWkFcI1YtLq0wiYbBPWfMcmTdMA=",
"dev": true,
"dependencies": {
"graceful-fs": "^4.1.2",
"parse-json": "^2.2.0",
"pify": "^2.0.0",
"pinkie-promise": "^2.0.0",
"strip-bom": "^2.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/gulp/node_modules/os-locale": {
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/os-locale/-/os-locale-1.4.0.tgz",
"integrity": "sha1-IPnxeuKe00XoveWDsT0gCYA8FNk=",
"dev": true,
"dependencies": {
"lcid": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/gulp/node_modules/path-exists": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.1.0.tgz",
"integrity": "sha1-D+tsZPD8UY2adU3V77YscCJ2H0s=",
"dev": true,
"dependencies": {
"pinkie-promise": "^2.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/gulp/node_modules/path-type": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.1.0.tgz",
"integrity": "sha1-WcRPfuSR2nBNpBXaWkBwuk+P5EE=",
"dev": true,
"dependencies": {
"graceful-fs": "^4.1.2",
"pify": "^2.0.0",
"pinkie-promise": "^2.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/gulp/node_modules/pify": {
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"integrity": "sha1-7RQaasBDqEnqWISY59yosVMw6Qw=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/gulp/node_modules/read-pkg": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"integrity": "sha1-9f+qXs0pyzHAR0vKfXVra7KePyg=",
"dev": true,
"dependencies": {
"load-json-file": "^1.0.0",
"normalize-package-data": "^2.3.2",
"path-type": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/gulp/node_modules/read-pkg-up": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"integrity": "sha1-nWPBMnbAZZGNV/ACpX9AobZD+wI=",
"dev": true,
"dependencies": {
"find-up": "^1.0.0",
"read-pkg": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/gulp/node_modules/which-module": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/which-module/-/which-module-1.0.0.tgz",
"integrity": "sha1-u6Y8qGGUiZT/MHc2CJ47lgJsKk8=",
"dev": true
},
"node_modules/gulp/node_modules/yargs": {
"version": "7.1.0",
"resolved": "https://registry.npmjs.org/yargs/-/yargs-7.1.0.tgz",
"integrity": "sha1-a6MY6xaWFyf10oT46gA+jWFU0Mg=",
"dev": true,
"dependencies": {
"camelcase": "^3.0.0",
"cliui": "^3.2.0",
"decamelize": "^1.1.1",
"get-caller-file": "^1.0.1",
"os-locale": "^1.4.0",
"read-pkg-up": "^1.0.1",
"require-directory": "^2.1.1",
"require-main-filename": "^1.0.1",
"set-blocking": "^2.0.0",
"string-width": "^1.0.2",
"which-module": "^1.0.0",
"y18n": "^3.2.1",
"yargs-parser": "^5.0.0"
}
},
"node_modules/gulp/node_modules/yargs-parser": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-5.0.1.tgz",
"integrity": "sha512-wpav5XYiddjXxirPoCTUPbqM0PXvJ9hiBMvuJgInvo4/lAOTZzUprArw17q2O1P2+GHhbBr18/iQwjL5Z9BqfA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"camelcase": "^3.0.0",
"object.assign": "^4.1.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/gulplog": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
"integrity": "sha1-4oxNRdBey77YGDY86PnFkmIp/+U=",
"dev": true,
"dependencies": {
"glogg": "^1.0.0"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/hard-rejection": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/hard-rejection/-/hard-rejection-2.1.0.tgz",
"integrity": "sha512-VIZB+ibDhx7ObhAe7OVtoEbuP4h/MuOTHJ+J8h/eBXotJYl0fBgR72xDFCKgIh22OJZIOVNxBMWuhAr10r8HdA==",
"dev": true,
"engines": {
"node": ">=6"
}
},
"node_modules/has": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/has/-/has-1.0.3.tgz",
"integrity": "sha512-f2dvO0VU6Oej7RkWJGrehjbzMAjFp5/VKPp5tTpWIV4JHHZK1/BxbFRtf/siA2SWTe09caDmVtYYzWEIbBS4zw==",
"dev": true,
"dependencies": {
"function-bind": "^1.1.1"
},
"engines": {
"node": ">= 0.4.0"
}
},
"node_modules/has-bigints": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/has-bigints/-/has-bigints-1.0.1.tgz",
"integrity": "sha512-LSBS2LjbNBTf6287JEbEzvJgftkF5qFkmCo9hDRpAzKhUOlJ+hx8dd4USs00SgsUNwc4617J9ki5YtEClM2ffA==",
"dev": true,
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/has-flag": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/has-flag/-/has-flag-3.0.0.tgz",
"integrity": "sha1-tdRU3CGZriJWmfNGfloH87lVuv0=",
"dev": true,
"engines": {
"node": ">=4"
}
},
"node_modules/has-symbols": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.0.tgz",
"integrity": "sha1-uhqPGvKg/DllD1yFA2dwQSIGO0Q=",
"dev": true,
"engines": {
"node": ">= 0.4"
}
},
"node_modules/has-tostringtag": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/has-tostringtag/-/has-tostringtag-1.0.0.tgz",
"integrity": "sha512-kFjcSNhnlGV1kyoGk7OXKSawH5JOb/LzUc5w9B02hOTO0dfFRjbHQKvg1d6cf3HbeUmtU9VbbV3qzZ2Teh97WQ==",
"dev": true,
"dependencies": {
"has-symbols": "^1.0.2"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/has-tostringtag/node_modules/has-symbols": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.2.tgz",
"integrity": "sha512-chXa79rL/UC2KlX17jo3vRGz0azaWEx5tGqZg5pO3NUyEJVB17dMruQlzCCOfUvElghKcm5194+BCRvi2Rv/Gw==",
"dev": true,
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/has-unicode": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/has-unicode/-/has-unicode-2.0.1.tgz",
"integrity": "sha1-4Ob+aijPUROIVeCG0Wkedx3iqLk=",
"dev": true
},
"node_modules/has-value": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/has-value/-/has-value-1.0.0.tgz",
"integrity": "sha1-GLKB2lhbHFxR3vJMkw7SmgvmsXc=",
"dev": true,
"dependencies": {
"get-value": "^2.0.6",
"has-values": "^1.0.0",
"isobject": "^3.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/has-values": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/has-values/-/has-values-1.0.0.tgz",
"integrity": "sha1-lbC2P+whRmGab+V/51Yo1aOe/k8=",
"dev": true,
"dependencies": {
"is-number": "^3.0.0",
"kind-of": "^4.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/has-values/node_modules/kind-of": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-4.0.0.tgz",
"integrity": "sha1-IIE989cSkosgc3hpGkUGb65y3Vc=",
"dev": true,
"dependencies": {
"is-buffer": "^1.1.5"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/highlight.js": {
"version": "9.18.5",
"resolved": "https://registry.npmjs.org/highlight.js/-/highlight.js-9.18.5.tgz",
"integrity": "sha512-a5bFyofd/BHCX52/8i8uJkjr9DYwXIPnM/plwI6W7ezItLGqzt7X2G2nXuYSfsIJdkwwj/g9DG1LkcGJI/dDoA==",
"deprecated": "Support has ended for 9.x series. Upgrade to @latest",
"dev": true,
"hasInstallScript": true,
"engines": {
"node": "*"
}
},
"node_modules/homedir-polyfill": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/homedir-polyfill/-/homedir-polyfill-1.0.3.tgz",
"integrity": "sha512-eSmmWE5bZTK2Nou4g0AI3zZ9rswp7GRKoKXS1BLUkvPviOqs4YTN1djQIqrXy9k5gEtdLPy86JjRwsNM9tnDcA==",
"dev": true,
"dependencies": {
"parse-passwd": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/hosted-git-info": {
"version": "2.8.9",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.9.tgz",
"integrity": "sha512-mxIDAb9Lsm6DoOJ7xH+5+X4y1LU/4Hi50L9C5sIswK3JzULS4bwk1FvjdBgvYR4bzT4tuUQiC15FE2f5HbLvYw==",
"dev": true
},
"node_modules/html-tags": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/html-tags/-/html-tags-3.1.0.tgz",
"integrity": "sha512-1qYz89hW3lFDEazhjW0yVAV87lw8lVkrJocr72XmBkMKsoSVJCQx3W8BXsC7hO2qAt8BoVjYjtAcZ9perqGnNg==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/htmlparser2": {
"version": "7.1.2",
"resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-7.1.2.tgz",
"integrity": "sha512-d6cqsbJba2nRdg8WW2okyD4ceonFHn9jLFxhwlNcLhQWcFPdxXeJulgOLjLKtAK9T6ahd+GQNZwG9fjmGW7lyg==",
"dev": true,
"funding": [
"https://github.com/fb55/htmlparser2?sponsor=1",
{
"type": "github",
"url": "https://github.com/sponsors/fb55"
}
],
"dependencies": {
"domelementtype": "^2.0.1",
"domhandler": "^4.2.2",
"domutils": "^2.8.0",
"entities": "^3.0.1"
}
},
"node_modules/htmlparser2/node_modules/entities": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/entities/-/entities-3.0.1.tgz",
"integrity": "sha512-WiyBqoomrwMdFG1e0kqvASYfnlb0lp8M5o5Fw2OFq1hNZxxcNk8Ik0Xm7LxzBhuidnZB/UtBqVCgUz3kBOP51Q==",
"dev": true,
"engines": {
"node": ">=0.12"
},
"funding": {
"url": "https://github.com/fb55/entities?sponsor=1"
}
},
"node_modules/https-proxy-agent": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/https-proxy-agent/-/https-proxy-agent-5.0.0.tgz",
"integrity": "sha512-EkYm5BcKUGiduxzSt3Eppko+PiNWNEpa4ySk9vTC6wDsQJW9rHSa+UhGNJoRYp7bz6Ht1eaRIa6QaJqO5rCFbA==",
"dev": true,
"dependencies": {
"agent-base": "6",
"debug": "4"
},
"engines": {
"node": ">= 6"
}
},
"node_modules/https-proxy-agent/node_modules/debug": {
"version": "4.3.1",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.1.tgz",
"integrity": "sha512-doEwdvm4PCeK4K3RQN2ZC2BYUBaxwLARCqZmMjtF8a51J2Rb0xpVloFRnCODwqjpwnAoao4pelN8l3RJdv3gRQ==",
"dev": true,
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/https-proxy-agent/node_modules/ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
},
"node_modules/iconv-lite": {
"version": "0.4.24",
"resolved": "https://registry.npmjs.org/iconv-lite/-/iconv-lite-0.4.24.tgz",
"integrity": "sha512-v3MXnZAcvnywkTUEZomIActle7RXXeedOR31wwl7VlyoXO4Qi9arvSenNQWne1TcRwhCL1HwLI21bEqdpj8/rA==",
"dev": true,
"dependencies": {
"safer-buffer": ">= 2.1.2 < 3"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/ieee754": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/ieee754/-/ieee754-1.2.1.tgz",
"integrity": "sha512-dcyqhDvX1C46lXZcVqCpK+FtMRQVdIMN6/Df5js2zouUsqG7I6sFxitIC+7KYK29KdXOLHdu9zL4sFnoVQnqaA==",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
]
},
"node_modules/ignore": {
"version": "4.0.6",
"resolved": "https://registry.npmjs.org/ignore/-/ignore-4.0.6.tgz",
"integrity": "sha512-cyFDKrqc/YdcWFniJhzI42+AzS+gNwmUzOSFcRCQYwySuBBBy/KjuxWLZ/FHEH6Moq1NizMOBWyTcv8O4OZIMg==",
"dev": true,
"engines": {
"node": ">= 4"
}
},
"node_modules/import-cwd": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/import-cwd/-/import-cwd-3.0.0.tgz",
"integrity": "sha512-4pnzH16plW+hgvRECbDWpQl3cqtvSofHWh44met7ESfZ8UZOWWddm8hEyDTqREJ9RbYHY8gi8DqmaelApoOGMg==",
"dev": true,
"dependencies": {
"import-from": "^3.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/import-fresh": {
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/import-fresh/-/import-fresh-3.3.0.tgz",
"integrity": "sha512-veYYhQa+D1QBKznvhUHxb8faxlrwUnxseDAbAp457E0wLNio2bOSKnjYDhMj+YiAq61xrMGhQk9iXVk5FzgQMw==",
"dev": true,
"dependencies": {
"parent-module": "^1.0.0",
"resolve-from": "^4.0.0"
},
"engines": {
"node": ">=6"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/import-from": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/import-from/-/import-from-3.0.0.tgz",
"integrity": "sha512-CiuXOFFSzkU5x/CR0+z7T91Iht4CXgfCxVOFRhh2Zyhg5wOpWvvDLQUsWl+gcN+QscYBjez8hDCt85O7RLDttQ==",
"dev": true,
"dependencies": {
"resolve-from": "^5.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/import-from/node_modules/resolve-from": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-5.0.0.tgz",
"integrity": "sha512-qYg9KP24dD5qka9J47d0aVky0N+b4fTU89LN9iDnjB5waksiC49rvMB0PrUJQGoTmH50XPiqOvAjDfaijGxYZw==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/import-lazy": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/import-lazy/-/import-lazy-4.0.0.tgz",
"integrity": "sha512-rKtvo6a868b5Hu3heneU+L4yEQ4jYKLtjpnPeUdK7h0yzXGmyBTypknlkCvHFBqfX9YlorEiMM6Dnq/5atfHkw==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/imurmurhash": {
"version": "0.1.4",
"resolved": "https://registry.npmjs.org/imurmurhash/-/imurmurhash-0.1.4.tgz",
"integrity": "sha1-khi5srkoojixPcT7a21XbyMUU+o=",
"dev": true,
"engines": {
"node": ">=0.8.19"
}
},
"node_modules/indent-string": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-4.0.0.tgz",
"integrity": "sha512-EdDDZu4A2OyIK7Lr/2zG+w5jmbuk1DVBnEwREQvBzspBJkCEbRa8GxU1lghYcaGJCnRWibjDXlq779X1/y5xwg==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/inflight": {
"version": "1.0.6",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.6.tgz",
"integrity": "sha1-Sb1jMdfQLQwJvJEKEHW6gWW1bfk=",
"dev": true,
"dependencies": {
"once": "^1.3.0",
"wrappy": "1"
}
},
"node_modules/inherits": {
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.4.tgz",
"integrity": "sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/ini": {
"version": "1.3.7",
"resolved": "https://registry.npmjs.org/ini/-/ini-1.3.7.tgz",
"integrity": "sha512-iKpRpXP+CrP2jyrxvg1kMUpXDyRUFDWurxbnVT1vQPx+Wz9uCYsMIqYuSBLV+PAaZG/d7kRLKRFc9oDMsH+mFQ==",
"dev": true
},
"node_modules/internal-slot": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/internal-slot/-/internal-slot-1.0.3.tgz",
"integrity": "sha512-O0DB1JC/sPyZl7cIo78n5dR7eUSwwpYPiXRhTzNxZVAMUuB8vlnRFyLxdrVToks6XPLVnFfbzaVd5WLjhgg+vA==",
"dev": true,
"dependencies": {
"get-intrinsic": "^1.1.0",
"has": "^1.0.3",
"side-channel": "^1.0.4"
},
"engines": {
"node": ">= 0.4"
}
},
"node_modules/interpret": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/interpret/-/interpret-1.1.0.tgz",
"integrity": "sha1-ftGxQQxqDg94z5XTuEQMY/eLhhQ=",
"dev": true
},
"node_modules/invert-kv": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/invert-kv/-/invert-kv-1.0.0.tgz",
"integrity": "sha1-EEqOSqym09jNFXqO+L+rLXo//bY=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-absolute": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-absolute/-/is-absolute-1.0.0.tgz",
"integrity": "sha512-dOWoqflvcydARa360Gvv18DZ/gRuHKi2NU/wU5X1ZFzdYfH29nkiNZsF3mp4OJ3H4yo9Mx8A/uAGNzpzPN3yBA==",
"dev": true,
"dependencies": {
"is-relative": "^1.0.0",
"is-windows": "^1.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-accessor-descriptor": {
"version": "0.1.6",
"resolved": "https://registry.npmjs.org/is-accessor-descriptor/-/is-accessor-descriptor-0.1.6.tgz",
"integrity": "sha1-qeEss66Nh2cn7u84Q/igiXtcmNY=",
"dev": true,
"dependencies": {
"kind-of": "^3.0.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-accessor-descriptor/node_modules/kind-of": {
"version": "3.2.2",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz",
"integrity": "sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=",
"dev": true,
"dependencies": {
"is-buffer": "^1.1.5"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-arrayish": {
"version": "0.2.1",
"resolved": "https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.2.1.tgz",
"integrity": "sha1-d8mYQFJ6qOyxqLppe4BkWnqSap0=",
"dev": true
},
"node_modules/is-bigint": {
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/is-bigint/-/is-bigint-1.0.4.tgz",
"integrity": "sha512-zB9CruMamjym81i2JZ3UMn54PKGsQzsJeo6xvN3HJJ4CAsQNB6iRutp2To77OfCNuoxspsIhzaPoO1zyCEhFOg==",
"dev": true,
"dependencies": {
"has-bigints": "^1.0.1"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/is-binary-path": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/is-binary-path/-/is-binary-path-1.0.1.tgz",
"integrity": "sha1-dfFmQrSA8YenEcgUFh/TpKdlWJg=",
"dev": true,
"dependencies": {
"binary-extensions": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-boolean-object": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/is-boolean-object/-/is-boolean-object-1.1.2.tgz",
"integrity": "sha512-gDYaKHJmnj4aWxyj6YHyXVpdQawtVLHU5cb+eztPGczf6cjuTdwve5ZIEfgXqH4e57An1D1AKf8CZ3kYrQRqYA==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.2",
"has-tostringtag": "^1.0.0"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/is-buffer": {
"version": "1.1.6",
"resolved": "https://registry.npmjs.org/is-buffer/-/is-buffer-1.1.6.tgz",
"integrity": "sha512-NcdALwpXkTm5Zvvbk7owOUSvVvBKDgKP5/ewfXEznmQFfs4ZRmanOeKBTjRVjka3QFoN6XJ+9F3USqfHqTaU5w==",
"dev": true
},
"node_modules/is-builtin-module": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"integrity": "sha1-VAVy0096wxGfj3bDDLwbHgN6/74=",
"dev": true,
"dependencies": {
"builtin-modules": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-callable": {
"version": "1.2.4",
"resolved": "https://registry.npmjs.org/is-callable/-/is-callable-1.2.4.tgz",
"integrity": "sha512-nsuwtxZfMX67Oryl9LCQ+upnC0Z0BgpwntpS89m1H/TLF0zNfzfLMV/9Wa/6MZsj0acpEjAO0KF1xT6ZdLl95w==",
"dev": true,
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/is-core-module": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/is-core-module/-/is-core-module-2.2.0.tgz",
"integrity": "sha512-XRAfAdyyY5F5cOXn7hYQDqh2Xmii+DEfIcQGxK/uNwMHhIkPWO0g8msXcbzLe+MpGoR951MlqM/2iIlU4vKDdQ==",
"dev": true,
"dependencies": {
"has": "^1.0.3"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/is-data-descriptor": {
"version": "0.1.4",
"resolved": "https://registry.npmjs.org/is-data-descriptor/-/is-data-descriptor-0.1.4.tgz",
"integrity": "sha1-C17mSDiOLIYCgueT8YVv7D8wG1Y=",
"dev": true,
"dependencies": {
"kind-of": "^3.0.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-data-descriptor/node_modules/kind-of": {
"version": "3.2.2",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz",
"integrity": "sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=",
"dev": true,
"dependencies": {
"is-buffer": "^1.1.5"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-date-object": {
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/is-date-object/-/is-date-object-1.0.5.tgz",
"integrity": "sha512-9YQaSxsAiSwcvS33MBk3wTCVnWK+HhF8VZR2jRxehM16QcVOdHqPn4VPHmRK4lSr38n9JriurInLcP90xsYNfQ==",
"dev": true,
"dependencies": {
"has-tostringtag": "^1.0.0"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/is-descriptor": {
"version": "0.1.6",
"resolved": "https://registry.npmjs.org/is-descriptor/-/is-descriptor-0.1.6.tgz",
"integrity": "sha512-avDYr0SB3DwO9zsMov0gKCESFYqCnE4hq/4z3TdUlukEy5t9C0YRq7HLrsN52NAcqXKaepeCD0n+B0arnVG3Hg==",
"dev": true,
"dependencies": {
"is-accessor-descriptor": "^0.1.6",
"is-data-descriptor": "^0.1.4",
"kind-of": "^5.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-descriptor/node_modules/kind-of": {
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-5.1.0.tgz",
"integrity": "sha512-NGEErnH6F2vUuXDh+OlbcKW7/wOcfdRHaZ7VWtqCztfHri/++YKmP51OdWeGPuqCOba6kk2OTe5d02VmTB80Pw==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-expression": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/is-expression/-/is-expression-3.0.0.tgz",
"integrity": "sha1-Oayqa+f9HzRx3ELHQW5hwkMXrJ8=",
"dev": true,
"dependencies": {
"acorn": "~4.0.2",
"object-assign": "^4.0.1"
}
},
"node_modules/is-expression/node_modules/acorn": {
"version": "4.0.13",
"resolved": "https://registry.npmjs.org/acorn/-/acorn-4.0.13.tgz",
"integrity": "sha1-EFSVrlNh1pe9GVyCUZLhrX8lN4c=",
"dev": true,
"bin": {
"acorn": "bin/acorn"
},
"engines": {
"node": ">=0.4.0"
}
},
"node_modules/is-extendable": {
"version": "0.1.1",
"resolved": "https://registry.npmjs.org/is-extendable/-/is-extendable-0.1.1.tgz",
"integrity": "sha1-YrEQ4omkcUGOPsNqYX1HLjAd/Ik=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-extglob": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/is-extglob/-/is-extglob-2.1.1.tgz",
"integrity": "sha1-qIwCU1eR8C7TfHahueqXc8gz+MI=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-fullwidth-code-point": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-1.0.0.tgz",
"integrity": "sha1-754xOG8DGn8NZDr4L95QxFfvAMs=",
"dev": true,
"dependencies": {
"number-is-nan": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-glob": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-3.1.0.tgz",
"integrity": "sha1-e6WuJCF4BKxwcHuWkiVnSGzD6Eo=",
"dev": true,
"dependencies": {
"is-extglob": "^2.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-negated-glob": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-negated-glob/-/is-negated-glob-1.0.0.tgz",
"integrity": "sha1-aRC8pdqMleeEtXUbl2z1oQ/uNtI=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-negative-zero": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/is-negative-zero/-/is-negative-zero-2.0.1.tgz",
"integrity": "sha512-2z6JzQvZRa9A2Y7xC6dQQm4FSTSTNWjKIYYTt4246eMTJmIo0Q+ZyOsU66X8lxK1AbB92dFeglPLrhwpeRKO6w==",
"dev": true,
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/is-number": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/is-number/-/is-number-3.0.0.tgz",
"integrity": "sha1-JP1iAaR4LPUFYcgQJ2r8fRLXEZU=",
"dev": true,
"dependencies": {
"kind-of": "^3.0.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-number-object": {
"version": "1.0.6",
"resolved": "https://registry.npmjs.org/is-number-object/-/is-number-object-1.0.6.tgz",
"integrity": "sha512-bEVOqiRcvo3zO1+G2lVMy+gkkEm9Yh7cDMRusKKu5ZJKPUYSJwICTKZrNKHA2EbSP0Tu0+6B/emsYNHZyn6K8g==",
"dev": true,
"dependencies": {
"has-tostringtag": "^1.0.0"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/is-number/node_modules/kind-of": {
"version": "3.2.2",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz",
"integrity": "sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=",
"dev": true,
"dependencies": {
"is-buffer": "^1.1.5"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-odd": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/is-odd/-/is-odd-2.0.0.tgz",
"integrity": "sha512-OTiixgpZAT1M4NHgS5IguFp/Vz2VI3U7Goh4/HA1adtwyLtSBrxYlcSYkhpAE07s4fKEcjrFxyvtQBND4vFQyQ==",
"dev": true,
"dependencies": {
"is-number": "^4.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-odd/node_modules/is-number": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/is-number/-/is-number-4.0.0.tgz",
"integrity": "sha512-rSklcAIlf1OmFdyAqbnWTLVelsQ58uvZ66S/ZyawjWqIviTWCjg2PzVGw8WUA+nNuPTqb4wgA+NszrJ+08LlgQ==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-plain-obj": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/is-plain-obj/-/is-plain-obj-1.1.0.tgz",
"integrity": "sha1-caUMhCnfync8kqOQpKA7OfzVHT4=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-plain-object": {
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/is-plain-object/-/is-plain-object-2.0.4.tgz",
"integrity": "sha512-h5PpgXkWitc38BBMYawTYMWJHFZJVnBquFE57xFpjB8pJFiF6gZ+bU+WyI/yqXiFR5mdLsgYNaPe8uao6Uv9Og==",
"dev": true,
"dependencies": {
"isobject": "^3.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-promise": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "2.2.2",
"resolved": "https://registry.npmjs.org/is-promise/-/is-promise-2.2.2.tgz",
"integrity": "sha512-+lP4/6lKUBfQjZ2pdxThZvLUAafmZb8OAxFb8XXtiQmS35INgr85hdOGoEs124ez1FCnZJt6jau/T+alh58QFQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/is-regex": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/is-regex/-/is-regex-1.1.4.tgz",
"integrity": "sha512-kvRdxDsxZjhzUX07ZnLydzS1TU/TJlTUHHY4YLL87e37oUA49DfkLqgy+VjFocowy29cKvcSiu+kIv728jTTVg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"call-bind": "^1.0.2",
"has-tostringtag": "^1.0.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">= 0.4"
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/is-regexp": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/is-regexp/-/is-regexp-2.1.0.tgz",
"integrity": "sha512-OZ4IlER3zmRIoB9AqNhEggVxqIH4ofDns5nRrPS6yQxXE1TPCUpFznBfRQmQa8uC+pXqjMnukiJBxCisIxiLGA==",
"dev": true,
"engines": {
"node": ">=6"
}
},
"node_modules/is-relative": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-relative/-/is-relative-1.0.0.tgz",
"integrity": "sha512-Kw/ReK0iqwKeu0MITLFuj0jbPAmEiOsIwyIXvvbfa6QfmN9pkD1M+8pdk7Rl/dTKbH34/XBFMbgD4iMJhLQbGA==",
"dev": true,
"dependencies": {
"is-unc-path": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-shared-array-buffer": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/is-shared-array-buffer/-/is-shared-array-buffer-1.0.1.tgz",
"integrity": "sha512-IU0NmyknYZN0rChcKhRO1X8LYz5Isj/Fsqh8NJOSf+N/hCOTwy29F32Ik7a+QszE63IdvmwdTPDd6cZ5pg4cwA==",
"dev": true,
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/is-stream": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/is-stream/-/is-stream-1.1.0.tgz",
"integrity": "sha1-EtSj3U5o4Lec6428hBc66A2RykQ=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-string": {
"version": "1.0.7",
"resolved": "https://registry.npmjs.org/is-string/-/is-string-1.0.7.tgz",
"integrity": "sha512-tE2UXzivje6ofPW7l23cjDOMa09gb7xlAqG6jG5ej6uPV32TlWP3NKPigtaGeHNu9fohccRYvIiZMfOOnOYUtg==",
"dev": true,
"dependencies": {
"has-tostringtag": "^1.0.0"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/is-symbol": {
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/is-symbol/-/is-symbol-1.0.4.tgz",
"integrity": "sha512-C/CPBqKWnvdcxqIARxyOh4v1UUEOCHpgDa0WYgpKDFMszcrPcffg5uhwSgPCLD2WWxmq6isisz87tzT01tuGhg==",
"dev": true,
"dependencies": {
"has-symbols": "^1.0.2"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/is-symbol/node_modules/has-symbols": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.2.tgz",
"integrity": "sha512-chXa79rL/UC2KlX17jo3vRGz0azaWEx5tGqZg5pO3NUyEJVB17dMruQlzCCOfUvElghKcm5194+BCRvi2Rv/Gw==",
"dev": true,
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/is-unc-path": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-unc-path/-/is-unc-path-1.0.0.tgz",
"integrity": "sha512-mrGpVd0fs7WWLfVsStvgF6iEJnbjDFZh9/emhRDcGWTduTfNHd9CHeUwH3gYIjdbwo4On6hunkztwOaAw0yllQ==",
"dev": true,
"dependencies": {
"unc-path-regex": "^0.1.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-utf8": {
"version": "0.2.1",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.1.tgz",
"integrity": "sha1-Sw2hRCEE0bM2NA6AeX6GXPOffXI=",
"dev": true
},
"node_modules/is-valid-glob": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-valid-glob/-/is-valid-glob-1.0.0.tgz",
"integrity": "sha1-Kb8+/3Ab4tTTFdusw5vDn+j2Aao=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-weakref": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/is-weakref/-/is-weakref-1.0.1.tgz",
"integrity": "sha512-b2jKc2pQZjaeFYWEf7ScFj+Be1I+PXmlu572Q8coTXZ+LD/QQZ7ShPMst8h16riVgyXTQwUsFEl74mDvc/3MHQ==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.0"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/is-windows": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/is-windows/-/is-windows-1.0.2.tgz",
"integrity": "sha512-eXK1UInq2bPmjyX6e3VHIzMLobc4J94i4AWn+Hpq3OU5KkrRC96OAcR3PRJ/pGu6m8TRnBHP9dkXQVsT/COVIA==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/isarray": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz",
"integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=",
"dev": true
},
"node_modules/isexe": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz",
"integrity": "sha1-6PvzdNxVb/iUehDcsFctYz8s+hA=",
"dev": true
},
"node_modules/isobject": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/isobject/-/isobject-3.0.1.tgz",
"integrity": "sha1-TkMekrEalzFjaqH5yNHMvP2reN8=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/isstream": {
"version": "0.1.2",
"resolved": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz",
"integrity": "sha1-R+Y/evVa+m+S4VAOaQ64uFKcCZo=",
"dev": true
},
"node_modules/istextorbinary": {
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/istextorbinary/-/istextorbinary-3.3.0.tgz",
"integrity": "sha512-Tvq1W6NAcZeJ8op+Hq7tdZ434rqnMx4CCZ7H0ff83uEloDvVbqAwaMTZcafKGJT0VHkYzuXUiCY4hlXQg6WfoQ==",
"dev": true,
"dependencies": {
"binaryextensions": "^2.2.0",
"textextensions": "^3.2.0"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://bevry.me/fund"
}
},
"node_modules/jasmine": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "4.0.2",
"resolved": "https://registry.npmjs.org/jasmine/-/jasmine-4.0.2.tgz",
"integrity": "sha512-YsrgxJQEggxzByYe4j68eQLOiQeSrPDYGv4sHhGBp3c6HHdq+uPXeAQ73kOAQpdLZ3/0zN7x/TZTloqeE1/qIA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"glob": "^7.1.6",
Update Jasmine to version 4 For the unit-tests that were updated in this patch, note that I settled on simply using `toEqual` comparisons rather than updating the custom matchers (since those don't seem necessary any more). Please refer to the following resources for additional information: - https://github.com/jasmine/jasmine/blob/main/release_notes/4.0.0.md - https://github.com/jasmine/jasmine-npm/blob/main/release_notes/4.0.0.md - https://jasmine.github.io/tutorials/upgrading_to_Jasmine_4.0
2022-01-09 18:27:06 +09:00
"jasmine-core": "^4.0.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"bin": {
"jasmine": "bin/jasmine.js"
}
},
"node_modules/jasmine-core": {
Update Jasmine to version 4 For the unit-tests that were updated in this patch, note that I settled on simply using `toEqual` comparisons rather than updating the custom matchers (since those don't seem necessary any more). Please refer to the following resources for additional information: - https://github.com/jasmine/jasmine/blob/main/release_notes/4.0.0.md - https://github.com/jasmine/jasmine-npm/blob/main/release_notes/4.0.0.md - https://jasmine.github.io/tutorials/upgrading_to_Jasmine_4.0
2022-01-09 18:27:06 +09:00
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/jasmine-core/-/jasmine-core-4.0.0.tgz",
"integrity": "sha512-tq24OCqHElgU9KDpb/8O21r1IfotgjIzalfW9eCmRR40LZpvwXT68iariIyayMwi0m98RDt16aljdbwK0sBMmQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/jasmine/node_modules/glob": {
"version": "7.2.0",
"resolved": "https://registry.npmjs.org/glob/-/glob-7.2.0.tgz",
"integrity": "sha512-lmLf6gtyrPq8tTjSmrO94wBeQbFR3HbLHbuyD69wuyQkImp2hWqMGB47OX65FBkPffO641IP9jWa1z4ivqG26Q==",
"dev": true,
"dependencies": {
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
"minimatch": "^3.0.4",
"once": "^1.3.0",
"path-is-absolute": "^1.0.0"
},
"engines": {
"node": "*"
},
"funding": {
"url": "https://github.com/sponsors/isaacs"
}
},
"node_modules/jest-worker": {
"version": "27.3.1",
"resolved": "https://registry.npmjs.org/jest-worker/-/jest-worker-27.3.1.tgz",
"integrity": "sha512-ks3WCzsiZaOPJl/oMsDjaf0TRiSv7ctNgs0FqRr2nARsovz6AWWy4oLElwcquGSz692DzgZQrCLScPNs5YlC4g==",
"dev": true,
"dependencies": {
"@types/node": "*",
"merge-stream": "^2.0.0",
"supports-color": "^8.0.0"
},
"engines": {
"node": ">= 10.13.0"
}
},
"node_modules/jest-worker/node_modules/has-flag": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz",
"integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/jest-worker/node_modules/supports-color": {
"version": "8.1.1",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-8.1.1.tgz",
"integrity": "sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q==",
"dev": true,
"dependencies": {
"has-flag": "^4.0.0"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/chalk/supports-color?sponsor=1"
}
},
"node_modules/js-stringify": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/js-stringify/-/js-stringify-1.0.2.tgz",
"integrity": "sha1-Fzb939lyTyijaCrcYjCufk6Weds=",
"dev": true
},
"node_modules/js-tokens": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/js-tokens/-/js-tokens-4.0.0.tgz",
"integrity": "sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==",
"dev": true
},
"node_modules/js-yaml": {
"version": "3.13.1",
"resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.13.1.tgz",
"integrity": "sha512-YfbcO7jXDdyj0DGxYVSlSeQNHbD7XPWvrVWeVUujrQEoZzWJIRrCPoyk6kL6IAjAG2IolMK4T0hNUe0HOUs5Jw==",
"dev": true,
"dependencies": {
"argparse": "^1.0.7",
"esprima": "^4.0.0"
},
"bin": {
"js-yaml": "bin/js-yaml.js"
}
},
"node_modules/js2xmlparser": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "4.0.2",
"resolved": "https://registry.npmjs.org/js2xmlparser/-/js2xmlparser-4.0.2.tgz",
"integrity": "sha512-6n4D8gLlLf1n5mNLQPRfViYzu9RATblzPEtm1SthMX1Pjao0r9YI9nw7ZIfRxQMERS87mcswrg+r/OYrPRX6jA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-23 18:58:15 +09:00
"xmlcreate": "^2.0.4"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/jsdoc": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "3.6.10",
"resolved": "https://registry.npmjs.org/jsdoc/-/jsdoc-3.6.10.tgz",
"integrity": "sha512-IdQ8ppSo5LKZ9o3M+LKIIK8i00DIe5msDvG3G81Km+1dhy0XrOWD0Ji8H61ElgyEj/O9KRLokgKbAM9XX9CJAg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"@babel/parser": "^7.9.4",
Update npm packages
2022-01-23 18:58:15 +09:00
"@types/markdown-it": "^12.2.3",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"bluebird": "^3.7.2",
"catharsis": "^0.9.0",
"escape-string-regexp": "^2.0.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"js2xmlparser": "^4.0.2",
"klaw": "^4.0.1",
"markdown-it": "^12.3.2",
"markdown-it-anchor": "^8.4.1",
"marked": "^4.0.10",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"mkdirp": "^1.0.4",
"requizzle": "^0.2.3",
"strip-json-comments": "^3.1.0",
"taffydb": "2.6.2",
Update npm packages
2022-01-23 18:58:15 +09:00
"underscore": "~1.13.2"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"bin": {
"jsdoc": "jsdoc.js"
},
"engines": {
"node": ">=8.15.0"
}
},
Update npm packages
2022-01-23 18:58:15 +09:00
"node_modules/jsdoc/node_modules/argparse": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/argparse/-/argparse-2.0.1.tgz",
"integrity": "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
Update npm packages
2022-01-23 18:58:15 +09:00
"node_modules/jsdoc/node_modules/entities": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/entities/-/entities-2.1.0.tgz",
"integrity": "sha512-hCx1oky9PFrJ611mf0ifBLBRW8lUUVRlFolb5gWRfIELabBlbp9xZvrqZLZAs+NxFnbfQoeGd8wDkygjg7U85w==",
"dev": true,
"funding": {
"url": "https://github.com/fb55/entities?sponsor=1"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/jsdoc/node_modules/escape-string-regexp": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-2.0.0.tgz",
"integrity": "sha512-UpzcLCXolUWcNu5HtVMHYdXJjArjsF9C0aNnquZYY4uW/Vu0miy5YoWvbV345HauVvcAUnpRuhMMcqTcGOY2+w==",
"dev": true,
"engines": {
"node": ">=8"
}
},
Update npm packages
2022-01-23 18:58:15 +09:00
"node_modules/jsdoc/node_modules/linkify-it": {
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/linkify-it/-/linkify-it-3.0.3.tgz",
"integrity": "sha512-ynTsyrFSdE5oZ/O9GEf00kPngmOfVwazR5GKDq6EYfhlpFug3J2zybX56a2PRRpc9P+FuSoGNAwjlbDs9jJBPQ==",
"dev": true,
"dependencies": {
"uc.micro": "^1.0.1"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/jsdoc/node_modules/markdown-it": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "12.3.2",
"resolved": "https://registry.npmjs.org/markdown-it/-/markdown-it-12.3.2.tgz",
"integrity": "sha512-TchMembfxfNVpHkbtriWltGWc+m3xszaRD0CZup7GFFhzIgQqxIfn3eGj1yZpfuflzPvfkt611B2Q/Bsk1YnGg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-01-23 18:58:15 +09:00
"argparse": "^2.0.1",
"entities": "~2.1.0",
"linkify-it": "^3.0.1",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"mdurl": "^1.0.1",
"uc.micro": "^1.0.5"
},
"bin": {
"markdown-it": "bin/markdown-it.js"
}
},
"node_modules/jsesc": {
"version": "2.5.2",
"resolved": "https://registry.npmjs.org/jsesc/-/jsesc-2.5.2.tgz",
"integrity": "sha512-OYu7XEzjkCQ3C5Ps3QIZsQfNpqoJyZZA99wd9aWd05NCtC5pWOkShK2mkL6HXQR6/Cy2lbNdPlZBpuQHXE63gA==",
"dev": true,
"bin": {
"jsesc": "bin/jsesc"
},
"engines": {
"node": ">=4"
}
},
"node_modules/json-parse-better-errors": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/json-parse-better-errors/-/json-parse-better-errors-1.0.2.tgz",
"integrity": "sha512-mrqyZKfX5EhL7hvqcV6WG1yYjnjeuYDzDhhcAAUrq8Po85NBQBJP+ZDUT75qZQ98IkUoBqdkExkukOU7Ts2wrw==",
"dev": true
},
"node_modules/json-parse-even-better-errors": {
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/json-parse-even-better-errors/-/json-parse-even-better-errors-2.3.1.tgz",
"integrity": "sha512-xyFwyhro/JEof6Ghe2iz2NcXoj2sloNsWr/XsERDK/oiPCfaNhl5ONfp+jQdAZRQQ0IJWNzH9zIZF7li91kh2w==",
"dev": true
},
"node_modules/json-schema-traverse": {
"version": "0.4.1",
"resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz",
"integrity": "sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==",
"dev": true
},
"node_modules/json-stable-stringify-without-jsonify": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/json-stable-stringify-without-jsonify/-/json-stable-stringify-without-jsonify-1.0.1.tgz",
"integrity": "sha1-nbe1lJatPzz+8wp1FC0tkwrXJlE=",
"dev": true
},
"node_modules/json5": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/json5/-/json5-2.2.0.tgz",
"integrity": "sha512-f+8cldu7X/y7RAJurMEJmdoKXGB/X550w2Nr3tTbezL6RwEE/iMcm+tZnXeoZtKuOq6ft8+CqzEkrIgx1fPoQA==",
"dev": true,
"dependencies": {
"minimist": "^1.2.5"
},
"bin": {
"json5": "lib/cli.js"
},
"engines": {
"node": ">=6"
}
},
"node_modules/jsonc-parser": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/jsonc-parser/-/jsonc-parser-3.0.0.tgz",
"integrity": "sha512-fQzRfAbIBnR0IQvftw9FJveWiHp72Fg20giDrHz6TdfB12UH/uue0D3hm57UB5KgAVuniLMCaS8P1IMj9NR7cA==",
"dev": true
},
"node_modules/jstransformer": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/jstransformer/-/jstransformer-1.0.0.tgz",
"integrity": "sha1-7Yvwkh4vPx7U1cGkT2hwntJHIsM=",
"dev": true,
"dependencies": {
"is-promise": "^2.0.0",
"promise": "^7.0.1"
}
},
"node_modules/jstransformer-markdown-it": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/jstransformer-markdown-it/-/jstransformer-markdown-it-2.1.0.tgz",
"integrity": "sha1-aewwzkUYvtWZezjwJ2SOjChekvc=",
"dev": true,
"dependencies": {
"markdown-it": "^8.0.0"
},
"engines": {
"node": ">=7"
}
},
"node_modules/just-debounce": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/just-debounce/-/just-debounce-1.0.0.tgz",
"integrity": "sha1-h/zPrv/AtozRnVX2cilD+SnqNeo=",
"dev": true
},
"node_modules/keypress": {
"version": "0.1.0",
"resolved": "https://registry.npmjs.org/keypress/-/keypress-0.1.0.tgz",
"integrity": "sha1-SjGI1CkbZrT2XtuZ+AaqmuKTWSo=",
"dev": true
},
"node_modules/kind-of": {
"version": "6.0.3",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-6.0.3.tgz",
"integrity": "sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/klaw": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/klaw/-/klaw-4.0.1.tgz",
"integrity": "sha512-pgsE40/SvC7st04AHiISNewaIMUbY5V/K8b21ekiPiFoYs/EYSdsGa+FJArB1d441uq4Q8zZyIxvAzkGNlBdRw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
Update npm packages
2022-01-23 18:58:15 +09:00
"engines": {
"node": ">=14.14.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/known-css-properties": {
Update npm packages
2021-12-26 19:09:29 +09:00
"version": "0.24.0",
"resolved": "https://registry.npmjs.org/known-css-properties/-/known-css-properties-0.24.0.tgz",
"integrity": "sha512-RTSoaUAfLvpR357vWzAz/50Q/BmHfmE6ETSWfutT0AJiw10e6CmcdYRQJlLRd95B53D0Y2aD1jSxD3V3ySF+PA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/kuler": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/kuler/-/kuler-1.0.1.tgz",
"integrity": "sha512-J9nVUucG1p/skKul6DU3PUZrhs0LPulNaeUOox0IyXDi8S4CztTHs1gQphhuZmzXG7VOQSf6NJfKuzteQLv9gQ==",
"dev": true,
"dependencies": {
"colornames": "^1.1.1"
}
},
"node_modules/last-run": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/last-run/-/last-run-1.1.1.tgz",
"integrity": "sha1-RblpQsF7HHnHchmCWbqUO+v4yls=",
"dev": true,
"dependencies": {
"default-resolution": "^2.0.0",
"es6-weak-map": "^2.0.1"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/lazy-cache": {
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/lazy-cache/-/lazy-cache-1.0.4.tgz",
"integrity": "sha1-odePw6UEdMuAhF07O24dpJpEbo4=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/lazystream": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/lazystream/-/lazystream-1.0.0.tgz",
"integrity": "sha1-9plf4PggOS9hOWvolGJAe7dxaOQ=",
"dev": true,
"dependencies": {
"readable-stream": "^2.0.5"
},
"engines": {
"node": ">= 0.6.3"
}
},
"node_modules/lcid": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/lcid/-/lcid-1.0.0.tgz",
"integrity": "sha1-MIrMr6C8SDo4Z7S28rlQYlHRuDU=",
"dev": true,
"dependencies": {
"invert-kv": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/lead": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/lead/-/lead-1.0.0.tgz",
"integrity": "sha1-bxT5mje+Op3XhPVJVpDlkDRm7kI=",
"dev": true,
"dependencies": {
"flush-write-stream": "^1.0.2"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/levn": {
"version": "0.3.0",
"resolved": "https://registry.npmjs.org/levn/-/levn-0.3.0.tgz",
"integrity": "sha1-OwmSTt+fCDwEkP3UwLxEIeBHZO4=",
"dev": true,
"dependencies": {
"prelude-ls": "~1.1.2",
"type-check": "~0.3.2"
},
"engines": {
"node": ">= 0.8.0"
}
},
"node_modules/liftoff": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/liftoff/-/liftoff-3.1.0.tgz",
"integrity": "sha512-DlIPlJUkCV0Ips2zf2pJP0unEoT1kwYhiiPUGF3s/jtxTCjziNLoiVVh+jqWOWeFi6mmwQ5fNxvAUyPad4Dfog==",
"dev": true,
"dependencies": {
"extend": "^3.0.0",
"findup-sync": "^3.0.0",
"fined": "^1.0.1",
"flagged-respawn": "^1.0.0",
"is-plain-object": "^2.0.4",
"object.map": "^1.0.0",
"rechoir": "^0.6.2",
"resolve": "^1.1.7"
},
"engines": {
"node": ">= 0.8"
}
},
"node_modules/lilconfig": {
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/lilconfig/-/lilconfig-2.0.3.tgz",
"integrity": "sha512-EHKqr/+ZvdKCifpNrJCKxBTgk5XupZA3y/aCPY9mxfgBzmgh93Mt/WqjjQ38oMxXuvDokaKiM3lAgvSH2sjtHg==",
"dev": true,
"engines": {
"node": ">=10"
}
},
"node_modules/lines-and-columns": {
"version": "1.1.6",
"resolved": "https://registry.npmjs.org/lines-and-columns/-/lines-and-columns-1.1.6.tgz",
"integrity": "sha1-HADHQ7QzzQpOgHWPe2SldEDZ/wA=",
"dev": true
},
"node_modules/linkify-it": {
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/linkify-it/-/linkify-it-2.0.3.tgz",
"integrity": "sha1-2UpGSPmxwXnWT6lykSaL22zpQ08=",
"dev": true,
"dependencies": {
"uc.micro": "^1.0.1"
}
},
"node_modules/loader-runner": {
"version": "4.2.0",
"resolved": "https://registry.npmjs.org/loader-runner/-/loader-runner-4.2.0.tgz",
"integrity": "sha512-92+huvxMvYlMzMt0iIOukcwYBFpkYJdpl2xsZ7LrlayO7E8SOv+JJUEK17B/dJIHAOLMfh2dZZ/Y18WgmGtYNw==",
"dev": true,
"engines": {
"node": ">=6.11.5"
}
},
"node_modules/loader-utils": {
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/loader-utils/-/loader-utils-1.4.0.tgz",
"integrity": "sha512-qH0WSMBtn/oHuwjy/NucEgbx5dbxxnxup9s4PVXJUDHZBQY+s0NWA9rJf53RBnQZxfch7euUui7hpoAPvALZdA==",
"dev": true,
"dependencies": {
"big.js": "^5.2.2",
"emojis-list": "^3.0.0",
"json5": "^1.0.1"
},
"engines": {
"node": ">=4.0.0"
}
},
"node_modules/loader-utils/node_modules/json5": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/json5/-/json5-1.0.1.tgz",
"integrity": "sha512-aKS4WQjPenRxiQsC93MNfjx+nbF4PAdYzmd/1JIj8HYzqfbu86beTuNgXDzPknWk0n0uARlyewZo4s++ES36Ow==",
"dev": true,
"dependencies": {
"minimist": "^1.2.0"
},
"bin": {
"json5": "lib/cli.js"
}
},
"node_modules/locate-path": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/locate-path/-/locate-path-2.0.0.tgz",
"integrity": "sha1-K1aLJl7slExtnA3pw9u7ygNUzY4=",
"dev": true,
"dependencies": {
"p-locate": "^2.0.0",
"path-exists": "^3.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/lodash": {
"version": "4.17.21",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz",
"integrity": "sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==",
"dev": true
},
"node_modules/lodash.clone": {
"version": "4.5.0",
"resolved": "https://registry.npmjs.org/lodash.clone/-/lodash.clone-4.5.0.tgz",
"integrity": "sha1-GVhwRQ9aExkkeN9Lw9I9LeoZB7Y=",
"dev": true
},
"node_modules/lodash.debounce": {
"version": "4.0.8",
"resolved": "https://registry.npmjs.org/lodash.debounce/-/lodash.debounce-4.0.8.tgz",
"integrity": "sha1-gteb/zCmfEAF/9XiUVMArZyk168=",
"dev": true
},
"node_modules/lodash.merge": {
"version": "4.6.2",
"resolved": "https://registry.npmjs.org/lodash.merge/-/lodash.merge-4.6.2.tgz",
"integrity": "sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==",
"dev": true
},
"node_modules/lodash.some": {
"version": "4.6.0",
"resolved": "https://registry.npmjs.org/lodash.some/-/lodash.some-4.6.0.tgz",
"integrity": "sha1-G7nzFO9ri63tE7VJFpsqlF62jk0=",
"dev": true
},
"node_modules/lodash.truncate": {
"version": "4.4.2",
"resolved": "https://registry.npmjs.org/lodash.truncate/-/lodash.truncate-4.4.2.tgz",
"integrity": "sha1-WjUNoLERO4N+z//VgSy+WNbq4ZM=",
"dev": true
},
"node_modules/logform": {
"version": "1.10.0",
"resolved": "https://registry.npmjs.org/logform/-/logform-1.10.0.tgz",
"integrity": "sha512-em5ojIhU18fIMOw/333mD+ZLE2fis0EzXl1ZwHx4iQzmpQi6odNiY/t+ITNr33JZhT9/KEaH+UPIipr6a9EjWg==",
"dev": true,
"dependencies": {
"colors": "^1.2.1",
"fast-safe-stringify": "^2.0.4",
"fecha": "^2.3.3",
"ms": "^2.1.1",
"triple-beam": "^1.2.0"
}
},
"node_modules/logform/node_modules/ms": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.1.tgz",
"integrity": "sha512-tgp+dl5cGk28utYktBsrFqA7HKgrhgPsg6Z/EfhWI4gl1Hwq8B/GmY/0oXZ6nF8hDVesS/FpnYaD/kOWhYQvyg==",
"dev": true
},
"node_modules/longest": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/longest/-/longest-1.0.1.tgz",
"integrity": "sha1-MKCy2jj3N3DoKUoNIuZiXtd9AJc=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/lru-cache": {
"version": "6.0.0",
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-6.0.0.tgz",
"integrity": "sha512-Jo6dJ04CmSjuznwJSS3pUeWmd/H0ffTlkXXgwZi+eq1UCmqQwCh+eLsYOYCwY991i2Fah4h1BEMCx4qThGbsiA==",
"dev": true,
"dependencies": {
"yallist": "^4.0.0"
},
"engines": {
"node": ">=10"
}
},
"node_modules/lru-cache/node_modules/yallist": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/yallist/-/yallist-4.0.0.tgz",
"integrity": "sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A==",
"dev": true
},
"node_modules/make-dir": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/make-dir/-/make-dir-3.1.0.tgz",
"integrity": "sha512-g3FeP20LNwhALb/6Cz6Dd4F2ngze0jz7tbzrD2wAV+o9FeNHe4rL+yK2md0J/fiSf1sa1ADhXqi5+oVwOM/eGw==",
"dev": true,
"dependencies": {
"semver": "^6.0.0"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/make-dir/node_modules/semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
"dev": true,
"bin": {
"semver": "bin/semver.js"
}
},
"node_modules/make-iterator": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/make-iterator/-/make-iterator-1.0.1.tgz",
"integrity": "sha512-pxiuXh0iVEq7VM7KMIhs5gxsfxCux2URptUQaXo4iZZJxBAzTPOLE2BumO5dbfVYq/hBJFBR/a1mFDmOx5AGmw==",
"dev": true,
"dependencies": {
"kind-of": "^6.0.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/map-cache": {
"version": "0.2.2",
"resolved": "https://registry.npmjs.org/map-cache/-/map-cache-0.2.2.tgz",
"integrity": "sha1-wyq9C9ZSXZsFFkW7TyasXcmKDb8=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/map-obj": {
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-4.3.0.tgz",
"integrity": "sha512-hdN1wVrZbb29eBGiGjJbeP8JbKjq1urkHJ/LIP/NY48MZ1QVXUsQBV1G1zvYFHn1XE06cwjBsOI2K3Ulnj1YXQ==",
"dev": true,
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/map-visit": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/map-visit/-/map-visit-1.0.0.tgz",
"integrity": "sha1-7Nyo8TFE5mDxtb1B8S80edmN+48=",
"dev": true,
"dependencies": {
"object-visit": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/markdown-it": {
"version": "8.4.2",
"resolved": "https://registry.npmjs.org/markdown-it/-/markdown-it-8.4.2.tgz",
"integrity": "sha512-GcRz3AWTqSUphY3vsUqQSFMbgR38a4Lh3GWlHRh/7MRwz8mcu9n2IO7HOh+bXHrR9kOPDl5RNCaEsrneb+xhHQ==",
"dev": true,
"dependencies": {
"argparse": "^1.0.7",
"entities": "~1.1.1",
"linkify-it": "^2.0.0",
"mdurl": "^1.0.1",
"uc.micro": "^1.0.5"
},
"bin": {
"markdown-it": "bin/markdown-it.js"
}
},
"node_modules/markdown-it-anchor": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "8.4.1",
"resolved": "https://registry.npmjs.org/markdown-it-anchor/-/markdown-it-anchor-8.4.1.tgz",
"integrity": "sha512-sLODeRetZ/61KkKLJElaU3NuU2z7MhXf12Ml1WJMSdwpngeofneCRF+JBbat8HiSqhniOMuTemXMrsI7hA6XyA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"peerDependencies": {
Update npm packages
2022-01-23 18:58:15 +09:00
"@types/markdown-it": "*",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"markdown-it": "*"
}
},
"node_modules/marked": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "4.0.10",
"resolved": "https://registry.npmjs.org/marked/-/marked-4.0.10.tgz",
"integrity": "sha512-+QvuFj0nGgO970fySghXGmuw+Fd0gD2x3+MqCWLIPf5oxdv1Ka6b2q+z9RP01P/IaKPMEramy+7cNy/Lw8c3hw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"bin": {
Update npm packages
2022-01-23 18:58:15 +09:00
"marked": "bin/marked.js"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
Update npm packages
2022-01-23 18:58:15 +09:00
"node": ">= 12"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/matchdep": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/matchdep/-/matchdep-2.0.0.tgz",
"integrity": "sha1-xvNINKDY28OzfCfui7yyfHd1WC4=",
"dev": true,
"dependencies": {
"findup-sync": "^2.0.0",
"micromatch": "^3.0.4",
"resolve": "^1.4.0",
"stack-trace": "0.0.10"
},
"engines": {
"node": ">= 0.10.0"
}
},
"node_modules/matchdep/node_modules/findup-sync": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/findup-sync/-/findup-sync-2.0.0.tgz",
"integrity": "sha1-kyaxSIwi0aYIhlCoaQGy2akKLLw=",
"dev": true,
"dependencies": {
"detect-file": "^1.0.0",
"is-glob": "^3.1.0",
"micromatch": "^3.0.4",
"resolve-dir": "^1.0.1"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/mathml-tag-names": {
"version": "2.1.3",
"resolved": "https://registry.npmjs.org/mathml-tag-names/-/mathml-tag-names-2.1.3.tgz",
"integrity": "sha512-APMBEanjybaPzUrfqU0IMU5I0AswKMH7k8OTLs0vvV4KZpExkTkY87nR/zpbuTPj+gARop7aGUbl11pnDfW6xg==",
"dev": true,
"funding": {
"type": "github",
"url": "https://github.com/sponsors/wooorm"
}
},
"node_modules/mdurl": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/mdurl/-/mdurl-1.0.1.tgz",
"integrity": "sha1-/oWy7HWlkDfyrf7BAP1sYBdhFS4=",
"dev": true
},
"node_modules/memory-fs": {
"version": "0.5.0",
"resolved": "https://registry.npmjs.org/memory-fs/-/memory-fs-0.5.0.tgz",
"integrity": "sha512-jA0rdU5KoQMC0e6ppoNRtpp6vjFq6+NY7r8hywnC7V+1Xj/MtHwGIbB1QaK/dunyjWteJzmkpd7ooeWg10T7GA==",
"dev": true,
"dependencies": {
"errno": "^0.1.3",
"readable-stream": "^2.0.1"
},
"engines": {
"node": ">=4.3.0 <5.0.0 || >=5.10"
}
},
"node_modules/meow": {
"version": "9.0.0",
"resolved": "https://registry.npmjs.org/meow/-/meow-9.0.0.tgz",
"integrity": "sha512-+obSblOQmRhcyBt62furQqRAQpNyWXo8BuQ5bN7dG8wmwQ+vwHKp/rCFD4CrTP8CsDQD1sjoZ94K417XEUk8IQ==",
"dev": true,
"dependencies": {
"@types/minimist": "^1.2.0",
"camelcase-keys": "^6.2.2",
"decamelize": "^1.2.0",
"decamelize-keys": "^1.1.0",
"hard-rejection": "^2.1.0",
"minimist-options": "4.1.0",
"normalize-package-data": "^3.0.0",
"read-pkg-up": "^7.0.1",
"redent": "^3.0.0",
"trim-newlines": "^3.0.0",
"type-fest": "^0.18.0",
"yargs-parser": "^20.2.3"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/meow/node_modules/hosted-git-info": {
"version": "4.0.2",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-4.0.2.tgz",
"integrity": "sha512-c9OGXbZ3guC/xOlCg1Ci/VgWlwsqDv1yMQL1CWqXDL0hDjXuNcq0zuR4xqPSuasI3kqFDhqSyTjREz5gzq0fXg==",
"dev": true,
"dependencies": {
"lru-cache": "^6.0.0"
},
"engines": {
"node": ">=10"
}
},
"node_modules/meow/node_modules/is-core-module": {
"version": "2.8.0",
"resolved": "https://registry.npmjs.org/is-core-module/-/is-core-module-2.8.0.tgz",
"integrity": "sha512-vd15qHsaqrRL7dtH6QNuy0ndJmRDrS9HAM1CAiSifNUFv4x1a0CCVsj18hJ1mShxIG6T2i1sO78MkP56r0nYRw==",
"dev": true,
"dependencies": {
"has": "^1.0.3"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/meow/node_modules/normalize-package-data": {
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-3.0.3.tgz",
"integrity": "sha512-p2W1sgqij3zMMyRC067Dg16bfzVH+w7hyegmpIvZ4JNjqtGOVAIvLmjBx3yP7YTe9vKJgkoNOPjwQGogDoMXFA==",
"dev": true,
"dependencies": {
"hosted-git-info": "^4.0.1",
"is-core-module": "^2.5.0",
"semver": "^7.3.4",
"validate-npm-package-license": "^3.0.1"
},
"engines": {
"node": ">=10"
}
},
"node_modules/meow/node_modules/semver": {
"version": "7.3.5",
"resolved": "https://registry.npmjs.org/semver/-/semver-7.3.5.tgz",
"integrity": "sha512-PoeGJYh8HK4BTO/a9Tf6ZG3veo/A7ZVsYrSA6J8ny9nb3B1VrpkuN+z9OE5wfE5p6H4LchYZsegiQgbJD94ZFQ==",
"dev": true,
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
"engines": {
"node": ">=10"
}
},
"node_modules/meow/node_modules/type-fest": {
"version": "0.18.1",
"resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.18.1.tgz",
"integrity": "sha512-OIAYXk8+ISY+qTOwkHtKqzAuxchoMiD9Udx+FSGQDuiRR+PJKJHc2NJAXlbhkGwTt/4/nKZxELY1w3ReWOL8mw==",
"dev": true,
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/merge-stream": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/merge-stream/-/merge-stream-2.0.0.tgz",
"integrity": "sha512-abv/qOcuPfk3URPfDzmZU1LKmuw8kT+0nIHvKrKgFrwifol/doWcdA4ZqsWQ8ENrFKkd67Mfpo/LovbIUsbt3w==",
"dev": true
},
"node_modules/merge2": {
"version": "1.4.1",
"resolved": "https://registry.npmjs.org/merge2/-/merge2-1.4.1.tgz",
"integrity": "sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==",
"dev": true,
"engines": {
"node": ">= 8"
}
},
"node_modules/micromatch": {
"version": "3.1.10",
"resolved": "https://registry.npmjs.org/micromatch/-/micromatch-3.1.10.tgz",
"integrity": "sha512-MWikgl9n9M3w+bpsY3He8L+w9eF9338xRl8IAO5viDizwSzziFEyUzo2xrrloB64ADbTf8uA8vRqqttDTOmccg==",
"dev": true,
"dependencies": {
"arr-diff": "^4.0.0",
"array-unique": "^0.3.2",
"braces": "^2.3.1",
"define-property": "^2.0.2",
"extend-shallow": "^3.0.2",
"extglob": "^2.0.4",
"fragment-cache": "^0.2.1",
"kind-of": "^6.0.2",
"nanomatch": "^1.2.9",
"object.pick": "^1.3.0",
"regex-not": "^1.0.0",
"snapdragon": "^0.8.1",
"to-regex": "^3.0.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/mime": {
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/mime/-/mime-2.3.1.tgz",
"integrity": "sha512-OEUllcVoydBHGN1z84yfQDimn58pZNNNXgZlHXSboxMlFvgI6MXSWpWKpFRra7H1HxpVhHTkrghfRW49k6yjeg==",
"dev": true,
"bin": {
"mime": "cli.js"
},
"engines": {
"node": ">=4.0.0"
}
},
"node_modules/mime-db": {
"version": "1.51.0",
"resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.51.0.tgz",
"integrity": "sha512-5y8A56jg7XVQx2mbv1lu49NR4dokRnhZYTtL+KGfaa27uq4pSTXkwQkFJl4pkRMyNFz/EtYDSkiiEHx3F7UN6g==",
"dev": true,
"engines": {
"node": ">= 0.6"
}
},
"node_modules/mime-types": {
"version": "2.1.34",
"resolved": "https://registry.npmjs.org/mime-types/-/mime-types-2.1.34.tgz",
"integrity": "sha512-6cP692WwGIs9XXdOO4++N+7qjqv0rqxxVvJ3VHPh/Sc9mVZcQP+ZGhkKiTvWMQRr2tbHkJP/Yn7Y0npb3ZBs4A==",
"dev": true,
"dependencies": {
"mime-db": "1.51.0"
},
"engines": {
"node": ">= 0.6"
}
},
"node_modules/mimic-response": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/mimic-response/-/mimic-response-2.1.0.tgz",
"integrity": "sha512-wXqjST+SLt7R009ySCglWBCFpjUygmCIfD790/kVbiGmUgfYGuB14PiTd5DwVxSV4NcYHjzMkoj5LjQZwTQLEA==",
"dev": true,
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/min-indent": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/min-indent/-/min-indent-1.0.1.tgz",
"integrity": "sha512-I9jwMn07Sy/IwOj3zVkVik2JTvgpaykDZEigL6Rx6N9LbMywwUSMtxET+7lVoDLLd3O3IXwJwvuuns8UB/HeAg==",
"dev": true,
"engines": {
"node": ">=4"
}
},
"node_modules/minimatch": {
"version": "3.0.4",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz",
"integrity": "sha512-yJHVQEhyqPLUTgt9B83PXu6W3rx4MvvHvSUvToogpwoGDOUQ+yDrR0HRot+yOCdCO7u4hX3pWft6kWBBcqh0UA==",
"dev": true,
"dependencies": {
"brace-expansion": "^1.1.7"
},
"engines": {
"node": "*"
}
},
"node_modules/minimist": {
"version": "1.2.5",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz",
"integrity": "sha512-FM9nNUYrRBAELZQT3xeZQ7fmMOBg6nWNmJKTcgsJeaLstP/UODVpGsr5OhXhhXg6f+qtJ8uiZ+PUxkDWcgIXLw==",
"dev": true
},
"node_modules/minimist-options": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/minimist-options/-/minimist-options-4.1.0.tgz",
"integrity": "sha512-Q4r8ghd80yhO/0j1O3B2BjweX3fiHg9cdOwjJd2J76Q135c+NDxGCqdYKQ1SKBuFfgWbAUzBfvYjPUEeNgqN1A==",
"dev": true,
"dependencies": {
"arrify": "^1.0.1",
"is-plain-obj": "^1.1.0",
"kind-of": "^6.0.3"
},
"engines": {
"node": ">= 6"
}
},
"node_modules/minipass": {
"version": "3.1.3",
"resolved": "https://registry.npmjs.org/minipass/-/minipass-3.1.3.tgz",
"integrity": "sha512-Mgd2GdMVzY+x3IJ+oHnVM+KG3lA5c8tnabyJKmHSaG2kAGpudxuOf8ToDkhumF7UzME7DecbQE9uOZhNm7PuJg==",
"dev": true,
"dependencies": {
"yallist": "^4.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/minipass/node_modules/yallist": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/yallist/-/yallist-4.0.0.tgz",
"integrity": "sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A==",
"dev": true
},
"node_modules/minizlib": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/minizlib/-/minizlib-2.1.2.tgz",
"integrity": "sha512-bAxsR8BVfj60DWXHE3u30oHzfl4G7khkSuPW+qvpd7jFRHm7dLxOjUk1EHACJ/hxLY8phGJ0YhYHZo7jil7Qdg==",
"dev": true,
"dependencies": {
"minipass": "^3.0.0",
"yallist": "^4.0.0"
},
"engines": {
"node": ">= 8"
}
},
"node_modules/minizlib/node_modules/yallist": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/yallist/-/yallist-4.0.0.tgz",
"integrity": "sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A==",
"dev": true
},
"node_modules/mixin-deep": {
"version": "1.3.2",
"resolved": "https://registry.npmjs.org/mixin-deep/-/mixin-deep-1.3.2.tgz",
"integrity": "sha512-WRoDn//mXBiJ1H40rqa3vH0toePwSsGb45iInWlTySa+Uu4k3tYUSxa2v1KqAiLtvlrSzaExqS1gtk96A9zvEA==",
"dev": true,
"dependencies": {
"for-in": "^1.0.2",
"is-extendable": "^1.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/mixin-deep/node_modules/is-extendable": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/is-extendable/-/is-extendable-1.0.1.tgz",
"integrity": "sha512-arnXMxT1hhoKo9k1LZdmlNyJdDDfy2v0fXjFlmok4+i8ul/6WlbVge9bhM74OpNPQPMGUToDtz+KXa1PneJxOA==",
"dev": true,
"dependencies": {
"is-plain-object": "^2.0.4"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/mkdirp": {
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-1.0.4.tgz",
"integrity": "sha512-vVqVZQyf3WLx2Shd0qJ9xuvqgAyKPLAiqITEtqW0oIUjzo3PePDd6fW9iFz30ef7Ysp/oiWqbhszeGWW2T6Gzw==",
"dev": true,
"bin": {
"mkdirp": "bin/cmd.js"
},
"engines": {
"node": ">=10"
}
},
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"node_modules/mkdirp-classic": {
"version": "0.5.3",
"resolved": "https://registry.npmjs.org/mkdirp-classic/-/mkdirp-classic-0.5.3.tgz",
"integrity": "sha512-gKLcREMhtuZRwRAfqP3RFW+TK4JqApVBtOIftVgjuABpAtpxhPGaDcfvbhNvD0B8iD1oUr/txX35NjcaY6Ns/A==",
"dev": true
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/ms": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.0.0.tgz",
"integrity": "sha1-VgiurfwAvmwpAd9fmGF4jeDVl8g=",
"dev": true
},
"node_modules/multi-ini": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/multi-ini/-/multi-ini-2.1.2.tgz",
"integrity": "sha512-m7G4SF3bo/VM+iyeiIlCvBVD0GY2NQ/PHh+H6y3sEYaRJ3fFeKo5/6e0O15B17+KpqDZ9ia+JBo8d7ZUYiEucw==",
"dev": true,
"dependencies": {
"lodash": "^4.0.0"
}
},
"node_modules/mute-stdout": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/mute-stdout/-/mute-stdout-1.0.1.tgz",
"integrity": "sha512-kDcwXR4PS7caBpuRYYBUz9iVixUk3anO3f5OYFiIPwK/20vCzKCHyKoulbiDY1S53zD2bxUpxN/IJ+TnXjfvxg==",
"dev": true,
"engines": {
"node": ">= 0.10"
}
},
"node_modules/nan": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "2.15.0",
"resolved": "https://registry.npmjs.org/nan/-/nan-2.15.0.tgz",
"integrity": "sha512-8ZtvEnA2c5aYCZYd1cvgdnU6cqwixRoYg70xPLWUws5ORTa/lnw+u4amixRS/Ac5U5mQVgp9pnlSUnbNWFaWZQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/nanoid": {
Bump nanoid from 3.1.30 to 3.2.0 Bumps [nanoid](https://github.com/ai/nanoid) from 3.1.30 to 3.2.0. - [Release notes](https://github.com/ai/nanoid/releases) - [Changelog](https://github.com/ai/nanoid/blob/main/CHANGELOG.md) - [Commits](https://github.com/ai/nanoid/compare/3.1.30...3.2.0) --- updated-dependencies: - dependency-name: nanoid dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-28 06:38:28 +09:00
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.2.0.tgz",
"integrity": "sha512-fmsZYa9lpn69Ad5eDn7FMcnnSR+8R34W9qJEijxYhTbfOWzr22n1QxCMzXLK+ODyW2973V3Fux959iQoUxzUIA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"bin": {
"nanoid": "bin/nanoid.cjs"
},
"engines": {
"node": "^10 || ^12 || ^13.7 || ^14 || >=15.0.1"
}
},
"node_modules/nanomatch": {
"version": "1.2.9",
"resolved": "https://registry.npmjs.org/nanomatch/-/nanomatch-1.2.9.tgz",
"integrity": "sha512-n8R9bS8yQ6eSXaV6jHUpKzD8gLsin02w1HSFiegwrs9E098Ylhw5jdyKPaYqvHknHaSCKTPp7C8dGCQ0q9koXA==",
"dev": true,
"dependencies": {
"arr-diff": "^4.0.0",
"array-unique": "^0.3.2",
"define-property": "^2.0.2",
"extend-shallow": "^3.0.2",
"fragment-cache": "^0.2.1",
"is-odd": "^2.0.0",
"is-windows": "^1.0.2",
"kind-of": "^6.0.2",
"object.pick": "^1.3.0",
"regex-not": "^1.0.0",
"snapdragon": "^0.8.1",
"to-regex": "^3.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/natural-compare": {
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/natural-compare/-/natural-compare-1.4.0.tgz",
"integrity": "sha1-Sr6/7tdUHywnrPspvbvRXI1bpPc=",
"dev": true
},
"node_modules/ncp": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/ncp/-/ncp-2.0.0.tgz",
"integrity": "sha1-GVoh1sRuNh0vsSgbo4uR6d9727M=",
"dev": true,
"bin": {
"ncp": "bin/ncp"
}
},
"node_modules/needle": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/needle/-/needle-3.0.0.tgz",
"integrity": "sha512-eGr0qnfHxAjr+Eptl1zr2lgUQUPC1SZfTkg2kFi0kxr1ChJonHUVYobkug8siBKMlyUVVp56MSkp6CSeXH/jgw==",
"dev": true,
"dependencies": {
"debug": "^3.2.6",
"iconv-lite": "^0.4.4",
"sax": "^1.2.4"
},
"bin": {
"needle": "bin/needle"
},
"engines": {
"node": ">= 4.4.x"
}
},
"node_modules/needle/node_modules/debug": {
"version": "3.2.7",
"resolved": "https://registry.npmjs.org/debug/-/debug-3.2.7.tgz",
"integrity": "sha512-CFjzYYAi4ThfiQvizrFQevTTXHtnCqWfe7x1AhgEscTz6ZbLbfoLRLPugTQyBth6f8ZERVUSyWHFD/7Wu4t1XQ==",
"dev": true,
"dependencies": {
"ms": "^2.1.1"
}
},
"node_modules/needle/node_modules/ms": {
"version": "2.1.3",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.3.tgz",
"integrity": "sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==",
"dev": true
},
"node_modules/neo-async": {
"version": "2.6.2",
"resolved": "https://registry.npmjs.org/neo-async/-/neo-async-2.6.2.tgz",
"integrity": "sha512-Yd3UES5mWCSqR+qNT93S3UoYUkqAZ9lLg8a7g9rimsWmYGK8cVToA4/sF3RrshdyV3sAGMXVUmpMYOw+dLpOuw==",
"dev": true
},
"node_modules/next-tick": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/next-tick/-/next-tick-1.0.0.tgz",
"integrity": "sha1-yobR/ogoFpsBICCOPchCS524NCw=",
"dev": true
},
"node_modules/node-fetch": {
Update Puppeteer to version `13.1.2` Note in particular https://github.com/puppeteer/puppeteer/releases/tag/v13.1.0 which includes an update to Chromium 98, which adds support for `structuredClone` in the browser.
2022-01-18 20:23:22 +09:00
"version": "2.6.7",
"resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.7.tgz",
"integrity": "sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"dependencies": {
"whatwg-url": "^5.0.0"
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"engines": {
"node": "4.x || >=6.0.0"
Update Puppeteer to version `13.1.2` Note in particular https://github.com/puppeteer/puppeteer/releases/tag/v13.1.0 which includes an update to Chromium 98, which adds support for `structuredClone` in the browser.
2022-01-18 20:23:22 +09:00
},
"peerDependencies": {
"encoding": "^0.1.0"
},
"peerDependenciesMeta": {
"encoding": {
"optional": true
}
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/node-releases": {
Update npm packages
2021-12-26 19:09:29 +09:00
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/node-releases/-/node-releases-2.0.1.tgz",
"integrity": "sha512-CqyzN6z7Q6aMeF/ktcMVTzhAHCEpf8SOarwpzpf8pNBY2k5/oM34UHldUwp8VKI7uxct2HxSRdJjBaZeESzcxA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/nopt": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/nopt/-/nopt-5.0.0.tgz",
"integrity": "sha512-Tbj67rffqceeLpcRXrT7vKAN8CwfPeIBgM7E6iBkmKLV7bEMwpGgYLGv0jACUsECaa/vuxP0IjEont6umdMgtQ==",
"dev": true,
"dependencies": {
"abbrev": "1"
},
"bin": {
"nopt": "bin/nopt.js"
},
"engines": {
"node": ">=6"
}
},
"node_modules/normalize-package-data": {
"version": "2.4.0",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.4.0.tgz",
"integrity": "sha512-9jjUFbTPfEy3R/ad/2oNbKtW9Hgovl5O1FvFWKkKblNXoN/Oou6+9+KKohPK13Yc3/TyunyWhJp6gvRNR/PPAw==",
"dev": true,
"dependencies": {
"hosted-git-info": "^2.1.4",
"is-builtin-module": "^1.0.0",
"semver": "2 || 3 || 4 || 5",
"validate-npm-package-license": "^3.0.1"
}
},
"node_modules/normalize-path": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/normalize-path/-/normalize-path-2.1.1.tgz",
"integrity": "sha1-GrKLVW4Zg2Oowab35vogE3/mrtk=",
"dev": true,
"dependencies": {
"remove-trailing-separator": "^1.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/normalize-range": {
"version": "0.1.2",
"resolved": "https://registry.npmjs.org/normalize-range/-/normalize-range-0.1.2.tgz",
"integrity": "sha1-LRDAa9/TEuqXd2laTShDlFa3WUI=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/normalize-selector": {
"version": "0.2.0",
"resolved": "https://registry.npmjs.org/normalize-selector/-/normalize-selector-0.2.0.tgz",
"integrity": "sha1-0LFF62kRicY6eNIB3E/bEpPvDAM=",
"dev": true
},
"node_modules/now-and-later": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/now-and-later/-/now-and-later-2.0.0.tgz",
"integrity": "sha1-vGHLtFbXnLMiB85HygUTb/Ln1u4=",
"dev": true,
"dependencies": {
"once": "^1.3.2"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/npm": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "6.14.15",
"resolved": "https://registry.npmjs.org/npm/-/npm-6.14.15.tgz",
"integrity": "sha512-dkcQc4n+DiJAMYG2haNAMyJbmuvevjXz+WC9dCUzodw8EovwTIc6CATSsTEplCY6c0jG4OshxFGFJsrnKJguWA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"bundleDependencies": [
"abbrev",
"ansicolors",
"ansistyles",
"aproba",
"archy",
"bin-links",
"bluebird",
"byte-size",
"cacache",
"call-limit",
"chownr",
"ci-info",
"cli-columns",
"cli-table3",
"cmd-shim",
"columnify",
"config-chain",
"debuglog",
"detect-indent",
"detect-newline",
"dezalgo",
"editor",
"figgy-pudding",
"find-npm-prefix",
"fs-vacuum",
"fs-write-stream-atomic",
"gentle-fs",
"glob",
"graceful-fs",
"has-unicode",
"hosted-git-info",
"iferr",
"imurmurhash",
"infer-owner",
"inflight",
"inherits",
"ini",
"init-package-json",
"is-cidr",
"json-parse-better-errors",
"JSONStream",
"lazy-property",
"libcipm",
"libnpm",
"libnpmaccess",
"libnpmhook",
"libnpmorg",
"libnpmsearch",
"libnpmteam",
"libnpx",
"lock-verify",
"lockfile",
"lodash._baseindexof",
"lodash._baseuniq",
"lodash._bindcallback",
"lodash._cacheindexof",
"lodash._createcache",
"lodash._getnative",
"lodash.clonedeep",
"lodash.restparam",
"lodash.union",
"lodash.uniq",
"lodash.without",
"lru-cache",
"meant",
"mississippi",
"mkdirp",
"move-concurrently",
"node-gyp",
"nopt",
"normalize-package-data",
"npm-audit-report",
"npm-cache-filename",
"npm-install-checks",
"npm-lifecycle",
"npm-package-arg",
"npm-packlist",
"npm-pick-manifest",
"npm-profile",
"npm-registry-fetch",
"npm-user-validate",
"npmlog",
"once",
"opener",
"osenv",
"pacote",
"path-is-inside",
"promise-inflight",
"qrcode-terminal",
"query-string",
"qw",
"read-cmd-shim",
"read-installed",
"read-package-json",
"read-package-tree",
"read",
"readable-stream",
"readdir-scoped-modules",
"request",
"retry",
"rimraf",
"safe-buffer",
"semver",
"sha",
"slide",
"sorted-object",
"sorted-union-stream",
"ssri",
"stringify-package",
"tar",
"text-table",
"tiny-relative-date",
"uid-number",
"umask",
"unique-filename",
"unpipe",
"update-notifier",
"uuid",
"validate-npm-package-license",
"validate-npm-package-name",
"which",
"worker-farm",
"write-file-atomic"
],
"dev": true,
"dependencies": {
"abbrev": "~1.1.1",
"ansicolors": "~0.3.2",
"ansistyles": "~0.1.3",
"aproba": "^2.0.0",
"archy": "~1.0.0",
"bin-links": "^1.1.8",
"bluebird": "^3.5.5",
"byte-size": "^5.0.1",
"cacache": "^12.0.3",
"call-limit": "^1.1.1",
"chownr": "^1.1.4",
"ci-info": "^2.0.0",
"cli-columns": "^3.1.2",
"cli-table3": "^0.5.1",
"cmd-shim": "^3.0.3",
"columnify": "~1.5.4",
"config-chain": "^1.1.12",
"debuglog": "*",
"detect-indent": "~5.0.0",
"detect-newline": "^2.1.0",
"dezalgo": "~1.0.3",
"editor": "~1.0.0",
"figgy-pudding": "^3.5.1",
"find-npm-prefix": "^1.0.2",
"fs-vacuum": "~1.2.10",
"fs-write-stream-atomic": "~1.0.10",
"gentle-fs": "^2.3.1",
"glob": "^7.1.6",
"graceful-fs": "^4.2.4",
"has-unicode": "~2.0.1",
"hosted-git-info": "^2.8.9",
"iferr": "^1.0.2",
"imurmurhash": "*",
"infer-owner": "^1.0.4",
"inflight": "~1.0.6",
"inherits": "^2.0.4",
"ini": "^1.3.8",
"init-package-json": "^1.10.3",
"is-cidr": "^3.0.0",
"json-parse-better-errors": "^1.0.2",
"JSONStream": "^1.3.5",
"lazy-property": "~1.0.0",
"libcipm": "^4.0.8",
"libnpm": "^3.0.1",
"libnpmaccess": "^3.0.2",
"libnpmhook": "^5.0.3",
"libnpmorg": "^1.0.1",
"libnpmsearch": "^2.0.2",
"libnpmteam": "^1.0.2",
"libnpx": "^10.2.4",
"lock-verify": "^2.1.0",
"lockfile": "^1.0.4",
"lodash._baseindexof": "*",
"lodash._baseuniq": "~4.6.0",
"lodash._bindcallback": "*",
"lodash._cacheindexof": "*",
"lodash._createcache": "*",
"lodash._getnative": "*",
"lodash.clonedeep": "~4.5.0",
"lodash.restparam": "*",
"lodash.union": "~4.6.0",
"lodash.uniq": "~4.5.0",
"lodash.without": "~4.4.0",
"lru-cache": "^5.1.1",
"meant": "^1.0.2",
"mississippi": "^3.0.0",
"mkdirp": "^0.5.5",
"move-concurrently": "^1.0.1",
"node-gyp": "^5.1.0",
"nopt": "^4.0.3",
"normalize-package-data": "^2.5.0",
"npm-audit-report": "^1.3.3",
"npm-cache-filename": "~1.0.2",
"npm-install-checks": "^3.0.2",
"npm-lifecycle": "^3.1.5",
"npm-package-arg": "^6.1.1",
"npm-packlist": "^1.4.8",
"npm-pick-manifest": "^3.0.2",
"npm-profile": "^4.0.4",
"npm-registry-fetch": "^4.0.7",
"npm-user-validate": "^1.0.1",
"npmlog": "~4.1.2",
"once": "~1.4.0",
"opener": "^1.5.2",
"osenv": "^0.1.5",
"pacote": "^9.5.12",
"path-is-inside": "~1.0.2",
"promise-inflight": "~1.0.1",
"qrcode-terminal": "^0.12.0",
"query-string": "^6.8.2",
"qw": "~1.0.1",
"read": "~1.0.7",
"read-cmd-shim": "^1.0.5",
"read-installed": "~4.0.3",
"read-package-json": "^2.1.1",
"read-package-tree": "^5.3.1",
"readable-stream": "^3.6.0",
"readdir-scoped-modules": "^1.1.0",
"request": "^2.88.0",
"retry": "^0.12.0",
"rimraf": "^2.7.1",
"safe-buffer": "^5.1.2",
"semver": "^5.7.1",
"sha": "^3.0.0",
"slide": "~1.1.6",
"sorted-object": "~2.0.1",
"sorted-union-stream": "~2.1.3",
"ssri": "^6.0.2",
"stringify-package": "^1.0.1",
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"tar": "^4.4.19",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"text-table": "~0.2.0",
"tiny-relative-date": "^1.3.0",
"uid-number": "0.0.6",
"umask": "~1.1.0",
"unique-filename": "^1.1.1",
"unpipe": "~1.0.0",
"update-notifier": "^2.5.0",
"uuid": "^3.3.3",
"validate-npm-package-license": "^3.0.4",
"validate-npm-package-name": "~3.0.0",
"which": "^1.3.1",
"worker-farm": "^1.7.0",
"write-file-atomic": "^2.4.3"
},
"bin": {
"npm": "bin/npm-cli.js",
"npx": "bin/npx-cli.js"
},
"engines": {
"node": "6 >=6.2.0 || 8 || >=9.3.0"
}
},
"node_modules/npm/node_modules/abbrev": {
"version": "1.1.1",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/agent-base": {
"version": "4.3.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"es6-promisify": "^5.0.0"
},
"engines": {
"node": ">= 4.0.0"
}
},
"node_modules/npm/node_modules/agentkeepalive": {
"version": "3.5.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"humanize-ms": "^1.2.1"
},
"engines": {
"node": ">= 4.0.0"
}
},
"node_modules/npm/node_modules/ansi-align": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"string-width": "^2.0.0"
}
},
"node_modules/npm/node_modules/ansi-regex": {
"version": "2.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/ansi-styles": {
"version": "3.2.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"color-convert": "^1.9.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/ansicolors": {
"version": "0.3.2",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/ansistyles": {
"version": "0.1.3",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/aproba": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/archy": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/are-we-there-yet": {
"version": "1.1.4",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"delegates": "^1.0.0",
"readable-stream": "^2.0.6"
}
},
"node_modules/npm/node_modules/are-we-there-yet/node_modules/readable-stream": {
"version": "2.3.6",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"node_modules/npm/node_modules/are-we-there-yet/node_modules/string_decoder": {
"version": "1.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"safe-buffer": "~5.1.0"
}
},
"node_modules/npm/node_modules/asap": {
"version": "2.0.6",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/asn1": {
"version": "0.2.4",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"safer-buffer": "~2.1.0"
}
},
"node_modules/npm/node_modules/assert-plus": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.8"
}
},
"node_modules/npm/node_modules/asynckit": {
"version": "0.4.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/aws-sign2": {
"version": "0.7.0",
"dev": true,
"inBundle": true,
"license": "Apache-2.0",
"engines": {
"node": "*"
}
},
"node_modules/npm/node_modules/aws4": {
"version": "1.8.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/balanced-match": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/bcrypt-pbkdf": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "BSD-3-Clause",
"optional": true,
"dependencies": {
"tweetnacl": "^0.14.3"
}
},
"node_modules/npm/node_modules/bin-links": {
"version": "1.1.8",
"dev": true,
"inBundle": true,
"license": "Artistic-2.0",
"dependencies": {
"bluebird": "^3.5.3",
"cmd-shim": "^3.0.0",
"gentle-fs": "^2.3.0",
"graceful-fs": "^4.1.15",
"npm-normalize-package-bin": "^1.0.0",
"write-file-atomic": "^2.3.0"
}
},
"node_modules/npm/node_modules/bluebird": {
"version": "3.5.5",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/boxen": {
"version": "1.3.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"ansi-align": "^2.0.0",
"camelcase": "^4.0.0",
"chalk": "^2.0.1",
"cli-boxes": "^1.0.0",
"string-width": "^2.0.0",
"term-size": "^1.2.0",
"widest-line": "^2.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/brace-expansion": {
"version": "1.1.11",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
}
},
"node_modules/npm/node_modules/buffer-from": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/builtins": {
"version": "1.0.3",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/byline": {
"version": "5.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/byte-size": {
"version": "5.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/npm/node_modules/cacache": {
"version": "12.0.3",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"bluebird": "^3.5.5",
"chownr": "^1.1.1",
"figgy-pudding": "^3.5.1",
"glob": "^7.1.4",
"graceful-fs": "^4.1.15",
"infer-owner": "^1.0.3",
"lru-cache": "^5.1.1",
"mississippi": "^3.0.0",
"mkdirp": "^0.5.1",
"move-concurrently": "^1.0.1",
"promise-inflight": "^1.0.1",
"rimraf": "^2.6.3",
"ssri": "^6.0.1",
"unique-filename": "^1.1.1",
"y18n": "^4.0.0"
}
},
"node_modules/npm/node_modules/call-limit": {
"version": "1.1.1",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/camelcase": {
"version": "4.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/capture-stack-trace": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/caseless": {
"version": "0.12.0",
"dev": true,
"inBundle": true,
"license": "Apache-2.0"
},
"node_modules/npm/node_modules/chalk": {
"version": "2.4.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"ansi-styles": "^3.2.1",
"escape-string-regexp": "^1.0.5",
"supports-color": "^5.3.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/chownr": {
"version": "1.1.4",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/ci-info": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/cidr-regex": {
"version": "2.0.10",
"dev": true,
"inBundle": true,
"license": "BSD-2-Clause",
"dependencies": {
"ip-regex": "^2.1.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/cli-boxes": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/cli-columns": {
"version": "3.1.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"string-width": "^2.0.0",
"strip-ansi": "^3.0.1"
},
"engines": {
"node": ">= 4"
}
},
"node_modules/npm/node_modules/cli-table3": {
"version": "0.5.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"object-assign": "^4.1.0",
"string-width": "^2.1.1"
},
"engines": {
"node": ">=6"
},
"optionalDependencies": {
"colors": "^1.1.2"
}
},
"node_modules/npm/node_modules/cliui": {
"version": "5.0.0",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"string-width": "^3.1.0",
"strip-ansi": "^5.2.0",
"wrap-ansi": "^5.1.0"
}
},
"node_modules/npm/node_modules/cliui/node_modules/ansi-regex": {
"version": "4.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/cliui/node_modules/is-fullwidth-code-point": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/cliui/node_modules/string-width": {
"version": "3.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"emoji-regex": "^7.0.1",
"is-fullwidth-code-point": "^2.0.0",
"strip-ansi": "^5.1.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/cliui/node_modules/strip-ansi": {
"version": "5.2.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"ansi-regex": "^4.1.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/clone": {
"version": "1.0.4",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.8"
}
},
"node_modules/npm/node_modules/cmd-shim": {
"version": "3.0.3",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"graceful-fs": "^4.1.2",
"mkdirp": "~0.5.0"
}
},
"node_modules/npm/node_modules/code-point-at": {
"version": "1.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/color-convert": {
"version": "1.9.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"color-name": "^1.1.1"
}
},
"node_modules/npm/node_modules/color-name": {
"version": "1.1.3",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/colors": {
"version": "1.3.3",
"dev": true,
"inBundle": true,
"license": "MIT",
"optional": true,
"engines": {
"node": ">=0.1.90"
}
},
"node_modules/npm/node_modules/columnify": {
"version": "1.5.4",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"strip-ansi": "^3.0.0",
"wcwidth": "^1.0.0"
}
},
"node_modules/npm/node_modules/combined-stream": {
"version": "1.0.6",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"delayed-stream": "~1.0.0"
},
"engines": {
"node": ">= 0.8"
}
},
"node_modules/npm/node_modules/concat-map": {
"version": "0.0.1",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/concat-stream": {
"version": "1.6.2",
"dev": true,
"engines": [
"node >= 0.8"
],
"inBundle": true,
"license": "MIT",
"dependencies": {
"buffer-from": "^1.0.0",
"inherits": "^2.0.3",
"readable-stream": "^2.2.2",
"typedarray": "^0.0.6"
}
},
"node_modules/npm/node_modules/concat-stream/node_modules/readable-stream": {
"version": "2.3.6",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"node_modules/npm/node_modules/concat-stream/node_modules/string_decoder": {
"version": "1.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"safe-buffer": "~5.1.0"
}
},
"node_modules/npm/node_modules/config-chain": {
"version": "1.1.12",
"dev": true,
"inBundle": true,
"dependencies": {
"ini": "^1.3.4",
"proto-list": "~1.2.1"
}
},
"node_modules/npm/node_modules/configstore": {
"version": "3.1.5",
"dev": true,
"inBundle": true,
"license": "BSD-2-Clause",
"dependencies": {
"dot-prop": "^4.2.1",
"graceful-fs": "^4.1.2",
"make-dir": "^1.0.0",
"unique-string": "^1.0.0",
"write-file-atomic": "^2.0.0",
"xdg-basedir": "^3.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/console-control-strings": {
"version": "1.1.0",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/copy-concurrently": {
"version": "1.0.5",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"aproba": "^1.1.1",
"fs-write-stream-atomic": "^1.0.8",
"iferr": "^0.1.5",
"mkdirp": "^0.5.1",
"rimraf": "^2.5.4",
"run-queue": "^1.0.0"
}
},
"node_modules/npm/node_modules/copy-concurrently/node_modules/aproba": {
"version": "1.2.0",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/copy-concurrently/node_modules/iferr": {
"version": "0.1.5",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/core-util-is": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/create-error-class": {
"version": "3.0.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"capture-stack-trace": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/cross-spawn": {
"version": "5.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"lru-cache": "^4.0.1",
"shebang-command": "^1.2.0",
"which": "^1.2.9"
}
},
"node_modules/npm/node_modules/cross-spawn/node_modules/lru-cache": {
"version": "4.1.5",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"pseudomap": "^1.0.2",
"yallist": "^2.1.2"
}
},
"node_modules/npm/node_modules/cross-spawn/node_modules/yallist": {
"version": "2.1.2",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/crypto-random-string": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/cyclist": {
"version": "0.2.2",
"dev": true,
"inBundle": true
},
"node_modules/npm/node_modules/dashdash": {
"version": "1.14.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"assert-plus": "^1.0.0"
},
"engines": {
"node": ">=0.10"
}
},
"node_modules/npm/node_modules/debug": {
"version": "3.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"ms": "2.0.0"
}
},
"node_modules/npm/node_modules/debug/node_modules/ms": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/debuglog": {
"version": "1.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": "*"
}
},
"node_modules/npm/node_modules/decamelize": {
"version": "1.2.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/decode-uri-component": {
"version": "0.2.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10"
}
},
"node_modules/npm/node_modules/deep-extend": {
"version": "0.6.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4.0.0"
}
},
"node_modules/npm/node_modules/defaults": {
"version": "1.0.3",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"clone": "^1.0.2"
}
},
"node_modules/npm/node_modules/define-properties": {
"version": "1.1.3",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"object-keys": "^1.0.12"
},
"engines": {
"node": ">= 0.4"
}
},
"node_modules/npm/node_modules/delayed-stream": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.4.0"
}
},
"node_modules/npm/node_modules/delegates": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/detect-indent": {
"version": "5.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/detect-newline": {
"version": "2.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/dezalgo": {
"version": "1.0.3",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"asap": "^2.0.0",
"wrappy": "1"
}
},
"node_modules/npm/node_modules/dot-prop": {
"version": "4.2.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"is-obj": "^1.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/dotenv": {
"version": "5.0.1",
"dev": true,
"inBundle": true,
"license": "BSD-2-Clause",
"engines": {
"node": ">=4.6.0"
}
},
"node_modules/npm/node_modules/duplexer3": {
"version": "0.1.4",
"dev": true,
"inBundle": true,
"license": "BSD-3-Clause"
},
"node_modules/npm/node_modules/duplexify": {
"version": "3.6.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"end-of-stream": "^1.0.0",
"inherits": "^2.0.1",
"readable-stream": "^2.0.0",
"stream-shift": "^1.0.0"
}
},
"node_modules/npm/node_modules/duplexify/node_modules/readable-stream": {
"version": "2.3.6",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"node_modules/npm/node_modules/duplexify/node_modules/string_decoder": {
"version": "1.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"safe-buffer": "~5.1.0"
}
},
"node_modules/npm/node_modules/ecc-jsbn": {
"version": "0.1.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"optional": true,
"dependencies": {
"jsbn": "~0.1.0",
"safer-buffer": "^2.1.0"
}
},
"node_modules/npm/node_modules/editor": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/emoji-regex": {
"version": "7.0.3",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/encoding": {
"version": "0.1.12",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"iconv-lite": "~0.4.13"
}
},
"node_modules/npm/node_modules/end-of-stream": {
"version": "1.4.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"once": "^1.4.0"
}
},
"node_modules/npm/node_modules/env-paths": {
"version": "2.2.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/err-code": {
"version": "1.1.2",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/errno": {
"version": "0.1.7",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"prr": "~1.0.1"
},
"bin": {
"errno": "cli.js"
}
},
"node_modules/npm/node_modules/es-abstract": {
"version": "1.12.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"es-to-primitive": "^1.1.1",
"function-bind": "^1.1.1",
"has": "^1.0.1",
"is-callable": "^1.1.3",
"is-regex": "^1.0.4"
},
"engines": {
"node": ">= 0.4"
}
},
"node_modules/npm/node_modules/es-to-primitive": {
"version": "1.2.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"is-callable": "^1.1.4",
"is-date-object": "^1.0.1",
"is-symbol": "^1.0.2"
},
"engines": {
"node": ">= 0.4"
}
},
"node_modules/npm/node_modules/es6-promise": {
"version": "4.2.8",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/es6-promisify": {
"version": "5.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"es6-promise": "^4.0.3"
}
},
"node_modules/npm/node_modules/escape-string-regexp": {
"version": "1.0.5",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.8.0"
}
},
"node_modules/npm/node_modules/execa": {
"version": "0.7.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"cross-spawn": "^5.0.1",
"get-stream": "^3.0.0",
"is-stream": "^1.1.0",
"npm-run-path": "^2.0.0",
"p-finally": "^1.0.0",
"signal-exit": "^3.0.0",
"strip-eof": "^1.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/execa/node_modules/get-stream": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/extend": {
"version": "3.0.2",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/extsprintf": {
"version": "1.3.0",
"dev": true,
"engines": [
"node >=0.6.0"
],
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/fast-json-stable-stringify": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/figgy-pudding": {
"version": "3.5.1",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/find-npm-prefix": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/flush-write-stream": {
"version": "1.0.3",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"inherits": "^2.0.1",
"readable-stream": "^2.0.4"
}
},
"node_modules/npm/node_modules/flush-write-stream/node_modules/readable-stream": {
"version": "2.3.6",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"node_modules/npm/node_modules/flush-write-stream/node_modules/string_decoder": {
"version": "1.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"safe-buffer": "~5.1.0"
}
},
"node_modules/npm/node_modules/forever-agent": {
"version": "0.6.1",
"dev": true,
"inBundle": true,
"license": "Apache-2.0",
"engines": {
"node": "*"
}
},
"node_modules/npm/node_modules/form-data": {
"version": "2.3.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"asynckit": "^0.4.0",
"combined-stream": "1.0.6",
"mime-types": "^2.1.12"
},
"engines": {
"node": ">= 0.12"
}
},
"node_modules/npm/node_modules/from2": {
"version": "2.3.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"inherits": "^2.0.1",
"readable-stream": "^2.0.0"
}
},
"node_modules/npm/node_modules/from2/node_modules/readable-stream": {
"version": "2.3.6",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"node_modules/npm/node_modules/from2/node_modules/string_decoder": {
"version": "1.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"safe-buffer": "~5.1.0"
}
},
"node_modules/npm/node_modules/fs-minipass": {
"version": "1.2.7",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"minipass": "^2.6.0"
}
},
"node_modules/npm/node_modules/fs-minipass/node_modules/minipass": {
"version": "2.9.0",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"safe-buffer": "^5.1.2",
"yallist": "^3.0.0"
}
},
"node_modules/npm/node_modules/fs-vacuum": {
"version": "1.2.10",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"graceful-fs": "^4.1.2",
"path-is-inside": "^1.0.1",
"rimraf": "^2.5.2"
}
},
"node_modules/npm/node_modules/fs-write-stream-atomic": {
"version": "1.0.10",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"graceful-fs": "^4.1.2",
"iferr": "^0.1.5",
"imurmurhash": "^0.1.4",
"readable-stream": "1 || 2"
}
},
"node_modules/npm/node_modules/fs-write-stream-atomic/node_modules/iferr": {
"version": "0.1.5",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/fs-write-stream-atomic/node_modules/readable-stream": {
"version": "2.3.6",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"node_modules/npm/node_modules/fs-write-stream-atomic/node_modules/string_decoder": {
"version": "1.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"safe-buffer": "~5.1.0"
}
},
"node_modules/npm/node_modules/fs.realpath": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/function-bind": {
"version": "1.1.1",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/gauge": {
"version": "2.7.4",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"aproba": "^1.0.3",
"console-control-strings": "^1.0.0",
"has-unicode": "^2.0.0",
"object-assign": "^4.1.0",
"signal-exit": "^3.0.0",
"string-width": "^1.0.1",
"strip-ansi": "^3.0.1",
"wide-align": "^1.1.0"
}
},
"node_modules/npm/node_modules/gauge/node_modules/aproba": {
"version": "1.2.0",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/gauge/node_modules/string-width": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"code-point-at": "^1.0.0",
"is-fullwidth-code-point": "^1.0.0",
"strip-ansi": "^3.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/genfun": {
"version": "5.0.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/gentle-fs": {
"version": "2.3.1",
"dev": true,
"inBundle": true,
"license": "Artistic-2.0",
"dependencies": {
"aproba": "^1.1.2",
"chownr": "^1.1.2",
"cmd-shim": "^3.0.3",
"fs-vacuum": "^1.2.10",
"graceful-fs": "^4.1.11",
"iferr": "^0.1.5",
"infer-owner": "^1.0.4",
"mkdirp": "^0.5.1",
"path-is-inside": "^1.0.2",
"read-cmd-shim": "^1.0.1",
"slide": "^1.1.6"
}
},
"node_modules/npm/node_modules/gentle-fs/node_modules/aproba": {
"version": "1.2.0",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/gentle-fs/node_modules/iferr": {
"version": "0.1.5",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/get-caller-file": {
"version": "2.0.5",
"dev": true,
"inBundle": true,
"license": "ISC",
"engines": {
"node": "6.* || 8.* || >= 10.*"
}
},
"node_modules/npm/node_modules/get-stream": {
"version": "4.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"pump": "^3.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/getpass": {
"version": "0.1.7",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"assert-plus": "^1.0.0"
}
},
"node_modules/npm/node_modules/glob": {
"version": "7.1.6",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
"minimatch": "^3.0.4",
"once": "^1.3.0",
"path-is-absolute": "^1.0.0"
},
"engines": {
"node": "*"
},
"funding": {
"url": "https://github.com/sponsors/isaacs"
}
},
"node_modules/npm/node_modules/global-dirs": {
"version": "0.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"ini": "^1.3.4"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/got": {
"version": "6.7.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"create-error-class": "^3.0.0",
"duplexer3": "^0.1.4",
"get-stream": "^3.0.0",
"is-redirect": "^1.0.0",
"is-retry-allowed": "^1.0.0",
"is-stream": "^1.0.0",
"lowercase-keys": "^1.0.0",
"safe-buffer": "^5.0.1",
"timed-out": "^4.0.0",
"unzip-response": "^2.0.1",
"url-parse-lax": "^1.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/got/node_modules/get-stream": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/graceful-fs": {
"version": "4.2.4",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/har-schema": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "ISC",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/har-validator": {
"version": "5.1.5",
"deprecated": "this library is no longer supported",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"ajv": "^6.12.3",
"har-schema": "^2.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/har-validator/node_modules/ajv": {
"version": "6.12.6",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"fast-deep-equal": "^3.1.1",
"fast-json-stable-stringify": "^2.0.0",
"json-schema-traverse": "^0.4.1",
"uri-js": "^4.2.2"
},
"funding": {
"type": "github",
"url": "https://github.com/sponsors/epoberezkin"
}
},
"node_modules/npm/node_modules/har-validator/node_modules/fast-deep-equal": {
"version": "3.1.3",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/har-validator/node_modules/json-schema-traverse": {
"version": "0.4.1",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/has": {
"version": "1.0.3",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"function-bind": "^1.1.1"
},
"engines": {
"node": ">= 0.4.0"
}
},
"node_modules/npm/node_modules/has-flag": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/has-symbols": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">= 0.4"
}
},
"node_modules/npm/node_modules/has-unicode": {
"version": "2.0.1",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/hosted-git-info": {
"version": "2.8.9",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/http-cache-semantics": {
"version": "3.8.1",
"dev": true,
"inBundle": true,
"license": "BSD-2-Clause"
},
"node_modules/npm/node_modules/http-proxy-agent": {
"version": "2.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"agent-base": "4",
"debug": "3.1.0"
},
"engines": {
"node": ">= 4.5.0"
}
},
"node_modules/npm/node_modules/http-signature": {
"version": "1.2.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"assert-plus": "^1.0.0",
"jsprim": "^1.2.2",
"sshpk": "^1.7.0"
},
"engines": {
"node": ">=0.8",
"npm": ">=1.3.7"
}
},
"node_modules/npm/node_modules/https-proxy-agent": {
"version": "2.2.4",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"agent-base": "^4.3.0",
"debug": "^3.1.0"
},
"engines": {
"node": ">= 4.5.0"
}
},
"node_modules/npm/node_modules/humanize-ms": {
"version": "1.2.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"ms": "^2.0.0"
}
},
"node_modules/npm/node_modules/iconv-lite": {
"version": "0.4.23",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"safer-buffer": ">= 2.1.2 < 3"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/iferr": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/npm/node_modules/ignore-walk": {
"version": "3.0.3",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"minimatch": "^3.0.4"
}
},
"node_modules/npm/node_modules/import-lazy": {
"version": "2.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/imurmurhash": {
"version": "0.1.4",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.8.19"
}
},
"node_modules/npm/node_modules/infer-owner": {
"version": "1.0.4",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/inflight": {
"version": "1.0.6",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"once": "^1.3.0",
"wrappy": "1"
}
},
"node_modules/npm/node_modules/inherits": {
"version": "2.0.4",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/ini": {
"version": "1.3.8",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/init-package-json": {
"version": "1.10.3",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"glob": "^7.1.1",
"npm-package-arg": "^4.0.0 || ^5.0.0 || ^6.0.0",
"promzard": "^0.3.0",
"read": "~1.0.1",
"read-package-json": "1 || 2",
"semver": "2.x || 3.x || 4 || 5",
"validate-npm-package-license": "^3.0.1",
"validate-npm-package-name": "^3.0.0"
}
},
"node_modules/npm/node_modules/ip": {
"version": "1.1.5",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/ip-regex": {
"version": "2.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/is-callable": {
"version": "1.1.4",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">= 0.4"
}
},
"node_modules/npm/node_modules/is-ci": {
"version": "1.2.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"ci-info": "^1.5.0"
},
"bin": {
"is-ci": "bin.js"
}
},
"node_modules/npm/node_modules/is-ci/node_modules/ci-info": {
"version": "1.6.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/is-cidr": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "BSD-2-Clause",
"dependencies": {
"cidr-regex": "^2.0.10"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/is-date-object": {
"version": "1.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">= 0.4"
}
},
"node_modules/npm/node_modules/is-fullwidth-code-point": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"number-is-nan": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/is-installed-globally": {
"version": "0.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"global-dirs": "^0.1.0",
"is-path-inside": "^1.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/is-npm": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/is-obj": {
"version": "1.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/is-path-inside": {
"version": "1.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"path-is-inside": "^1.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/is-redirect": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/is-regex": {
"version": "1.0.4",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"has": "^1.0.1"
},
"engines": {
"node": ">= 0.4"
}
},
"node_modules/npm/node_modules/is-retry-allowed": {
"version": "1.2.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/is-stream": {
"version": "1.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/is-symbol": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"has-symbols": "^1.0.0"
},
"engines": {
"node": ">= 0.4"
}
},
"node_modules/npm/node_modules/is-typedarray": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/isarray": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/isexe": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/isstream": {
"version": "0.1.2",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/jsbn": {
"version": "0.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"optional": true
},
"node_modules/npm/node_modules/json-parse-better-errors": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/json-schema": {
"version": "0.2.3",
"dev": true,
"inBundle": true
},
"node_modules/npm/node_modules/json-stringify-safe": {
"version": "5.0.1",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/jsonparse": {
"version": "1.3.1",
"dev": true,
"engines": [
"node >= 0.2.0"
],
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/JSONStream": {
"version": "1.3.5",
"dev": true,
"inBundle": true,
"license": "(MIT OR Apache-2.0)",
"dependencies": {
"jsonparse": "^1.2.0",
"through": ">=2.2.7 <3"
},
"bin": {
"JSONStream": "bin.js"
},
"engines": {
"node": "*"
}
},
"node_modules/npm/node_modules/jsprim": {
"version": "1.4.1",
"dev": true,
"engines": [
"node >=0.6.0"
],
"inBundle": true,
"license": "MIT",
"dependencies": {
"assert-plus": "1.0.0",
"extsprintf": "1.3.0",
"json-schema": "0.2.3",
"verror": "1.10.0"
}
},
"node_modules/npm/node_modules/latest-version": {
"version": "3.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"package-json": "^4.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/lazy-property": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/libcipm": {
"version": "4.0.8",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"bin-links": "^1.1.2",
"bluebird": "^3.5.1",
"figgy-pudding": "^3.5.1",
"find-npm-prefix": "^1.0.2",
"graceful-fs": "^4.1.11",
"ini": "^1.3.5",
"lock-verify": "^2.1.0",
"mkdirp": "^0.5.1",
"npm-lifecycle": "^3.0.0",
"npm-logical-tree": "^1.2.1",
"npm-package-arg": "^6.1.0",
"pacote": "^9.1.0",
"read-package-json": "^2.0.13",
"rimraf": "^2.6.2",
"worker-farm": "^1.6.0"
}
},
"node_modules/npm/node_modules/libnpm": {
"version": "3.0.1",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"bin-links": "^1.1.2",
"bluebird": "^3.5.3",
"find-npm-prefix": "^1.0.2",
"libnpmaccess": "^3.0.2",
"libnpmconfig": "^1.2.1",
"libnpmhook": "^5.0.3",
"libnpmorg": "^1.0.1",
"libnpmpublish": "^1.1.2",
"libnpmsearch": "^2.0.2",
"libnpmteam": "^1.0.2",
"lock-verify": "^2.0.2",
"npm-lifecycle": "^3.0.0",
"npm-logical-tree": "^1.2.1",
"npm-package-arg": "^6.1.0",
"npm-profile": "^4.0.2",
"npm-registry-fetch": "^4.0.0",
"npmlog": "^4.1.2",
"pacote": "^9.5.3",
"read-package-json": "^2.0.13",
"stringify-package": "^1.0.0"
}
},
"node_modules/npm/node_modules/libnpmaccess": {
"version": "3.0.2",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"aproba": "^2.0.0",
"get-stream": "^4.0.0",
"npm-package-arg": "^6.1.0",
"npm-registry-fetch": "^4.0.0"
}
},
"node_modules/npm/node_modules/libnpmconfig": {
"version": "1.2.1",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"figgy-pudding": "^3.5.1",
"find-up": "^3.0.0",
"ini": "^1.3.5"
}
},
"node_modules/npm/node_modules/libnpmconfig/node_modules/find-up": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"locate-path": "^3.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/libnpmconfig/node_modules/locate-path": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"p-locate": "^3.0.0",
"path-exists": "^3.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/libnpmconfig/node_modules/p-limit": {
"version": "2.2.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"p-try": "^2.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/libnpmconfig/node_modules/p-locate": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"p-limit": "^2.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/libnpmconfig/node_modules/p-try": {
"version": "2.2.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/libnpmhook": {
"version": "5.0.3",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"aproba": "^2.0.0",
"figgy-pudding": "^3.4.1",
"get-stream": "^4.0.0",
"npm-registry-fetch": "^4.0.0"
}
},
"node_modules/npm/node_modules/libnpmorg": {
"version": "1.0.1",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"aproba": "^2.0.0",
"figgy-pudding": "^3.4.1",
"get-stream": "^4.0.0",
"npm-registry-fetch": "^4.0.0"
}
},
"node_modules/npm/node_modules/libnpmpublish": {
"version": "1.1.2",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"aproba": "^2.0.0",
"figgy-pudding": "^3.5.1",
"get-stream": "^4.0.0",
"lodash.clonedeep": "^4.5.0",
"normalize-package-data": "^2.4.0",
"npm-package-arg": "^6.1.0",
"npm-registry-fetch": "^4.0.0",
"semver": "^5.5.1",
"ssri": "^6.0.1"
}
},
"node_modules/npm/node_modules/libnpmsearch": {
"version": "2.0.2",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"figgy-pudding": "^3.5.1",
"get-stream": "^4.0.0",
"npm-registry-fetch": "^4.0.0"
}
},
"node_modules/npm/node_modules/libnpmteam": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"aproba": "^2.0.0",
"figgy-pudding": "^3.4.1",
"get-stream": "^4.0.0",
"npm-registry-fetch": "^4.0.0"
}
},
"node_modules/npm/node_modules/libnpx": {
"version": "10.2.4",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"dotenv": "^5.0.1",
"npm-package-arg": "^6.0.0",
"rimraf": "^2.6.2",
"safe-buffer": "^5.1.0",
"update-notifier": "^2.3.0",
"which": "^1.3.0",
"y18n": "^4.0.0",
"yargs": "^14.2.3"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/lock-verify": {
"version": "2.1.0",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"npm-package-arg": "^6.1.0",
"semver": "^5.4.1"
}
},
"node_modules/npm/node_modules/lockfile": {
"version": "1.0.4",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"signal-exit": "^3.0.2"
}
},
"node_modules/npm/node_modules/lodash._baseindexof": {
"version": "3.1.0",
Add the `caniuse-lite` package Since the Autoprefixer plugin indirectly depends on this, it seems like a good idea to add this as a direct dependency in the PDF.js project to hopefully avoid having to manually update `caniuse-lite` in the future; see https://github.com/browserslist/browserslist#browsers-data-updating Also, slightly tweaks the Autoprefixer config for GENERIC-builds of the PDF.js library; note that this change doesn't affect the contents of the *built* `web/viewer.js` file.
2022-02-27 19:32:23 +09:00
"dev": true,
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/lodash._baseuniq": {
"version": "4.6.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"lodash._createset": "~4.0.0",
"lodash._root": "~3.0.0"
}
},
"node_modules/npm/node_modules/lodash._bindcallback": {
"version": "3.0.1",
Add the `caniuse-lite` package Since the Autoprefixer plugin indirectly depends on this, it seems like a good idea to add this as a direct dependency in the PDF.js project to hopefully avoid having to manually update `caniuse-lite` in the future; see https://github.com/browserslist/browserslist#browsers-data-updating Also, slightly tweaks the Autoprefixer config for GENERIC-builds of the PDF.js library; note that this change doesn't affect the contents of the *built* `web/viewer.js` file.
2022-02-27 19:32:23 +09:00
"dev": true,
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/lodash._cacheindexof": {
"version": "3.0.2",
Add the `caniuse-lite` package Since the Autoprefixer plugin indirectly depends on this, it seems like a good idea to add this as a direct dependency in the PDF.js project to hopefully avoid having to manually update `caniuse-lite` in the future; see https://github.com/browserslist/browserslist#browsers-data-updating Also, slightly tweaks the Autoprefixer config for GENERIC-builds of the PDF.js library; note that this change doesn't affect the contents of the *built* `web/viewer.js` file.
2022-02-27 19:32:23 +09:00
"dev": true,
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/lodash._createcache": {
"version": "3.1.2",
Add the `caniuse-lite` package Since the Autoprefixer plugin indirectly depends on this, it seems like a good idea to add this as a direct dependency in the PDF.js project to hopefully avoid having to manually update `caniuse-lite` in the future; see https://github.com/browserslist/browserslist#browsers-data-updating Also, slightly tweaks the Autoprefixer config for GENERIC-builds of the PDF.js library; note that this change doesn't affect the contents of the *built* `web/viewer.js` file.
2022-02-27 19:32:23 +09:00
"dev": true,
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"inBundle": true,
"license": "MIT",
"dependencies": {
"lodash._getnative": "^3.0.0"
}
},
"node_modules/npm/node_modules/lodash._createset": {
"version": "4.0.3",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/lodash._getnative": {
"version": "3.9.1",
Add the `caniuse-lite` package Since the Autoprefixer plugin indirectly depends on this, it seems like a good idea to add this as a direct dependency in the PDF.js project to hopefully avoid having to manually update `caniuse-lite` in the future; see https://github.com/browserslist/browserslist#browsers-data-updating Also, slightly tweaks the Autoprefixer config for GENERIC-builds of the PDF.js library; note that this change doesn't affect the contents of the *built* `web/viewer.js` file.
2022-02-27 19:32:23 +09:00
"dev": true,
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/lodash._root": {
"version": "3.0.1",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/lodash.clonedeep": {
"version": "4.5.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/lodash.restparam": {
"version": "3.6.1",
Add the `caniuse-lite` package Since the Autoprefixer plugin indirectly depends on this, it seems like a good idea to add this as a direct dependency in the PDF.js project to hopefully avoid having to manually update `caniuse-lite` in the future; see https://github.com/browserslist/browserslist#browsers-data-updating Also, slightly tweaks the Autoprefixer config for GENERIC-builds of the PDF.js library; note that this change doesn't affect the contents of the *built* `web/viewer.js` file.
2022-02-27 19:32:23 +09:00
"dev": true,
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/lodash.union": {
"version": "4.6.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/lodash.uniq": {
"version": "4.5.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/lodash.without": {
"version": "4.4.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/lowercase-keys": {
"version": "1.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/lru-cache": {
"version": "5.1.1",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"yallist": "^3.0.2"
}
},
"node_modules/npm/node_modules/make-dir": {
"version": "1.3.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"pify": "^3.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/make-fetch-happen": {
"version": "5.0.2",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"agentkeepalive": "^3.4.1",
"cacache": "^12.0.0",
"http-cache-semantics": "^3.8.1",
"http-proxy-agent": "^2.1.0",
"https-proxy-agent": "^2.2.3",
"lru-cache": "^5.1.1",
"mississippi": "^3.0.0",
"node-fetch-npm": "^2.0.2",
"promise-retry": "^1.1.1",
"socks-proxy-agent": "^4.0.0",
"ssri": "^6.0.0"
}
},
"node_modules/npm/node_modules/meant": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/mime-db": {
"version": "1.35.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">= 0.6"
}
},
"node_modules/npm/node_modules/mime-types": {
"version": "2.1.19",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"mime-db": "~1.35.0"
},
"engines": {
"node": ">= 0.6"
}
},
"node_modules/npm/node_modules/minimatch": {
"version": "3.0.4",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"brace-expansion": "^1.1.7"
},
"engines": {
"node": "*"
}
},
"node_modules/npm/node_modules/minimist": {
"version": "1.2.5",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/minizlib": {
"version": "1.3.3",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"minipass": "^2.9.0"
}
},
"node_modules/npm/node_modules/minizlib/node_modules/minipass": {
"version": "2.9.0",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"safe-buffer": "^5.1.2",
"yallist": "^3.0.0"
}
},
"node_modules/npm/node_modules/mississippi": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "BSD-2-Clause",
"dependencies": {
"concat-stream": "^1.5.0",
"duplexify": "^3.4.2",
"end-of-stream": "^1.1.0",
"flush-write-stream": "^1.0.0",
"from2": "^2.1.0",
"parallel-transform": "^1.1.0",
"pump": "^3.0.0",
"pumpify": "^1.3.3",
"stream-each": "^1.1.0",
"through2": "^2.0.0"
},
"engines": {
"node": ">=4.0.0"
}
},
"node_modules/npm/node_modules/mkdirp": {
"version": "0.5.5",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"minimist": "^1.2.5"
},
"bin": {
"mkdirp": "bin/cmd.js"
}
},
"node_modules/npm/node_modules/mkdirp/node_modules/minimist": {
"version": "1.2.5",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/move-concurrently": {
"version": "1.0.1",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"aproba": "^1.1.1",
"copy-concurrently": "^1.0.0",
"fs-write-stream-atomic": "^1.0.8",
"mkdirp": "^0.5.1",
"rimraf": "^2.5.4",
"run-queue": "^1.0.3"
}
},
"node_modules/npm/node_modules/move-concurrently/node_modules/aproba": {
"version": "1.2.0",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/ms": {
"version": "2.1.1",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/mute-stream": {
"version": "0.0.7",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/node-fetch-npm": {
"version": "2.0.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"encoding": "^0.1.11",
"json-parse-better-errors": "^1.0.0",
"safe-buffer": "^5.1.1"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/node-gyp": {
"version": "5.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"env-paths": "^2.2.0",
"glob": "^7.1.4",
"graceful-fs": "^4.2.2",
"mkdirp": "^0.5.1",
"nopt": "^4.0.1",
"npmlog": "^4.1.2",
"request": "^2.88.0",
"rimraf": "^2.6.3",
"semver": "^5.7.1",
"tar": "^4.4.12",
"which": "^1.3.1"
},
"bin": {
"node-gyp": "bin/node-gyp.js"
},
"engines": {
"node": ">= 6.0.0"
}
},
"node_modules/npm/node_modules/nopt": {
"version": "4.0.3",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"abbrev": "1",
"osenv": "^0.1.4"
},
"bin": {
"nopt": "bin/nopt.js"
}
},
"node_modules/npm/node_modules/normalize-package-data": {
"version": "2.5.0",
"dev": true,
"inBundle": true,
"license": "BSD-2-Clause",
"dependencies": {
"hosted-git-info": "^2.1.4",
"resolve": "^1.10.0",
"semver": "2 || 3 || 4 || 5",
"validate-npm-package-license": "^3.0.1"
}
},
"node_modules/npm/node_modules/normalize-package-data/node_modules/resolve": {
"version": "1.10.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"path-parse": "^1.0.6"
}
},
"node_modules/npm/node_modules/npm-audit-report": {
"version": "1.3.3",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"cli-table3": "^0.5.0",
"console-control-strings": "^1.1.0"
}
},
"node_modules/npm/node_modules/npm-bundled": {
"version": "1.1.1",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"npm-normalize-package-bin": "^1.0.1"
}
},
"node_modules/npm/node_modules/npm-cache-filename": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/npm-install-checks": {
"version": "3.0.2",
"dev": true,
"inBundle": true,
"license": "BSD-2-Clause",
"dependencies": {
"semver": "^2.3.0 || 3.x || 4 || 5"
}
},
"node_modules/npm/node_modules/npm-lifecycle": {
"version": "3.1.5",
"dev": true,
"inBundle": true,
"license": "Artistic-2.0",
"dependencies": {
"byline": "^5.0.0",
"graceful-fs": "^4.1.15",
"node-gyp": "^5.0.2",
"resolve-from": "^4.0.0",
"slide": "^1.1.6",
"uid-number": "0.0.6",
"umask": "^1.1.0",
"which": "^1.3.1"
}
},
"node_modules/npm/node_modules/npm-logical-tree": {
"version": "1.2.1",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/npm-normalize-package-bin": {
"version": "1.0.1",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/npm-package-arg": {
"version": "6.1.1",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"hosted-git-info": "^2.7.1",
"osenv": "^0.1.5",
"semver": "^5.6.0",
"validate-npm-package-name": "^3.0.0"
}
},
"node_modules/npm/node_modules/npm-packlist": {
"version": "1.4.8",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"ignore-walk": "^3.0.1",
"npm-bundled": "^1.0.1",
"npm-normalize-package-bin": "^1.0.1"
}
},
"node_modules/npm/node_modules/npm-pick-manifest": {
"version": "3.0.2",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"figgy-pudding": "^3.5.1",
"npm-package-arg": "^6.0.0",
"semver": "^5.4.1"
}
},
"node_modules/npm/node_modules/npm-profile": {
"version": "4.0.4",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"aproba": "^1.1.2 || 2",
"figgy-pudding": "^3.4.1",
"npm-registry-fetch": "^4.0.0"
}
},
"node_modules/npm/node_modules/npm-registry-fetch": {
"version": "4.0.7",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"bluebird": "^3.5.1",
"figgy-pudding": "^3.4.1",
"JSONStream": "^1.3.4",
"lru-cache": "^5.1.1",
"make-fetch-happen": "^5.0.0",
"npm-package-arg": "^6.1.0",
"safe-buffer": "^5.2.0"
}
},
"node_modules/npm/node_modules/npm-registry-fetch/node_modules/safe-buffer": {
"version": "5.2.1",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
],
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/npm-run-path": {
"version": "2.0.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"path-key": "^2.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/npm-user-validate": {
"version": "1.0.1",
"dev": true,
"inBundle": true,
"license": "BSD-2-Clause"
},
"node_modules/npm/node_modules/npmlog": {
"version": "4.1.2",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"are-we-there-yet": "~1.1.2",
"console-control-strings": "~1.1.0",
"gauge": "~2.7.3",
"set-blocking": "~2.0.0"
}
},
"node_modules/npm/node_modules/number-is-nan": {
"version": "1.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/oauth-sign": {
"version": "0.9.0",
"dev": true,
"inBundle": true,
"license": "Apache-2.0",
"engines": {
"node": "*"
}
},
"node_modules/npm/node_modules/object-assign": {
"version": "4.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/object-keys": {
"version": "1.0.12",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">= 0.4"
}
},
"node_modules/npm/node_modules/object.getownpropertydescriptors": {
"version": "2.0.3",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"define-properties": "^1.1.2",
"es-abstract": "^1.5.1"
},
"engines": {
"node": ">= 0.8"
}
},
"node_modules/npm/node_modules/once": {
"version": "1.4.0",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"wrappy": "1"
}
},
"node_modules/npm/node_modules/opener": {
"version": "1.5.2",
"dev": true,
"inBundle": true,
"license": "(WTFPL OR MIT)",
"bin": {
"opener": "bin/opener-bin.js"
}
},
"node_modules/npm/node_modules/os-homedir": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/os-tmpdir": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/osenv": {
"version": "0.1.5",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"os-homedir": "^1.0.0",
"os-tmpdir": "^1.0.0"
}
},
"node_modules/npm/node_modules/p-finally": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/package-json": {
"version": "4.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"got": "^6.7.1",
"registry-auth-token": "^3.0.1",
"registry-url": "^3.0.3",
"semver": "^5.1.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/pacote": {
"version": "9.5.12",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"bluebird": "^3.5.3",
"cacache": "^12.0.2",
"chownr": "^1.1.2",
"figgy-pudding": "^3.5.1",
"get-stream": "^4.1.0",
"glob": "^7.1.3",
"infer-owner": "^1.0.4",
"lru-cache": "^5.1.1",
"make-fetch-happen": "^5.0.0",
"minimatch": "^3.0.4",
"minipass": "^2.3.5",
"mississippi": "^3.0.0",
"mkdirp": "^0.5.1",
"normalize-package-data": "^2.4.0",
"npm-normalize-package-bin": "^1.0.0",
"npm-package-arg": "^6.1.0",
"npm-packlist": "^1.1.12",
"npm-pick-manifest": "^3.0.0",
"npm-registry-fetch": "^4.0.0",
"osenv": "^0.1.5",
"promise-inflight": "^1.0.1",
"promise-retry": "^1.1.1",
"protoduck": "^5.0.1",
"rimraf": "^2.6.2",
"safe-buffer": "^5.1.2",
"semver": "^5.6.0",
"ssri": "^6.0.1",
"tar": "^4.4.10",
"unique-filename": "^1.1.1",
"which": "^1.3.1"
}
},
"node_modules/npm/node_modules/pacote/node_modules/minipass": {
"version": "2.9.0",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"safe-buffer": "^5.1.2",
"yallist": "^3.0.0"
}
},
"node_modules/npm/node_modules/parallel-transform": {
"version": "1.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"cyclist": "~0.2.2",
"inherits": "^2.0.3",
"readable-stream": "^2.1.5"
}
},
"node_modules/npm/node_modules/parallel-transform/node_modules/readable-stream": {
"version": "2.3.6",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"node_modules/npm/node_modules/parallel-transform/node_modules/string_decoder": {
"version": "1.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"safe-buffer": "~5.1.0"
}
},
"node_modules/npm/node_modules/path-exists": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/path-is-absolute": {
"version": "1.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/path-is-inside": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "(WTFPL OR MIT)"
},
"node_modules/npm/node_modules/path-key": {
"version": "2.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/path-parse": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "1.0.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/performance-now": {
"version": "2.1.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/pify": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/prepend-http": {
"version": "1.0.4",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/process-nextick-args": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/promise-inflight": {
"version": "1.0.1",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/promise-retry": {
"version": "1.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"err-code": "^1.0.0",
"retry": "^0.10.0"
},
"engines": {
"node": ">=0.12"
}
},
"node_modules/npm/node_modules/promise-retry/node_modules/retry": {
"version": "0.10.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": "*"
}
},
"node_modules/npm/node_modules/promzard": {
"version": "0.3.0",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"read": "1"
}
},
"node_modules/npm/node_modules/proto-list": {
"version": "1.2.4",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/protoduck": {
"version": "5.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"genfun": "^5.0.0"
}
},
"node_modules/npm/node_modules/prr": {
"version": "1.0.1",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/pseudomap": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/psl": {
"version": "1.1.29",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/pump": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"end-of-stream": "^1.1.0",
"once": "^1.3.1"
}
},
"node_modules/npm/node_modules/pumpify": {
"version": "1.5.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"duplexify": "^3.6.0",
"inherits": "^2.0.3",
"pump": "^2.0.0"
}
},
"node_modules/npm/node_modules/pumpify/node_modules/pump": {
"version": "2.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"end-of-stream": "^1.1.0",
"once": "^1.3.1"
}
},
"node_modules/npm/node_modules/punycode": {
"version": "1.4.1",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/qrcode-terminal": {
"version": "0.12.0",
"dev": true,
"inBundle": true,
"bin": {
"qrcode-terminal": "bin/qrcode-terminal.js"
}
},
"node_modules/npm/node_modules/qs": {
"version": "6.5.2",
"dev": true,
"inBundle": true,
"license": "BSD-3-Clause",
"engines": {
"node": ">=0.6"
}
},
"node_modules/npm/node_modules/query-string": {
"version": "6.8.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"decode-uri-component": "^0.2.0",
"split-on-first": "^1.0.0",
"strict-uri-encode": "^2.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/qw": {
"version": "1.0.1",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/rc": {
"version": "1.2.8",
"dev": true,
"inBundle": true,
"license": "(BSD-2-Clause OR MIT OR Apache-2.0)",
"dependencies": {
"deep-extend": "^0.6.0",
"ini": "~1.3.0",
"minimist": "^1.2.0",
"strip-json-comments": "~2.0.1"
},
"bin": {
"rc": "cli.js"
}
},
"node_modules/npm/node_modules/read": {
"version": "1.0.7",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"mute-stream": "~0.0.4"
},
"engines": {
"node": ">=0.8"
}
},
"node_modules/npm/node_modules/read-cmd-shim": {
"version": "1.0.5",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"graceful-fs": "^4.1.2"
}
},
"node_modules/npm/node_modules/read-installed": {
"version": "4.0.3",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"debuglog": "^1.0.1",
"read-package-json": "^2.0.0",
"readdir-scoped-modules": "^1.0.0",
"semver": "2 || 3 || 4 || 5",
"slide": "~1.1.3",
"util-extend": "^1.0.1"
},
"optionalDependencies": {
"graceful-fs": "^4.1.2"
}
},
"node_modules/npm/node_modules/read-package-json": {
"version": "2.1.1",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"glob": "^7.1.1",
"json-parse-better-errors": "^1.0.1",
"normalize-package-data": "^2.0.0",
"npm-normalize-package-bin": "^1.0.0"
},
"optionalDependencies": {
"graceful-fs": "^4.1.2"
}
},
"node_modules/npm/node_modules/read-package-tree": {
"version": "5.3.1",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"read-package-json": "^2.0.0",
"readdir-scoped-modules": "^1.0.0",
"util-promisify": "^2.1.0"
}
},
"node_modules/npm/node_modules/readable-stream": {
"version": "3.6.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"inherits": "^2.0.3",
"string_decoder": "^1.1.1",
"util-deprecate": "^1.0.1"
},
"engines": {
"node": ">= 6"
}
},
"node_modules/npm/node_modules/readdir-scoped-modules": {
"version": "1.1.0",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"debuglog": "^1.0.1",
"dezalgo": "^1.0.0",
"graceful-fs": "^4.1.2",
"once": "^1.3.0"
}
},
"node_modules/npm/node_modules/registry-auth-token": {
"version": "3.4.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"rc": "^1.1.6",
"safe-buffer": "^5.0.1"
}
},
"node_modules/npm/node_modules/registry-url": {
"version": "3.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"rc": "^1.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/request": {
"version": "2.88.0",
"dev": true,
"inBundle": true,
"license": "Apache-2.0",
"dependencies": {
"aws-sign2": "~0.7.0",
"aws4": "^1.8.0",
"caseless": "~0.12.0",
"combined-stream": "~1.0.6",
"extend": "~3.0.2",
"forever-agent": "~0.6.1",
"form-data": "~2.3.2",
"har-validator": "~5.1.0",
"http-signature": "~1.2.0",
"is-typedarray": "~1.0.0",
"isstream": "~0.1.2",
"json-stringify-safe": "~5.0.1",
"mime-types": "~2.1.19",
"oauth-sign": "~0.9.0",
"performance-now": "^2.1.0",
"qs": "~6.5.2",
"safe-buffer": "^5.1.2",
"tough-cookie": "~2.4.3",
"tunnel-agent": "^0.6.0",
"uuid": "^3.3.2"
},
"engines": {
"node": ">= 4"
}
},
"node_modules/npm/node_modules/require-directory": {
"version": "2.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/require-main-filename": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/resolve-from": {
"version": "4.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/retry": {
"version": "0.12.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">= 4"
}
},
"node_modules/npm/node_modules/rimraf": {
"version": "2.7.1",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"glob": "^7.1.3"
},
"bin": {
"rimraf": "bin.js"
}
},
"node_modules/npm/node_modules/run-queue": {
"version": "1.0.3",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"aproba": "^1.1.1"
}
},
"node_modules/npm/node_modules/run-queue/node_modules/aproba": {
"version": "1.2.0",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/safe-buffer": {
"version": "5.1.2",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/safer-buffer": {
"version": "2.1.2",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/semver": {
"version": "5.7.1",
"dev": true,
"inBundle": true,
"license": "ISC",
"bin": {
"semver": "bin/semver"
}
},
"node_modules/npm/node_modules/semver-diff": {
"version": "2.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"semver": "^5.0.3"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/set-blocking": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/sha": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "(BSD-2-Clause OR MIT)",
"dependencies": {
"graceful-fs": "^4.1.2"
}
},
"node_modules/npm/node_modules/shebang-command": {
"version": "1.2.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"shebang-regex": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/shebang-regex": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/signal-exit": {
"version": "3.0.2",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/slide": {
"version": "1.1.6",
"dev": true,
"inBundle": true,
"license": "ISC",
"engines": {
"node": "*"
}
},
"node_modules/npm/node_modules/smart-buffer": {
"version": "4.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">= 6.0.0",
"npm": ">= 3.0.0"
}
},
"node_modules/npm/node_modules/socks": {
"version": "2.3.3",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"ip": "1.1.5",
"smart-buffer": "^4.1.0"
},
"engines": {
"node": ">= 6.0.0",
"npm": ">= 3.0.0"
}
},
"node_modules/npm/node_modules/socks-proxy-agent": {
"version": "4.0.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"agent-base": "~4.2.1",
"socks": "~2.3.2"
},
"engines": {
"node": ">= 6"
}
},
"node_modules/npm/node_modules/socks-proxy-agent/node_modules/agent-base": {
"version": "4.2.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"es6-promisify": "^5.0.0"
},
"engines": {
"node": ">= 4.0.0"
}
},
"node_modules/npm/node_modules/sorted-object": {
"version": "2.0.1",
"dev": true,
"inBundle": true,
"license": "(WTFPL OR MIT)"
},
"node_modules/npm/node_modules/sorted-union-stream": {
"version": "2.1.3",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"from2": "^1.3.0",
"stream-iterate": "^1.1.0"
}
},
"node_modules/npm/node_modules/sorted-union-stream/node_modules/from2": {
"version": "1.3.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"inherits": "~2.0.1",
"readable-stream": "~1.1.10"
}
},
"node_modules/npm/node_modules/sorted-union-stream/node_modules/isarray": {
"version": "0.0.1",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/sorted-union-stream/node_modules/readable-stream": {
"version": "1.1.14",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.1",
"isarray": "0.0.1",
"string_decoder": "~0.10.x"
}
},
"node_modules/npm/node_modules/sorted-union-stream/node_modules/string_decoder": {
"version": "0.10.31",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/spdx-correct": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "Apache-2.0",
"dependencies": {
"spdx-expression-parse": "^3.0.0",
"spdx-license-ids": "^3.0.0"
}
},
"node_modules/npm/node_modules/spdx-exceptions": {
"version": "2.1.0",
"dev": true,
"inBundle": true,
"license": "CC-BY-3.0"
},
"node_modules/npm/node_modules/spdx-expression-parse": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"spdx-exceptions": "^2.1.0",
"spdx-license-ids": "^3.0.0"
}
},
"node_modules/npm/node_modules/spdx-license-ids": {
"version": "3.0.5",
"dev": true,
"inBundle": true,
"license": "CC0-1.0"
},
"node_modules/npm/node_modules/split-on-first": {
"version": "1.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/sshpk": {
"version": "1.14.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"asn1": "~0.2.3",
"assert-plus": "^1.0.0",
"dashdash": "^1.12.0",
"getpass": "^0.1.1",
"safer-buffer": "^2.0.2"
},
"bin": {
"sshpk-conv": "bin/sshpk-conv",
"sshpk-sign": "bin/sshpk-sign",
"sshpk-verify": "bin/sshpk-verify"
},
"engines": {
"node": ">=0.10.0"
},
"optionalDependencies": {
"bcrypt-pbkdf": "^1.0.0",
"ecc-jsbn": "~0.1.1",
"jsbn": "~0.1.0",
"tweetnacl": "~0.14.0"
}
},
"node_modules/npm/node_modules/ssri": {
"version": "6.0.2",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"figgy-pudding": "^3.5.1"
}
},
"node_modules/npm/node_modules/stream-each": {
"version": "1.2.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"end-of-stream": "^1.1.0",
"stream-shift": "^1.0.0"
}
},
"node_modules/npm/node_modules/stream-iterate": {
"version": "1.2.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"readable-stream": "^2.1.5",
"stream-shift": "^1.0.0"
}
},
"node_modules/npm/node_modules/stream-iterate/node_modules/readable-stream": {
"version": "2.3.6",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"node_modules/npm/node_modules/stream-iterate/node_modules/string_decoder": {
"version": "1.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"safe-buffer": "~5.1.0"
}
},
"node_modules/npm/node_modules/stream-shift": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/strict-uri-encode": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/string_decoder": {
"version": "1.3.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"safe-buffer": "~5.2.0"
}
},
"node_modules/npm/node_modules/string_decoder/node_modules/safe-buffer": {
"version": "5.2.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/string-width": {
"version": "2.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"is-fullwidth-code-point": "^2.0.0",
"strip-ansi": "^4.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/string-width/node_modules/ansi-regex": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/string-width/node_modules/is-fullwidth-code-point": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/string-width/node_modules/strip-ansi": {
"version": "4.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"ansi-regex": "^3.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/stringify-package": {
"version": "1.0.1",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/strip-ansi": {
"version": "3.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"ansi-regex": "^2.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/strip-eof": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/strip-json-comments": {
"version": "2.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/supports-color": {
"version": "5.4.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"has-flag": "^3.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/tar": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "4.4.19",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"chownr": "^1.1.4",
"fs-minipass": "^1.2.7",
"minipass": "^2.9.0",
"minizlib": "^1.3.3",
"mkdirp": "^0.5.5",
"safe-buffer": "^5.2.1",
"yallist": "^3.1.1"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=4.5"
}
},
"node_modules/npm/node_modules/tar/node_modules/minipass": {
"version": "2.9.0",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"safe-buffer": "^5.1.2",
"yallist": "^3.0.0"
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/npm/node_modules/tar/node_modules/safe-buffer": {
"version": "5.2.1",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
],
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/tar/node_modules/yallist": {
"version": "3.1.1",
"dev": true,
"inBundle": true,
"license": "ISC"
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/npm/node_modules/term-size": {
"version": "1.2.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"execa": "^0.7.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/text-table": {
"version": "0.2.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/through": {
"version": "2.3.8",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/through2": {
"version": "2.0.3",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"readable-stream": "^2.1.5",
"xtend": "~4.0.1"
}
},
"node_modules/npm/node_modules/through2/node_modules/readable-stream": {
"version": "2.3.6",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"node_modules/npm/node_modules/through2/node_modules/string_decoder": {
"version": "1.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"safe-buffer": "~5.1.0"
}
},
"node_modules/npm/node_modules/timed-out": {
"version": "4.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/tiny-relative-date": {
"version": "1.3.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/tough-cookie": {
"version": "2.4.3",
"dev": true,
"inBundle": true,
"license": "BSD-3-Clause",
"dependencies": {
"psl": "^1.1.24",
"punycode": "^1.4.1"
},
"engines": {
"node": ">=0.8"
}
},
"node_modules/npm/node_modules/tunnel-agent": {
"version": "0.6.0",
"dev": true,
"inBundle": true,
"license": "Apache-2.0",
"dependencies": {
"safe-buffer": "^5.0.1"
},
"engines": {
"node": "*"
}
},
"node_modules/npm/node_modules/tweetnacl": {
"version": "0.14.5",
"dev": true,
"inBundle": true,
"license": "Unlicense",
"optional": true
},
"node_modules/npm/node_modules/typedarray": {
"version": "0.0.6",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/uid-number": {
"version": "0.0.6",
"dev": true,
"inBundle": true,
"license": "ISC",
"engines": {
"node": "*"
}
},
"node_modules/npm/node_modules/umask": {
"version": "1.1.0",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/unique-filename": {
"version": "1.1.1",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"unique-slug": "^2.0.0"
}
},
"node_modules/npm/node_modules/unique-slug": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"imurmurhash": "^0.1.4"
}
},
"node_modules/npm/node_modules/unique-string": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"crypto-random-string": "^1.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/unpipe": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">= 0.8"
}
},
"node_modules/npm/node_modules/unzip-response": {
"version": "2.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/update-notifier": {
"version": "2.5.0",
"dev": true,
"inBundle": true,
"license": "BSD-2-Clause",
"dependencies": {
"boxen": "^1.2.1",
"chalk": "^2.0.1",
"configstore": "^3.0.0",
"import-lazy": "^2.1.0",
"is-ci": "^1.0.10",
"is-installed-globally": "^0.1.0",
"is-npm": "^1.0.0",
"latest-version": "^3.0.0",
"semver-diff": "^2.0.0",
"xdg-basedir": "^3.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/uri-js": {
"version": "4.4.0",
"dev": true,
"inBundle": true,
"license": "BSD-2-Clause",
"dependencies": {
"punycode": "^2.1.0"
}
},
"node_modules/npm/node_modules/uri-js/node_modules/punycode": {
"version": "2.1.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/url-parse-lax": {
"version": "1.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"prepend-http": "^1.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/util-deprecate": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/util-extend": {
"version": "1.0.3",
"dev": true,
"inBundle": true,
"license": "MIT"
},
"node_modules/npm/node_modules/util-promisify": {
"version": "2.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"object.getownpropertydescriptors": "^2.0.3"
}
},
"node_modules/npm/node_modules/uuid": {
"version": "3.3.3",
"dev": true,
"inBundle": true,
"license": "MIT",
"bin": {
"uuid": "bin/uuid"
}
},
"node_modules/npm/node_modules/validate-npm-package-license": {
"version": "3.0.4",
"dev": true,
"inBundle": true,
"license": "Apache-2.0",
"dependencies": {
"spdx-correct": "^3.0.0",
"spdx-expression-parse": "^3.0.0"
}
},
"node_modules/npm/node_modules/validate-npm-package-name": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"builtins": "^1.0.3"
}
},
"node_modules/npm/node_modules/verror": {
"version": "1.10.0",
"dev": true,
"engines": [
"node >=0.6.0"
],
"inBundle": true,
"license": "MIT",
"dependencies": {
"assert-plus": "^1.0.0",
"core-util-is": "1.0.2",
"extsprintf": "^1.2.0"
}
},
"node_modules/npm/node_modules/wcwidth": {
"version": "1.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"defaults": "^1.0.3"
}
},
"node_modules/npm/node_modules/which": {
"version": "1.3.1",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"isexe": "^2.0.0"
},
"bin": {
"which": "bin/which"
}
},
"node_modules/npm/node_modules/which-module": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/wide-align": {
"version": "1.1.2",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"string-width": "^1.0.2"
}
},
"node_modules/npm/node_modules/wide-align/node_modules/string-width": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"code-point-at": "^1.0.0",
"is-fullwidth-code-point": "^1.0.0",
"strip-ansi": "^3.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/npm/node_modules/widest-line": {
"version": "2.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"string-width": "^2.1.1"
},
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/worker-farm": {
"version": "1.7.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"errno": "~0.1.7"
}
},
"node_modules/npm/node_modules/wrap-ansi": {
"version": "5.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"ansi-styles": "^3.2.0",
"string-width": "^3.0.0",
"strip-ansi": "^5.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/wrap-ansi/node_modules/ansi-regex": {
"version": "4.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/wrap-ansi/node_modules/is-fullwidth-code-point": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/wrap-ansi/node_modules/string-width": {
"version": "3.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"emoji-regex": "^7.0.1",
"is-fullwidth-code-point": "^2.0.0",
"strip-ansi": "^5.1.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/wrap-ansi/node_modules/strip-ansi": {
"version": "5.2.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"ansi-regex": "^4.1.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/wrappy": {
"version": "1.0.2",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/write-file-atomic": {
"version": "2.4.3",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"graceful-fs": "^4.1.11",
"imurmurhash": "^0.1.4",
"signal-exit": "^3.0.2"
}
},
"node_modules/npm/node_modules/xdg-basedir": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/xtend": {
"version": "4.0.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=0.4"
}
},
"node_modules/npm/node_modules/y18n": {
"version": "4.0.1",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/yallist": {
"version": "3.0.3",
"dev": true,
"inBundle": true,
"license": "ISC"
},
"node_modules/npm/node_modules/yargs": {
"version": "14.2.3",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"cliui": "^5.0.0",
"decamelize": "^1.2.0",
"find-up": "^3.0.0",
"get-caller-file": "^2.0.1",
"require-directory": "^2.1.1",
"require-main-filename": "^2.0.0",
"set-blocking": "^2.0.0",
"string-width": "^3.0.0",
"which-module": "^2.0.0",
"y18n": "^4.0.0",
"yargs-parser": "^15.0.1"
}
},
"node_modules/npm/node_modules/yargs-parser": {
"version": "15.0.1",
"dev": true,
"inBundle": true,
"license": "ISC",
"dependencies": {
"camelcase": "^5.0.0",
"decamelize": "^1.2.0"
}
},
"node_modules/npm/node_modules/yargs-parser/node_modules/camelcase": {
"version": "5.3.1",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/yargs/node_modules/ansi-regex": {
"version": "4.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/yargs/node_modules/find-up": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"locate-path": "^3.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/yargs/node_modules/is-fullwidth-code-point": {
"version": "2.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=4"
}
},
"node_modules/npm/node_modules/yargs/node_modules/locate-path": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"p-locate": "^3.0.0",
"path-exists": "^3.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/yargs/node_modules/p-limit": {
"version": "2.3.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"p-try": "^2.0.0"
},
"engines": {
"node": ">=6"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/npm/node_modules/yargs/node_modules/p-locate": {
"version": "3.0.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"p-limit": "^2.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/yargs/node_modules/p-try": {
"version": "2.2.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/yargs/node_modules/string-width": {
"version": "3.1.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"emoji-regex": "^7.0.1",
"is-fullwidth-code-point": "^2.0.0",
"strip-ansi": "^5.1.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npm/node_modules/yargs/node_modules/strip-ansi": {
"version": "5.2.0",
"dev": true,
"inBundle": true,
"license": "MIT",
"dependencies": {
"ansi-regex": "^4.1.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/npmlog": {
"version": "4.1.2",
"resolved": "https://registry.npmjs.org/npmlog/-/npmlog-4.1.2.tgz",
"integrity": "sha512-2uUqazuKlTaSI/dC8AzicUck7+IrEaOnN/e0jd3Xtt1KcGpwx30v50mL7oPyr/h9bL3E4aZccVwpwP+5W9Vjkg==",
"dev": true,
"dependencies": {
"are-we-there-yet": "~1.1.2",
"console-control-strings": "~1.1.0",
"gauge": "~2.7.3",
"set-blocking": "~2.0.0"
}
},
"node_modules/number-is-nan": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.1.tgz",
"integrity": "sha1-CXtgK1NCKlIsGvuHkDGDNpQaAR0=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/object-assign": {
"version": "4.1.1",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.1.1.tgz",
"integrity": "sha1-IQmtx5ZYh8/AXLvUQsrIv7s2CGM=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/object-copy": {
"version": "0.1.0",
"resolved": "https://registry.npmjs.org/object-copy/-/object-copy-0.1.0.tgz",
"integrity": "sha1-fn2Fi3gb18mRpBupde04EnVOmYw=",
"dev": true,
"dependencies": {
"copy-descriptor": "^0.1.0",
"define-property": "^0.2.5",
"kind-of": "^3.0.3"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/object-copy/node_modules/define-property": {
"version": "0.2.5",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-0.2.5.tgz",
"integrity": "sha1-w1se+RjsPJkPmlvFe+BKrOxcgRY=",
"dev": true,
"dependencies": {
"is-descriptor": "^0.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/object-copy/node_modules/kind-of": {
"version": "3.2.2",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz",
"integrity": "sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=",
"dev": true,
"dependencies": {
"is-buffer": "^1.1.5"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/object-inspect": {
"version": "1.11.0",
"resolved": "https://registry.npmjs.org/object-inspect/-/object-inspect-1.11.0.tgz",
"integrity": "sha512-jp7ikS6Sd3GxQfZJPyH3cjcbJF6GZPClgdV+EFygjFLQ5FmW/dRUnTd9PQ9k0JhoNDabWFbpF1yCdSWCC6gexg==",
"dev": true,
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/object-keys": {
"version": "1.0.11",
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.0.11.tgz",
"integrity": "sha1-xUYBd4rVYPEULODgG8yotW0TQm0=",
"dev": true,
"engines": {
"node": ">= 0.4"
}
},
"node_modules/object-visit": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/object-visit/-/object-visit-1.0.1.tgz",
"integrity": "sha1-95xEk68MU3e1n+OdOV5BBC3QRbs=",
"dev": true,
"dependencies": {
"isobject": "^3.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/object.assign": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/object.assign/-/object.assign-4.1.0.tgz",
"integrity": "sha512-exHJeq6kBKj58mqGyTQ9DFvrZC/eR6OwxzoM9YRoGBqrXYonaFyGiFMuc9VZrXf7DarreEwMpurG3dd+CNyW5w==",
"dev": true,
"dependencies": {
"define-properties": "^1.1.2",
"function-bind": "^1.1.1",
"has-symbols": "^1.0.0",
"object-keys": "^1.0.11"
},
"engines": {
"node": ">= 0.4"
}
},
"node_modules/object.defaults": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/object.defaults/-/object.defaults-1.1.0.tgz",
"integrity": "sha1-On+GgzS0B96gbaFtiNXNKeQ1/s8=",
"dev": true,
"dependencies": {
"array-each": "^1.0.1",
"array-slice": "^1.0.0",
"for-own": "^1.0.0",
"isobject": "^3.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/object.map": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/object.map/-/object.map-1.0.1.tgz",
"integrity": "sha1-z4Plncj8wK1fQlDh94s7gb2AHTc=",
"dev": true,
"dependencies": {
"for-own": "^1.0.0",
"make-iterator": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/object.pick": {
"version": "1.3.0",
"resolved": "https://registry.npmjs.org/object.pick/-/object.pick-1.3.0.tgz",
"integrity": "sha1-h6EKxMFpS9Lhy/U1kaZhQftd10c=",
"dev": true,
"dependencies": {
"isobject": "^3.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/object.reduce": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/object.reduce/-/object.reduce-1.0.1.tgz",
"integrity": "sha1-b+NI8qx/oPlcpiEiZZkJaCW7A60=",
"dev": true,
"dependencies": {
"for-own": "^1.0.0",
"make-iterator": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/object.values": {
"version": "1.1.5",
"resolved": "https://registry.npmjs.org/object.values/-/object.values-1.1.5.tgz",
"integrity": "sha512-QUZRW0ilQ3PnPpbNtgdNV1PDbEqLIiSFB3l+EnGtBQ/8SUTLj1PZwtQHABZtLgwpJZTSZhuGLOGk57Drx2IvYg==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.2",
"define-properties": "^1.1.3",
"es-abstract": "^1.19.1"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/object.values/node_modules/define-properties": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.1.3.tgz",
"integrity": "sha512-3MqfYKj2lLzdMSf8ZIZE/V+Zuy+BgD6f164e8K2w7dgnpKArBDerGYpM46IYYcjnkdPNMjPk9A6VFB8+3SKlXQ==",
"dev": true,
"dependencies": {
"object-keys": "^1.0.12"
},
"engines": {
"node": ">= 0.4"
}
},
"node_modules/object.values/node_modules/object-keys": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz",
"integrity": "sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==",
"dev": true,
"engines": {
"node": ">= 0.4"
}
},
"node_modules/once": {
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/once/-/once-1.4.0.tgz",
"integrity": "sha1-WDsap3WWHUsROsF9nFC6753Xa9E=",
"dev": true,
"dependencies": {
"wrappy": "1"
}
},
"node_modules/one-time": {
"version": "0.0.4",
"resolved": "https://registry.npmjs.org/one-time/-/one-time-0.0.4.tgz",
"integrity": "sha1-+M33eISCb+Tf+T46nMN7HkSAdC4=",
"dev": true
},
"node_modules/optionator": {
"version": "0.8.3",
"resolved": "https://registry.npmjs.org/optionator/-/optionator-0.8.3.tgz",
"integrity": "sha512-+IW9pACdk3XWmmTXG8m3upGUJst5XRGzxMRjXzAuJ1XnIFNvfhjjIuYkDvysnPQ7qzqVzLt78BCruntqRhWQbA==",
"dev": true,
"dependencies": {
"deep-is": "~0.1.3",
"fast-levenshtein": "~2.0.6",
"levn": "~0.3.0",
"prelude-ls": "~1.1.2",
"type-check": "~0.3.2",
"word-wrap": "~1.2.3"
},
"engines": {
"node": ">= 0.8.0"
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/ordered-read-streams": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/ordered-read-streams/-/ordered-read-streams-1.0.1.tgz",
"integrity": "sha1-d8DLN8QVJdZBZtmQ/61+xqDhNj4=",
"dev": true,
"dependencies": {
"readable-stream": "^2.0.1"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/p-limit": {
"version": "1.3.0",
"resolved": "https://registry.npmjs.org/p-limit/-/p-limit-1.3.0.tgz",
"integrity": "sha512-vvcXsLAJ9Dr5rQOPk7toZQZJApBl2K4J6dANSsEuh6QI41JYcsS/qhTGa9ErIUUgK3WNQoJYvylxvjqmiqEA9Q==",
"dev": true,
"dependencies": {
"p-try": "^1.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/p-locate": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/p-locate/-/p-locate-2.0.0.tgz",
"integrity": "sha1-IKAQOyIqcMj9OcwuWAaA893l7EM=",
"dev": true,
"dependencies": {
"p-limit": "^1.1.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/p-try": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/p-try/-/p-try-1.0.0.tgz",
"integrity": "sha1-y8ec26+P1CKOE/Yh8rGiN8GyB7M=",
"dev": true,
"engines": {
"node": ">=4"
}
},
"node_modules/parent-module": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/parent-module/-/parent-module-1.0.1.tgz",
"integrity": "sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==",
"dev": true,
"dependencies": {
"callsites": "^3.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/parse-filepath": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/parse-filepath/-/parse-filepath-1.0.2.tgz",
"integrity": "sha1-pjISf1Oq89FYdvWHLz/6x2PWyJE=",
"dev": true,
"dependencies": {
"is-absolute": "^1.0.0",
"map-cache": "^0.2.0",
"path-root": "^0.1.1"
},
"engines": {
"node": ">=0.8"
}
},
"node_modules/parse-json": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"integrity": "sha1-9ID0BDTvgHQfhGkJn43qGPVaTck=",
"dev": true,
"dependencies": {
"error-ex": "^1.2.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/parse-node-version": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/parse-node-version/-/parse-node-version-1.0.0.tgz",
"integrity": "sha512-02GTVHD1u0nWc20n2G7WX/PgdhNFG04j5fi1OkaJzPWLTcf6vh6229Lta1wTmXG/7Dg42tCssgkccVt7qvd8Kg==",
"dev": true,
"engines": {
"node": ">= 0.10"
}
},
"node_modules/parse-passwd": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/parse-passwd/-/parse-passwd-1.0.0.tgz",
"integrity": "sha1-bVuTSkVpk7I9N/QKOC1vFmao5cY=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/pascalcase": {
"version": "0.1.1",
"resolved": "https://registry.npmjs.org/pascalcase/-/pascalcase-0.1.1.tgz",
"integrity": "sha1-s2PlXoAGym/iF4TS2yK9FdeRfxQ=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/path-dirname": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/path-dirname/-/path-dirname-1.0.2.tgz",
"integrity": "sha1-zDPSTVJeCZpTiMAzbG4yuRYGCeA=",
"dev": true
},
"node_modules/path-exists": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-3.0.0.tgz",
"integrity": "sha1-zg6+ql94yxiSXqfYENe1mwEP1RU=",
"dev": true,
"engines": {
"node": ">=4"
}
},
"node_modules/path-is-absolute": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.1.tgz",
"integrity": "sha1-F0uSaHNVNP+8es5r9TpanhtcX18=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/path-parse": {
"version": "1.0.7",
"resolved": "https://registry.npmjs.org/path-parse/-/path-parse-1.0.7.tgz",
"integrity": "sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==",
"dev": true
},
"node_modules/path-root": {
"version": "0.1.1",
"resolved": "https://registry.npmjs.org/path-root/-/path-root-0.1.1.tgz",
"integrity": "sha1-mkpoFMrBwM1zNgqV8yCDyOpHRbc=",
"dev": true,
"dependencies": {
"path-root-regex": "^0.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/path-root-regex": {
"version": "0.1.2",
"resolved": "https://registry.npmjs.org/path-root-regex/-/path-root-regex-0.1.2.tgz",
"integrity": "sha1-v8zcjfWxLcUsi0PsONGNcsBLqW0=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/path-type": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-4.0.0.tgz",
"integrity": "sha512-gDKb8aZMDeD/tZWs9P6+q0J9Mwkdl6xMV8TjnGP3qJVJ06bdMgkbBlLU8IdfOsIsFz2BW1rNVT3XuNEl8zPAvw==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/pend": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/pend/-/pend-1.2.0.tgz",
"integrity": "sha1-elfrVQpng/kRUzH89GY9XI4AelA=",
"dev": true
},
"node_modules/picocolors": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/picocolors/-/picocolors-1.0.0.tgz",
"integrity": "sha512-1fygroTLlHu66zi26VoTDv8yRgm0Fccecssto+MhsZ0D/DGW2sm8E8AjW7NU5VVTRt5GxbeZ5qBuJr+HyLYkjQ==",
"dev": true
},
"node_modules/picomatch": {
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/picomatch/-/picomatch-2.3.0.tgz",
"integrity": "sha512-lY1Q/PiJGC2zOv/z391WOTD+Z02bCgsFfvxoXXf6h7kv9o+WmsmzYqrAwY63sNgOxE4xEdq0WyUnXfKeBrSvYw==",
"dev": true,
"engines": {
"node": ">=8.6"
},
"funding": {
"url": "https://github.com/sponsors/jonschlinkert"
}
},
"node_modules/pinkie": {
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-2.0.4.tgz",
"integrity": "sha1-clVrgM+g1IqXToDnckjoDtT3+HA=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/pinkie-promise": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-2.0.1.tgz",
"integrity": "sha1-ITXW36ejWMBprJsXh3YogihFD/o=",
"dev": true,
"dependencies": {
"pinkie": "^2.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/pkg-dir": {
"version": "4.2.0",
"resolved": "https://registry.npmjs.org/pkg-dir/-/pkg-dir-4.2.0.tgz",
"integrity": "sha512-HRDzbaKjC+AOWVXxAU/x54COGeIv9eb+6CkDSQoNTt4XyWoIJvuPsXizxu/Fr23EiekbtZwmh1IcIG/l/a10GQ==",
"dev": true,
"dependencies": {
"find-up": "^4.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/pkg-dir/node_modules/find-up": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-4.1.0.tgz",
"integrity": "sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw==",
"dev": true,
"dependencies": {
"locate-path": "^5.0.0",
"path-exists": "^4.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/pkg-dir/node_modules/locate-path": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/locate-path/-/locate-path-5.0.0.tgz",
"integrity": "sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g==",
"dev": true,
"dependencies": {
"p-locate": "^4.1.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/pkg-dir/node_modules/p-limit": {
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/p-limit/-/p-limit-2.3.0.tgz",
"integrity": "sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w==",
"dev": true,
"dependencies": {
"p-try": "^2.0.0"
},
"engines": {
"node": ">=6"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/pkg-dir/node_modules/p-locate": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/p-locate/-/p-locate-4.1.0.tgz",
"integrity": "sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A==",
"dev": true,
"dependencies": {
"p-limit": "^2.2.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/pkg-dir/node_modules/p-try": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/p-try/-/p-try-2.2.0.tgz",
"integrity": "sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ==",
"dev": true,
"engines": {
"node": ">=6"
}
},
"node_modules/pkg-dir/node_modules/path-exists": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-4.0.0.tgz",
"integrity": "sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/plugin-error": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/plugin-error/-/plugin-error-1.0.1.tgz",
"integrity": "sha512-L1zP0dk7vGweZME2i+EeakvUNqSrdiI3F91TwEoYiGrAfUXmVv6fJIq4g82PAXxNsWOp0J7ZqQy/3Szz0ajTxA==",
"dev": true,
"dependencies": {
"ansi-colors": "^1.0.1",
"arr-diff": "^4.0.0",
"arr-union": "^3.1.0",
"extend-shallow": "^3.0.2"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/pluralize": {
"version": "8.0.0",
"resolved": "https://registry.npmjs.org/pluralize/-/pluralize-8.0.0.tgz",
"integrity": "sha512-Nc3IT5yHzflTfbjgqWcCPpo7DaKy4FnpB0l/zCAW0Tc7jxAiuqSxHasntB3D7887LSrA93kDJ9IXovxJYxyLCA==",
"dev": true,
"engines": {
"node": ">=4"
}
},
"node_modules/posix-character-classes": {
"version": "0.1.1",
"resolved": "https://registry.npmjs.org/posix-character-classes/-/posix-character-classes-0.1.1.tgz",
"integrity": "sha1-AerA/jta9xoqbAL+q7jB/vfgDqs=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/postcss": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "8.4.6",
"resolved": "https://registry.npmjs.org/postcss/-/postcss-8.4.6.tgz",
"integrity": "sha512-OovjwIzs9Te46vlEx7+uXB0PLijpwjXGKXjVGGPIGubGpq7uh5Xgf6D6FiJ/SzJMBosHDp6a2hiXOS97iBXcaA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-02-06 19:24:14 +09:00
"nanoid": "^3.2.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"picocolors": "^1.0.0",
Update npm packages
2022-02-06 19:24:14 +09:00
"source-map-js": "^1.0.2"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": "^10 || ^12 || >=14"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/postcss/"
}
},
"node_modules/postcss-calc": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "8.2.4",
"resolved": "https://registry.npmjs.org/postcss-calc/-/postcss-calc-8.2.4.tgz",
"integrity": "sha512-SmWMSJmB8MRnnULldx0lQIyhSNvuDl9HfrZkaqqE/WHAhToYsAvDq+yAsA/kIyINDszOp3Rh0GFoNuH5Ypsm3Q==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-02-20 18:08:23 +09:00
"postcss-selector-parser": "^6.0.9",
"postcss-value-parser": "^4.2.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"peerDependencies": {
"postcss": "^8.2.2"
}
},
"node_modules/postcss-load-config": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/postcss-load-config/-/postcss-load-config-3.1.0.tgz",
"integrity": "sha512-ipM8Ds01ZUophjDTQYSVP70slFSYg3T0/zyfII5vzhN6V57YSxMgG5syXuwi5VtS8wSf3iL30v0uBdoIVx4Q0g==",
"dev": true,
"dependencies": {
"import-cwd": "^3.0.0",
"lilconfig": "^2.0.3",
"yaml": "^1.10.2"
},
"engines": {
"node": ">= 10"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/postcss/"
},
"peerDependencies": {
"ts-node": ">=9.0.0"
},
"peerDependenciesMeta": {
"ts-node": {
"optional": true
}
}
},
"node_modules/postcss-media-query-parser": {
"version": "0.2.3",
"resolved": "https://registry.npmjs.org/postcss-media-query-parser/-/postcss-media-query-parser-0.2.3.tgz",
"integrity": "sha1-J7Ocb02U+Bsac7j3Y1HGCeXO8kQ=",
"dev": true
},
"node_modules/postcss-resolve-nested-selector": {
"version": "0.1.1",
"resolved": "https://registry.npmjs.org/postcss-resolve-nested-selector/-/postcss-resolve-nested-selector-0.1.1.tgz",
"integrity": "sha1-Kcy8fDfe36wwTp//C/FZaz9qDk4=",
"dev": true
},
"node_modules/postcss-safe-parser": {
"version": "6.0.0",
"resolved": "https://registry.npmjs.org/postcss-safe-parser/-/postcss-safe-parser-6.0.0.tgz",
"integrity": "sha512-FARHN8pwH+WiS2OPCxJI8FuRJpTVnn6ZNFiqAM2aeW2LwTHWWmWgIyKC6cUo0L8aeKiF/14MNvnpls6R2PBeMQ==",
"dev": true,
"engines": {
"node": ">=12.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/postcss/"
},
"peerDependencies": {
"postcss": "^8.3.3"
}
},
"node_modules/postcss-selector-parser": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "6.0.9",
"resolved": "https://registry.npmjs.org/postcss-selector-parser/-/postcss-selector-parser-6.0.9.tgz",
"integrity": "sha512-UO3SgnZOVTwu4kyLR22UQ1xZh086RyNZppb7lLAKBFK8a32ttG5i87Y/P3+2bRSjZNyJ1B7hfFNo273tKe9YxQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"cssesc": "^3.0.0",
"util-deprecate": "^1.0.2"
},
"engines": {
"node": ">=4"
}
},
"node_modules/postcss-value-parser": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "4.2.0",
"resolved": "https://registry.npmjs.org/postcss-value-parser/-/postcss-value-parser-4.2.0.tgz",
"integrity": "sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/prelude-ls": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.1.2.tgz",
"integrity": "sha1-IZMqVJ9eUv/ZqCf1cOBL5iqX2lQ=",
"dev": true,
"engines": {
"node": ">= 0.8.0"
}
},
"node_modules/prettier": {
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"version": "2.5.1",
"resolved": "https://registry.npmjs.org/prettier/-/prettier-2.5.1.tgz",
"integrity": "sha512-vBZcPRUR5MZJwoyi3ZoyQlc1rXeEck8KgeC9AwwOn+exuxLxq5toTRDTSaVrXHxelDMHy9zlicw8u66yxoSUFg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"bin": {
"prettier": "bin-prettier.js"
},
"engines": {
"node": ">=10.13.0"
}
},
"node_modules/prettier-linter-helpers": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/prettier-linter-helpers/-/prettier-linter-helpers-1.0.0.tgz",
"integrity": "sha512-GbK2cP9nraSSUF9N2XwUwqfzlAFlMNYYl+ShE/V+H8a9uNl/oUqB1w2EL54Jh0OlyRSd8RfWYJ3coVS4TROP2w==",
"dev": true,
"dependencies": {
"fast-diff": "^1.1.2"
},
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/pretty-hrtime": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/pretty-hrtime/-/pretty-hrtime-1.0.3.tgz",
"integrity": "sha1-t+PqQkNaTJsnWdmeDyAesZWALuE=",
"dev": true,
"engines": {
"node": ">= 0.8"
}
},
"node_modules/process-nextick-args": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-2.0.0.tgz",
"integrity": "sha512-MtEC1TqN0EU5nephaJ4rAtThHtC86dNN9qCuEhtshvpVBkAW5ZO7BASN9REnF9eoXGcRub+pFuKEpOHE+HbEMw==",
"dev": true
},
"node_modules/progress": {
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/progress/-/progress-2.0.3.tgz",
"integrity": "sha512-7PiHtLll5LdnKIMw100I+8xJXR5gW2QwWYkT6iJva0bXitZKa/XMrSbdmg3r2Xnaidz9Qumd0VPaMrZlF9V9sA==",
"dev": true,
"engines": {
"node": ">=0.4.0"
}
},
"node_modules/promise": {
"version": "7.3.1",
"resolved": "https://registry.npmjs.org/promise/-/promise-7.3.1.tgz",
"integrity": "sha512-nolQXZ/4L+bP/UGlkfaIujX9BKxGwmQ9OT4mOt5yvy8iK1h3wqTEJCijzGANTCCl9nWjY41juyAn2K3Q1hLLTg==",
"dev": true,
"dependencies": {
"asap": "~2.0.3"
}
},
"node_modules/proxy-from-env": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/proxy-from-env/-/proxy-from-env-1.1.0.tgz",
"integrity": "sha512-D+zkORCbA9f1tdWRK0RaCR3GPv50cMxcrz4X8k5LTSUD1Dkw47mKJEZQNunItRTkWwgtaUSo1RVFRIG9ZXiFYg==",
"dev": true
},
"node_modules/prr": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/prr/-/prr-1.0.1.tgz",
"integrity": "sha1-0/wRS6BplaRexok/SEzrHXj19HY=",
"dev": true
},
"node_modules/pug": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/pug/-/pug-2.0.4.tgz",
"integrity": "sha512-XhoaDlvi6NIzL49nu094R2NA6P37ijtgMDuWE+ofekDChvfKnzFal60bhSdiy8y2PBO6fmz3oMEIcfpBVRUdvw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"pug-code-gen": "^2.0.2",
"pug-filters": "^3.1.1",
"pug-lexer": "^4.1.0",
"pug-linker": "^3.0.6",
"pug-load": "^2.0.12",
"pug-parser": "^5.0.1",
"pug-runtime": "^2.0.5",
"pug-strip-comments": "^1.0.4"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/pug-code-gen": {
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/pug-code-gen/-/pug-code-gen-2.0.3.tgz",
"integrity": "sha512-r9sezXdDuZJfW9J91TN/2LFbiqDhmltTFmGpHTsGdrNGp3p4SxAjjXEfnuK2e4ywYsRIVP0NeLbSAMHUcaX1EA==",
"dev": true,
"dependencies": {
"constantinople": "^3.1.2",
"doctypes": "^1.1.0",
"js-stringify": "^1.0.1",
"pug-attrs": "^2.0.4",
"pug-error": "^1.3.3",
"pug-runtime": "^2.0.5",
"void-elements": "^2.0.1",
"with": "^5.0.0"
}
},
"node_modules/pug-code-gen/node_modules/pug-attrs": {
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/pug-attrs/-/pug-attrs-2.0.4.tgz",
"integrity": "sha512-TaZ4Z2TWUPDJcV3wjU3RtUXMrd3kM4Wzjbe3EWnSsZPsJ3LDI0F3yCnf2/W7PPFF+edUFQ0HgDL1IoxSz5K8EQ==",
"dev": true,
"dependencies": {
"constantinople": "^3.0.1",
"js-stringify": "^1.0.1",
"pug-runtime": "^2.0.5"
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/pug-error": {
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"version": "1.3.3",
"resolved": "https://registry.npmjs.org/pug-error/-/pug-error-1.3.3.tgz",
"integrity": "sha512-qE3YhESP2mRAWMFJgKdtT5D7ckThRScXRwkfo+Erqga7dyJdY3ZquspprMCj/9sJ2ijm5hXFWQE/A3l4poMWiQ==",
"dev": true
},
"node_modules/pug-filters": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/pug-filters/-/pug-filters-3.1.1.tgz",
"integrity": "sha512-lFfjNyGEyVWC4BwX0WyvkoWLapI5xHSM3xZJFUhx4JM4XyyRdO8Aucc6pCygnqV2uSgJFaJWW3Ft1wCWSoQkQg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"clean-css": "^4.1.11",
"constantinople": "^3.0.1",
"jstransformer": "1.0.0",
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"pug-error": "^1.3.3",
"pug-walk": "^1.1.8",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"resolve": "^1.1.6",
"uglify-js": "^2.6.1"
}
},
"node_modules/pug-lexer": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/pug-lexer/-/pug-lexer-4.1.0.tgz",
"integrity": "sha512-i55yzEBtjm0mlplW4LoANq7k3S8gDdfC6+LThGEvsK4FuobcKfDAwt6V4jKPH9RtiE3a2Akfg5UpafZ1OksaPA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"character-parser": "^2.1.1",
"is-expression": "^3.0.0",
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"pug-error": "^1.3.3"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/pug-linker": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "3.0.6",
"resolved": "https://registry.npmjs.org/pug-linker/-/pug-linker-3.0.6.tgz",
"integrity": "sha512-bagfuHttfQOpANGy1Y6NJ+0mNb7dD2MswFG2ZKj22s8g0wVsojpRlqveEQHmgXXcfROB2RT6oqbPYr9EN2ZWzg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"pug-error": "^1.3.3",
"pug-walk": "^1.1.8"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/pug-load": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "2.0.12",
"resolved": "https://registry.npmjs.org/pug-load/-/pug-load-2.0.12.tgz",
"integrity": "sha512-UqpgGpyyXRYgJs/X60sE6SIf8UBsmcHYKNaOccyVLEuT6OPBIMo6xMPhoJnqtB3Q3BbO4Z3Bjz5qDsUWh4rXsg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"object-assign": "^4.1.0",
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"pug-walk": "^1.1.8"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/pug-parser": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/pug-parser/-/pug-parser-5.0.1.tgz",
"integrity": "sha512-nGHqK+w07p5/PsPIyzkTQfzlYfuqoiGjaoqHv1LjOv2ZLXmGX1O+4Vcvps+P4LhxZ3drYSljjq4b+Naid126wA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"pug-error": "^1.3.3",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"token-stream": "0.0.1"
}
},
"node_modules/pug-runtime": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/pug-runtime/-/pug-runtime-2.0.5.tgz",
"integrity": "sha512-P+rXKn9un4fQY77wtpcuFyvFaBww7/91f3jHa154qU26qFAnOe6SW1CbIDcxiG5lLK9HazYrMCCuDvNgDQNptw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/pug-strip-comments": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/pug-strip-comments/-/pug-strip-comments-1.0.4.tgz",
"integrity": "sha512-i5j/9CS4yFhSxHp5iKPHwigaig/VV9g+FgReLJWWHEHbvKsbqL0oP/K5ubuLco6Wu3Kan5p7u7qk8A4oLLh6vw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"pug-error": "^1.3.3"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/pug-walk": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "1.1.8",
"resolved": "https://registry.npmjs.org/pug-walk/-/pug-walk-1.1.8.tgz",
"integrity": "sha512-GMu3M5nUL3fju4/egXwZO0XLi6fW/K3T3VTgFQ14GxNi8btlxgT5qZL//JwZFm/2Fa64J/PNS8AZeys3wiMkVA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/pump": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/pump/-/pump-2.0.1.tgz",
"integrity": "sha512-ruPMNRkN3MHP1cWJc9OWr+T/xDP0jhXYCLfJcBuX54hhfIBnaQmAUMfDcG4DM5UMWByBbJY69QSphm3jtDKIkA==",
"dev": true,
"dependencies": {
"end-of-stream": "^1.1.0",
"once": "^1.3.1"
}
},
"node_modules/pumpify": {
"version": "1.5.1",
"resolved": "https://registry.npmjs.org/pumpify/-/pumpify-1.5.1.tgz",
"integrity": "sha512-oClZI37HvuUJJxSKKrC17bZ9Cu0ZYhEAGPsPUy9KlMUmv9dKX2o77RUmq7f3XjIxbwyGwYzbzQ1L2Ks8sIradQ==",
"dev": true,
"dependencies": {
"duplexify": "^3.6.0",
"inherits": "^2.0.3",
"pump": "^2.0.0"
}
},
"node_modules/punycode": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/punycode/-/punycode-2.1.1.tgz",
"integrity": "sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A==",
"dev": true,
"engines": {
"node": ">=6"
}
},
"node_modules/puppeteer": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "13.3.2",
"resolved": "https://registry.npmjs.org/puppeteer/-/puppeteer-13.3.2.tgz",
"integrity": "sha512-TIt8/R0eaUwY1c0/O0sCJpSglvGEWVoWFfGZ2dNtxX3eHuBo1ln9abaWfxTjZfsrkYATLSs8oqEdRZpMNnCsvg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"hasInstallScript": true,
"dependencies": {
Update npm packages
2022-02-20 18:08:23 +09:00
"cross-fetch": "3.1.5",
"debug": "4.3.3",
"devtools-protocol": "0.0.960912",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"extract-zip": "2.0.1",
"https-proxy-agent": "5.0.0",
"pkg-dir": "4.2.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"progress": "2.0.3",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"proxy-from-env": "1.1.0",
"rimraf": "3.0.2",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"tar-fs": "2.1.1",
"unbzip2-stream": "1.4.3",
Update npm packages
2022-02-20 18:08:23 +09:00
"ws": "8.5.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=10.18.1"
}
},
"node_modules/puppeteer/node_modules/debug": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "4.3.3",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.3.tgz",
"integrity": "sha512-/zxw5+vh1Tfv+4Qn7a5nsbcJKPaSvCDhojn6FEl9vupwK2VCSDtEiEtqr8DFtzYFOdz63LBkxec7DYuc2jon6Q==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/puppeteer/node_modules/ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
},
"node_modules/queue-microtask": {
"version": "1.2.3",
"resolved": "https://registry.npmjs.org/queue-microtask/-/queue-microtask-1.2.3.tgz",
"integrity": "sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
]
},
"node_modules/quick-lru": {
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-4.0.1.tgz",
"integrity": "sha512-ARhCpm70fzdcvNQfPoy49IaanKkTlRWF2JMzqhcJbhSFRZv7nPTvZJdcY7301IPmvW+/p0RgIWnQDLJxifsQ7g==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/randombytes": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/randombytes/-/randombytes-2.1.0.tgz",
"integrity": "sha512-vYl3iOX+4CKUWuxGi9Ukhie6fsqXqS9FE2Zaic4tNFD2N2QQaXOMFbuKK4QmDHC0JO6B1Zp41J0LpT0oR68amQ==",
"dev": true,
"dependencies": {
"safe-buffer": "^5.1.0"
}
},
"node_modules/read-pkg": {
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-5.2.0.tgz",
"integrity": "sha512-Ug69mNOpfvKDAc2Q8DRpMjjzdtrnv9HcSMX+4VsZxD1aZ6ZzrIE7rlzXBtWTyhULSMKg076AW6WR5iZpD0JiOg==",
"dev": true,
"dependencies": {
"@types/normalize-package-data": "^2.4.0",
"normalize-package-data": "^2.5.0",
"parse-json": "^5.0.0",
"type-fest": "^0.6.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/read-pkg-up": {
"version": "7.0.1",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-7.0.1.tgz",
"integrity": "sha512-zK0TB7Xd6JpCLmlLmufqykGE+/TlOePD6qKClNW7hHDKFh/J7/7gCWGR7joEQEW1bKq3a3yUZSObOoWLFQ4ohg==",
"dev": true,
"dependencies": {
"find-up": "^4.1.0",
"read-pkg": "^5.2.0",
"type-fest": "^0.8.1"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/read-pkg-up/node_modules/find-up": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-4.1.0.tgz",
"integrity": "sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw==",
"dev": true,
"dependencies": {
"locate-path": "^5.0.0",
"path-exists": "^4.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/read-pkg-up/node_modules/locate-path": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/locate-path/-/locate-path-5.0.0.tgz",
"integrity": "sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g==",
"dev": true,
"dependencies": {
"p-locate": "^4.1.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/read-pkg-up/node_modules/p-limit": {
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/p-limit/-/p-limit-2.3.0.tgz",
"integrity": "sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w==",
"dev": true,
"dependencies": {
"p-try": "^2.0.0"
},
"engines": {
"node": ">=6"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/read-pkg-up/node_modules/p-locate": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/p-locate/-/p-locate-4.1.0.tgz",
"integrity": "sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A==",
"dev": true,
"dependencies": {
"p-limit": "^2.2.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/read-pkg-up/node_modules/p-try": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/p-try/-/p-try-2.2.0.tgz",
"integrity": "sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ==",
"dev": true,
"engines": {
"node": ">=6"
}
},
"node_modules/read-pkg-up/node_modules/path-exists": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-4.0.0.tgz",
"integrity": "sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/read-pkg/node_modules/normalize-package-data": {
"version": "2.5.0",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.5.0.tgz",
"integrity": "sha512-/5CMN3T0R4XTj4DcGaexo+roZSdSFW/0AOOTROrjxzCG1wrWXEsGbRKevjlIL+ZDE4sZlJr5ED4YW0yqmkK+eA==",
"dev": true,
"dependencies": {
"hosted-git-info": "^2.1.4",
"resolve": "^1.10.0",
"semver": "2 || 3 || 4 || 5",
"validate-npm-package-license": "^3.0.1"
}
},
"node_modules/read-pkg/node_modules/parse-json": {
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-5.2.0.tgz",
"integrity": "sha512-ayCKvm/phCGxOkYRSCM82iDwct8/EonSEgCSxWxD7ve6jHggsFl4fZVQBPRNgQoKiuV/odhFrGzQXZwbifC8Rg==",
"dev": true,
"dependencies": {
"@babel/code-frame": "^7.0.0",
"error-ex": "^1.3.1",
"json-parse-even-better-errors": "^2.3.0",
"lines-and-columns": "^1.1.6"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/read-pkg/node_modules/resolve": {
"version": "1.20.0",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.20.0.tgz",
"integrity": "sha512-wENBPt4ySzg4ybFQW2TT1zMQucPK95HSh/nq2CFTZVOGut2+pQvSsgtda4d26YrYcr067wjbmzOG8byDPBX63A==",
"dev": true,
"dependencies": {
"is-core-module": "^2.2.0",
"path-parse": "^1.0.6"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/read-pkg/node_modules/type-fest": {
"version": "0.6.0",
"resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.6.0.tgz",
"integrity": "sha512-q+MB8nYR1KDLrgr4G5yemftpMC7/QLqVndBmEEdqzmNj5dcFOO4Oo8qlwZE3ULT3+Zim1F8Kq4cBnikNhlCMlg==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/readable-stream": {
"version": "2.3.6",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.6.tgz",
"integrity": "sha512-tQtKA9WIAhBF3+VLAseyMqZeBjW0AHJoxOtYqSUZNJxauErmLbVm2FW1y+J/YA9dUrAC39ITejlZWhVIwawkKw==",
"dev": true,
"dependencies": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"node_modules/readdirp": {
"version": "2.2.1",
"resolved": "https://registry.npmjs.org/readdirp/-/readdirp-2.2.1.tgz",
"integrity": "sha512-1JU/8q+VgFZyxwrJ+SVIOsh+KywWGpds3NTqikiKpDMZWScmAYyKIgqkO+ARvNWJfXeXR1zxz7aHF4u4CyH6vQ==",
"dev": true,
"dependencies": {
"graceful-fs": "^4.1.11",
"micromatch": "^3.1.10",
"readable-stream": "^2.0.2"
},
"engines": {
"node": ">=0.10"
}
},
"node_modules/rechoir": {
"version": "0.6.2",
"resolved": "https://registry.npmjs.org/rechoir/-/rechoir-0.6.2.tgz",
"integrity": "sha1-hSBLVNuoLVdC4oyWdW70OvUOM4Q=",
"dev": true,
"dependencies": {
"resolve": "^1.1.6"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/redent": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/redent/-/redent-3.0.0.tgz",
"integrity": "sha512-6tDA8g98We0zd0GvVeMT9arEOnTw9qM03L9cJXaCjrip1OO764RDBLBfrB4cwzNGDj5OA5ioymC9GkizgWJDUg==",
"dev": true,
"dependencies": {
"indent-string": "^4.0.0",
"strip-indent": "^3.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/regenerate": {
"version": "1.4.2",
"resolved": "https://registry.npmjs.org/regenerate/-/regenerate-1.4.2.tgz",
"integrity": "sha512-zrceR/XhGYU/d/opr2EKO7aRHUeiBI8qjtfHqADTwZd6Szfy16la6kqD0MIUs5z5hx6AaKa+PixpPrR289+I0A==",
"dev": true
},
Update npm packages
2022-01-09 18:05:52 +09:00
"node_modules/regenerate-unicode-properties": {
"version": "9.0.0",
"resolved": "https://registry.npmjs.org/regenerate-unicode-properties/-/regenerate-unicode-properties-9.0.0.tgz",
"integrity": "sha512-3E12UeNSPfjrgwjkR81m5J7Aw/T55Tu7nUyZVQYCKEOs+2dkxEY+DpPtZzO4YruuiPb7NkYLVcyJC4+zCbk5pA==",
"dev": true,
"dependencies": {
"regenerate": "^1.4.2"
},
"engines": {
"node": ">=4"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/regenerator-runtime": {
"version": "0.11.1",
"resolved": "https://registry.npmjs.org/regenerator-runtime/-/regenerator-runtime-0.11.1.tgz",
"integrity": "sha512-MguG95oij0fC3QV3URf4V2SDYGJhJnJGqvIIgdECeODCT98wSWDAJ94SSuVpYQUoTcGUIL6L4yNB7j1DFFHSBg==",
"dev": true
},
"node_modules/regenerator-transform": {
"version": "0.14.5",
"resolved": "https://registry.npmjs.org/regenerator-transform/-/regenerator-transform-0.14.5.tgz",
"integrity": "sha512-eOf6vka5IO151Jfsw2NO9WpGX58W6wWmefK3I1zEGr0lOD0u8rwPaNqQL1aRxUaxLeKO3ArNh3VYg1KbaD+FFw==",
"dev": true,
"dependencies": {
"@babel/runtime": "^7.8.4"
}
},
"node_modules/regex-not": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/regex-not/-/regex-not-1.0.2.tgz",
"integrity": "sha512-J6SDjUgDxQj5NusnOtdFxDwN/+HWykR8GELwctJ7mdqhcyy1xEc4SRFHUXvxTp661YaVKAjfRLZ9cCqS6tn32A==",
"dev": true,
"dependencies": {
"extend-shallow": "^3.0.2",
"safe-regex": "^1.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/regexp-tree": {
"version": "0.1.24",
"resolved": "https://registry.npmjs.org/regexp-tree/-/regexp-tree-0.1.24.tgz",
"integrity": "sha512-s2aEVuLhvnVJW6s/iPgEGK6R+/xngd2jNQ+xy4bXNDKxZKJH6jpPHY6kVeVv1IeLCHgswRj+Kl3ELaDjG6V1iw==",
"dev": true,
"bin": {
"regexp-tree": "bin/regexp-tree"
}
},
"node_modules/regexpp": {
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/regexpp/-/regexpp-3.2.0.tgz",
"integrity": "sha512-pq2bWo9mVD43nbts2wGv17XLiNLya+GklZ8kaDLV2Z08gDCsGpnKn9BFMepvWuHCbyVvY7J5o5+BVvoQbmlJLg==",
"dev": true,
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/mysticatea"
}
},
"node_modules/regexpu-core": {
"version": "4.8.0",
"resolved": "https://registry.npmjs.org/regexpu-core/-/regexpu-core-4.8.0.tgz",
"integrity": "sha512-1F6bYsoYiz6is+oz70NWur2Vlh9KWtswuRuzJOfeYUrfPX2o8n74AnUVaOGDbUqVGO9fNHu48/pjJO4sNVwsOg==",
"dev": true,
"dependencies": {
"regenerate": "^1.4.2",
"regenerate-unicode-properties": "^9.0.0",
"regjsgen": "^0.5.2",
"regjsparser": "^0.7.0",
"unicode-match-property-ecmascript": "^2.0.0",
"unicode-match-property-value-ecmascript": "^2.0.0"
},
"engines": {
"node": ">=4"
}
},
Update npm packages
2022-01-09 18:05:52 +09:00
"node_modules/regjsgen": {
"version": "0.5.2",
"resolved": "https://registry.npmjs.org/regjsgen/-/regjsgen-0.5.2.tgz",
"integrity": "sha512-OFFT3MfrH90xIW8OOSyUrk6QHD5E9JOTeGodiJeBS3J6IwlgzJMNE/1bZklWz5oTg+9dCMyEetclvCVXOPoN3A==",
"dev": true
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
Update npm packages
2022-01-09 18:05:52 +09:00
"node_modules/regjsparser": {
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"version": "0.7.0",
"resolved": "https://registry.npmjs.org/regjsparser/-/regjsparser-0.7.0.tgz",
"integrity": "sha512-A4pcaORqmNMDVwUjWoTzuhwMGpP+NykpfqAsEgI1FSH/EzC7lrN5TMd+kN8YCovX+jMpu8eaqXgXPCa0g8FQNQ==",
"dev": true,
"dependencies": {
"jsesc": "~0.5.0"
},
"bin": {
"regjsparser": "bin/parser"
}
},
Update npm packages
2022-01-09 18:05:52 +09:00
"node_modules/regjsparser/node_modules/jsesc": {
"version": "0.5.0",
"resolved": "https://registry.npmjs.org/jsesc/-/jsesc-0.5.0.tgz",
"integrity": "sha1-597mbjXW/Bb3EP6R1c9p9w8IkR0=",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
Update npm packages
2022-01-09 18:05:52 +09:00
"bin": {
"jsesc": "bin/jsesc"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/remove-bom-buffer": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/remove-bom-buffer/-/remove-bom-buffer-3.0.0.tgz",
"integrity": "sha512-8v2rWhaakv18qcvNeli2mZ/TMTL2nEyAKRvzo1WtnZBl15SHyEhrCu2/xKlJyUFKHiHgfXIyuY6g2dObJJycXQ==",
"dev": true,
"dependencies": {
"is-buffer": "^1.1.5",
"is-utf8": "^0.2.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/remove-bom-stream": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/remove-bom-stream/-/remove-bom-stream-1.2.0.tgz",
"integrity": "sha1-BfGlk/FuQuH7kOv1nejlaVJflSM=",
"dev": true,
"dependencies": {
"remove-bom-buffer": "^3.0.0",
"safe-buffer": "^5.1.0",
"through2": "^2.0.3"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/remove-bom-stream/node_modules/through2": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.5.tgz",
"integrity": "sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==",
"dev": true,
"dependencies": {
"readable-stream": "~2.3.6",
"xtend": "~4.0.1"
}
},
"node_modules/remove-trailing-separator": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/remove-trailing-separator/-/remove-trailing-separator-1.1.0.tgz",
"integrity": "sha1-wkvOKig62tW8P1jg1IJJuSN52O8=",
"dev": true
},
"node_modules/repeat-element": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/repeat-element/-/repeat-element-1.1.2.tgz",
"integrity": "sha1-7wiaF40Ug7quTZPrmLT55OEdmQo=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/repeat-string": {
"version": "1.6.1",
"resolved": "https://registry.npmjs.org/repeat-string/-/repeat-string-1.6.1.tgz",
"integrity": "sha1-jcrkcOHIirwtYA//Sndihtp15jc=",
"dev": true,
"engines": {
"node": ">=0.10"
}
},
"node_modules/replace-ext": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/replace-ext/-/replace-ext-1.0.0.tgz",
"integrity": "sha1-3mMSg3P8v3w8z6TeWkgMRaZ5WOs=",
"dev": true,
"engines": {
"node": ">= 0.10"
}
},
"node_modules/replace-homedir": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/replace-homedir/-/replace-homedir-1.0.0.tgz",
"integrity": "sha1-6H9tUTuSjd6AgmDBK+f+xv9ueYw=",
"dev": true,
"dependencies": {
"homedir-polyfill": "^1.0.1",
"is-absolute": "^1.0.0",
"remove-trailing-separator": "^1.1.0"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/replacestream": {
"version": "4.0.3",
"resolved": "https://registry.npmjs.org/replacestream/-/replacestream-4.0.3.tgz",
"integrity": "sha512-AC0FiLS352pBBiZhd4VXB1Ab/lh0lEgpP+GGvZqbQh8a5cmXVoTe5EX/YeTFArnp4SRGTHh1qCHu9lGs1qG8sA==",
"dev": true,
"dependencies": {
"escape-string-regexp": "^1.0.3",
"object-assign": "^4.0.1",
"readable-stream": "^2.0.2"
}
},
"node_modules/require-directory": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/require-directory/-/require-directory-2.1.1.tgz",
"integrity": "sha1-jGStX9MNqxyXbiNE/+f3kqam30I=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/require-from-string": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/require-from-string/-/require-from-string-2.0.2.tgz",
"integrity": "sha512-Xf0nWe6RseziFMu+Ap9biiUbmplq6S9/p+7w7YXP/JBHhrUDDUhwa+vANyubuqfZWTveU//DYVGsDG7RKL/vEw==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/require-main-filename": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/require-main-filename/-/require-main-filename-1.0.1.tgz",
"integrity": "sha1-l/cXtp1IeE9fUmpsWqj/3aBVpNE=",
"dev": true
},
"node_modules/requizzle": {
"version": "0.2.3",
"resolved": "https://registry.npmjs.org/requizzle/-/requizzle-0.2.3.tgz",
"integrity": "sha512-YanoyJjykPxGHii0fZP0uUPEXpvqfBDxWV7s6GKAiiOsiqhX6vHNyW3Qzdmqp/iq/ExbhaGbVrjB4ruEVSM4GQ==",
"dev": true,
"dependencies": {
"lodash": "^4.17.14"
}
},
"node_modules/resolve": {
"version": "1.7.1",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.7.1.tgz",
"integrity": "sha512-c7rwLofp8g1U+h1KNyHL/jicrKg1Ek4q+Lr33AL65uZTinUZHe30D5HlyN5V9NW0JX1D5dXQ4jqW5l7Sy/kGfw==",
"dev": true,
"dependencies": {
"path-parse": "^1.0.5"
}
},
"node_modules/resolve-dir": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/resolve-dir/-/resolve-dir-1.0.1.tgz",
"integrity": "sha1-eaQGRMNivoLybv/nOcm7U4IEb0M=",
"dev": true,
"dependencies": {
"expand-tilde": "^2.0.0",
"global-modules": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/resolve-from": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-4.0.0.tgz",
"integrity": "sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==",
"dev": true,
"engines": {
"node": ">=4"
}
},
"node_modules/resolve-options": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/resolve-options/-/resolve-options-1.1.0.tgz",
"integrity": "sha1-MrueOcBtZzONyTeMDW1gdFZq0TE=",
"dev": true,
"dependencies": {
"value-or-function": "^3.0.0"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/resolve-url": {
"version": "0.2.1",
"resolved": "https://registry.npmjs.org/resolve-url/-/resolve-url-0.2.1.tgz",
"integrity": "sha1-LGN/53yJOv0qZj/iGqkIAGjiBSo=",
"deprecated": "https://github.com/lydell/resolve-url#deprecated",
"dev": true
},
"node_modules/ret": {
"version": "0.1.15",
"resolved": "https://registry.npmjs.org/ret/-/ret-0.1.15.tgz",
"integrity": "sha512-TTlYpa+OL+vMMNG24xSlQGEJ3B/RzEfUlLct7b5G/ytav+wPrplCpVMFuwzXbkecJrb6IYo1iFb0S9v37754mg==",
"dev": true,
"engines": {
"node": ">=0.12"
}
},
"node_modules/reusify": {
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/reusify/-/reusify-1.0.4.tgz",
"integrity": "sha512-U9nH88a3fc/ekCF1l0/UP1IosiuIjyTh7hBvXVMHYgVcfGvt897Xguj2UOLDeI5BG2m7/uwyaLVT6fbtCwTyzw==",
"dev": true,
"engines": {
"iojs": ">=1.0.0",
"node": ">=0.10.0"
}
},
"node_modules/right-align": {
"version": "0.1.3",
"resolved": "https://registry.npmjs.org/right-align/-/right-align-0.1.3.tgz",
"integrity": "sha1-YTObci/mo1FWiSENJOFMlhSGE+8=",
"dev": true,
"dependencies": {
"align-text": "^0.1.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/rimraf": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-3.0.2.tgz",
"integrity": "sha512-JZkJMZkAGFFPP2YqXZXPbMlMBgsxzE8ILs4lMIX/2o0L9UBw9O/Y3o6wFw/i9YLapcUJWwqbi3kdxIPdC62TIA==",
"dev": true,
"dependencies": {
"glob": "^7.1.3"
},
"bin": {
"rimraf": "bin.js"
},
"funding": {
"url": "https://github.com/sponsors/isaacs"
}
},
"node_modules/rimraf/node_modules/glob": {
"version": "7.1.6",
"resolved": "https://registry.npmjs.org/glob/-/glob-7.1.6.tgz",
"integrity": "sha512-LwaxwyZ72Lk7vZINtNNrywX0ZuLyStrdDtabefZKAY5ZGJhVtgdznluResxNmPitE0SAO+O26sWTHeKSI2wMBA==",
"dev": true,
"dependencies": {
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
"minimatch": "^3.0.4",
"once": "^1.3.0",
"path-is-absolute": "^1.0.0"
},
"engines": {
"node": "*"
},
"funding": {
"url": "https://github.com/sponsors/isaacs"
}
},
"node_modules/run-parallel": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/run-parallel/-/run-parallel-1.2.0.tgz",
"integrity": "sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
],
"dependencies": {
"queue-microtask": "^1.2.2"
}
},
"node_modules/safe-buffer": {
"version": "5.1.2",
"resolved": "https://registry.npmjs.org/safe-buffer/-/safe-buffer-5.1.2.tgz",
"integrity": "sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==",
"dev": true
},
"node_modules/safe-regex": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/safe-regex/-/safe-regex-1.1.0.tgz",
"integrity": "sha1-QKNmnzsHfR6UPURinhV91IAjvy4=",
"dev": true,
"dependencies": {
"ret": "~0.1.10"
}
},
"node_modules/safer-buffer": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/safer-buffer/-/safer-buffer-2.1.2.tgz",
"integrity": "sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==",
"dev": true
},
"node_modules/sax": {
"version": "1.2.4",
"resolved": "https://registry.npmjs.org/sax/-/sax-1.2.4.tgz",
"integrity": "sha512-NqVDv9TpANUjFm0N8uM5GxL36UgKi9/atZw+x7YFnQ8ckwFGKrl4xX4yWtrey3UJm5nP1kUbnYgLopqWNSRhWw==",
"dev": true
},
"node_modules/schema-utils": {
"version": "2.7.1",
"resolved": "https://registry.npmjs.org/schema-utils/-/schema-utils-2.7.1.tgz",
"integrity": "sha512-SHiNtMOUGWBQJwzISiVYKu82GiV4QYGePp3odlY1tuKO7gPtphAT5R/py0fA6xtbgLL/RvtJZnU9b8s0F1q0Xg==",
"dev": true,
"dependencies": {
"@types/json-schema": "^7.0.5",
"ajv": "^6.12.4",
"ajv-keywords": "^3.5.2"
},
"engines": {
"node": ">= 8.9.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
}
},
"node_modules/semver": {
"version": "5.5.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-5.5.0.tgz",
"integrity": "sha512-4SJ3dm0WAwWy/NVeioZh5AntkdJoWKxHxcmyP622fOkgHa4z3R0TdBJICINyaSDE6uNwVc8gZr+ZinwZAH4xIA==",
"dev": true,
"bin": {
"semver": "bin/semver"
}
},
"node_modules/semver-greatest-satisfied-range": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/semver-greatest-satisfied-range/-/semver-greatest-satisfied-range-1.1.0.tgz",
"integrity": "sha1-E+jCZYq5aRywzXEJMkAoDTb3els=",
"dev": true,
"dependencies": {
"sver-compat": "^1.5.0"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/serialize-javascript": {
"version": "6.0.0",
"resolved": "https://registry.npmjs.org/serialize-javascript/-/serialize-javascript-6.0.0.tgz",
"integrity": "sha512-Qr3TosvguFt8ePWqsvRfrKyQXIiW+nGbYpy8XK24NQHE83caxWt+mIymTT19DGFbNWNLfEwsrkSmN64lVWB9ag==",
"dev": true,
"dependencies": {
"randombytes": "^2.1.0"
}
},
"node_modules/server-destroy": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/server-destroy/-/server-destroy-1.0.1.tgz",
"integrity": "sha1-8Tv5KOQrnD55OD5hzDmYtdFObN0=",
"dev": true
},
"node_modules/set-blocking": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/set-blocking/-/set-blocking-2.0.0.tgz",
"integrity": "sha1-BF+XgtARrppoA93TgrJDkrPYkPc=",
"dev": true
},
"node_modules/set-value": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/set-value/-/set-value-2.0.1.tgz",
"integrity": "sha512-JxHc1weCN68wRY0fhCoXpyK55m/XPHafOmK4UWD7m2CI14GMcFypt4w/0+NV5f/ZMby2F6S2wwA7fgynh9gWSw==",
"dev": true,
"dependencies": {
"extend-shallow": "^2.0.1",
"is-extendable": "^0.1.1",
"is-plain-object": "^2.0.3",
"split-string": "^3.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/set-value/node_modules/extend-shallow": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/extend-shallow/-/extend-shallow-2.0.1.tgz",
"integrity": "sha1-Ua99YUrZqfYQ6huvu5idaxxWiQ8=",
"dev": true,
"dependencies": {
"is-extendable": "^0.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/side-channel": {
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/side-channel/-/side-channel-1.0.4.tgz",
"integrity": "sha512-q5XPytqFEIKHkGdiMIrY10mvLRvnQh42/+GoBlFW3b2LXLE2xxJpZFdm94we0BaoV3RwJyGqg5wS7epxTv0Zvw==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.0",
"get-intrinsic": "^1.0.2",
"object-inspect": "^1.9.0"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/signal-exit": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "3.0.7",
"resolved": "https://registry.npmjs.org/signal-exit/-/signal-exit-3.0.7.tgz",
"integrity": "sha512-wnD2ZE+l+SPC/uoS0vXeE9L1+0wuaMqKlfz9AMUo38JsyLSBWSFcHR1Rri62LZc12vLr1gb3jl7iwQhgwpAbGQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/simple-concat": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/simple-concat/-/simple-concat-1.0.1.tgz",
"integrity": "sha512-cSFtAPtRhljv69IK0hTVZQ+OfE9nePi/rtJmw5UjHeVyVroEqJXP1sFztKUy1qU+xvz3u/sfYJLa947b7nAN2Q==",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
]
},
"node_modules/simple-get": {
Bump simple-get from 3.1.0 to 3.1.1 Bumps [simple-get](https://github.com/feross/simple-get) from 3.1.0 to 3.1.1. - [Release notes](https://github.com/feross/simple-get/releases) - [Commits](https://github.com/feross/simple-get/compare/v3.1.0...v3.1.1) --- updated-dependencies: - dependency-name: simple-get dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-06 21:14:16 +09:00
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/simple-get/-/simple-get-3.1.1.tgz",
"integrity": "sha512-CQ5LTKGfCpvE1K0n2us+kuMPbk/q0EKl82s4aheV9oXjFEz6W/Y7oQFVJuU6QG77hRT4Ghb5RURteF5vnWjupA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"decompress-response": "^4.2.0",
"once": "^1.3.1",
"simple-concat": "^1.0.0"
}
},
"node_modules/simple-swizzle": {
"version": "0.2.2",
"resolved": "https://registry.npmjs.org/simple-swizzle/-/simple-swizzle-0.2.2.tgz",
"integrity": "sha1-pNprY1/8zMoz9w0Xy5JZLeleVXo=",
"dev": true,
"dependencies": {
"is-arrayish": "^0.3.1"
}
},
"node_modules/simple-swizzle/node_modules/is-arrayish": {
"version": "0.3.2",
"resolved": "https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.3.2.tgz",
"integrity": "sha512-eVRqCvVlZbuw3GrM63ovNSNAeA1K16kaR/LRY/92w0zxQ5/1YzwblUX652i4Xs9RwAGjW9d9y6X88t8OaAJfWQ==",
"dev": true
},
"node_modules/slash": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/slash/-/slash-3.0.0.tgz",
"integrity": "sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/slice-ansi": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/slice-ansi/-/slice-ansi-4.0.0.tgz",
"integrity": "sha512-qMCMfhY040cVHT43K9BFygqYbUPFZKHOg7K73mtTWJRb8pyP3fzf4Ixd5SzdEJQ6MRUg/WBnOLxghZtKKurENQ==",
"dev": true,
"dependencies": {
"ansi-styles": "^4.0.0",
"astral-regex": "^2.0.0",
"is-fullwidth-code-point": "^3.0.0"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/chalk/slice-ansi?sponsor=1"
}
},
"node_modules/slice-ansi/node_modules/ansi-styles": {
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz",
"integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==",
"dev": true,
"dependencies": {
"color-convert": "^2.0.1"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/chalk/ansi-styles?sponsor=1"
}
},
"node_modules/slice-ansi/node_modules/color-convert": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz",
"integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==",
"dev": true,
"dependencies": {
"color-name": "~1.1.4"
},
"engines": {
"node": ">=7.0.0"
}
},
"node_modules/slice-ansi/node_modules/is-fullwidth-code-point": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz",
"integrity": "sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/slugg": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/slugg/-/slugg-1.2.1.tgz",
"integrity": "sha1-51KvIkGvPycURjxd4iXOpHYIdAo=",
"dev": true
},
"node_modules/snapdragon": {
"version": "0.8.2",
"resolved": "https://registry.npmjs.org/snapdragon/-/snapdragon-0.8.2.tgz",
"integrity": "sha512-FtyOnWN/wCHTVXOMwvSv26d+ko5vWlIDD6zoUJ7LW8vh+ZBC8QdljveRP+crNrtBwioEUWy/4dMtbBjA4ioNlg==",
"dev": true,
"dependencies": {
"base": "^0.11.1",
"debug": "^2.2.0",
"define-property": "^0.2.5",
"extend-shallow": "^2.0.1",
"map-cache": "^0.2.2",
"source-map": "^0.5.6",
"source-map-resolve": "^0.5.0",
"use": "^3.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/snapdragon-node": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/snapdragon-node/-/snapdragon-node-2.1.1.tgz",
"integrity": "sha512-O27l4xaMYt/RSQ5TR3vpWCAB5Kb/czIcqUFOM/C4fYcLnbZUc1PkjTAMjof2pBWaSTwOUd6qUHcFGVGj7aIwnw==",
"dev": true,
"dependencies": {
"define-property": "^1.0.0",
"isobject": "^3.0.0",
"snapdragon-util": "^3.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/snapdragon-node/node_modules/define-property": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-1.0.0.tgz",
"integrity": "sha1-dp66rz9KY6rTr56NMEybvnm/sOY=",
"dev": true,
"dependencies": {
"is-descriptor": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/snapdragon-node/node_modules/is-accessor-descriptor": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-accessor-descriptor/-/is-accessor-descriptor-1.0.0.tgz",
"integrity": "sha512-m5hnHTkcVsPfqx3AKlyttIPb7J+XykHvJP2B9bZDjlhLIoEq4XoK64Vg7boZlVWYK6LUY94dYPEE7Lh0ZkZKcQ==",
"dev": true,
"dependencies": {
"kind-of": "^6.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/snapdragon-node/node_modules/is-data-descriptor": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-data-descriptor/-/is-data-descriptor-1.0.0.tgz",
"integrity": "sha512-jbRXy1FmtAoCjQkVmIVYwuuqDFUbaOeDjmed1tOGPrsMhtJA4rD9tkgA0F1qJ3gRFRXcHYVkdeaP50Q5rE/jLQ==",
"dev": true,
"dependencies": {
"kind-of": "^6.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/snapdragon-node/node_modules/is-descriptor": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/is-descriptor/-/is-descriptor-1.0.2.tgz",
"integrity": "sha512-2eis5WqQGV7peooDyLmNEPUrps9+SXX5c9pL3xEB+4e9HnGuDa7mB7kHxHw4CbqS9k1T2hOH3miL8n8WtiYVtg==",
"dev": true,
"dependencies": {
"is-accessor-descriptor": "^1.0.0",
"is-data-descriptor": "^1.0.0",
"kind-of": "^6.0.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/snapdragon-util": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/snapdragon-util/-/snapdragon-util-3.0.1.tgz",
"integrity": "sha512-mbKkMdQKsjX4BAL4bRYTj21edOf8cN7XHdYUJEe+Zn99hVEYcMvKPct1IqNe7+AZPirn8BCDOQBHQZknqmKlZQ==",
"dev": true,
"dependencies": {
"kind-of": "^3.2.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/snapdragon-util/node_modules/kind-of": {
"version": "3.2.2",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz",
"integrity": "sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=",
"dev": true,
"dependencies": {
"is-buffer": "^1.1.5"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/snapdragon/node_modules/define-property": {
"version": "0.2.5",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-0.2.5.tgz",
"integrity": "sha1-w1se+RjsPJkPmlvFe+BKrOxcgRY=",
"dev": true,
"dependencies": {
"is-descriptor": "^0.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/snapdragon/node_modules/extend-shallow": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/extend-shallow/-/extend-shallow-2.0.1.tgz",
"integrity": "sha1-Ua99YUrZqfYQ6huvu5idaxxWiQ8=",
"dev": true,
"dependencies": {
"is-extendable": "^0.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/snapdragon/node_modules/source-map": {
"version": "0.5.7",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.7.tgz",
"integrity": "sha1-igOdLRAh0i0eoUyA2OpGi6LvP8w=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/source-map": {
"version": "0.6.1",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.6.1.tgz",
"integrity": "sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/source-map-js": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/source-map-js/-/source-map-js-1.0.2.tgz",
"integrity": "sha512-R0XvVJ9WusLiqTCEiGCmICCMplcCkIwwR11mOSD9CR5u+IXYdiseeEuXCVAjS54zqwkLcPNnmU4OeJ6tUrWhDw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/source-map-resolve": {
"version": "0.5.2",
"resolved": "https://registry.npmjs.org/source-map-resolve/-/source-map-resolve-0.5.2.tgz",
"integrity": "sha512-MjqsvNwyz1s0k81Goz/9vRBe9SZdB09Bdw+/zYyO+3CuPk6fouTaxscHkgtE8jKvf01kVfl8riHzERQ/kefaSA==",
"dev": true,
"dependencies": {
"atob": "^2.1.1",
"decode-uri-component": "^0.2.0",
"resolve-url": "^0.2.1",
"source-map-url": "^0.4.0",
"urix": "^0.1.0"
}
},
"node_modules/source-map-support": {
"version": "0.5.20",
"resolved": "https://registry.npmjs.org/source-map-support/-/source-map-support-0.5.20.tgz",
"integrity": "sha512-n1lZZ8Ve4ksRqizaBQgxXDgKwttHDhyfQjA6YZZn8+AroHbsIz+JjwxQDxbp+7y5OYCI8t1Yk7etjD9CRd2hIw==",
"dev": true,
"dependencies": {
"buffer-from": "^1.0.0",
"source-map": "^0.6.0"
}
},
"node_modules/source-map-url": {
"version": "0.4.0",
"resolved": "https://registry.npmjs.org/source-map-url/-/source-map-url-0.4.0.tgz",
"integrity": "sha1-PpNdfd1zYxuXZZlW1VEo6HtQhKM=",
"dev": true
},
"node_modules/sparkles": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.1.tgz",
"integrity": "sha512-dSO0DDYUahUt/0/pD/Is3VIm5TGJjludZ0HVymmhYF6eNA53PVLhnUk0znSYbH8IYBuJdCE+1luR22jNLMaQdw==",
"dev": true,
"engines": {
"node": ">= 0.10"
}
},
"node_modules/spdx-correct": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-3.0.0.tgz",
"integrity": "sha512-N19o9z5cEyc8yQQPukRCZ9EUmb4HUpnrmaL/fxS2pBo2jbfcFRVuFZ/oFC+vZz0MNNk0h80iMn5/S6qGZOL5+g==",
"dev": true,
"dependencies": {
"spdx-expression-parse": "^3.0.0",
"spdx-license-ids": "^3.0.0"
}
},
"node_modules/spdx-exceptions": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-2.1.0.tgz",
"integrity": "sha512-4K1NsmrlCU1JJgUrtgEeTVyfx8VaYea9J9LvARxhbHtVtohPs/gFGG5yy49beySjlIMhhXZ4QqujIZEfS4l6Cg==",
"dev": true
},
"node_modules/spdx-expression-parse": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-3.0.0.tgz",
"integrity": "sha512-Yg6D3XpRD4kkOmTpdgbUiEJFKghJH03fiC1OPll5h/0sO6neh2jqRDVHOQ4o/LMea0tgCkbMgea5ip/e+MkWyg==",
"dev": true,
"dependencies": {
"spdx-exceptions": "^2.1.0",
"spdx-license-ids": "^3.0.0"
}
},
"node_modules/spdx-license-ids": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-3.0.0.tgz",
"integrity": "sha512-2+EPwgbnmOIl8HjGBXXMd9NAu02vLjOO1nWw4kmeRDFyHn+M/ETfHxQUK0oXg8ctgVnl9t3rosNVsZ1jG61nDA==",
"dev": true
},
"node_modules/specificity": {
"version": "0.4.1",
"resolved": "https://registry.npmjs.org/specificity/-/specificity-0.4.1.tgz",
"integrity": "sha512-1klA3Gi5PD1Wv9Q0wUoOQN1IWAuPu0D1U03ThXTr0cJ20+/iq2tHSDnK7Kk/0LXJ1ztUB2/1Os0wKmfyNgUQfg==",
"dev": true,
"bin": {
"specificity": "bin/specificity"
}
},
"node_modules/split-string": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/split-string/-/split-string-3.1.0.tgz",
"integrity": "sha512-NzNVhJDYpwceVVii8/Hu6DKfD2G+NrQHlS/V/qgv763EYudVwEcMQNxd2lh+0VrUByXN/oJkl5grOhYWvQUYiw==",
"dev": true,
"dependencies": {
"extend-shallow": "^3.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/sprintf-js": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.0.3.tgz",
"integrity": "sha1-BOaSb2YolTVPPdAVIDYzuFcpfiw=",
"dev": true
},
"node_modules/stack-trace": {
"version": "0.0.10",
"resolved": "https://registry.npmjs.org/stack-trace/-/stack-trace-0.0.10.tgz",
"integrity": "sha1-VHxws0fo0ytOEI6hoqFZ5f3eGcA=",
"dev": true,
"engines": {
"node": "*"
}
},
"node_modules/static-extend": {
"version": "0.1.2",
"resolved": "https://registry.npmjs.org/static-extend/-/static-extend-0.1.2.tgz",
"integrity": "sha1-YICcOcv/VTNyJv1eC1IPNB8ftcY=",
"dev": true,
"dependencies": {
"define-property": "^0.2.5",
"object-copy": "^0.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/static-extend/node_modules/define-property": {
"version": "0.2.5",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-0.2.5.tgz",
"integrity": "sha1-w1se+RjsPJkPmlvFe+BKrOxcgRY=",
"dev": true,
"dependencies": {
"is-descriptor": "^0.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/stream-exhaust": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/stream-exhaust/-/stream-exhaust-1.0.2.tgz",
"integrity": "sha512-b/qaq/GlBK5xaq1yrK9/zFcyRSTNxmcZwFLGSTG0mXgZl/4Z6GgiyYOXOvY7N3eEvFRAG1bkDRz5EPGSvPYQlw==",
"dev": true
},
"node_modules/stream-shift": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/stream-shift/-/stream-shift-1.0.0.tgz",
"integrity": "sha1-1cdSgl5TZ+eG944Y5EXqIjoVWVI=",
"dev": true
},
"node_modules/streamqueue": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/streamqueue/-/streamqueue-1.1.2.tgz",
"integrity": "sha512-CHUpqa+1BM99z7clQz9W6L9ZW4eXRRQCR0H+utVAGGvNo2ePlJAFjhdK0IjunaBbY/gWKJawk5kpJeyz0EXxRA==",
"dev": true,
"dependencies": {
"isstream": "^0.1.2",
"readable-stream": "^2.3.3"
},
"engines": {
"node": ">=6.9.5"
}
},
"node_modules/string_decoder": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-1.1.1.tgz",
"integrity": "sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==",
"dev": true,
"dependencies": {
"safe-buffer": "~5.1.0"
}
},
"node_modules/string-width": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/string-width/-/string-width-1.0.2.tgz",
"integrity": "sha1-EYvfW4zcUaKn5w0hHgfisLmxB9M=",
"dev": true,
"dependencies": {
"code-point-at": "^1.0.0",
"is-fullwidth-code-point": "^1.0.0",
"strip-ansi": "^3.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/string.prototype.trimend": {
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/string.prototype.trimend/-/string.prototype.trimend-1.0.4.tgz",
"integrity": "sha512-y9xCjw1P23Awk8EvTpcyL2NIr1j7wJ39f+k6lvRnSMz+mz9CGz9NYPelDk42kOz6+ql8xjfK8oYzy3jAP5QU5A==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.2",
"define-properties": "^1.1.3"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/string.prototype.trimend/node_modules/define-properties": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.1.3.tgz",
"integrity": "sha512-3MqfYKj2lLzdMSf8ZIZE/V+Zuy+BgD6f164e8K2w7dgnpKArBDerGYpM46IYYcjnkdPNMjPk9A6VFB8+3SKlXQ==",
"dev": true,
"dependencies": {
"object-keys": "^1.0.12"
},
"engines": {
"node": ">= 0.4"
}
},
"node_modules/string.prototype.trimend/node_modules/object-keys": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz",
"integrity": "sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==",
"dev": true,
"engines": {
"node": ">= 0.4"
}
},
"node_modules/string.prototype.trimstart": {
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/string.prototype.trimstart/-/string.prototype.trimstart-1.0.4.tgz",
"integrity": "sha512-jh6e984OBfvxS50tdY2nRZnoC5/mLFKOREQfw8t5yytkoUsJRNxvI/E39qu1sD0OtWI3OC0XgKSmcWwziwYuZw==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.2",
"define-properties": "^1.1.3"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/string.prototype.trimstart/node_modules/define-properties": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.1.3.tgz",
"integrity": "sha512-3MqfYKj2lLzdMSf8ZIZE/V+Zuy+BgD6f164e8K2w7dgnpKArBDerGYpM46IYYcjnkdPNMjPk9A6VFB8+3SKlXQ==",
"dev": true,
"dependencies": {
"object-keys": "^1.0.12"
},
"engines": {
"node": ">= 0.4"
}
},
"node_modules/string.prototype.trimstart/node_modules/object-keys": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz",
"integrity": "sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==",
"dev": true,
"engines": {
"node": ">= 0.4"
}
},
"node_modules/strip-ansi": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.1.tgz",
"integrity": "sha1-ajhfuIU9lS1f8F0Oiq+UJ43GPc8=",
"dev": true,
"dependencies": {
"ansi-regex": "^2.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/strip-bom": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"integrity": "sha1-YhmoVhZSBJHzV4i9vxRHqZx+aw4=",
"dev": true,
"dependencies": {
"is-utf8": "^0.2.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/strip-indent": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-3.0.0.tgz",
"integrity": "sha512-laJTa3Jb+VQpaC6DseHhF7dXVqHTfJPCRDaEbid/drOhgitgYku/letMUqOXFoWV0zIIUbjpdH2t+tYj4bQMRQ==",
"dev": true,
"dependencies": {
"min-indent": "^1.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/strip-json-comments": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/strip-json-comments/-/strip-json-comments-3.1.1.tgz",
"integrity": "sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig==",
"dev": true,
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/style-search": {
"version": "0.1.0",
"resolved": "https://registry.npmjs.org/style-search/-/style-search-0.1.0.tgz",
"integrity": "sha1-eVjHk+R+MuB9K1yv5cC/jhLneQI=",
"dev": true
},
"node_modules/stylelint": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "14.5.1",
"resolved": "https://registry.npmjs.org/stylelint/-/stylelint-14.5.1.tgz",
"integrity": "sha512-8Hf4HtnhxlWlf7iXF9zFfhSc3X0teRnVzl6PqPs2JEFx+dy/mhMhghZfiTDW4QG0ihDw9+WP7GZw5Nzx7cQF5A==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"balanced-match": "^2.0.0",
Update npm packages
2021-12-26 19:09:29 +09:00
"colord": "^2.9.2",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"cosmiconfig": "^7.0.1",
Update npm packages
2022-02-20 18:08:23 +09:00
"css-functions-list": "^3.0.1",
Update npm packages
2021-12-26 19:09:29 +09:00
"debug": "^4.3.3",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"execall": "^2.0.0",
Update npm packages
2022-02-06 19:24:14 +09:00
"fast-glob": "^3.2.11",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"fastest-levenshtein": "^1.0.12",
"file-entry-cache": "^6.0.1",
"get-stdin": "^8.0.0",
"global-modules": "^2.0.0",
Update npm packages
2022-02-06 19:24:14 +09:00
"globby": "^11.1.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"globjoin": "^0.1.4",
"html-tags": "^3.1.0",
Update npm packages
2021-12-26 19:09:29 +09:00
"ignore": "^5.2.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"import-lazy": "^4.0.0",
"imurmurhash": "^0.1.4",
"is-plain-object": "^5.0.0",
Update npm packages
2021-12-26 19:09:29 +09:00
"known-css-properties": "^0.24.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"mathml-tag-names": "^2.1.3",
"meow": "^9.0.0",
"micromatch": "^4.0.4",
"normalize-path": "^3.0.0",
"normalize-selector": "^0.2.0",
"picocolors": "^1.0.0",
Update npm packages
2022-02-20 18:08:23 +09:00
"postcss": "^8.4.6",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"postcss-media-query-parser": "^0.2.3",
"postcss-resolve-nested-selector": "^0.1.1",
"postcss-safe-parser": "^6.0.0",
Update npm packages
2022-02-06 19:24:14 +09:00
"postcss-selector-parser": "^6.0.9",
"postcss-value-parser": "^4.2.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"resolve-from": "^5.0.0",
"specificity": "^0.4.1",
"string-width": "^4.2.3",
"strip-ansi": "^6.0.1",
"style-search": "^0.1.0",
Update npm packages
2022-02-06 19:24:14 +09:00
"supports-hyperlinks": "^2.2.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"svg-tags": "^1.0.0",
Update npm packages
2022-02-06 19:24:14 +09:00
"table": "^6.8.0",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"v8-compile-cache": "^2.3.0",
Update npm packages
2022-02-20 18:08:23 +09:00
"write-file-atomic": "^4.0.1"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"bin": {
"stylelint": "bin/stylelint.js"
},
"engines": {
"node": "^12.20.0 || ^14.13.1 || >=16.0.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/stylelint"
}
},
"node_modules/stylelint-config-prettier": {
"version": "9.0.3",
"resolved": "https://registry.npmjs.org/stylelint-config-prettier/-/stylelint-config-prettier-9.0.3.tgz",
"integrity": "sha512-5n9gUDp/n5tTMCq1GLqSpA30w2sqWITSSEiAWQlpxkKGAUbjcemQ0nbkRvRUa0B1LgD3+hCvdL7B1eTxy1QHJg==",
"dev": true,
"bin": {
"stylelint-config-prettier": "bin/check.js",
"stylelint-config-prettier-check": "bin/check.js"
},
"engines": {
"node": ">= 12"
},
"peerDependencies": {
"stylelint": ">=11.0.0"
}
},
"node_modules/stylelint-prettier": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/stylelint-prettier/-/stylelint-prettier-2.0.0.tgz",
"integrity": "sha512-jvT3G+9lopkeB0ARmDPszyfaOnvnIF+30QCjZxyt7E6fynI1T9mOKgYDNb9bXX17M7PXMZaX3j/26wqakjp1tw==",
"dev": true,
"dependencies": {
"prettier-linter-helpers": "^1.0.0"
},
"engines": {
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
},
"peerDependencies": {
"prettier": ">=2.0.0",
"stylelint": ">=14.0.0"
}
},
"node_modules/stylelint/node_modules/ansi-regex": {
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
"integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/stylelint/node_modules/balanced-match": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-2.0.0.tgz",
"integrity": "sha512-1ugUSr8BHXRnK23KfuYS+gVMC3LB8QGH9W1iGtDPsNWoQbgtXSExkBu2aDR4epiGWZOjZsj6lDl/N/AqqTC3UA==",
"dev": true
},
"node_modules/stylelint/node_modules/braces": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/braces/-/braces-3.0.2.tgz",
"integrity": "sha512-b8um+L1RzM3WDSzvhm6gIz1yfTbBt6YTlcEKAvsmqCZZFw46z626lVj9j1yEPW33H5H+lBQpZMP1k8l+78Ha0A==",
"dev": true,
"dependencies": {
"fill-range": "^7.0.1"
},
"engines": {
"node": ">=8"
}
},
"node_modules/stylelint/node_modules/debug": {
"version": "4.3.3",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.3.tgz",
"integrity": "sha512-/zxw5+vh1Tfv+4Qn7a5nsbcJKPaSvCDhojn6FEl9vupwK2VCSDtEiEtqr8DFtzYFOdz63LBkxec7DYuc2jon6Q==",
"dev": true,
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/stylelint/node_modules/fill-range": {
"version": "7.0.1",
"resolved": "https://registry.npmjs.org/fill-range/-/fill-range-7.0.1.tgz",
"integrity": "sha512-qOo9F+dMUmC2Lcb4BbVvnKJxTPjCm+RRpe4gDuGrzkL7mEVl/djYSu2OdQ2Pa302N4oqkSg9ir6jaLWJ2USVpQ==",
"dev": true,
"dependencies": {
"to-regex-range": "^5.0.1"
},
"engines": {
"node": ">=8"
}
},
"node_modules/stylelint/node_modules/global-modules": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/global-modules/-/global-modules-2.0.0.tgz",
"integrity": "sha512-NGbfmJBp9x8IxyJSd1P+otYK8vonoJactOogrVfFRIAEY1ukil8RSKDz2Yo7wh1oihl51l/r6W4epkeKJHqL8A==",
"dev": true,
"dependencies": {
"global-prefix": "^3.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/stylelint/node_modules/global-prefix": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/global-prefix/-/global-prefix-3.0.0.tgz",
"integrity": "sha512-awConJSVCHVGND6x3tmMaKcQvwXLhjdkmomy2W+Goaui8YPgYgXJZewhg3fWC+DlfqqQuWg8AwqjGTD2nAPVWg==",
"dev": true,
"dependencies": {
"ini": "^1.3.5",
"kind-of": "^6.0.2",
"which": "^1.3.1"
},
"engines": {
"node": ">=6"
}
},
"node_modules/stylelint/node_modules/ignore": {
Update npm packages
2021-12-26 19:09:29 +09:00
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/ignore/-/ignore-5.2.0.tgz",
"integrity": "sha512-CmxgYGiEPCLhfLnpPp1MoRmifwEIOgjcHXxOBjv7mY96c+eWScsOP9c112ZyLdWHi0FxHjI+4uVhKYp/gcdRmQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"engines": {
"node": ">= 4"
}
},
"node_modules/stylelint/node_modules/is-fullwidth-code-point": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz",
"integrity": "sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/stylelint/node_modules/is-number": {
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/is-number/-/is-number-7.0.0.tgz",
"integrity": "sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==",
"dev": true,
"engines": {
"node": ">=0.12.0"
}
},
"node_modules/stylelint/node_modules/is-plain-object": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/is-plain-object/-/is-plain-object-5.0.0.tgz",
"integrity": "sha512-VRSzKkbMm5jMDoKLbltAkFQ5Qr7VDiTFGXxYFXXowVj387GeGNOCsOH6Msy00SGZ3Fp84b1Naa1psqgcCIEP5Q==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/stylelint/node_modules/micromatch": {
"version": "4.0.4",
"resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.4.tgz",
"integrity": "sha512-pRmzw/XUcwXGpD9aI9q/0XOwLNygjETJ8y0ao0wdqprrzDa4YnxLcz7fQRZr8voh8V10kGhABbNcHVk5wHgWwg==",
"dev": true,
"dependencies": {
"braces": "^3.0.1",
"picomatch": "^2.2.3"
},
"engines": {
"node": ">=8.6"
}
},
"node_modules/stylelint/node_modules/ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
},
"node_modules/stylelint/node_modules/normalize-path": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/normalize-path/-/normalize-path-3.0.0.tgz",
"integrity": "sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/stylelint/node_modules/resolve-from": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-5.0.0.tgz",
"integrity": "sha512-qYg9KP24dD5qka9J47d0aVky0N+b4fTU89LN9iDnjB5waksiC49rvMB0PrUJQGoTmH50XPiqOvAjDfaijGxYZw==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/stylelint/node_modules/string-width": {
"version": "4.2.3",
"resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz",
"integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==",
"dev": true,
"dependencies": {
"emoji-regex": "^8.0.0",
"is-fullwidth-code-point": "^3.0.0",
"strip-ansi": "^6.0.1"
},
"engines": {
"node": ">=8"
}
},
"node_modules/stylelint/node_modules/strip-ansi": {
"version": "6.0.1",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
"integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
"dev": true,
"dependencies": {
"ansi-regex": "^5.0.1"
},
"engines": {
"node": ">=8"
}
},
"node_modules/stylelint/node_modules/to-regex-range": {
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/to-regex-range/-/to-regex-range-5.0.1.tgz",
"integrity": "sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==",
"dev": true,
"dependencies": {
"is-number": "^7.0.0"
},
"engines": {
"node": ">=8.0"
}
},
"node_modules/summary": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/summary/-/summary-2.1.0.tgz",
"integrity": "sha512-nMIjMrd5Z2nuB2RZCKJfFMjgS3fygbeyGk9PxPPaJR1RIcyN9yn4A63Isovzm3ZtQuEkLBVgMdPup8UeLH7aQw==",
"dev": true
},
"node_modules/supports-color": {
"version": "5.4.0",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-5.4.0.tgz",
"integrity": "sha512-zjaXglF5nnWpsq470jSv6P9DwPvgLkuapYmfDm3JWOm0vkNTVF2tI4UrN2r6jH1qM/uc/WtxYY1hYoA2dOKj5w==",
"dev": true,
"dependencies": {
"has-flag": "^3.0.0"
},
"engines": {
"node": ">=4"
}
},
Update npm packages
2022-02-06 19:24:14 +09:00
"node_modules/supports-hyperlinks": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/supports-hyperlinks/-/supports-hyperlinks-2.2.0.tgz",
"integrity": "sha512-6sXEzV5+I5j8Bmq9/vUphGRM/RJNT9SCURJLjwfOg51heRtguGWDzcaBlgAzKhQa0EVNpPEKzQuBwZ8S8WaCeQ==",
"dev": true,
"dependencies": {
"has-flag": "^4.0.0",
"supports-color": "^7.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/supports-hyperlinks/node_modules/has-flag": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz",
"integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/supports-hyperlinks/node_modules/supports-color": {
"version": "7.2.0",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-7.2.0.tgz",
"integrity": "sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==",
"dev": true,
"dependencies": {
"has-flag": "^4.0.0"
},
"engines": {
"node": ">=8"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/sver-compat": {
"version": "1.5.0",
"resolved": "https://registry.npmjs.org/sver-compat/-/sver-compat-1.5.0.tgz",
"integrity": "sha1-PPh9/rTQe0o/FIJ7wYaz/QxkXNg=",
"dev": true,
"dependencies": {
"es6-iterator": "^2.0.1",
"es6-symbol": "^3.1.1"
}
},
"node_modules/svg-tags": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/svg-tags/-/svg-tags-1.0.0.tgz",
"integrity": "sha1-WPcc7jvVGbWdSyqEO2x95krAR2Q=",
"dev": true
},
"node_modules/systemjs": {
"version": "0.21.6",
"resolved": "https://registry.npmjs.org/systemjs/-/systemjs-0.21.6.tgz",
"integrity": "sha512-R+5S9eV9vcQgWOoS4D87joZ4xkFJHb19ZsyKY07D1+VBDE9bwYcU+KXE0r5XlDA8mFoJGyuWDbfrNoh90JsA8g==",
"dev": true
},
"node_modules/systemjs-plugin-babel": {
"version": "0.0.25",
"resolved": "https://registry.npmjs.org/systemjs-plugin-babel/-/systemjs-plugin-babel-0.0.25.tgz",
"integrity": "sha512-RMKSizWWlw4+IpDB385ugxn7Owd9W+HEtjYDQ6yO1FpsnER/vk6FbXRweUF+mvRi6EHgk8vDdUdtui7ReDwX3w==",
"dev": true
},
"node_modules/table": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "6.8.0",
"resolved": "https://registry.npmjs.org/table/-/table-6.8.0.tgz",
"integrity": "sha512-s/fitrbVeEyHKFa7mFdkuQMWlH1Wgw/yEXMt5xACT4ZpzWFluehAxRtUUQKPuWhaLAWhFcVx6w3oC8VKaUfPGA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"ajv": "^8.0.1",
"lodash.truncate": "^4.4.2",
"slice-ansi": "^4.0.0",
"string-width": "^4.2.3",
"strip-ansi": "^6.0.1"
},
"engines": {
"node": ">=10.0.0"
}
},
"node_modules/table/node_modules/ajv": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "8.10.0",
"resolved": "https://registry.npmjs.org/ajv/-/ajv-8.10.0.tgz",
"integrity": "sha512-bzqAEZOjkrUMl2afH8dknrq5KEk2SrwdBROR+vH1EKVQTqaUbJVPdc/gEdggTMM0Se+s+Ja4ju4TlNcStKl2Hw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"fast-deep-equal": "^3.1.1",
"json-schema-traverse": "^1.0.0",
"require-from-string": "^2.0.2",
"uri-js": "^4.2.2"
},
"funding": {
"type": "github",
"url": "https://github.com/sponsors/epoberezkin"
}
},
"node_modules/table/node_modules/ansi-regex": {
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
"integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/table/node_modules/is-fullwidth-code-point": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz",
"integrity": "sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/table/node_modules/json-schema-traverse": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-1.0.0.tgz",
"integrity": "sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug==",
"dev": true
},
"node_modules/table/node_modules/string-width": {
"version": "4.2.3",
"resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz",
"integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==",
"dev": true,
"dependencies": {
"emoji-regex": "^8.0.0",
"is-fullwidth-code-point": "^3.0.0",
"strip-ansi": "^6.0.1"
},
"engines": {
"node": ">=8"
}
},
"node_modules/table/node_modules/strip-ansi": {
"version": "6.0.1",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
"integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
"dev": true,
"dependencies": {
"ansi-regex": "^5.0.1"
},
"engines": {
"node": ">=8"
}
},
"node_modules/taffydb": {
"version": "2.6.2",
"resolved": "https://registry.npmjs.org/taffydb/-/taffydb-2.6.2.tgz",
"integrity": "sha1-fLy2S1oUG2ou/CxdLGe04VCyomg=",
"dev": true
},
"node_modules/tapable": {
"version": "2.2.1",
"resolved": "https://registry.npmjs.org/tapable/-/tapable-2.2.1.tgz",
"integrity": "sha512-GNzQvQTOIP6RyTfE2Qxb8ZVlNmw0n88vp1szwWRimP02mnTsx3Wtn5qRdqY9w2XduFNUgvOwhNnQsjwCp+kqaQ==",
"dev": true,
"engines": {
"node": ">=6"
}
},
"node_modules/tar": {
"version": "6.1.11",
"resolved": "https://registry.npmjs.org/tar/-/tar-6.1.11.tgz",
"integrity": "sha512-an/KZQzQUkZCkuoAA64hM92X0Urb6VpRhAFllDzz44U2mcD5scmT3zBc4VgVpkugF580+DQn8eAFSyoQt0tznA==",
"dev": true,
"dependencies": {
"chownr": "^2.0.0",
"fs-minipass": "^2.0.0",
"minipass": "^3.0.0",
"minizlib": "^2.1.1",
"mkdirp": "^1.0.3",
"yallist": "^4.0.0"
},
"engines": {
"node": ">= 10"
}
},
"node_modules/tar-fs": {
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/tar-fs/-/tar-fs-2.1.1.tgz",
"integrity": "sha512-V0r2Y9scmbDRLCNex/+hYzvp/zyYjvFbHPNgVTKfQvVrb6guiE/fxP+XblDNR011utopbkex2nM4dHNV6GDsng==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"chownr": "^1.1.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"mkdirp-classic": "^0.5.2",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"pump": "^3.0.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"tar-stream": "^2.1.4"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/tar-fs/node_modules/pump": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/pump/-/pump-3.0.0.tgz",
"integrity": "sha512-LwZy+p3SFs1Pytd/jYct4wpv49HiYCqd9Rlc5ZVdk0V+8Yzv6jR5Blk3TRmPL1ft69TxP0IMZGJ+WPFU2BFhww==",
"dev": true,
"dependencies": {
"end-of-stream": "^1.1.0",
"once": "^1.3.1"
}
},
"node_modules/tar-stream": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/tar-stream/-/tar-stream-2.2.0.tgz",
"integrity": "sha512-ujeqbceABgwMZxEJnk2HDY2DlnUZ+9oEcb1KzTVfYHio0UE6dG71n60d8D2I4qNvleWrrXpmjpt7vZeF1LnMZQ==",
"dev": true,
"dependencies": {
"bl": "^4.0.3",
"end-of-stream": "^1.4.1",
"fs-constants": "^1.0.0",
"inherits": "^2.0.3",
"readable-stream": "^3.1.1"
},
"engines": {
"node": ">=6"
}
},
"node_modules/tar-stream/node_modules/readable-stream": {
"version": "3.6.0",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-3.6.0.tgz",
"integrity": "sha512-BViHy7LKeTz4oNnkcLJ+lVSL6vpiFeX6/d3oSH8zCW7UxP2onchk+vTGB143xuFjHS3deTgkKoXXymXqymiIdA==",
"dev": true,
"dependencies": {
"inherits": "^2.0.3",
"string_decoder": "^1.1.1",
"util-deprecate": "^1.0.1"
},
"engines": {
"node": ">= 6"
}
},
"node_modules/tar/node_modules/chownr": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/chownr/-/chownr-2.0.0.tgz",
"integrity": "sha512-bIomtDF5KGpdogkLd9VspvFzk9KfpyyGlS8YFVZl7TGPBHL5snIOnxeshwVgPteQ9b4Eydl+pVbIyE1DcvCWgQ==",
"dev": true,
"engines": {
"node": ">=10"
}
},
"node_modules/tar/node_modules/yallist": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/yallist/-/yallist-4.0.0.tgz",
"integrity": "sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A==",
"dev": true
},
"node_modules/terser": {
"version": "5.10.0",
"resolved": "https://registry.npmjs.org/terser/-/terser-5.10.0.tgz",
"integrity": "sha512-AMmF99DMfEDiRJfxfY5jj5wNH/bYO09cniSqhfoyxc8sFoYIgkJy86G04UoZU5VjlpnplVu0K6Tx6E9b5+DlHA==",
"dev": true,
"dependencies": {
"commander": "^2.20.0",
"source-map": "~0.7.2",
"source-map-support": "~0.5.20"
},
"bin": {
"terser": "bin/terser"
},
"engines": {
"node": ">=10"
},
"peerDependencies": {
"acorn": "^8.5.0"
},
"peerDependenciesMeta": {
"acorn": {
"optional": true
}
}
},
"node_modules/terser-webpack-plugin": {
"version": "5.2.5",
"resolved": "https://registry.npmjs.org/terser-webpack-plugin/-/terser-webpack-plugin-5.2.5.tgz",
"integrity": "sha512-3luOVHku5l0QBeYS8r4CdHYWEGMmIj3H1U64jgkdZzECcSOJAyJ9TjuqcQZvw1Y+4AOBN9SeYJPJmFn2cM4/2g==",
"dev": true,
"dependencies": {
"jest-worker": "^27.0.6",
"schema-utils": "^3.1.1",
"serialize-javascript": "^6.0.0",
"source-map": "^0.6.1",
"terser": "^5.7.2"
},
"engines": {
"node": ">= 10.13.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
},
"peerDependencies": {
"webpack": "^5.1.0"
},
"peerDependenciesMeta": {
"@swc/core": {
"optional": true
},
"esbuild": {
"optional": true
},
"uglify-js": {
"optional": true
}
}
},
"node_modules/terser-webpack-plugin/node_modules/schema-utils": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/schema-utils/-/schema-utils-3.1.1.tgz",
"integrity": "sha512-Y5PQxS4ITlC+EahLuXaY86TXfR7Dc5lw294alXOq86JAHCihAIZfqv8nNCWvaEJvaC51uN9hbLGeV0cFBdH+Fw==",
"dev": true,
"dependencies": {
"@types/json-schema": "^7.0.8",
"ajv": "^6.12.5",
"ajv-keywords": "^3.5.2"
},
"engines": {
"node": ">= 10.13.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
}
},
"node_modules/terser/node_modules/commander": {
"version": "2.20.3",
"resolved": "https://registry.npmjs.org/commander/-/commander-2.20.3.tgz",
"integrity": "sha512-GpVkmM8vF2vQUkj2LvZmD35JxeJOLCwJ9cUkugyk2nuhbv3+mJvpLYYt+0+USMxE+oj+ey/lJEnhZw75x/OMcQ==",
"dev": true
},
"node_modules/terser/node_modules/source-map": {
"version": "0.7.3",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.7.3.tgz",
"integrity": "sha512-CkCj6giN3S+n9qrYiBTX5gystlENnRW5jZeNLHpe6aue+SrHcG5VYwujhW9s4dY31mEGsxBDrHR6oI69fTXsaQ==",
"dev": true,
"engines": {
"node": ">= 8"
}
},
"node_modules/text-hex": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/text-hex/-/text-hex-1.0.0.tgz",
"integrity": "sha512-uuVGNWzgJ4yhRaNSiubPY7OjISw4sw4E5Uv0wbjp+OzcbmVU/rsT8ujgcXJhn9ypzsgr5vlzpPqP+MBBKcGvbg==",
"dev": true
},
"node_modules/text-table": {
"version": "0.2.0",
"resolved": "https://registry.npmjs.org/text-table/-/text-table-0.2.0.tgz",
"integrity": "sha1-f17oI66AUgfACvLfSoTsP8+lcLQ=",
"dev": true
},
"node_modules/textextensions": {
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/textextensions/-/textextensions-3.3.0.tgz",
"integrity": "sha512-mk82dS8eRABNbeVJrEiN5/UMSCliINAuz8mkUwH4SwslkNP//gbEzlWNS5au0z5Dpx40SQxzqZevZkn+WYJ9Dw==",
"dev": true,
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://bevry.me/fund"
}
},
"node_modules/through": {
"version": "2.3.8",
"resolved": "https://registry.npmjs.org/through/-/through-2.3.8.tgz",
"integrity": "sha1-DdTJ/6q8NXlgsbckEV1+Doai4fU=",
"dev": true
},
"node_modules/through2": {
"version": "4.0.2",
"resolved": "https://registry.npmjs.org/through2/-/through2-4.0.2.tgz",
"integrity": "sha512-iOqSav00cVxEEICeD7TjLB1sueEL+81Wpzp2bY17uZjZN0pWZPuo4suZ/61VujxmqSGFfgOcNuTZ85QJwNZQpw==",
"dev": true,
"dependencies": {
"readable-stream": "3"
}
},
"node_modules/through2-filter": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/through2-filter/-/through2-filter-3.0.0.tgz",
"integrity": "sha512-jaRjI2WxN3W1V8/FMZ9HKIBXixtiqs3SQSX4/YGIiP3gL6djW48VoZq9tDqeCWs3MT8YY5wb/zli8VW8snY1CA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"through2": "~2.0.0",
"xtend": "~4.0.0"
}
},
"node_modules/through2-filter/node_modules/through2": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.5.tgz",
"integrity": "sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==",
"dev": true,
"dependencies": {
"readable-stream": "~2.3.6",
"xtend": "~4.0.1"
}
},
"node_modules/through2/node_modules/readable-stream": {
"version": "3.6.0",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-3.6.0.tgz",
"integrity": "sha512-BViHy7LKeTz4oNnkcLJ+lVSL6vpiFeX6/d3oSH8zCW7UxP2onchk+vTGB143xuFjHS3deTgkKoXXymXqymiIdA==",
"dev": true,
"dependencies": {
"inherits": "^2.0.3",
"string_decoder": "^1.1.1",
"util-deprecate": "^1.0.1"
},
"engines": {
"node": ">= 6"
}
},
"node_modules/time-stamp": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/time-stamp/-/time-stamp-1.1.0.tgz",
"integrity": "sha1-dkpaEa9QVhkhsTPztE5hhofg9cM=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/to-absolute-glob": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/to-absolute-glob/-/to-absolute-glob-2.0.2.tgz",
"integrity": "sha1-GGX0PZ50sIItufFFt4z/fQ98hJs=",
"dev": true,
"dependencies": {
"is-absolute": "^1.0.0",
"is-negated-glob": "^1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/to-fast-properties": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/to-fast-properties/-/to-fast-properties-1.0.3.tgz",
"integrity": "sha1-uDVx+k2MJbguIxsG46MFXeTKGkc=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/to-object-path": {
"version": "0.3.0",
"resolved": "https://registry.npmjs.org/to-object-path/-/to-object-path-0.3.0.tgz",
"integrity": "sha1-KXWIt7Dn4KwI4E5nL4XB9JmeF68=",
"dev": true,
"dependencies": {
"kind-of": "^3.0.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/to-object-path/node_modules/kind-of": {
"version": "3.2.2",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz",
"integrity": "sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=",
"dev": true,
"dependencies": {
"is-buffer": "^1.1.5"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/to-regex": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/to-regex/-/to-regex-3.0.2.tgz",
"integrity": "sha512-FWtleNAtZ/Ki2qtqej2CXTOayOH9bHDQF+Q48VpWyDXjbYxA4Yz8iDB31zXOBUlOHHKidDbqGVrTUvQMPmBGBw==",
"dev": true,
"dependencies": {
"define-property": "^2.0.2",
"extend-shallow": "^3.0.2",
"regex-not": "^1.0.2",
"safe-regex": "^1.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/to-regex-range": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/to-regex-range/-/to-regex-range-2.1.1.tgz",
"integrity": "sha1-fIDBe53+vlmeJzZ+DU3VWQFB2zg=",
"dev": true,
"dependencies": {
"is-number": "^3.0.0",
"repeat-string": "^1.6.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/to-through": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/to-through/-/to-through-2.0.0.tgz",
"integrity": "sha1-/JKtq6ByZHvAtn1rA2ZKoZUJOvY=",
"dev": true,
"dependencies": {
"through2": "^2.0.3"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/to-through/node_modules/through2": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.5.tgz",
"integrity": "sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==",
"dev": true,
"dependencies": {
"readable-stream": "~2.3.6",
"xtend": "~4.0.1"
}
},
"node_modules/token-stream": {
"version": "0.0.1",
"resolved": "https://registry.npmjs.org/token-stream/-/token-stream-0.0.1.tgz",
"integrity": "sha1-zu78cXp2xDFvEm0LnbqlXX598Bo=",
"dev": true
},
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"node_modules/tr46": {
"version": "0.0.3",
"resolved": "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz",
"integrity": "sha1-gYT9NH2snNwYWZLzpmIuFLnZq2o=",
"dev": true
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/trim-newlines": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-3.0.1.tgz",
"integrity": "sha512-c1PTsA3tYrIsLGkJkzHF+w9F2EyxfXGo4UyJc4pFL++FMjnq0HJS69T3M7d//gKrFKwy429bouPescbjecU+Zw==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/triple-beam": {
"version": "1.3.0",
"resolved": "https://registry.npmjs.org/triple-beam/-/triple-beam-1.3.0.tgz",
"integrity": "sha512-XrHUvV5HpdLmIj4uVMxHggLbFSZYIn7HEWsqePZcI50pco+MPqJ50wMGY794X7AOOhxOBAjbkqfAbEe/QMp2Lw==",
"dev": true
},
"node_modules/tsconfig-paths": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "3.12.0",
"resolved": "https://registry.npmjs.org/tsconfig-paths/-/tsconfig-paths-3.12.0.tgz",
"integrity": "sha512-e5adrnOYT6zqVnWqZu7i/BQ3BnhzvGbjEjejFXO20lKIKpwTaupkCPgEfv4GZK1IBciJUEhYs3J3p75FdaTFVg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"@types/json5": "^0.0.29",
"json5": "^1.0.1",
"minimist": "^1.2.0",
"strip-bom": "^3.0.0"
}
},
"node_modules/tsconfig-paths/node_modules/json5": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/json5/-/json5-1.0.1.tgz",
"integrity": "sha512-aKS4WQjPenRxiQsC93MNfjx+nbF4PAdYzmd/1JIj8HYzqfbu86beTuNgXDzPknWk0n0uARlyewZo4s++ES36Ow==",
"dev": true,
"dependencies": {
"minimist": "^1.2.0"
},
"bin": {
"json5": "lib/cli.js"
}
},
"node_modules/tsconfig-paths/node_modules/strip-bom": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-3.0.0.tgz",
"integrity": "sha1-IzTBjpx1n3vdVv3vfprj1YjmjtM=",
"dev": true,
"engines": {
"node": ">=4"
}
},
"node_modules/ttest": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/ttest/-/ttest-3.0.0.tgz",
"integrity": "sha512-bLo+LdYokiDZHVFIWJmC5afoh7wZ+o1h++0XXKh01+yprzz8CnaiGNcbcbqP0e3+iyDqclLI+rM0j/9AwmRljw==",
"dev": true,
"dependencies": {
"distributions": "^2.1.0",
"summary": "^2.0.0"
}
},
"node_modules/type-check": {
"version": "0.3.2",
"resolved": "https://registry.npmjs.org/type-check/-/type-check-0.3.2.tgz",
"integrity": "sha1-WITKtRLPHTVeP7eE8wgEsrUg23I=",
"dev": true,
"dependencies": {
"prelude-ls": "~1.1.2"
},
"engines": {
"node": ">= 0.8.0"
}
},
"node_modules/type-fest": {
"version": "0.8.1",
"resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.8.1.tgz",
"integrity": "sha512-4dbzIzqvjtgiM5rw1k5rEHtBANKmdudhGyBEajN01fEyhaAIhsoKNy6y7+IN93IfpFtwY9iqi7kD+xwKhQsNJA==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/typedarray": {
"version": "0.0.6",
"resolved": "https://registry.npmjs.org/typedarray/-/typedarray-0.0.6.tgz",
"integrity": "sha1-hnrHTjhkGHsdPUfZlqeOxciDB3c=",
"dev": true
},
"node_modules/typescript": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "4.5.5",
"resolved": "https://registry.npmjs.org/typescript/-/typescript-4.5.5.tgz",
"integrity": "sha512-TCTIul70LyWe6IJWT8QSYeA54WQe8EjQFU4wY52Fasj5UKx88LNYKCgBEHcOMOrFF1rKGbD8v/xcNWVUq9SymA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"bin": {
"tsc": "bin/tsc",
"tsserver": "bin/tsserver"
},
"engines": {
"node": ">=4.2.0"
}
},
"node_modules/typogr": {
"version": "0.6.8",
"resolved": "https://registry.npmjs.org/typogr/-/typogr-0.6.8.tgz",
"integrity": "sha512-zjUkJd8Nt9NvXTzjBYpk5Pw0OgXTStgATbUAAhVvCrFtjvRVcDvtKjtxCRMRZsK0fx2MVa8hoqMiTPSgWOA9pg==",
"dev": true,
"dependencies": {
"async": "0.2",
"commander": "1.0",
"glob": "^7.1.2",
"mkdirp": "0.3"
},
"bin": {
"typogr": "bin/typogr"
}
},
"node_modules/typogr/node_modules/mkdirp": {
"version": "0.3.5",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz",
"integrity": "sha1-3j5fiWHIjHh+4TaN+EmsRBPsqNc=",
"deprecated": "Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)",
"dev": true
},
"node_modules/uc.micro": {
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/uc.micro/-/uc.micro-1.0.5.tgz",
"integrity": "sha512-JoLI4g5zv5qNyT09f4YAvEZIIV1oOjqnewYg5D38dkQljIzpPT296dbIGvKro3digYI1bkb7W6EP1y4uDlmzLg==",
"dev": true
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/uglify-js": {
"version": "2.8.29",
"resolved": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.8.29.tgz",
"integrity": "sha1-KcVzMUgFe7Th913zW3qcty5qWd0=",
"dev": true,
"dependencies": {
"source-map": "~0.5.1",
"yargs": "~3.10.0"
},
"bin": {
"uglifyjs": "bin/uglifyjs"
},
"engines": {
"node": ">=0.8.0"
},
"optionalDependencies": {
"uglify-to-browserify": "~1.0.0"
}
},
"node_modules/uglify-js/node_modules/source-map": {
"version": "0.5.7",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.7.tgz",
"integrity": "sha1-igOdLRAh0i0eoUyA2OpGi6LvP8w=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/uglify-js/node_modules/yargs": {
"version": "3.10.0",
"resolved": "https://registry.npmjs.org/yargs/-/yargs-3.10.0.tgz",
"integrity": "sha1-9+572FfdfB0tOMDnTvvWgdFDH9E=",
"dev": true,
"dependencies": {
"camelcase": "^1.0.2",
"cliui": "^2.1.0",
"decamelize": "^1.0.0",
"window-size": "0.1.0"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/uglify-to-browserify": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/uglify-to-browserify/-/uglify-to-browserify-1.0.2.tgz",
"integrity": "sha1-bgkk1r2mta/jSeOabWMoUKD4grc=",
"dev": true,
"optional": true
},
"node_modules/unbox-primitive": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/unbox-primitive/-/unbox-primitive-1.0.1.tgz",
"integrity": "sha512-tZU/3NqK3dA5gpE1KtyiJUrEB0lxnGkMFHptJ7q6ewdZ8s12QrODwNbhIJStmJkd1QDXa1NRA8aF2A1zk/Ypyw==",
"dev": true,
"dependencies": {
"function-bind": "^1.1.1",
"has-bigints": "^1.0.1",
"has-symbols": "^1.0.2",
"which-boxed-primitive": "^1.0.2"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/unbox-primitive/node_modules/has-symbols": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.2.tgz",
"integrity": "sha512-chXa79rL/UC2KlX17jo3vRGz0azaWEx5tGqZg5pO3NUyEJVB17dMruQlzCCOfUvElghKcm5194+BCRvi2Rv/Gw==",
"dev": true,
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/unbzip2-stream": {
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"version": "1.4.3",
"resolved": "https://registry.npmjs.org/unbzip2-stream/-/unbzip2-stream-1.4.3.tgz",
"integrity": "sha512-mlExGW4w71ebDJviH16lQLtZS32VKqsSfk80GCfUlwT/4/hNRFsoscrF/c++9xinkMzECL1uL9DDwXqFWkruPg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"buffer": "^5.2.1",
"through": "^2.3.8"
}
},
"node_modules/unc-path-regex": {
"version": "0.1.2",
"resolved": "https://registry.npmjs.org/unc-path-regex/-/unc-path-regex-0.1.2.tgz",
"integrity": "sha1-5z3T17DXxe2G+6xrCufYxqadUPo=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/underscore": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "1.13.2",
"resolved": "https://registry.npmjs.org/underscore/-/underscore-1.13.2.tgz",
"integrity": "sha512-ekY1NhRzq0B08g4bGuX4wd2jZx5GnKz6mKSqFL4nqBlfyMGiG10gDFhDTMEfYmDL6Jy0FUIZp7wiRB+0BP7J2g==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/undertaker": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/undertaker/-/undertaker-1.2.1.tgz",
"integrity": "sha512-71WxIzDkgYk9ZS+spIB8iZXchFhAdEo2YU8xYqBYJ39DIUIqziK78ftm26eecoIY49X0J2MLhG4hr18Yp6/CMA==",
"dev": true,
"dependencies": {
"arr-flatten": "^1.0.1",
"arr-map": "^2.0.0",
"bach": "^1.0.0",
"collection-map": "^1.0.0",
"es6-weak-map": "^2.0.1",
"last-run": "^1.1.0",
"object.defaults": "^1.0.0",
"object.reduce": "^1.0.0",
"undertaker-registry": "^1.0.0"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/undertaker-registry": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/undertaker-registry/-/undertaker-registry-1.0.1.tgz",
"integrity": "sha1-XkvaMI5KiirlhPm5pDWaSZglzFA=",
"dev": true,
"engines": {
"node": ">= 0.10"
}
},
Update npm packages
2022-01-09 18:05:52 +09:00
"node_modules/unicode-canonical-property-names-ecmascript": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/unicode-canonical-property-names-ecmascript/-/unicode-canonical-property-names-ecmascript-2.0.0.tgz",
"integrity": "sha512-yY5PpDlfVIU5+y/BSCxAJRBIS1Zc2dDG3Ujq+sR0U+JjUevW2JhocOF+soROYDSaAezOzOKuyyixhD6mBknSmQ==",
"dev": true,
"engines": {
"node": ">=4"
}
},
"node_modules/unicode-match-property-ecmascript": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/unicode-match-property-ecmascript/-/unicode-match-property-ecmascript-2.0.0.tgz",
"integrity": "sha512-5kaZCrbp5mmbz5ulBkDkbY0SsPOjKqVS35VpL9ulMPfSl0J0Xsm+9Evphv9CoIZFwre7aJoa94AY6seMKGVN5Q==",
"dev": true,
"dependencies": {
"unicode-canonical-property-names-ecmascript": "^2.0.0",
"unicode-property-aliases-ecmascript": "^2.0.0"
},
"engines": {
"node": ">=4"
}
},
"node_modules/unicode-match-property-value-ecmascript": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/unicode-match-property-value-ecmascript/-/unicode-match-property-value-ecmascript-2.0.0.tgz",
"integrity": "sha512-7Yhkc0Ye+t4PNYzOGKedDhXbYIBe1XEQYQxOPyhcXNMJ0WCABqqj6ckydd6pWRZTHV4GuCPKdBAUiMc60tsKVw==",
"dev": true,
"engines": {
"node": ">=4"
}
},
"node_modules/unicode-property-aliases-ecmascript": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/unicode-property-aliases-ecmascript/-/unicode-property-aliases-ecmascript-2.0.0.tgz",
"integrity": "sha512-5Zfuy9q/DFr4tfO7ZPeVXb1aPoeQSdeFMLpYuFebehDAhbuevLs5yxSZmIFN1tP5F9Wl4IpJrYojg85/zgyZHQ==",
"dev": true,
"engines": {
"node": ">=4"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/union-value": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/union-value/-/union-value-1.0.1.tgz",
"integrity": "sha512-tJfXmxMeWYnczCVs7XAEvIV7ieppALdyepWMkHkwciRpZraG/xwT+s2JN8+pr1+8jCRf80FFzvr+MpQeeoF4Xg==",
"dev": true,
"dependencies": {
"arr-union": "^3.1.0",
"get-value": "^2.0.6",
"is-extendable": "^0.1.1",
"set-value": "^2.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/unique-stream": {
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/unique-stream/-/unique-stream-2.3.1.tgz",
"integrity": "sha512-2nY4TnBE70yoxHkDli7DMazpWiP7xMdCYqU2nBRO0UB+ZpEkGsSija7MvmvnZFUeC+mrgiUfcHSr3LmRFIg4+A==",
"dev": true,
"dependencies": {
"json-stable-stringify-without-jsonify": "^1.0.1",
"through2-filter": "^3.0.0"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/unset-value": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/unset-value/-/unset-value-1.0.0.tgz",
"integrity": "sha1-g3aHP30jNRef+x5vw6jtDfyKtVk=",
"dev": true,
"dependencies": {
"has-value": "^0.3.1",
"isobject": "^3.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/unset-value/node_modules/has-value": {
"version": "0.3.1",
"resolved": "https://registry.npmjs.org/has-value/-/has-value-0.3.1.tgz",
"integrity": "sha1-ex9YutpiyoJ+wKIHgCVlSEWZXh8=",
"dev": true,
"dependencies": {
"get-value": "^2.0.3",
"has-values": "^0.1.4",
"isobject": "^2.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/unset-value/node_modules/has-value/node_modules/isobject": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/isobject/-/isobject-2.1.0.tgz",
"integrity": "sha1-8GVWEJaj8dou9GJy+BXIQNh+DIk=",
"dev": true,
"dependencies": {
"isarray": "1.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/unset-value/node_modules/has-values": {
"version": "0.1.4",
"resolved": "https://registry.npmjs.org/has-values/-/has-values-0.1.4.tgz",
"integrity": "sha1-bWHeldkd/Km5oCCJrThL/49it3E=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/upath": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/upath/-/upath-1.2.0.tgz",
"integrity": "sha512-aZwGpamFO61g3OlfT7OQCHqhGnW43ieH9WZeP7QxN/G/jS4jfqUkZxoryvJgVPEcrl5NL/ggHsSmLMHuH64Lhg==",
"dev": true,
"engines": {
"node": ">=4",
"yarn": "*"
}
},
"node_modules/uri-js": {
"version": "4.2.2",
"resolved": "https://registry.npmjs.org/uri-js/-/uri-js-4.2.2.tgz",
"integrity": "sha512-KY9Frmirql91X2Qgjry0Wd4Y+YTdrdZheS8TFwvkbLWf/G5KNJDCh6pKL5OZctEW4+0Baa5idK2ZQuELRwPznQ==",
"dev": true,
"dependencies": {
"punycode": "^2.1.0"
}
},
"node_modules/urix": {
"version": "0.1.0",
"resolved": "https://registry.npmjs.org/urix/-/urix-0.1.0.tgz",
"integrity": "sha1-2pN/emLiH+wf0Y1Js1wpNQZ6bHI=",
"deprecated": "Please see https://github.com/lydell/urix#deprecated",
"dev": true
},
"node_modules/use": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/use/-/use-3.1.0.tgz",
"integrity": "sha512-6UJEQM/L+mzC3ZJNM56Q4DFGLX/evKGRg15UJHGB9X5j5Z3AFbgZvjUh2yq/UJUY4U5dh7Fal++XbNg1uzpRAw==",
"dev": true,
"dependencies": {
"kind-of": "^6.0.2"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/util-deprecate": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"integrity": "sha1-RQ1Nyfpw3nMnYvvS1KKJgUGaDM8=",
"dev": true
},
"node_modules/v8-compile-cache": {
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/v8-compile-cache/-/v8-compile-cache-2.3.0.tgz",
"integrity": "sha512-l8lCEmLcLYZh4nbunNZvQCJc5pv7+RCwa8q/LdUx8u7lsWvPDKmpodJAJNwkAhJC//dFY48KuIEmjtd4RViDrA==",
"dev": true
},
"node_modules/v8flags": {
"version": "3.1.3",
"resolved": "https://registry.npmjs.org/v8flags/-/v8flags-3.1.3.tgz",
"integrity": "sha512-amh9CCg3ZxkzQ48Mhcb8iX7xpAfYJgePHxWMQCBWECpOSqJUXgY26ncA61UTV0BkPqfhcy6mzwCIoP4ygxpW8w==",
"dev": true,
"dependencies": {
"homedir-polyfill": "^1.0.1"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/validate-npm-package-license": {
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.3.tgz",
"integrity": "sha512-63ZOUnL4SIXj4L0NixR3L1lcjO38crAbgrTpl28t8jjrfuiOBL5Iygm+60qPs/KsZGzPNg6Smnc/oY16QTjF0g==",
"dev": true,
"dependencies": {
"spdx-correct": "^3.0.0",
"spdx-expression-parse": "^3.0.0"
}
},
"node_modules/value-or-function": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/value-or-function/-/value-or-function-3.0.0.tgz",
"integrity": "sha1-HCQ6ULWVwb5Up1S/7OhWO5/42BM=",
"dev": true,
"engines": {
"node": ">= 0.10"
}
},
"node_modules/vinyl": {
"version": "2.2.1",
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-2.2.1.tgz",
"integrity": "sha512-LII3bXRFBZLlezoG5FfZVcXflZgWP/4dCwKtxd5ky9+LOtM4CS3bIRQsmR1KMnMW07jpE8fqR2lcxPZ+8sJIcw==",
"dev": true,
"dependencies": {
"clone": "^2.1.1",
"clone-buffer": "^1.0.0",
"clone-stats": "^1.0.0",
"cloneable-readable": "^1.0.0",
"remove-trailing-separator": "^1.0.1",
"replace-ext": "^1.0.0"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/vinyl-fs": {
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/vinyl-fs/-/vinyl-fs-3.0.3.tgz",
"integrity": "sha512-vIu34EkyNyJxmP0jscNzWBSygh7VWhqun6RmqVfXePrOwi9lhvRs//dOaGOTRUQr4tx7/zd26Tk5WeSVZitgng==",
"dev": true,
"dependencies": {
"fs-mkdirp-stream": "^1.0.0",
"glob-stream": "^6.1.0",
"graceful-fs": "^4.0.0",
"is-valid-glob": "^1.0.0",
"lazystream": "^1.0.0",
"lead": "^1.0.0",
"object.assign": "^4.0.4",
"pumpify": "^1.3.5",
"readable-stream": "^2.3.3",
"remove-bom-buffer": "^3.0.0",
"remove-bom-stream": "^1.2.0",
"resolve-options": "^1.1.0",
"through2": "^2.0.0",
"to-through": "^2.0.0",
"value-or-function": "^3.0.0",
"vinyl": "^2.0.0",
"vinyl-sourcemap": "^1.1.0"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/vinyl-fs/node_modules/through2": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.5.tgz",
"integrity": "sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==",
"dev": true,
"dependencies": {
"readable-stream": "~2.3.6",
"xtend": "~4.0.1"
}
},
"node_modules/vinyl-sourcemap": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/vinyl-sourcemap/-/vinyl-sourcemap-1.1.0.tgz",
"integrity": "sha1-kqgAWTo4cDqM2xHYswCtS+Y7PhY=",
"dev": true,
"dependencies": {
"append-buffer": "^1.0.2",
"convert-source-map": "^1.5.0",
"graceful-fs": "^4.1.6",
"normalize-path": "^2.1.1",
"now-and-later": "^2.0.0",
"remove-bom-buffer": "^3.0.0",
"vinyl": "^2.0.0"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/vinyl-sourcemaps-apply": {
"version": "0.2.1",
"resolved": "https://registry.npmjs.org/vinyl-sourcemaps-apply/-/vinyl-sourcemaps-apply-0.2.1.tgz",
"integrity": "sha1-q2VJ1h0XLCsbh75cUI0jnI74dwU=",
"dev": true,
"dependencies": {
"source-map": "^0.5.1"
}
},
"node_modules/vinyl-sourcemaps-apply/node_modules/source-map": {
"version": "0.5.7",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.7.tgz",
"integrity": "sha1-igOdLRAh0i0eoUyA2OpGi6LvP8w=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/void-elements": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/void-elements/-/void-elements-2.0.1.tgz",
"integrity": "sha1-wGavtYK7HLQSjWDqkjkulNXp2+w=",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/vscode-json-languageservice": {
"version": "4.1.6",
"resolved": "https://registry.npmjs.org/vscode-json-languageservice/-/vscode-json-languageservice-4.1.6.tgz",
"integrity": "sha512-DIKb3tcfRtb3tIE6g9SLOl5E9tNSt6kljH08Wa5RwFlVshtXGrDDzttchze4CYy9pJpE9mBtCbRHmLvY1Z1ZXA==",
"dev": true,
"dependencies": {
"jsonc-parser": "^3.0.0",
"vscode-languageserver-textdocument": "^1.0.1",
"vscode-languageserver-types": "^3.16.0",
"vscode-nls": "^5.0.0",
"vscode-uri": "^3.0.2"
},
"engines": {
"npm": ">=7.0.0"
}
},
"node_modules/vscode-languageserver-textdocument": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/vscode-languageserver-textdocument/-/vscode-languageserver-textdocument-1.0.1.tgz",
"integrity": "sha512-UIcJDjX7IFkck7cSkNNyzIz5FyvpQfY7sdzVy+wkKN/BLaD4DQ0ppXQrKePomCxTS7RrolK1I0pey0bG9eh8dA==",
"dev": true
},
"node_modules/vscode-languageserver-types": {
"version": "3.16.0",
"resolved": "https://registry.npmjs.org/vscode-languageserver-types/-/vscode-languageserver-types-3.16.0.tgz",
"integrity": "sha512-k8luDIWJWyenLc5ToFQQMaSrqCHiLwyKPHKPQZ5zz21vM+vIVUSvsRpcbiECH4WR88K2XZqc4ScRcZ7nk/jbeA==",
"dev": true
},
"node_modules/vscode-nls": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/vscode-nls/-/vscode-nls-5.0.0.tgz",
"integrity": "sha512-u0Lw+IYlgbEJFF6/qAqG2d1jQmJl0eyAGJHoAJqr2HT4M2BNuQYSEiSE75f52pXHSJm8AlTjnLLbBFPrdz2hpA==",
"dev": true
},
"node_modules/vscode-uri": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/vscode-uri/-/vscode-uri-3.0.2.tgz",
"integrity": "sha512-jkjy6pjU1fxUvI51P+gCsxg1u2n8LSt0W6KrCNQceaziKzff74GoWmjVG46KieVzybO1sttPQmYfrwSHey7GUA==",
"dev": true
},
"node_modules/watchpack": {
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/watchpack/-/watchpack-2.3.1.tgz",
"integrity": "sha512-x0t0JuydIo8qCNctdDrn1OzH/qDzk2+rdCOC3YzumZ42fiMqmQ7T3xQurykYMhYfHaPHTp4ZxAx2NfUo1K6QaA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"glob-to-regexp": "^0.4.1",
"graceful-fs": "^4.1.2"
},
"engines": {
"node": ">=10.13.0"
}
},
"node_modules/web-streams-polyfill": {
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/web-streams-polyfill/-/web-streams-polyfill-3.2.0.tgz",
"integrity": "sha512-EqPmREeOzttaLRm5HS7io98goBgZ7IVz79aDvqjD0kYXLtFZTc0T/U6wHTPKyIjb+MdN7DFIIX6hgdBEpWmfPA==",
"dev": true,
"engines": {
"node": ">= 8"
}
},
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"node_modules/webidl-conversions": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz",
"integrity": "sha1-JFNCdeKnvGvnvIZhHMFq4KVlSHE=",
"dev": true
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/webpack": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "5.69.1",
"resolved": "https://registry.npmjs.org/webpack/-/webpack-5.69.1.tgz",
"integrity": "sha512-+VyvOSJXZMT2V5vLzOnDuMz5GxEqLk7hKWQ56YxPW/PQRUuKimPqmEIJOx8jHYeyo65pKbapbW464mvsKbaj4A==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Update npm packages
2022-02-20 18:08:23 +09:00
"@types/eslint-scope": "^3.7.3",
"@types/estree": "^0.0.51",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"@webassemblyjs/ast": "1.11.1",
"@webassemblyjs/wasm-edit": "1.11.1",
"@webassemblyjs/wasm-parser": "1.11.1",
"acorn": "^8.4.1",
"acorn-import-assertions": "^1.7.6",
"browserslist": "^4.14.5",
"chrome-trace-event": "^1.0.2",
"enhanced-resolve": "^5.8.3",
"es-module-lexer": "^0.9.0",
"eslint-scope": "5.1.1",
"events": "^3.2.0",
"glob-to-regexp": "^0.4.1",
Update npm packages
2022-01-23 18:58:15 +09:00
"graceful-fs": "^4.2.9",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"json-parse-better-errors": "^1.0.2",
"loader-runner": "^4.2.0",
"mime-types": "^2.1.27",
"neo-async": "^2.6.2",
"schema-utils": "^3.1.0",
"tapable": "^2.1.1",
"terser-webpack-plugin": "^5.1.3",
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"watchpack": "^2.3.1",
Update npm packages
2022-01-23 18:58:15 +09:00
"webpack-sources": "^3.2.3"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"bin": {
"webpack": "bin/webpack.js"
},
"engines": {
"node": ">=10.13.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
},
"peerDependenciesMeta": {
"webpack-cli": {
"optional": true
}
}
},
"node_modules/webpack-sources": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "3.2.3",
"resolved": "https://registry.npmjs.org/webpack-sources/-/webpack-sources-3.2.3.tgz",
"integrity": "sha512-/DyMEOrDgLKKIG0fmvtz+4dUX/3Ghozwgm6iPp8KRhvn+eQf9+Q7GWxVNMk3+uCPWfdXYC4ExGBckIXdFEfH1w==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"engines": {
"node": ">=10.13.0"
}
},
"node_modules/webpack-stream": {
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/webpack-stream/-/webpack-stream-7.0.0.tgz",
"integrity": "sha512-XoAQTHyCaYMo6TS7Atv1HYhtmBgKiVLONJbzLBl2V3eibXQ2IT/MCRM841RW/r3vToKD5ivrTJFWgd/ghoxoRg==",
"dev": true,
"dependencies": {
"fancy-log": "^1.3.3",
"lodash.clone": "^4.3.2",
"lodash.some": "^4.2.2",
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"memory-fs": "^0.5.0",
"plugin-error": "^1.0.1",
"supports-color": "^8.1.1",
"through": "^2.3.8",
"vinyl": "^2.2.1"
},
"engines": {
"node": ">= 10.0.0"
},
"peerDependencies": {
"webpack": "^5.21.2"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/webpack-stream/node_modules/has-flag": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz",
"integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"engines": {
"node": ">=8"
}
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/webpack-stream/node_modules/supports-color": {
"version": "8.1.1",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-8.1.1.tgz",
"integrity": "sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"has-flag": "^4.0.0"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/chalk/supports-color?sponsor=1"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/webpack/node_modules/schema-utils": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/schema-utils/-/schema-utils-3.1.1.tgz",
"integrity": "sha512-Y5PQxS4ITlC+EahLuXaY86TXfR7Dc5lw294alXOq86JAHCihAIZfqv8nNCWvaEJvaC51uN9hbLGeV0cFBdH+Fw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"@types/json-schema": "^7.0.8",
"ajv": "^6.12.5",
"ajv-keywords": "^3.5.2"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node": ">= 10.13.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/whatwg-url": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/whatwg-url/-/whatwg-url-5.0.0.tgz",
"integrity": "sha1-lmRU6HZUYuN2RNNib2dCzotwll0=",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"tr46": "~0.0.3",
"webidl-conversions": "^3.0.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/which": {
"version": "1.3.1",
"resolved": "https://registry.npmjs.org/which/-/which-1.3.1.tgz",
"integrity": "sha512-HxJdYWq1MTIQbJ3nw0cqssHoTNU267KlrDuGZ1WYlxDStUtKUhOaJmh112/TZmHxxUfuJqPXSOm7tDyas0OSIQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"dependencies": {
"isexe": "^2.0.0"
},
"bin": {
"which": "bin/which"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/which-boxed-primitive": {
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"version": "1.0.2",
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"resolved": "https://registry.npmjs.org/which-boxed-primitive/-/which-boxed-primitive-1.0.2.tgz",
"integrity": "sha512-bwZdv0AKLpplFY2KZRX6TvyuN7ojjr7lwkg6ml0roIy9YeuSr7JS372qlNW18UQYzgYK9ziGcerWqZOmEn9VNg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"dependencies": {
"is-bigint": "^1.0.1",
"is-boolean-object": "^1.1.0",
"is-number-object": "^1.0.4",
"is-string": "^1.0.5",
"is-symbol": "^1.0.3"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/wide-align": {
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"version": "1.1.3",
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"resolved": "https://registry.npmjs.org/wide-align/-/wide-align-1.1.3.tgz",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"integrity": "sha512-QGkOQc8XL6Bt5PwnsExKBPuMKBxnGxWWW3fU55Xt4feHozMUhdUMaBCk290qpm/wG5u/RSKzwdAC4i51YigihA==",
"dev": true,
"dependencies": {
"string-width": "^1.0.2 || 2"
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/window-size": {
"version": "0.1.0",
"resolved": "https://registry.npmjs.org/window-size/-/window-size-0.1.0.tgz",
"integrity": "sha1-VDjNLqk7IC76Ohn+iIeu58lPnJ0=",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"engines": {
"node": ">= 0.8.0"
}
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/winston": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/winston/-/winston-3.1.0.tgz",
"integrity": "sha512-FsQfEE+8YIEeuZEYhHDk5cILo1HOcWkGwvoidLrDgPog0r4bser1lEIOco2dN9zpDJ1M88hfDgZvxe5z4xNcwg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"dependencies": {
"async": "^2.6.0",
"diagnostics": "^1.1.1",
"is-stream": "^1.1.0",
"logform": "^1.9.1",
"one-time": "0.0.4",
"readable-stream": "^2.3.6",
"stack-trace": "0.0.x",
"triple-beam": "^1.3.0",
"winston-transport": "^4.2.0"
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"engines": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node": ">= 6.4.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/winston-transport": {
"version": "4.2.0",
"resolved": "https://registry.npmjs.org/winston-transport/-/winston-transport-4.2.0.tgz",
"integrity": "sha512-0R1bvFqxSlK/ZKTH86nymOuKv/cT1PQBMuDdA7k7f0S9fM44dNH6bXnuxwXPrN8lefJgtZq08BKdyZ0DZIy/rg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"readable-stream": "^2.3.6",
"triple-beam": "^1.2.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node": ">= 6.4.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/winston/node_modules/async": {
"version": "2.6.1",
"resolved": "https://registry.npmjs.org/async/-/async-2.6.1.tgz",
"integrity": "sha512-fNEiL2+AZt6AlAw/29Cr0UDe4sRAHCpEHh54WMz+Bb7QfNcFw4h3loofyJpLeQs4Yx7yuqu/2dLgM5hKOs6HlQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"dependencies": {
"lodash": "^4.17.10"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/wintersmith": {
"version": "2.5.0",
"resolved": "https://registry.npmjs.org/wintersmith/-/wintersmith-2.5.0.tgz",
"integrity": "sha512-2NWoVZOYkzyH2CutEaHyZWBzW9mIxaGuolzcH8lEWOxNROTV3XJ7Fd5VTp46WtvBm77czCXe+SLtEsIt/OSJvA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"async": "^2.6.1",
"chalk": "^2.4.1",
"chokidar": "^2.0.4",
"coffee-script": "^1.12.7",
"highlight.js": "^9.13.1",
"js-yaml": "^3.12.0",
"marked": "^0.5.1",
"mime": "^2.3.1",
"minimatch": "^3.0.3",
"minimist": "^1.2.0",
"mkdirp": "^0.5.1",
"ncp": "^2.0.0",
"npm": "^6.4.1",
"pug": "^2.0.3",
"rimraf": "^2.6.2",
"server-destroy": "^1.0.1",
"slugg": "^1.2.1",
"winston": "^3.1.0"
},
"bin": {
"wintersmith": "bin/wintersmith"
}
},
"node_modules/wintersmith/node_modules/async": {
"version": "2.6.1",
"resolved": "https://registry.npmjs.org/async/-/async-2.6.1.tgz",
"integrity": "sha512-fNEiL2+AZt6AlAw/29Cr0UDe4sRAHCpEHh54WMz+Bb7QfNcFw4h3loofyJpLeQs4Yx7yuqu/2dLgM5hKOs6HlQ==",
"dev": true,
"dependencies": {
"lodash": "^4.17.10"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/wintersmith/node_modules/glob": {
"version": "7.1.6",
"resolved": "https://registry.npmjs.org/glob/-/glob-7.1.6.tgz",
"integrity": "sha512-LwaxwyZ72Lk7vZINtNNrywX0ZuLyStrdDtabefZKAY5ZGJhVtgdznluResxNmPitE0SAO+O26sWTHeKSI2wMBA==",
"dev": true,
"dependencies": {
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
"minimatch": "^3.0.4",
"once": "^1.3.0",
"path-is-absolute": "^1.0.0"
},
"engines": {
"node": "*"
},
"funding": {
"url": "https://github.com/sponsors/isaacs"
}
},
"node_modules/wintersmith/node_modules/marked": {
"version": "0.5.2",
"resolved": "https://registry.npmjs.org/marked/-/marked-0.5.2.tgz",
"integrity": "sha512-fdZvBa7/vSQIZCi4uuwo2N3q+7jJURpMVCcbaX0S1Mg65WZ5ilXvC67MviJAsdjqqgD+CEq4RKo5AYGgINkVAA==",
"dev": true,
"bin": {
"marked": "bin/marked"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/wintersmith/node_modules/mkdirp": {
"version": "0.5.4",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.4.tgz",
"integrity": "sha512-iG9AK/dJLtJ0XNgTuDbSyNS3zECqDlAhnQW4CsNxBG3LQJBbHmRX1egw39DmtOdCAqY+dKXV+sgPgilNWUKMVw==",
"deprecated": "Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)",
"dev": true,
"dependencies": {
"minimist": "^1.2.5"
},
"bin": {
"mkdirp": "bin/cmd.js"
}
},
"node_modules/wintersmith/node_modules/rimraf": {
"version": "2.7.1",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.7.1.tgz",
"integrity": "sha512-uWjbaKIK3T1OSVptzX7Nl6PvQ3qAGtKEtVRjRuazjfL3Bx5eI409VZSqgND+4UNnmzLVdPj9FqFJNPqBZFve4w==",
"dev": true,
"dependencies": {
"glob": "^7.1.3"
},
"bin": {
"rimraf": "bin.js"
}
},
"node_modules/with": {
"version": "5.1.1",
"resolved": "https://registry.npmjs.org/with/-/with-5.1.1.tgz",
"integrity": "sha1-+k2qktrzLE6pTtRTyB8EaGtXXf4=",
"dev": true,
"dependencies": {
"acorn": "^3.1.0",
"acorn-globals": "^3.0.0"
}
},
"node_modules/with/node_modules/acorn": {
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/acorn/-/acorn-3.3.0.tgz",
"integrity": "sha1-ReN/s56No/JbruP/U2niu18iAXo=",
"dev": true,
"bin": {
"acorn": "bin/acorn"
},
"engines": {
"node": ">=0.4.0"
}
},
"node_modules/word-wrap": {
"version": "1.2.3",
"resolved": "https://registry.npmjs.org/word-wrap/-/word-wrap-1.2.3.tgz",
"integrity": "sha512-Hz/mrNwitNRh/HUAtM/VT/5VH+ygD6DV7mYKZAtHOrbs8U7lvPS6xf7EJKMF0uW1KJCl0H701g3ZGus+muE5vQ==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"node_modules/wordwrap": {
"version": "0.0.2",
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.2.tgz",
"integrity": "sha1-t5Zpu0LstAn4PVg8rVLKF+qhZD8=",
"dev": true,
"engines": {
"node": ">=0.4.0"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/wrap-ansi": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-2.1.0.tgz",
"integrity": "sha1-2Pw9KE3QV5T+hJc8rs3Rz4JP3YU=",
"dev": true,
"dependencies": {
"string-width": "^1.0.1",
"strip-ansi": "^3.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/wrappy": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.2.tgz",
"integrity": "sha1-tSQ9jz7BqjXxNkYFvA0QNuMKtp8=",
"dev": true
},
"node_modules/write-file-atomic": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/write-file-atomic/-/write-file-atomic-4.0.1.tgz",
"integrity": "sha512-nSKUxgAbyioruk6hU87QzVbY279oYT6uiwgDoujth2ju4mJ+TZau7SQBhtbTmUyuNYTuXnSyRn66FV0+eCgcrQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"imurmurhash": "^0.1.4",
Update npm packages
2022-02-20 18:08:23 +09:00
"signal-exit": "^3.0.7"
Update npm packages
2022-02-06 19:24:14 +09:00
},
"engines": {
"node": "^12.13.0 || ^14.15.0 || >=16"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
}
},
"node_modules/ws": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "8.5.0",
"resolved": "https://registry.npmjs.org/ws/-/ws-8.5.0.tgz",
"integrity": "sha512-BWX0SWVgLPzYwF8lTzEy1egjhS4S4OEAHfsO8o65WOVsrnSRGaSiUaa9e0ggGlkMTtBlmOpEXiie9RUcBO86qg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"engines": {
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"node": ">=10.0.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"peerDependencies": {
"bufferutil": "^4.0.1",
"utf-8-validate": "^5.0.2"
},
"peerDependenciesMeta": {
"bufferutil": {
"optional": true
},
"utf-8-validate": {
"optional": true
}
}
},
"node_modules/xmlcreate": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/xmlcreate/-/xmlcreate-2.0.4.tgz",
"integrity": "sha512-nquOebG4sngPmGPICTS5EnxqhKbCmz5Ox5hsszI2T6U5qdrJizBc+0ilYSEjTSzU0yZcmvppztXe/5Al5fUwdg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true
},
"node_modules/xtend": {
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"integrity": "sha1-pcbVMr5lbiPbgg77lDofBJmNY68=",
"dev": true,
"engines": {
"node": ">=0.4"
}
},
"node_modules/y18n": {
"version": "3.2.2",
"resolved": "https://registry.npmjs.org/y18n/-/y18n-3.2.2.tgz",
"integrity": "sha512-uGZHXkHnhF0XeeAPgnKfPv1bgKAYyVvmNL1xlKsPYZPaIHxGti2hHqvOCQv71XMsLxu1QjergkqogUnms5D3YQ==",
"dev": true
},
"node_modules/yaml": {
"version": "1.10.2",
"resolved": "https://registry.npmjs.org/yaml/-/yaml-1.10.2.tgz",
"integrity": "sha512-r3vXyErRCYJ7wg28yvBY5VSoAF8ZvlcW9/BwUzEtUsjvX/DKs24dIkuwjtuprwJJHsbyUbLApepYTR1BN4uHrg==",
"dev": true,
"engines": {
"node": ">= 6"
}
},
"node_modules/yargs": {
Update npm packages
2021-12-26 19:09:29 +09:00
"version": "17.3.1",
"resolved": "https://registry.npmjs.org/yargs/-/yargs-17.3.1.tgz",
"integrity": "sha512-WUANQeVgjLbNsEmGk20f+nlHgOqzRFpiGWVaBrYGYIGANIIu3lWjoyi0fNlFmJkvfhCZ6BXINe7/W2O2bV4iaA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"dependencies": {
"cliui": "^7.0.2",
"escalade": "^3.1.1",
"get-caller-file": "^2.0.5",
"require-directory": "^2.1.1",
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"string-width": "^4.2.3",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"y18n": "^5.0.5",
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"yargs-parser": "^21.0.0"
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
},
"engines": {
"node": ">=12"
}
},
"node_modules/yargs-parser": {
"version": "20.2.6",
"resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-20.2.6.tgz",
"integrity": "sha512-AP1+fQIWSM/sMiET8fyayjx/J+JmTPt2Mr0FkrgqB4todtfa53sOsrSAcIrJRD5XS20bKUwaDIuMkWKCEiQLKA==",
"dev": true,
"engines": {
"node": ">=10"
}
},
"node_modules/yargs/node_modules/ansi-regex": {
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
"integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/yargs/node_modules/ansi-styles": {
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz",
"integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==",
"dev": true,
"dependencies": {
"color-convert": "^2.0.1"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/chalk/ansi-styles?sponsor=1"
}
},
"node_modules/yargs/node_modules/cliui": {
"version": "7.0.4",
"resolved": "https://registry.npmjs.org/cliui/-/cliui-7.0.4.tgz",
"integrity": "sha512-OcRE68cOsVMXp1Yvonl/fzkQOyjLSu/8bhPDfQt0e0/Eb283TKP20Fs2MqoPsr9SwA595rRCA+QMzYc9nBP+JQ==",
"dev": true,
"dependencies": {
"string-width": "^4.2.0",
"strip-ansi": "^6.0.0",
"wrap-ansi": "^7.0.0"
}
},
"node_modules/yargs/node_modules/color-convert": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz",
"integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==",
"dev": true,
"dependencies": {
"color-name": "~1.1.4"
},
"engines": {
"node": ">=7.0.0"
}
},
"node_modules/yargs/node_modules/get-caller-file": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/get-caller-file/-/get-caller-file-2.0.5.tgz",
"integrity": "sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==",
"dev": true,
"engines": {
"node": "6.* || 8.* || >= 10.*"
}
},
"node_modules/yargs/node_modules/is-fullwidth-code-point": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz",
"integrity": "sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/yargs/node_modules/string-width": {
"version": "4.2.3",
"resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz",
"integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==",
"dev": true,
"dependencies": {
"emoji-regex": "^8.0.0",
"is-fullwidth-code-point": "^3.0.0",
"strip-ansi": "^6.0.1"
},
"engines": {
"node": ">=8"
}
},
"node_modules/yargs/node_modules/strip-ansi": {
"version": "6.0.1",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
"integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
"dev": true,
"dependencies": {
"ansi-regex": "^5.0.1"
},
"engines": {
"node": ">=8"
}
},
"node_modules/yargs/node_modules/wrap-ansi": {
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-7.0.0.tgz",
"integrity": "sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==",
"dev": true,
"dependencies": {
"ansi-styles": "^4.0.0",
"string-width": "^4.1.0",
"strip-ansi": "^6.0.0"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/chalk/wrap-ansi?sponsor=1"
}
},
"node_modules/yargs/node_modules/y18n": {
"version": "5.0.8",
"resolved": "https://registry.npmjs.org/y18n/-/y18n-5.0.8.tgz",
"integrity": "sha512-0pfFzegeDWJHJIAmTLRP2DwHjdF5s7jo9tuztdQxAhINCdvS+3nGINqPd00AphqJR/0LhANUS6/+7SCb98YOfA==",
"dev": true,
"engines": {
"node": ">=10"
}
},
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"node_modules/yargs/node_modules/yargs-parser": {
"version": "21.0.0",
"resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-21.0.0.tgz",
"integrity": "sha512-z9kApYUOCwoeZ78rfRYYWdiU/iNL6mwwYlkkZfJoyMR1xps+NEBX5X7XmRpxkZHhXJ6+Ey00IwKxBBSW9FIjyA==",
"dev": true,
"engines": {
"node": ">=12"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"node_modules/yauzl": {
"version": "2.10.0",
"resolved": "https://registry.npmjs.org/yauzl/-/yauzl-2.10.0.tgz",
"integrity": "sha1-x+sXyT4RLLEIb6bY5R+wZnt5pfk=",
"dev": true,
"dependencies": {
"buffer-crc32": "~0.2.3",
"fd-slicer": "~1.1.0"
}
},
"node_modules/yazl": {
"version": "2.5.1",
"resolved": "https://registry.npmjs.org/yazl/-/yazl-2.5.1.tgz",
"integrity": "sha512-phENi2PLiHnHb6QBVot+dJnaAZ0xosj7p3fWl+znIjBDlnMI2PsZCJZ306BPTFOaHf5qdDEI8x5qFrSOBN5vrw==",
"dev": true,
"dependencies": {
"buffer-crc32": "~0.2.3"
}
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dependencies": {
Update npm packages
2022-02-06 19:24:14 +09:00
"@ampproject/remapping": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/@ampproject/remapping/-/remapping-2.1.2.tgz",
"integrity": "sha512-hoyByceqwKirw7w3Z7gnIIZC3Wx3J484Y3L/cMpXFbr7d9ZQj2mODrirNzcJa+SM3UlpWXYvKV4RlRpFXlWgXg==",
Update npm packages
2022-02-06 19:24:14 +09:00
"dev": true,
"requires": {
"@jridgewell/trace-mapping": "^0.3.0"
}
},
Update packages
2018-09-10 00:54:24 +09:00
"@babel/code-frame": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.16.7.tgz",
"integrity": "sha512-iAXqUn8IIeBTNd72xsFlgaXHkMBMt6y4HJp1tIaK465CWLT/fG1aqB7ykr95gHHmlBdGbFeWWfyB4NJJ0nmeIg==",
Update packages
2018-09-10 00:54:24 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/highlight": "^7.16.7"
Update packages
2018-09-10 00:54:24 +09:00
}
},
Update `npm` packages
2020-01-31 22:04:49 +09:00
"@babel/compat-data": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.8",
"resolved": "https://registry.npmjs.org/@babel/compat-data/-/compat-data-7.16.8.tgz",
"integrity": "sha512-m7OkX0IdKLKPpBlJtF561YJal5y/jyI5fNfWbPxh2D/nbzzGI4qRyrD8xO2jB24u7l+5I2a43scCG2IrfjC50Q==",
Update `npm` packages
2020-10-18 17:57:52 +09:00
"dev": true
Update `npm` packages
2020-01-31 22:04:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/core": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "7.17.5",
"resolved": "https://registry.npmjs.org/@babel/core/-/core-7.17.5.tgz",
"integrity": "sha512-/BBMw4EvjmyquN5O+t5eh0+YqB3XXJkYD2cjKpYtWOfFy4lQ4UozNSmxAcWT8r2XtZs0ewG+zrfsqeR15i1ajA==",
Update npm packages
2022-01-09 18:05:52 +09:00
"dev": true,
"requires": {
Update npm packages
2022-02-20 18:08:23 +09:00
"@ampproject/remapping": "^2.1.0",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/code-frame": "^7.16.7",
Update npm packages
2022-02-20 18:08:23 +09:00
"@babel/generator": "^7.17.3",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-compilation-targets": "^7.16.7",
"@babel/helper-module-transforms": "^7.16.7",
Update npm packages
2022-02-20 18:08:23 +09:00
"@babel/helpers": "^7.17.2",
"@babel/parser": "^7.17.3",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/template": "^7.16.7",
Update npm packages
2022-02-20 18:08:23 +09:00
"@babel/traverse": "^7.17.3",
Update npm packages
2022-02-06 19:24:14 +09:00
"@babel/types": "^7.17.0",
Update npm packages
2019-11-11 19:22:03 +09:00
"convert-source-map": "^1.7.0",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"debug": "^4.1.0",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"gensync": "^1.0.0-beta.2",
Update `npm` packages
2020-04-02 19:13:14 +09:00
"json5": "^2.1.2",
Update npm packages
2022-02-06 19:24:14 +09:00
"semver": "^6.3.0"
Update packages
2018-09-10 00:54:24 +09:00
},
"dependencies": {
Update npm packages
2019-11-11 19:22:03 +09:00
"convert-source-map": {
Update npm packages
2021-06-27 17:25:40 +09:00
"version": "1.8.0",
"resolved": "https://registry.npmjs.org/convert-source-map/-/convert-source-map-1.8.0.tgz",
"integrity": "sha512-+OQdjP49zViI/6i7nIJpA8rAl4sV/JdPfU9nZs3VqOwGIgizICvuN2ru6fMd+4llL0tar18UYJXfZ/TWtmhUjA==",
Update npm packages
2019-11-11 19:22:03 +09:00
"dev": true,
"requires": {
"safe-buffer": "~5.1.1"
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"debug": {
Update npm packages
2021-07-25 17:24:10 +09:00
"version": "4.3.2",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.2.tgz",
"integrity": "sha512-mOp8wKcvj7XxC78zLgw/ZA+6TSgkoE2C/ienthhRD298T7UNwAg9diBpLRxC0mOezLl4B0xV7M0cCO6P/O0Xhw==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-10-18 17:57:52 +09:00
"ms": "2.1.2"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
},
"ms": {
Update packages
2019-08-25 03:08:09 +09:00
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true
},
Update `npm` packages
2021-03-07 20:00:57 +09:00
"semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
"dev": true
Update packages
2018-09-10 00:54:24 +09:00
}
}
},
Update `eslint-config-prettier`/`eslint-plugin-unicorn` packages to their latest versions Both of these ESLint "helpers" has increased their *major* version numbers, which `npm update` doesn't handle automatically (since that could cause errors), hence this patch which updates them manually. https://www.npmjs.com/package/eslint-config-prettier https://www.npmjs.com/package/eslint-plugin-unicorn
2021-04-14 19:39:19 +09:00
"@babel/eslint-parser": {
Update the `eslint-plugin-unicorn` package to the latest version
2021-11-14 18:27:29 +09:00
"version": "7.16.3",
"resolved": "https://registry.npmjs.org/@babel/eslint-parser/-/eslint-parser-7.16.3.tgz",
"integrity": "sha512-iB4ElZT0jAt7PKVaeVulOECdGe6UnmA/O0P9jlF5g5GBOwDVbna8AXhHRu4s27xQf6OkveyA8iTDv1jHdDejgQ==",
Update `eslint-config-prettier`/`eslint-plugin-unicorn` packages to their latest versions Both of these ESLint "helpers" has increased their *major* version numbers, which `npm update` doesn't handle automatically (since that could cause errors), hence this patch which updates them manually. https://www.npmjs.com/package/eslint-config-prettier https://www.npmjs.com/package/eslint-plugin-unicorn
2021-04-14 19:39:19 +09:00
"dev": true,
"requires": {
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"eslint-scope": "^5.1.1",
"eslint-visitor-keys": "^2.1.0",
Update `eslint-config-prettier`/`eslint-plugin-unicorn` packages to their latest versions Both of these ESLint "helpers" has increased their *major* version numbers, which `npm update` doesn't handle automatically (since that could cause errors), hence this patch which updates them manually. https://www.npmjs.com/package/eslint-config-prettier https://www.npmjs.com/package/eslint-plugin-unicorn
2021-04-14 19:39:19 +09:00
"semver": "^6.3.0"
},
"dependencies": {
"semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
"dev": true
}
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/generator": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "7.17.3",
"resolved": "https://registry.npmjs.org/@babel/generator/-/generator-7.17.3.tgz",
"integrity": "sha512-+R6Dctil/MgUsZsZAkYgK+ADNSZzJRRy0TvY65T71z/CR854xHQ1EweBYXdfT+HNeN7w0cSJJEzgxZMv40pxsg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-02-06 19:24:14 +09:00
"@babel/types": "^7.17.0",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"jsesc": "^2.5.1",
Update packages
2019-10-18 23:42:02 +09:00
"source-map": "^0.5.0"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
},
"dependencies": {
"source-map": {
"version": "0.5.7",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.7.tgz",
"integrity": "sha1-igOdLRAh0i0eoUyA2OpGi6LvP8w=",
"dev": true
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/helper-annotate-as-pure": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-annotate-as-pure/-/helper-annotate-as-pure-7.16.7.tgz",
"integrity": "sha512-s6t2w/IPQVTAET1HitoowRGXooX8mCgtuP5195wD/QJPV6wYjpujCGF7JuMODVX2ZAJOf1GT6DT9MHEZvLOFSw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/helper-builder-binary-assignment-operator-visitor": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-builder-binary-assignment-operator-visitor/-/helper-builder-binary-assignment-operator-visitor-7.16.7.tgz",
"integrity": "sha512-C6FdbRaxYjwVu/geKW4ZeQ0Q31AftgRcdSnZ5/jsH6BzCJbtvXvhpfkbkThYSuutZA7nCXpPR6AD9zd1dprMkA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-explode-assignable-expression": "^7.16.7",
"@babel/types": "^7.16.7"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update `npm` packages
2020-01-31 22:04:49 +09:00
"@babel/helper-compilation-targets": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-compilation-targets/-/helper-compilation-targets-7.16.7.tgz",
"integrity": "sha512-mGojBwIWcwGD6rfqgRXVlVYmPAv7eOpIemUG3dGnDdCY4Pae70ROij3XmfrH6Fa1h1aiDylpglbZyktfzyo/hA==",
Update `npm` packages
2020-01-31 22:04:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/compat-data": "^7.16.4",
"@babel/helper-validator-option": "^7.16.7",
Update npm packages
2021-12-26 19:09:29 +09:00
"browserslist": "^4.17.5",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"semver": "^6.3.0"
},
"dependencies": {
"semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
"dev": true
}
Update npm packages
2019-11-11 19:22:03 +09:00
}
},
Update `npm` packages
2020-05-30 17:58:10 +09:00
"@babel/helper-create-class-features-plugin": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.10",
"resolved": "https://registry.npmjs.org/@babel/helper-create-class-features-plugin/-/helper-create-class-features-plugin-7.16.10.tgz",
"integrity": "sha512-wDeej0pu3WN/ffTxMNCPW5UCiOav8IcLRxSIyp/9+IF2xJUM9h/OYjg0IJLHaL6F8oU8kqMz9nc1vryXhMsgXg==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-annotate-as-pure": "^7.16.7",
"@babel/helper-environment-visitor": "^7.16.7",
"@babel/helper-function-name": "^7.16.7",
"@babel/helper-member-expression-to-functions": "^7.16.7",
"@babel/helper-optimise-call-expression": "^7.16.7",
"@babel/helper-replace-supers": "^7.16.7",
"@babel/helper-split-export-declaration": "^7.16.7"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update `npm` packages
2020-05-30 17:58:10 +09:00
"@babel/helper-create-regexp-features-plugin": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-create-regexp-features-plugin/-/helper-create-regexp-features-plugin-7.16.7.tgz",
"integrity": "sha512-fk5A6ymfp+O5+p2yCkXAu5Kyj6v0xh0RBeNcAkYUMDvvAAoxvSKXn+Jb37t/yWFiQVDFK1ELpUTD8/aLhCPu+g==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-annotate-as-pure": "^7.16.7",
Update `npm` packages
2020-10-18 17:57:52 +09:00
"regexpu-core": "^4.7.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update `npm` packages
2021-03-07 20:00:57 +09:00
"@babel/helper-define-polyfill-provider": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "0.3.1",
"resolved": "https://registry.npmjs.org/@babel/helper-define-polyfill-provider/-/helper-define-polyfill-provider-0.3.1.tgz",
"integrity": "sha512-J9hGMpJQmtWmj46B3kBHmL38UhJGhYX7eqkcq+2gsstyYt341HmPeWspihX43yVRA0mS+8GGk2Gckc7bY/HCmA==",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"dev": true,
"requires": {
"@babel/helper-compilation-targets": "^7.13.0",
"@babel/helper-module-imports": "^7.12.13",
"@babel/helper-plugin-utils": "^7.13.0",
"@babel/traverse": "^7.13.0",
"debug": "^4.1.1",
"lodash.debounce": "^4.0.8",
"resolve": "^1.14.2",
"semver": "^6.1.2"
},
"dependencies": {
Update `npm` packages
2021-04-18 18:02:42 +09:00
"debug": {
Update npm packages
2021-11-28 18:40:29 +09:00
"version": "4.3.3",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.3.tgz",
"integrity": "sha512-/zxw5+vh1Tfv+4Qn7a5nsbcJKPaSvCDhojn6FEl9vupwK2VCSDtEiEtqr8DFtzYFOdz63LBkxec7DYuc2jon6Q==",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"dev": true,
"requires": {
Update `npm` packages
2021-04-18 18:02:42 +09:00
"ms": "2.1.2"
Update `npm` packages
2021-03-07 20:00:57 +09:00
}
},
"ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
},
"resolve": {
"version": "1.20.0",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.20.0.tgz",
Update `npm` packages
2021-04-18 18:02:42 +09:00
"integrity": "sha512-wENBPt4ySzg4ybFQW2TT1zMQucPK95HSh/nq2CFTZVOGut2+pQvSsgtda4d26YrYcr067wjbmzOG8byDPBX63A==",
"dev": true,
"requires": {
"is-core-module": "^2.2.0",
"path-parse": "^1.0.6"
}
Update `npm` packages
2020-08-09 18:03:07 +09:00
},
Update `npm` packages
2021-04-18 18:02:42 +09:00
"semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
Update `npm` packages
2020-05-30 17:58:10 +09:00
"dev": true
}
}
},
Update npm packages
2021-12-26 19:09:29 +09:00
"@babel/helper-environment-visitor": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-environment-visitor/-/helper-environment-visitor-7.16.7.tgz",
"integrity": "sha512-SLLb0AAn6PkUeAfKJCCOl9e1R53pQlGAfc4y4XuMRZfqeMYLE0dM1LMhqbGAlGQY0lfw5/ohoYWAe9V1yibRag==",
Update npm packages
2021-12-26 19:09:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Update npm packages
2021-12-26 19:09:29 +09:00
}
},
Update `npm` packages
2021-04-18 18:02:42 +09:00
"@babel/helper-explode-assignable-expression": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-explode-assignable-expression/-/helper-explode-assignable-expression-7.16.7.tgz",
"integrity": "sha512-KyUenhWMC8VrxzkGP0Jizjo4/Zx+1nNZhgocs+gLzyZyB8SHidhoq9KK/8Ato4anhwsivfkBLftky7gvzbZMtQ==",
Update `npm` packages
2021-04-18 18:02:42 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Update `npm` packages
2021-04-18 18:02:42 +09:00
}
},
"@babel/helper-function-name": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-function-name/-/helper-function-name-7.16.7.tgz",
"integrity": "sha512-QfDfEnIUyyBSR3HtrtGECuZ6DAyCkYFp7GHl75vFtTnn6pjKeK0T1DB5lLkFvBea8MdaiUABx3osbgLyInoejA==",
Update `npm` packages
2021-04-18 18:02:42 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-get-function-arity": "^7.16.7",
"@babel/template": "^7.16.7",
"@babel/types": "^7.16.7"
Update `npm` packages
2021-04-18 18:02:42 +09:00
}
},
"@babel/helper-get-function-arity": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-get-function-arity/-/helper-get-function-arity-7.16.7.tgz",
"integrity": "sha512-flc+RLSOBXzNzVhcLu6ujeHUrD6tANAOU5ojrRx/as+tbzf8+stUCj7+IfRRoAbEZqj/ahXEMsjhOhgeZsrnTw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Update `npm` packages
2021-04-18 18:02:42 +09:00
}
},
"@babel/helper-hoist-variables": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-hoist-variables/-/helper-hoist-variables-7.16.7.tgz",
"integrity": "sha512-m04d/0Op34H5v7pbZw6pSKP7weA6lsMvfiIAMeIvkY/R4xQtBSMFEigu9QTZ2qB/9l22vsxtM8a+Q8CzD255fg==",
Update `npm` packages
2021-04-18 18:02:42 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update npm packages
2021-05-02 16:30:09 +09:00
"@babel/helper-member-expression-to-functions": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-member-expression-to-functions/-/helper-member-expression-to-functions-7.16.7.tgz",
"integrity": "sha512-VtJ/65tYiU/6AbMTDwyoXGPKHgTsfRarivm+YbB5uAzKUyuPjgZSgAFeG87FCigc7KNHu2Pegh1XIT3lXjvz3Q==",
Update npm packages
2021-05-02 16:30:09 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Update npm packages
2021-05-02 16:30:09 +09:00
}
},
Update `npm` packages
2021-04-18 18:02:42 +09:00
"@babel/helper-module-imports": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-module-imports/-/helper-module-imports-7.16.7.tgz",
"integrity": "sha512-LVtS6TqjJHFc+nYeITRo6VLXve70xmq7wPhWTqDJusJEgGmkAACWwMiTNrvfoQo6hEhFwAIixNkvB0jPXDL8Wg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Update `npm` packages
2020-08-09 18:03:07 +09:00
}
},
Update `npm` packages
2021-04-18 18:02:42 +09:00
"@babel/helper-module-transforms": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-module-transforms/-/helper-module-transforms-7.16.7.tgz",
"integrity": "sha512-gaqtLDxJEFCeQbYp9aLAefjhkKdjKcdh6DB7jniIGU3Pz52WAmP268zK0VgPz9hUNkMSYeH976K2/Y6yPadpng==",
Update `npm` packages
2020-08-09 18:03:07 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-environment-visitor": "^7.16.7",
"@babel/helper-module-imports": "^7.16.7",
"@babel/helper-simple-access": "^7.16.7",
"@babel/helper-split-export-declaration": "^7.16.7",
"@babel/helper-validator-identifier": "^7.16.7",
"@babel/template": "^7.16.7",
"@babel/traverse": "^7.16.7",
"@babel/types": "^7.16.7"
Update npm packages
2021-09-05 16:47:57 +09:00
}
},
"@babel/helper-optimise-call-expression": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-optimise-call-expression/-/helper-optimise-call-expression-7.16.7.tgz",
"integrity": "sha512-EtgBhg7rd/JcnpZFXpBy0ze1YRfdm7BnBX4uKMBd3ixa3RGAE002JZB66FJyNH7g0F38U05pXmA5P8cBh7z+1w==",
Update npm packages
2021-09-05 16:47:57 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Update npm packages
2021-09-05 16:47:57 +09:00
}
},
Update npm packages
2021-10-17 18:33:19 +09:00
"@babel/helper-plugin-utils": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-plugin-utils/-/helper-plugin-utils-7.16.7.tgz",
"integrity": "sha512-Qg3Nk7ZxpgMrsox6HreY1ZNKdBq7K72tDSliA6dCl5f007jR4ne8iD5UzuNnCJH2xBf2BEEVGr+/OL6Gdp7RxA==",
Update npm packages
2021-10-17 18:33:19 +09:00
"dev": true
},
"@babel/helper-remap-async-to-generator": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.8",
"resolved": "https://registry.npmjs.org/@babel/helper-remap-async-to-generator/-/helper-remap-async-to-generator-7.16.8.tgz",
"integrity": "sha512-fm0gH7Flb8H51LqJHy3HJ3wnE1+qtYR2A99K06ahwrawLdOFsCEWjZOrYricXJHoPSudNKxrMBUPEIPxiIIvBw==",
Update npm packages
2021-09-05 16:47:57 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-annotate-as-pure": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/helper-wrap-function": "^7.16.8",
"@babel/types": "^7.16.8"
Update npm packages
2021-10-17 18:33:19 +09:00
}
},
"@babel/helper-replace-supers": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-replace-supers/-/helper-replace-supers-7.16.7.tgz",
"integrity": "sha512-y9vsWilTNaVnVh6xiJfABzsNpgDPKev9HnAgz6Gb1p6UUwf9NepdlsV7VXGCftJM+jqD5f7JIEubcpLjZj5dBw==",
Update npm packages
2021-10-17 18:33:19 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-environment-visitor": "^7.16.7",
"@babel/helper-member-expression-to-functions": "^7.16.7",
"@babel/helper-optimise-call-expression": "^7.16.7",
"@babel/traverse": "^7.16.7",
"@babel/types": "^7.16.7"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update npm packages
2021-10-17 18:33:19 +09:00
"@babel/helper-simple-access": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-simple-access/-/helper-simple-access-7.16.7.tgz",
"integrity": "sha512-ZIzHVyoeLMvXMN/vok/a4LWRy8G2v205mNP0XOuf9XRLyX5/u9CnVulUtDgUTama3lT+bf/UqucuZjqiGuTS1g==",
Update npm packages
2021-10-17 18:33:19 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Update npm packages
2021-10-17 18:33:19 +09:00
}
},
"@babel/helper-skip-transparent-expression-wrappers": {
Update npm packages
2021-10-31 17:38:18 +09:00
"version": "7.16.0",
"resolved": "https://registry.npmjs.org/@babel/helper-skip-transparent-expression-wrappers/-/helper-skip-transparent-expression-wrappers-7.16.0.tgz",
"integrity": "sha512-+il1gTy0oHwUsBQZyJvukbB4vPMdcYBrFHa0Uc4AizLxbq6BOYC51Rv4tWocX9BLBDLZ4kc6qUFpQ6HRgL+3zw==",
Update npm packages
2021-10-17 18:33:19 +09:00
"dev": true,
"requires": {
Update npm packages
2021-10-31 17:38:18 +09:00
"@babel/types": "^7.16.0"
Update npm packages
2021-10-17 18:33:19 +09:00
}
},
"@babel/helper-split-export-declaration": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-split-export-declaration/-/helper-split-export-declaration-7.16.7.tgz",
"integrity": "sha512-xbWoy/PFoxSWazIToT9Sif+jJTlrMcndIsaOKvTA6u7QEo7ilkRZpjew18/W3c7nm8fXdUDXh02VXTbZ0pGDNw==",
Update npm packages
2021-10-17 18:33:19 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/types": "^7.16.7"
Update npm packages
2021-10-17 18:33:19 +09:00
}
},
"@babel/helper-validator-identifier": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-validator-identifier/-/helper-validator-identifier-7.16.7.tgz",
"integrity": "sha512-hsEnFemeiW4D08A5gUAZxLBTXpZ39P+a+DGDsHw1yxqyQ/jzFEnxf5uTEGp+3bzAbNOxU1paTgYS4ECU/IgfDw==",
Update npm packages
2021-10-17 18:33:19 +09:00
"dev": true
},
"@babel/helper-validator-option": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/helper-validator-option/-/helper-validator-option-7.16.7.tgz",
"integrity": "sha512-TRtenOuRUVo9oIQGPC5G9DgK4743cdxvtOw0weQNpZXaS16SCBi5MNjZF8vba3ETURjZpTbVn7Vvcf2eAwFozQ==",
Update npm packages
2021-10-17 18:33:19 +09:00
"dev": true
},
"@babel/helper-wrap-function": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.8",
"resolved": "https://registry.npmjs.org/@babel/helper-wrap-function/-/helper-wrap-function-7.16.8.tgz",
"integrity": "sha512-8RpyRVIAW1RcDDGTA+GpPAwV22wXCfKOoM9bet6TLkGIFTkRQSkH1nMQ5Yet4MpoXe1ZwHPVtNasc2w0uZMqnw==",
Update npm packages
2021-10-17 18:33:19 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-function-name": "^7.16.7",
"@babel/template": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/traverse": "^7.16.8",
"@babel/types": "^7.16.8"
Update npm packages
2021-10-17 18:33:19 +09:00
}
},
"@babel/helpers": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "7.17.2",
"resolved": "https://registry.npmjs.org/@babel/helpers/-/helpers-7.17.2.tgz",
"integrity": "sha512-0Qu7RLR1dILozr/6M0xgj+DFPmi6Bnulgm9M8BVa9ZCWxDqlSnqt3cf8IDPB5m45sVXUZ0kuQAgUrdSFFH79fQ==",
Update npm packages
2021-10-17 18:33:19 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/template": "^7.16.7",
Update npm packages
2022-02-06 19:24:14 +09:00
"@babel/traverse": "^7.17.0",
"@babel/types": "^7.17.0"
Update npm packages
2021-10-17 18:33:19 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/highlight": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/highlight/-/highlight-7.16.7.tgz",
"integrity": "sha512-aKpPMfLvGO3Q97V0qhw/V2SWNWlwfJknuwAunU7wZLSfrM4xTBvg7E5opUVi1kJTBKihE38CPg4nBiqX83PWYw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-validator-identifier": "^7.16.7",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"chalk": "^2.0.0",
"js-tokens": "^4.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/parser": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "7.17.3",
"resolved": "https://registry.npmjs.org/@babel/parser/-/parser-7.17.3.tgz",
"integrity": "sha512-7yJPvPV+ESz2IUTPbOL+YkIGyCqOyNIzdguKQuJGnH7bg1WTIifuM21YqokFt/THWh1AkCRn9IgoykTRCBVpzA==",
Update packages
2018-11-18 05:32:10 +09:00
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update npm packages
2021-10-31 17:38:18 +09:00
"@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression/-/plugin-bugfix-safari-id-destructuring-collision-in-function-expression-7.16.7.tgz",
"integrity": "sha512-anv/DObl7waiGEnC24O9zqL0pSuI9hljihqiDuFHC8d7/bjr/4RLGPWuc8rYOff/QPzbEPSkzG8wGG9aDuhHRg==",
Update npm packages
2021-10-31 17:38:18 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update npm packages
2021-10-31 17:38:18 +09:00
}
},
Update `npm` packages
2021-04-04 17:53:29 +09:00
"@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining/-/plugin-bugfix-v8-spread-parameters-in-optional-chaining-7.16.7.tgz",
"integrity": "sha512-di8vUHRdf+4aJ7ltXhaDbPoszdkh59AQtJM5soLsuHpQJdFQZOA4uGj0V2u/CZ8bJ/u8ULDL5yq6FO/bCXnKHw==",
Update `npm` packages
2021-04-04 17:53:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Update npm packages
2021-10-31 17:38:18 +09:00
"@babel/helper-skip-transparent-expression-wrappers": "^7.16.0",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/plugin-proposal-optional-chaining": "^7.16.7"
Update `npm` packages
2021-04-04 17:53:29 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-proposal-async-generator-functions": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.8",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-async-generator-functions/-/plugin-proposal-async-generator-functions-7.16.8.tgz",
"integrity": "sha512-71YHIvMuiuqWJQkebWJtdhQTfd4Q4mF76q2IX37uZPkG9+olBxsX+rH1vkhFto4UeJZ9dPY2s+mDvhDm1u2BGQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/helper-remap-async-to-generator": "^7.16.8",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"@babel/plugin-syntax-async-generators": "^7.8.4"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update `npm` packages
2020-05-30 17:58:10 +09:00
"@babel/plugin-proposal-class-properties": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-class-properties/-/plugin-proposal-class-properties-7.16.7.tgz",
"integrity": "sha512-IobU0Xme31ewjYOShSIqd/ZGM/r/cuOz2z0MDbNrhF5FW+ZVgi0f2lyeoj9KFPDOAqsYxmLWZte1WOwlvY9aww==",
Update `npm` packages
2020-05-30 17:58:10 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-create-class-features-plugin": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7"
Update `npm` packages
2020-05-30 17:58:10 +09:00
}
},
Update npm packages
2021-05-02 16:30:09 +09:00
"@babel/plugin-proposal-class-static-block": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-class-static-block/-/plugin-proposal-class-static-block-7.16.7.tgz",
"integrity": "sha512-dgqJJrcZoG/4CkMopzhPJjGxsIe9A8RlkQLnL/Vhhx8AA9ZuaRwGSlscSh42hazc7WSrya/IK7mTeoF0DP9tEw==",
Update npm packages
2021-05-02 16:30:09 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-create-class-features-plugin": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
Update npm packages
2021-06-13 16:59:44 +09:00
"@babel/plugin-syntax-class-static-block": "^7.14.5"
Update npm packages
2021-05-02 16:30:09 +09:00
}
},
Update packages
2019-08-25 03:08:09 +09:00
"@babel/plugin-proposal-dynamic-import": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-dynamic-import/-/plugin-proposal-dynamic-import-7.16.7.tgz",
"integrity": "sha512-I8SW9Ho3/8DRSdmDdH3gORdyUuYnk1m4cMxUAdu5oy4n3OfN8flDEH+d60iG7dUfi0KkYwSvoalHzzdRzpWHTg==",
Update packages
2019-08-25 03:08:09 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"@babel/plugin-syntax-dynamic-import": "^7.8.3"
Update packages
2019-08-25 03:08:09 +09:00
}
},
Update `npm` packages
2020-08-09 18:03:07 +09:00
"@babel/plugin-proposal-export-namespace-from": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-export-namespace-from/-/plugin-proposal-export-namespace-from-7.16.7.tgz",
"integrity": "sha512-ZxdtqDXLRGBL64ocZcs7ovt71L3jhC1RGSyR996svrCi3PYqHNkb3SwPJCs8RIzD86s+WPpt2S73+EHCGO+NUA==",
Update `npm` packages
2020-08-09 18:03:07 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Update `npm` packages
2020-08-09 18:03:07 +09:00
"@babel/plugin-syntax-export-namespace-from": "^7.8.3"
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-proposal-json-strings": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-json-strings/-/plugin-proposal-json-strings-7.16.7.tgz",
"integrity": "sha512-lNZ3EEggsGY78JavgbHsK9u5P3pQaW7k4axlgFLYkMd7UBsiNahCITShLjNQschPyjtO6dADrL24757IdhBrsQ==",
Update `npm` packages
2020-01-31 22:04:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"@babel/plugin-syntax-json-strings": "^7.8.3"
Update `npm` packages
2020-01-31 22:04:49 +09:00
}
},
Update `npm` packages
2020-08-09 18:03:07 +09:00
"@babel/plugin-proposal-logical-assignment-operators": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-logical-assignment-operators/-/plugin-proposal-logical-assignment-operators-7.16.7.tgz",
"integrity": "sha512-K3XzyZJGQCr00+EtYtrDjmwX7o7PLK6U9bi1nCwkQioRFVUv6dJoxbQjtWVtP+bCPy82bONBKG8NPyQ4+i6yjg==",
Update `npm` packages
2020-08-09 18:03:07 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Update `npm` packages
2020-08-09 18:03:07 +09:00
"@babel/plugin-syntax-logical-assignment-operators": "^7.10.4"
}
},
Update `npm` packages
2020-01-31 22:04:49 +09:00
"@babel/plugin-proposal-nullish-coalescing-operator": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-nullish-coalescing-operator/-/plugin-proposal-nullish-coalescing-operator-7.16.7.tgz",
"integrity": "sha512-aUOrYU3EVtjf62jQrCj63pYZ7k6vns2h/DQvHPWGmsJRYzWXZ6/AsfgpiRy6XiuIDADhJzP2Q9MwSMKauBQ+UQ==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"@babel/plugin-syntax-nullish-coalescing-operator": "^7.8.3"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update `npm` packages
2020-04-02 19:13:14 +09:00
"@babel/plugin-proposal-numeric-separator": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-numeric-separator/-/plugin-proposal-numeric-separator-7.16.7.tgz",
"integrity": "sha512-vQgPMknOIgiuVqbokToyXbkY/OmmjAzr/0lhSIbG/KmnzXPGwW/AdhdKpi+O4X/VkWiWjnkKOBiqJrTaC98VKw==",
Update `npm` packages
2020-04-02 19:13:14 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Update `npm` packages
2020-07-13 18:05:50 +09:00
"@babel/plugin-syntax-numeric-separator": "^7.10.4"
Update `npm` packages
2020-04-02 19:13:14 +09:00
}
},
"@babel/plugin-proposal-object-rest-spread": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-object-rest-spread/-/plugin-proposal-object-rest-spread-7.16.7.tgz",
"integrity": "sha512-3O0Y4+dw94HA86qSg9IHfyPktgR7q3gpNVAeiKQd+8jBKFaU5NQS1Yatgo4wY+UFNuLjvxcSmzcsHqrhgTyBUA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-12-26 19:09:29 +09:00
"@babel/compat-data": "^7.16.4",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-compilation-targets": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"@babel/plugin-syntax-object-rest-spread": "^7.8.3",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/plugin-transform-parameters": "^7.16.7"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
},
"@babel/plugin-proposal-optional-catch-binding": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-optional-catch-binding/-/plugin-proposal-optional-catch-binding-7.16.7.tgz",
"integrity": "sha512-eMOH/L4OvWSZAE1VkHbr1vckLG1WUcHGJSLqqQwl2GaUqG6QjddvrOaTUMNYiv77H5IKPMZ9U9P7EaHwvAShfA==",
Update `npm` packages
2020-01-31 22:04:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"@babel/plugin-syntax-optional-catch-binding": "^7.8.3"
Update `npm` packages
2020-01-31 22:04:49 +09:00
}
},
"@babel/plugin-proposal-optional-chaining": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-optional-chaining/-/plugin-proposal-optional-chaining-7.16.7.tgz",
"integrity": "sha512-eC3xy+ZrUcBtP7x+sq62Q/HYd674pPTb/77XZMb5wbDPGWIdUbSr4Agr052+zaUPSb+gGRnjxXfKFvx5iMJ+DA==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Update npm packages
2021-10-31 17:38:18 +09:00
"@babel/helper-skip-transparent-expression-wrappers": "^7.16.0",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"@babel/plugin-syntax-optional-chaining": "^7.8.3"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
},
Update `npm` packages
2020-05-30 17:58:10 +09:00
"@babel/plugin-proposal-private-methods": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.11",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-private-methods/-/plugin-proposal-private-methods-7.16.11.tgz",
"integrity": "sha512-F/2uAkPlXDr8+BHpZvo19w3hLFKge+k75XUprE6jaqKxjGkSYcK+4c+bup5PdW/7W/Rpjwql7FTVEDW+fRAQsw==",
Update `npm` packages
2020-05-30 17:58:10 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/helper-create-class-features-plugin": "^7.16.10",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update `npm` packages
2020-05-30 17:58:10 +09:00
}
},
Update npm packages
2021-05-02 16:30:09 +09:00
"@babel/plugin-proposal-private-property-in-object": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-private-property-in-object/-/plugin-proposal-private-property-in-object-7.16.7.tgz",
"integrity": "sha512-rMQkjcOFbm+ufe3bTZLyOfsOUOxyvLXZJCTARhJr+8UMSoZmqTe1K1BgkFcrW37rAchWg57yI69ORxiWvUINuQ==",
Update npm packages
2021-05-02 16:30:09 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-annotate-as-pure": "^7.16.7",
"@babel/helper-create-class-features-plugin": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
Update npm packages
2021-06-13 16:59:44 +09:00
"@babel/plugin-syntax-private-property-in-object": "^7.14.5"
Update npm packages
2021-05-02 16:30:09 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-proposal-unicode-property-regex": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-proposal-unicode-property-regex/-/plugin-proposal-unicode-property-regex-7.16.7.tgz",
"integrity": "sha512-QRK0YI/40VLhNVGIjRNAAQkEHws0cswSdFFjpFyt943YmJIU1da9uW63Iu6NFV6CxTZW5eTDCrwZUstBWgp/Rg==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-create-regexp-features-plugin": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-syntax-async-generators": {
Update `npm` packages
2020-01-31 22:04:49 +09:00
"version": "7.8.4",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-async-generators/-/plugin-syntax-async-generators-7.8.4.tgz",
"integrity": "sha512-tycmZxkGfZaxhMRbXlPXuVFpdWlXpir2W4AMhSJgRKzk/eDlIXOhb2LHWoLpDF7TEHylV5zNhykX6KAgHJmTNw==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-01-31 22:04:49 +09:00
"@babel/helper-plugin-utils": "^7.8.0"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update `npm` packages
2020-05-30 17:58:10 +09:00
"@babel/plugin-syntax-class-properties": {
Update `npm` packages
2021-02-07 19:55:03 +09:00
"version": "7.12.13",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-class-properties/-/plugin-syntax-class-properties-7.12.13.tgz",
"integrity": "sha512-fm4idjKla0YahUNgFNLCB0qySdsoPiZP3iQE3rky0mBUtMZ23yDJ9SJdg6dXTSDnulOVqiF3Hgr9nbXvXTQZYA==",
Update `npm` packages
2020-05-30 17:58:10 +09:00
"dev": true,
"requires": {
Update `npm` packages
2021-02-07 19:55:03 +09:00
"@babel/helper-plugin-utils": "^7.12.13"
Update `npm` packages
2020-05-30 17:58:10 +09:00
}
},
Update npm packages
2021-05-02 16:30:09 +09:00
"@babel/plugin-syntax-class-static-block": {
Update npm packages
2021-06-13 16:59:44 +09:00
"version": "7.14.5",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-class-static-block/-/plugin-syntax-class-static-block-7.14.5.tgz",
"integrity": "sha512-b+YyPmr6ldyNnM6sqYeMWE+bgJcJpO6yS4QD7ymxgH34GBPNDM/THBh8iunyvKIZztiwLH4CJZ0RxTk9emgpjw==",
Update npm packages
2021-05-02 16:30:09 +09:00
"dev": true,
"requires": {
Update npm packages
2021-06-13 16:59:44 +09:00
"@babel/helper-plugin-utils": "^7.14.5"
Update npm packages
2021-05-02 16:30:09 +09:00
}
},
Update packages
2019-08-25 03:08:09 +09:00
"@babel/plugin-syntax-dynamic-import": {
Update `npm` packages
2020-01-31 22:04:49 +09:00
"version": "7.8.3",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-dynamic-import/-/plugin-syntax-dynamic-import-7.8.3.tgz",
"integrity": "sha512-5gdGbFon+PszYzqs83S3E5mpi7/y/8M9eC90MRTZfduQOYW76ig6SOSPNe41IG5LoP3FGBn2N0RjVDSQiS94kQ==",
Update packages
2019-08-25 03:08:09 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-01-31 22:04:49 +09:00
"@babel/helper-plugin-utils": "^7.8.0"
Update packages
2019-08-25 03:08:09 +09:00
}
},
Update `npm` packages
2020-08-09 18:03:07 +09:00
"@babel/plugin-syntax-export-namespace-from": {
"version": "7.8.3",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-export-namespace-from/-/plugin-syntax-export-namespace-from-7.8.3.tgz",
"integrity": "sha512-MXf5laXo6c1IbEbegDmzGPwGNTsHZmEy6QGznu5Sh2UCWvueywb2ee+CCE4zQiZstxU9BMoQO9i6zUFSY0Kj0Q==",
"dev": true,
"requires": {
"@babel/helper-plugin-utils": "^7.8.3"
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-syntax-json-strings": {
Update `npm` packages
2020-01-31 22:04:49 +09:00
"version": "7.8.3",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-json-strings/-/plugin-syntax-json-strings-7.8.3.tgz",
"integrity": "sha512-lY6kdGpWHvjoe2vk4WrAapEuBR69EMxZl+RoGRhrFGNYVK8mOPAW8VfbT/ZgrFbXlDNiiaxQnAtgVCZ6jv30EA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-01-31 22:04:49 +09:00
"@babel/helper-plugin-utils": "^7.8.0"
}
},
Update `npm` packages
2020-08-09 18:03:07 +09:00
"@babel/plugin-syntax-logical-assignment-operators": {
"version": "7.10.4",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-logical-assignment-operators/-/plugin-syntax-logical-assignment-operators-7.10.4.tgz",
"integrity": "sha512-d8waShlpFDinQ5MtvGU9xDAOzKH47+FFoney2baFIoMr952hKOLp1HR7VszoZvOsV/4+RRszNY7D17ba0te0ig==",
"dev": true,
"requires": {
"@babel/helper-plugin-utils": "^7.10.4"
}
},
Update `npm` packages
2020-01-31 22:04:49 +09:00
"@babel/plugin-syntax-nullish-coalescing-operator": {
"version": "7.8.3",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-nullish-coalescing-operator/-/plugin-syntax-nullish-coalescing-operator-7.8.3.tgz",
"integrity": "sha512-aSff4zPII1u2QD7y+F8oDsz19ew4IGEJg9SVW+bqwpwtfFleiQDMdzA/R+UlWDzfnHFCxxleFT0PMIrR36XLNQ==",
"dev": true,
"requires": {
"@babel/helper-plugin-utils": "^7.8.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update `npm` packages
2020-04-02 19:13:14 +09:00
"@babel/plugin-syntax-numeric-separator": {
Update `npm` packages
2020-07-13 18:05:50 +09:00
"version": "7.10.4",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-numeric-separator/-/plugin-syntax-numeric-separator-7.10.4.tgz",
"integrity": "sha512-9H6YdfkcK/uOnY/K7/aA2xpzaAgkQn37yzWUMRK7OaPOqOpGS1+n0H5hxT9AUw9EsSjPW8SVyMJwYRtWs3X3ug==",
Update `npm` packages
2020-04-02 19:13:14 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-07-13 18:05:50 +09:00
"@babel/helper-plugin-utils": "^7.10.4"
Update `npm` packages
2020-04-02 19:13:14 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-syntax-object-rest-spread": {
Update `npm` packages
2020-01-31 22:04:49 +09:00
"version": "7.8.3",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-object-rest-spread/-/plugin-syntax-object-rest-spread-7.8.3.tgz",
"integrity": "sha512-XoqMijGZb9y3y2XskN+P1wUGiVwWZ5JmoDRwx5+3GmEplNyVM2s2Dg8ILFQm8rWM48orGy5YpI5Bl8U1y7ydlA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-01-31 22:04:49 +09:00
"@babel/helper-plugin-utils": "^7.8.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-syntax-optional-catch-binding": {
Update `npm` packages
2020-01-31 22:04:49 +09:00
"version": "7.8.3",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-optional-catch-binding/-/plugin-syntax-optional-catch-binding-7.8.3.tgz",
"integrity": "sha512-6VPD0Pc1lpTqw0aKoeRTMiB+kWhAoT24PA+ksWSBrFtl5SIRVpZlwN3NNPQjehA2E/91FV3RjLWoVTglWcSV3Q==",
"dev": true,
"requires": {
"@babel/helper-plugin-utils": "^7.8.0"
}
},
"@babel/plugin-syntax-optional-chaining": {
"version": "7.8.3",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-optional-chaining/-/plugin-syntax-optional-chaining-7.8.3.tgz",
"integrity": "sha512-KoK9ErH1MBlCPxV0VANkXW2/dw4vlbGDrFgz8bmUsBGYkFRcbRwMh6cIJubdPrkxRwuGdtCk0v/wPTKbQgBjkg==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-01-31 22:04:49 +09:00
"@babel/helper-plugin-utils": "^7.8.0"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update npm packages
2021-05-02 16:30:09 +09:00
"@babel/plugin-syntax-private-property-in-object": {
Update npm packages
2021-06-13 16:59:44 +09:00
"version": "7.14.5",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-private-property-in-object/-/plugin-syntax-private-property-in-object-7.14.5.tgz",
"integrity": "sha512-0wVnp9dxJ72ZUJDV27ZfbSj6iHLoytYZmh3rFcxNnvsJF3ktkzLDZPy/mA17HGsaQT3/DQsWYX1f1QGWkCoVUg==",
Update npm packages
2021-05-02 16:30:09 +09:00
"dev": true,
"requires": {
Update npm packages
2021-06-13 16:59:44 +09:00
"@babel/helper-plugin-utils": "^7.14.5"
Update npm packages
2021-05-02 16:30:09 +09:00
}
Update npm packages
2021-10-17 18:33:19 +09:00
},
"@babel/plugin-syntax-top-level-await": {
"version": "7.14.5",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-top-level-await/-/plugin-syntax-top-level-await-7.14.5.tgz",
"integrity": "sha512-hx++upLv5U1rgYfwe1xBQUhRmU41NEvpUvrp8jkrSCdvGSnM5/qdRMtylJ6PG5OFkBaHkbTAKTnd3/YyESRHFw==",
"dev": true,
"requires": {
"@babel/helper-plugin-utils": "^7.14.5"
}
},
"@babel/plugin-transform-arrow-functions": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-arrow-functions/-/plugin-transform-arrow-functions-7.16.7.tgz",
"integrity": "sha512-9ffkFFMbvzTvv+7dTp/66xvZAWASuPD5Tl9LK3Z9vhOmANo6j94rik+5YMBt4CwHVMWLWpMsriIc2zsa3WW3xQ==",
Update npm packages
2021-10-17 18:33:19 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update npm packages
2021-10-17 18:33:19 +09:00
}
},
"@babel/plugin-transform-async-to-generator": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.8",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-async-to-generator/-/plugin-transform-async-to-generator-7.16.8.tgz",
"integrity": "sha512-MtmUmTJQHCnyJVrScNzNlofQJ3dLFuobYn3mwOTKHnSCMtbNsqvF71GQmJfFjdrXSsAA7iysFmYWw4bXZ20hOg==",
Update npm packages
2021-10-17 18:33:19 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-module-imports": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/helper-remap-async-to-generator": "^7.16.8"
Update npm packages
2021-10-17 18:33:19 +09:00
}
},
"@babel/plugin-transform-block-scoped-functions": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-block-scoped-functions/-/plugin-transform-block-scoped-functions-7.16.7.tgz",
"integrity": "sha512-JUuzlzmF40Z9cXyytcbZEZKckgrQzChbQJw/5PuEHYeqzCsvebDx0K0jWnIIVcmmDOAVctCgnYs0pMcrYj2zJg==",
Update npm packages
2021-10-17 18:33:19 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update npm packages
2021-10-17 18:33:19 +09:00
}
},
"@babel/plugin-transform-block-scoping": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-block-scoping/-/plugin-transform-block-scoping-7.16.7.tgz",
"integrity": "sha512-ObZev2nxVAYA4bhyusELdo9hb3H+A56bxH3FZMbEImZFiEDYVHXQSJ1hQKFlDnlt8G9bBrCZ5ZpURZUrV4G5qQ==",
Update npm packages
2021-10-17 18:33:19 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update npm packages
2021-10-17 18:33:19 +09:00
}
},
"@babel/plugin-transform-classes": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-classes/-/plugin-transform-classes-7.16.7.tgz",
"integrity": "sha512-WY7og38SFAGYRe64BrjKf8OrE6ulEHtr5jEYaZMwox9KebgqPi67Zqz8K53EKk1fFEJgm96r32rkKZ3qA2nCWQ==",
"dev": true,
"requires": {
"@babel/helper-annotate-as-pure": "^7.16.7",
"@babel/helper-environment-visitor": "^7.16.7",
"@babel/helper-function-name": "^7.16.7",
"@babel/helper-optimise-call-expression": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
"@babel/helper-replace-supers": "^7.16.7",
"@babel/helper-split-export-declaration": "^7.16.7",
Update npm packages
2021-10-17 18:33:19 +09:00
"globals": "^11.1.0"
},
"dependencies": {
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"globals": {
"version": "11.12.0",
"resolved": "https://registry.npmjs.org/globals/-/globals-11.12.0.tgz",
"integrity": "sha512-WOBp/EEGUiIsJSp7wcv/y6MO+lV9UoncWqxuFfm8eBwzWNgyfBd6Gz+IeKQ9jCmyhoH99g15M3T+QaVHFjizVA==",
"dev": true
}
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-computed-properties": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-computed-properties/-/plugin-transform-computed-properties-7.16.7.tgz",
"integrity": "sha512-gN72G9bcmenVILj//sv1zLNaPyYcOzUho2lIJBMh/iakJ9ygCo/hEF9cpGb61SCMEDxbbyBoVQxrt+bWKu5KGw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-destructuring": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-destructuring/-/plugin-transform-destructuring-7.16.7.tgz",
"integrity": "sha512-VqAwhTHBnu5xBVDCvrvqJbtLUa++qZaWC0Fgr2mqokBlulZARGyIvZDoqbPlPaKImQ9dKAcCzbv+ul//uqu70A==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-dotall-regex": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-dotall-regex/-/plugin-transform-dotall-regex-7.16.7.tgz",
"integrity": "sha512-Lyttaao2SjZF6Pf4vk1dVKv8YypMpomAbygW+mU5cYP3S5cWTfCJjG8xV6CFdzGFlfWK81IjL9viiTvpb6G7gQ==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-create-regexp-features-plugin": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-duplicate-keys": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-duplicate-keys/-/plugin-transform-duplicate-keys-7.16.7.tgz",
"integrity": "sha512-03DvpbRfvWIXyK0/6QiR1KMTWeT6OcQ7tbhjrXyFS02kjuX/mu5Bvnh5SDSWHxyawit2g5aWhKwI86EE7GUnTw==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-exponentiation-operator": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-exponentiation-operator/-/plugin-transform-exponentiation-operator-7.16.7.tgz",
"integrity": "sha512-8UYLSlyLgRixQvlYH3J2ekXFHDFLQutdy7FfFAMm3CPZ6q9wHCwnUyiXpQCe3gVVnQlHc5nsuiEVziteRNTXEA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-builder-binary-assignment-operator-visitor": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-for-of": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-for-of/-/plugin-transform-for-of-7.16.7.tgz",
"integrity": "sha512-/QZm9W92Ptpw7sjI9Nx1mbcsWz33+l8kuMIQnDwgQBG5s3fAfQvkRjQ7NqXhtNcKOnPkdICmUHyCaWW06HCsqg==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-function-name": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-function-name/-/plugin-transform-function-name-7.16.7.tgz",
"integrity": "sha512-SU/C68YVwTRxqWj5kgsbKINakGag0KTgq9f2iZEXdStoAbOzLHEBRYzImmA6yFo8YZhJVflvXmIHUO7GWHmxxA==",
Update `npm` packages
2021-04-18 18:02:42 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-compilation-targets": "^7.16.7",
"@babel/helper-function-name": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-literals": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-literals/-/plugin-transform-literals-7.16.7.tgz",
"integrity": "sha512-6tH8RTpTWI0s2sV6uq3e/C9wPo4PTqqZps4uF0kzQ9/xPLFQtipynvmT1g/dOfEJ+0EQsHhkQ/zyRId8J2b8zQ==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update packages
2019-04-14 00:25:41 +09:00
"@babel/plugin-transform-member-expression-literals": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-member-expression-literals/-/plugin-transform-member-expression-literals-7.16.7.tgz",
"integrity": "sha512-mBruRMbktKQwbxaJof32LT9KLy2f3gH+27a5XSuXo6h7R3vqltl0PgZ80C8ZMKw98Bf8bqt6BEVi3svOh2PzMw==",
Update packages
2019-04-14 00:25:41 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update packages
2019-04-14 00:25:41 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-modules-amd": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-modules-amd/-/plugin-transform-modules-amd-7.16.7.tgz",
"integrity": "sha512-KaaEtgBL7FKYwjJ/teH63oAmE3lP34N3kshz8mm4VMAw7U3PxjVwwUmxEFksbgsNUaO3wId9R2AVQYSEGRa2+g==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-module-transforms": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
Update `npm` packages
2020-05-02 20:23:41 +09:00
"babel-plugin-dynamic-import-node": "^2.3.3"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-modules-commonjs": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.8",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-modules-commonjs/-/plugin-transform-modules-commonjs-7.16.8.tgz",
"integrity": "sha512-oflKPvsLT2+uKQopesJt3ApiaIS2HW+hzHFcwRNtyDGieAeC/dIHZX8buJQ2J2X1rxGPy4eRcUijm3qcSPjYcA==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-module-transforms": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
"@babel/helper-simple-access": "^7.16.7",
Update `npm` packages
2020-05-02 20:23:41 +09:00
"babel-plugin-dynamic-import-node": "^2.3.3"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-modules-systemjs": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-modules-systemjs/-/plugin-transform-modules-systemjs-7.16.7.tgz",
"integrity": "sha512-DuK5E3k+QQmnOqBR9UkusByy5WZWGRxfzV529s9nPra1GE7olmxfqO2FHobEOYSPIjPBTr4p66YDcjQnt8cBmw==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-hoist-variables": "^7.16.7",
"@babel/helper-module-transforms": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
"@babel/helper-validator-identifier": "^7.16.7",
Update `npm` packages
2020-05-02 20:23:41 +09:00
"babel-plugin-dynamic-import-node": "^2.3.3"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-modules-umd": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-modules-umd/-/plugin-transform-modules-umd-7.16.7.tgz",
"integrity": "sha512-EMh7uolsC8O4xhudF2F6wedbSHm1HHZ0C6aJ7K67zcDNidMzVcxWdGr+htW9n21klm+bOn+Rx4CBsAntZd3rEQ==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-module-transforms": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update packages
2019-02-18 00:44:36 +09:00
"@babel/plugin-transform-named-capturing-groups-regex": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.8",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-named-capturing-groups-regex/-/plugin-transform-named-capturing-groups-regex-7.16.8.tgz",
"integrity": "sha512-j3Jw+n5PvpmhRR+mrgIh04puSANCk/T/UA3m3P1MjJkhlK906+ApHhDIqBQDdOgL/r1UYpz4GNclTXxyZrYGSw==",
Update packages
2019-02-18 00:44:36 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-create-regexp-features-plugin": "^7.16.7"
Update packages
2019-02-18 00:44:36 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-new-target": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-new-target/-/plugin-transform-new-target-7.16.7.tgz",
"integrity": "sha512-xiLDzWNMfKoGOpc6t3U+etCE2yRnn3SM09BXqWPIZOBpL2gvVrBWUKnsJx0K/ADi5F5YC5f8APFfWrz25TdlGg==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-object-super": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-object-super/-/plugin-transform-object-super-7.16.7.tgz",
"integrity": "sha512-14J1feiQVWaGvRxj2WjyMuXS2jsBkgB3MdSN5HuC2G5nRspa5RK9COcs82Pwy5BuGcjb+fYaUj94mYcOj7rCvw==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
"@babel/helper-replace-supers": "^7.16.7"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-parameters": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-parameters/-/plugin-transform-parameters-7.16.7.tgz",
"integrity": "sha512-AT3MufQ7zZEhU2hwOA11axBnExW0Lszu4RL/tAlUJBuNoRak+wehQW8h6KcXOcgjY42fHtDxswuMhMjFEuv/aw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2019-04-14 00:25:41 +09:00
"@babel/plugin-transform-property-literals": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-property-literals/-/plugin-transform-property-literals-7.16.7.tgz",
"integrity": "sha512-z4FGr9NMGdoIl1RqavCqGG+ZuYjfZ/hkCIeuH6Do7tXmSm0ls11nYVSJqFEUOSJbDab5wC6lRE/w6YjVcr6Hqw==",
Update packages
2019-04-14 00:25:41 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update packages
2019-04-14 00:25:41 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-regenerator": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-regenerator/-/plugin-transform-regenerator-7.16.7.tgz",
"integrity": "sha512-mF7jOgGYCkSJagJ6XCujSQg+6xC1M77/03K2oBmVJWoFGNUtnVJO4WHKJk3dnPC8HCcj4xBQP1Egm8DWh3Pb3Q==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-03-06 21:06:21 +09:00
"regenerator-transform": "^0.14.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2019-04-14 00:25:41 +09:00
"@babel/plugin-transform-reserved-words": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-reserved-words/-/plugin-transform-reserved-words-7.16.7.tgz",
"integrity": "sha512-KQzzDnZ9hWQBjwi5lpY5v9shmm6IVG0U9pB18zvMu2i4H90xpT4gmqwPYsn8rObiadYe2M0gmgsiOIF5A/2rtg==",
Update packages
2019-04-14 00:25:41 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update packages
2019-04-14 00:25:41 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-runtime": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "7.17.0",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-runtime/-/plugin-transform-runtime-7.17.0.tgz",
"integrity": "sha512-fr7zPWnKXNc1xoHfrIU9mN/4XKX4VLZ45Q+oMhfsYIaHvg7mHgmhfOy/ckRWqDK7XF3QDigRpkh5DKq6+clE8A==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-module-imports": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
Update npm packages
2021-11-28 18:40:29 +09:00
"babel-plugin-polyfill-corejs2": "^0.3.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"babel-plugin-polyfill-corejs3": "^0.5.0",
Update npm packages
2021-11-28 18:40:29 +09:00
"babel-plugin-polyfill-regenerator": "^0.3.0",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"semver": "^6.3.0"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
},
"dependencies": {
"semver": {
Update `npm` packages
2021-03-07 20:00:57 +09:00
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true
}
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-shorthand-properties": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-shorthand-properties/-/plugin-transform-shorthand-properties-7.16.7.tgz",
"integrity": "sha512-hah2+FEnoRoATdIb05IOXf+4GzXYTq75TVhIn1PewihbpyrNWUt2JbudKQOETWw6QpLe+AIUpJ5MVLYTQbeeUg==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-spread": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-spread/-/plugin-transform-spread-7.16.7.tgz",
"integrity": "sha512-+pjJpgAngb53L0iaA5gU/1MLXJIfXcYepLgXB3esVRf4fqmj8f2cxM3/FKaHsZms08hFQJkFccEWuIpm429TXg==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7",
Update npm packages
2021-10-31 17:38:18 +09:00
"@babel/helper-skip-transparent-expression-wrappers": "^7.16.0"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
},
"@babel/plugin-transform-sticky-regex": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-sticky-regex/-/plugin-transform-sticky-regex-7.16.7.tgz",
"integrity": "sha512-NJa0Bd/87QV5NZZzTuZG5BPJjLYadeSZ9fO6oOUoL4iQx+9EEuw/eEM92SrsT19Yc2jgB1u1hsjqDtH02c3Drw==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-template-literals": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-template-literals/-/plugin-transform-template-literals-7.16.7.tgz",
"integrity": "sha512-VwbkDDUeenlIjmfNeDX/V0aWrQH2QiVyJtwymVQSzItFDTpxfyJh3EVaQiS0rIN/CqbLGr0VcGmuwyTdZtdIsA==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-typeof-symbol": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-typeof-symbol/-/plugin-transform-typeof-symbol-7.16.7.tgz",
"integrity": "sha512-p2rOixCKRJzpg9JB4gjnG4gjWkWa89ZoYUnl9snJ1cWIcTH/hvxZqfO+WjG6T8DRBpctEol5jw1O5rA8gkCokQ==",
Update `npm` packages
2020-05-30 17:58:10 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update `npm` packages
2020-05-30 17:58:10 +09:00
}
},
"@babel/plugin-transform-unicode-escapes": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-unicode-escapes/-/plugin-transform-unicode-escapes-7.16.7.tgz",
"integrity": "sha512-TAV5IGahIz3yZ9/Hfv35TV2xEm+kaBDaZQCn2S/hG9/CZ0DktxJv9eKfPc7yYCvOYR4JGx1h8C+jcSOvgaaI/Q==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-plugin-utils": "^7.16.7"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/plugin-transform-unicode-regex": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-unicode-regex/-/plugin-transform-unicode-regex-7.16.7.tgz",
"integrity": "sha512-oC5tYYKw56HO75KZVLQ+R/Nl3Hro9kf8iG0hXoaHP7tjAyCpvqBiSNe6vGrZni1Z6MggmUOC6A7VP7AVmw225Q==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-create-regexp-features-plugin": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/preset-env": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "7.16.11",
"resolved": "https://registry.npmjs.org/@babel/preset-env/-/preset-env-7.16.11.tgz",
"integrity": "sha512-qcmWG8R7ZW6WBRPZK//y+E3Cli151B20W1Rv7ln27vuPaXU/8TKms6jFdiJtF7UDTxcrb7mZd88tAeK9LjdT8g==",
Update npm packages
2021-06-13 16:59:44 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/compat-data": "^7.16.8",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-compilation-targets": "^7.16.7",
"@babel/helper-plugin-utils": "^7.16.7",
"@babel/helper-validator-option": "^7.16.7",
"@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression": "^7.16.7",
"@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/plugin-proposal-async-generator-functions": "^7.16.8",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/plugin-proposal-class-properties": "^7.16.7",
"@babel/plugin-proposal-class-static-block": "^7.16.7",
"@babel/plugin-proposal-dynamic-import": "^7.16.7",
"@babel/plugin-proposal-export-namespace-from": "^7.16.7",
"@babel/plugin-proposal-json-strings": "^7.16.7",
"@babel/plugin-proposal-logical-assignment-operators": "^7.16.7",
"@babel/plugin-proposal-nullish-coalescing-operator": "^7.16.7",
"@babel/plugin-proposal-numeric-separator": "^7.16.7",
"@babel/plugin-proposal-object-rest-spread": "^7.16.7",
"@babel/plugin-proposal-optional-catch-binding": "^7.16.7",
"@babel/plugin-proposal-optional-chaining": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/plugin-proposal-private-methods": "^7.16.11",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/plugin-proposal-private-property-in-object": "^7.16.7",
"@babel/plugin-proposal-unicode-property-regex": "^7.16.7",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"@babel/plugin-syntax-async-generators": "^7.8.4",
Update `npm` packages
2021-02-07 19:55:03 +09:00
"@babel/plugin-syntax-class-properties": "^7.12.13",
Update npm packages
2021-06-13 16:59:44 +09:00
"@babel/plugin-syntax-class-static-block": "^7.14.5",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"@babel/plugin-syntax-dynamic-import": "^7.8.3",
Update `npm` packages
2020-08-09 18:03:07 +09:00
"@babel/plugin-syntax-export-namespace-from": "^7.8.3",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"@babel/plugin-syntax-json-strings": "^7.8.3",
Update `npm` packages
2020-08-09 18:03:07 +09:00
"@babel/plugin-syntax-logical-assignment-operators": "^7.10.4",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"@babel/plugin-syntax-nullish-coalescing-operator": "^7.8.3",
Update `npm` packages
2020-07-13 18:05:50 +09:00
"@babel/plugin-syntax-numeric-separator": "^7.10.4",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"@babel/plugin-syntax-object-rest-spread": "^7.8.3",
"@babel/plugin-syntax-optional-catch-binding": "^7.8.3",
"@babel/plugin-syntax-optional-chaining": "^7.8.3",
Update npm packages
2021-06-13 16:59:44 +09:00
"@babel/plugin-syntax-private-property-in-object": "^7.14.5",
"@babel/plugin-syntax-top-level-await": "^7.14.5",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/plugin-transform-arrow-functions": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/plugin-transform-async-to-generator": "^7.16.8",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/plugin-transform-block-scoped-functions": "^7.16.7",
"@babel/plugin-transform-block-scoping": "^7.16.7",
"@babel/plugin-transform-classes": "^7.16.7",
"@babel/plugin-transform-computed-properties": "^7.16.7",
"@babel/plugin-transform-destructuring": "^7.16.7",
"@babel/plugin-transform-dotall-regex": "^7.16.7",
"@babel/plugin-transform-duplicate-keys": "^7.16.7",
"@babel/plugin-transform-exponentiation-operator": "^7.16.7",
"@babel/plugin-transform-for-of": "^7.16.7",
"@babel/plugin-transform-function-name": "^7.16.7",
"@babel/plugin-transform-literals": "^7.16.7",
"@babel/plugin-transform-member-expression-literals": "^7.16.7",
"@babel/plugin-transform-modules-amd": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/plugin-transform-modules-commonjs": "^7.16.8",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/plugin-transform-modules-systemjs": "^7.16.7",
"@babel/plugin-transform-modules-umd": "^7.16.7",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/plugin-transform-named-capturing-groups-regex": "^7.16.8",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/plugin-transform-new-target": "^7.16.7",
"@babel/plugin-transform-object-super": "^7.16.7",
"@babel/plugin-transform-parameters": "^7.16.7",
"@babel/plugin-transform-property-literals": "^7.16.7",
"@babel/plugin-transform-regenerator": "^7.16.7",
"@babel/plugin-transform-reserved-words": "^7.16.7",
"@babel/plugin-transform-shorthand-properties": "^7.16.7",
"@babel/plugin-transform-spread": "^7.16.7",
"@babel/plugin-transform-sticky-regex": "^7.16.7",
"@babel/plugin-transform-template-literals": "^7.16.7",
"@babel/plugin-transform-typeof-symbol": "^7.16.7",
"@babel/plugin-transform-unicode-escapes": "^7.16.7",
"@babel/plugin-transform-unicode-regex": "^7.16.7",
Update npm packages
2021-10-31 17:38:18 +09:00
"@babel/preset-modules": "^0.1.5",
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/types": "^7.16.8",
Update npm packages
2021-11-28 18:40:29 +09:00
"babel-plugin-polyfill-corejs2": "^0.3.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"babel-plugin-polyfill-corejs3": "^0.5.0",
Update npm packages
2021-11-28 18:40:29 +09:00
"babel-plugin-polyfill-regenerator": "^0.3.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"core-js-compat": "^3.20.2",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"semver": "^6.3.0"
Update `npm` packages
2020-09-06 18:49:49 +09:00
},
"dependencies": {
Update `npm` packages
2021-03-07 20:00:57 +09:00
"semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
"dev": true
Update `npm` packages
2020-09-06 18:49:49 +09:00
}
Update `npm` packages
2020-04-02 19:13:14 +09:00
}
},
"@babel/preset-modules": {
Update npm packages
2021-10-31 17:38:18 +09:00
"version": "0.1.5",
"resolved": "https://registry.npmjs.org/@babel/preset-modules/-/preset-modules-0.1.5.tgz",
"integrity": "sha512-A57th6YRG7oR3cq/yt/Y84MvGgE0eJG2F1JLhKuyG+jFxEgrd/HAMJatiFtmOiZurz+0DkrvbheCLaV5f2JfjA==",
Update `npm` packages
2020-04-02 19:13:14 +09:00
"dev": true,
"requires": {
"@babel/helper-plugin-utils": "^7.0.0",
"@babel/plugin-proposal-unicode-property-regex": "^7.4.4",
"@babel/plugin-transform-dotall-regex": "^7.4.4",
"@babel/types": "^7.4.4",
"esutils": "^2.0.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/runtime": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "7.17.2",
"resolved": "https://registry.npmjs.org/@babel/runtime/-/runtime-7.17.2.tgz",
"integrity": "sha512-hzeyJyMA1YGdJTuWU0e/j4wKXrU4OMFvY2MSlaI9B7VQb0r5cxTE3EAIS2Q7Tn2RIcDkRvTA/v2JsAEhxe99uw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-03-06 21:06:21 +09:00
"regenerator-runtime": "^0.13.4"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"regenerator-runtime": {
Update npm packages
2021-07-25 17:24:10 +09:00
"version": "0.13.9",
"resolved": "https://registry.npmjs.org/regenerator-runtime/-/regenerator-runtime-0.13.9.tgz",
"integrity": "sha512-p3VT+cOEgxFsRRA9X4lkI1E+k2/CtnKtU4gcxyaCUreilL/vqI6CdZ3wxVUx3UOUg+gnUOQQcRI7BmSI656MYA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
}
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/template": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "7.16.7",
"resolved": "https://registry.npmjs.org/@babel/template/-/template-7.16.7.tgz",
"integrity": "sha512-I8j/x8kHUrbYRTUxXrrMbfCa7jxkE7tZre39x3kjr9hvI82cK1FfqLygotcWN5kdPGWcLdWMHpSBavse5tWw3w==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/code-frame": "^7.16.7",
"@babel/parser": "^7.16.7",
"@babel/types": "^7.16.7"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
},
"@babel/traverse": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "7.17.3",
"resolved": "https://registry.npmjs.org/@babel/traverse/-/traverse-7.17.3.tgz",
"integrity": "sha512-5irClVky7TxRWIRtxlh2WPUUOLhcPN06AGgaQSB8AEwuyEBgJVuJ5imdHm5zxk8w0QS5T+tDfnDxAlhWjpb7cw==",
Update npm packages
2022-01-09 18:05:52 +09:00
"dev": true,
"requires": {
"@babel/code-frame": "^7.16.7",
Update npm packages
2022-02-20 18:08:23 +09:00
"@babel/generator": "^7.17.3",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-environment-visitor": "^7.16.7",
"@babel/helper-function-name": "^7.16.7",
"@babel/helper-hoist-variables": "^7.16.7",
"@babel/helper-split-export-declaration": "^7.16.7",
Update npm packages
2022-02-20 18:08:23 +09:00
"@babel/parser": "^7.17.3",
Update npm packages
2022-02-06 19:24:14 +09:00
"@babel/types": "^7.17.0",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"debug": "^4.1.0",
Update `npm` packages
2021-04-18 18:02:42 +09:00
"globals": "^11.1.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"debug": {
Update npm packages
2021-08-08 17:45:36 +09:00
"version": "4.3.2",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.2.tgz",
"integrity": "sha512-mOp8wKcvj7XxC78zLgw/ZA+6TSgkoE2C/ienthhRD298T7UNwAg9diBpLRxC0mOezLl4B0xV7M0cCO6P/O0Xhw==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update `npm` packages
2021-04-18 18:02:42 +09:00
"ms": "2.1.2"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
},
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"globals": {
"version": "11.12.0",
"resolved": "https://registry.npmjs.org/globals/-/globals-11.12.0.tgz",
"integrity": "sha512-WOBp/EEGUiIsJSp7wcv/y6MO+lV9UoncWqxuFfm8eBwzWNgyfBd6Gz+IeKQ9jCmyhoH99g15M3T+QaVHFjizVA==",
"dev": true
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"ms": {
Update packages
2019-08-25 03:08:09 +09:00
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
}
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@babel/types": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "7.17.0",
"resolved": "https://registry.npmjs.org/@babel/types/-/types-7.17.0.tgz",
"integrity": "sha512-TmKSNO4D5rzhL5bjWFcVHHLETzfQ/AmbKpKPOSjlP0WoHZ6L911fgoOKY4Alp/emzG4cHJdyN49zpgkbXFEHHw==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-validator-identifier": "^7.16.7",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"to-fast-properties": "^2.0.0"
},
"dependencies": {
"to-fast-properties": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/to-fast-properties/-/to-fast-properties-2.0.0.tgz",
"integrity": "sha1-3F5pjL0HkmW8c+A3doGk5Og/YW4=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
}
}
},
Update `npm` packages
2020-09-06 18:49:49 +09:00
"@eslint/eslintrc": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/@eslint/eslintrc/-/eslintrc-1.1.0.tgz",
"integrity": "sha512-C1DfL7XX4nPqGd6jcP01W9pVM1HYCuUkFk1432D7F0v3JSlUIeOYn9oCoi3eoLZ+iwBSb29BMFxxny0YrrEZqg==",
Update `npm` packages
2020-09-06 18:49:49 +09:00
"dev": true,
"requires": {
"ajv": "^6.12.4",
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"debug": "^4.3.2",
Update npm packages
2022-02-20 18:08:23 +09:00
"espree": "^9.3.1",
Update npm packages
2021-06-13 16:59:44 +09:00
"globals": "^13.9.0",
Update `npm` packages
2020-09-06 18:49:49 +09:00
"ignore": "^4.0.6",
"import-fresh": "^3.2.1",
Update npm packages
2021-11-14 18:17:30 +09:00
"js-yaml": "^4.1.0",
Update `npm` packages
2020-09-06 18:49:49 +09:00
"minimatch": "^3.0.4",
"strip-json-comments": "^3.1.1"
},
"dependencies": {
Update npm packages
2021-11-14 18:17:30 +09:00
"argparse": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/argparse/-/argparse-2.0.1.tgz",
"integrity": "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==",
"dev": true
},
Update `npm` packages
2020-09-06 18:49:49 +09:00
"debug": {
Update npm packages
2021-11-28 18:40:29 +09:00
"version": "4.3.3",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.3.tgz",
"integrity": "sha512-/zxw5+vh1Tfv+4Qn7a5nsbcJKPaSvCDhojn6FEl9vupwK2VCSDtEiEtqr8DFtzYFOdz63LBkxec7DYuc2jon6Q==",
Update `npm` packages
2020-09-06 18:49:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-09-20 18:34:24 +09:00
"ms": "2.1.2"
Update `npm` packages
2020-09-06 18:49:49 +09:00
}
},
Update npm packages
2021-11-14 18:17:30 +09:00
"js-yaml": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.0.tgz",
"integrity": "sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==",
"dev": true,
"requires": {
"argparse": "^2.0.1"
}
},
Update `npm` packages
2020-09-06 18:49:49 +09:00
"ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
Update npm packages
2021-05-30 14:43:13 +09:00
}
}
},
Update npm packages
2021-07-11 19:14:47 +09:00
"@humanwhocodes/config-array": {
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"version": "0.9.2",
"resolved": "https://registry.npmjs.org/@humanwhocodes/config-array/-/config-array-0.9.2.tgz",
"integrity": "sha512-UXOuFCGcwciWckOpmfKDq/GyhlTf9pN/BzG//x8p8zTOFEcGuA68ANXheFS0AGvy3qgZqLBUkMs7hqzqCKOVwA==",
Update npm packages
2021-07-11 19:14:47 +09:00
"dev": true,
"requires": {
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"@humanwhocodes/object-schema": "^1.2.1",
Update npm packages
2021-07-11 19:14:47 +09:00
"debug": "^4.1.1",
"minimatch": "^3.0.4"
},
"dependencies": {
"debug": {
Update npm packages
2021-11-28 18:40:29 +09:00
"version": "4.3.3",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.3.tgz",
"integrity": "sha512-/zxw5+vh1Tfv+4Qn7a5nsbcJKPaSvCDhojn6FEl9vupwK2VCSDtEiEtqr8DFtzYFOdz63LBkxec7DYuc2jon6Q==",
Update npm packages
2021-07-11 19:14:47 +09:00
"dev": true,
"requires": {
"ms": "2.1.2"
}
},
"ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
}
}
},
"@humanwhocodes/object-schema": {
Update npm packages
2021-11-14 18:17:30 +09:00
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/@humanwhocodes/object-schema/-/object-schema-1.2.1.tgz",
"integrity": "sha512-ZnQMnLV4e7hDlUvw8H+U8ASL02SS2Gn6+9Ac3wGGLIe7+je2AeAOxPY+izIPJDfFDb7eDjev0Us8MO1iFRN8hA==",
Update npm packages
2021-07-11 19:14:47 +09:00
"dev": true
},
Add support for modern ECMAScript `class` features With ESLint 8 we should now finally be able to start using modern `class` features, see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Public_class_fields and https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Private_class_fields However, while both ESLint and Acorn now support this, it unfortunately turns out that Escodegen (which we use during building) still lack the necessary support. Looking at https://github.com/estools/escodegen there's not been any updates since last year, and there's also open PRs adding support for these new `class` features. To avoid blocking usage of these `class` features in the PDF.js code-base, in particular *private* fields/methods, this patch thus proposes that we (hopefully temporarily) switch to an `escodegen` fork that has the necessary support; please see https://www.npmjs.com/package/@javascript-obfuscator/escodegen While I have no reason to doubt the security of the `escodegen` fork, this patch nonetheless pins the version number. Furthermore, I've also diffed the output of the two `.js`-files in this forked package against the original files without finding anything that looks immediately "dangerous".
2021-10-17 20:30:09 +09:00
"@javascript-obfuscator/escodegen": {
Update the `@javascript-obfuscator/escodegen` package to the latest version The only changes are support for [Class static initialization blocks](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Class_static_initialization_blocks), and the diff for the `node_modules\@javascript-obfuscator\escodegen\escodegen.js` file contains only: ```diff @@ -1506,6 +1506,13 @@ return result; }, + StaticBlock: function (stmt, flags) { + return [ + 'static' + space, + this.BlockStatement(stmt, flags) + ]; + }, + ThrowStatement: function (stmt, flags) { return [join( 'throw', ```
2022-02-06 19:26:07 +09:00
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/@javascript-obfuscator/escodegen/-/escodegen-2.3.0.tgz",
"integrity": "sha512-QVXwMIKqYMl3KwtTirYIA6gOCiJ0ZDtptXqAv/8KWLG9uQU2fZqTVy7a/A5RvcoZhbDoFfveTxuGxJ5ibzQtkw==",
Add support for modern ECMAScript `class` features With ESLint 8 we should now finally be able to start using modern `class` features, see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Public_class_fields and https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Private_class_fields However, while both ESLint and Acorn now support this, it unfortunately turns out that Escodegen (which we use during building) still lack the necessary support. Looking at https://github.com/estools/escodegen there's not been any updates since last year, and there's also open PRs adding support for these new `class` features. To avoid blocking usage of these `class` features in the PDF.js code-base, in particular *private* fields/methods, this patch thus proposes that we (hopefully temporarily) switch to an `escodegen` fork that has the necessary support; please see https://www.npmjs.com/package/@javascript-obfuscator/escodegen While I have no reason to doubt the security of the `escodegen` fork, this patch nonetheless pins the version number. Furthermore, I've also diffed the output of the two `.js`-files in this forked package against the original files without finding anything that looks immediately "dangerous".
2021-10-17 20:30:09 +09:00
"dev": true,
"requires": {
"@javascript-obfuscator/estraverse": "^5.3.0",
"esprima": "^4.0.1",
"esutils": "^2.0.2",
"optionator": "^0.8.1",
"source-map": "~0.6.1"
}
},
"@javascript-obfuscator/estraverse": {
"version": "5.3.0",
"resolved": "https://registry.npmjs.org/@javascript-obfuscator/estraverse/-/estraverse-5.3.0.tgz",
"integrity": "sha512-SxIFtV5/wlXYS7G3zLVj7CddLolX8Bm/hr68fiyNL3MyG2k4FwF9B5Z5GTpVLhw2EELYNwyoYBvFlR4gGnQPdw==",
"dev": true
},
Update npm packages
2022-02-06 19:24:14 +09:00
"@jridgewell/resolve-uri": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "3.0.5",
"resolved": "https://registry.npmjs.org/@jridgewell/resolve-uri/-/resolve-uri-3.0.5.tgz",
"integrity": "sha512-VPeQ7+wH0itvQxnG+lIzWgkysKIr3L9sslimFW55rHMdGu/qCQ5z5h9zq4gI8uBtqkpHhsF4Z/OwExufUCThew==",
Update npm packages
2022-02-06 19:24:14 +09:00
"dev": true
},
"@jridgewell/sourcemap-codec": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "1.4.11",
"resolved": "https://registry.npmjs.org/@jridgewell/sourcemap-codec/-/sourcemap-codec-1.4.11.tgz",
"integrity": "sha512-Fg32GrJo61m+VqYSdRSjRXMjQ06j8YIYfcTqndLYVAaHmroZHLJZCydsWBOTDqXS2v+mjxohBWEMfg97GXmYQg==",
Update npm packages
2022-02-06 19:24:14 +09:00
"dev": true
},
"@jridgewell/trace-mapping": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "0.3.4",
"resolved": "https://registry.npmjs.org/@jridgewell/trace-mapping/-/trace-mapping-0.3.4.tgz",
"integrity": "sha512-vFv9ttIedivx0ux3QSjhgtCVjPZd5l46ZOMDSCwnH1yUO2e964gO8LZGyv2QkqcgR6TnBU1v+1IFqmeoG+0UJQ==",
Update npm packages
2022-02-06 19:24:14 +09:00
"dev": true,
"requires": {
"@jridgewell/resolve-uri": "^3.0.3",
"@jridgewell/sourcemap-codec": "^1.4.10"
}
},
Update npm packages
2021-05-30 14:43:13 +09:00
"@mapbox/node-pre-gyp": {
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/@mapbox/node-pre-gyp/-/node-pre-gyp-1.0.5.tgz",
"integrity": "sha512-4srsKPXWlIxp5Vbqz5uLfBN+du2fJChBoYn/f2h991WLdk7jUvcSk/McVLSv/X+xQIPI8eGD5GjrnygdyHnhPA==",
"dev": true,
"requires": {
"detect-libc": "^1.0.3",
"https-proxy-agent": "^5.0.0",
"make-dir": "^3.1.0",
"node-fetch": "^2.6.1",
"nopt": "^5.0.0",
"npmlog": "^4.1.2",
"rimraf": "^3.0.2",
"semver": "^7.3.4",
"tar": "^6.1.0"
},
"dependencies": {
"semver": {
"version": "7.3.5",
"resolved": "https://registry.npmjs.org/semver/-/semver-7.3.5.tgz",
"integrity": "sha512-PoeGJYh8HK4BTO/a9Tf6ZG3veo/A7ZVsYrSA6J8ny9nb3B1VrpkuN+z9OE5wfE5p6H4LchYZsegiQgbJD94ZFQ==",
"dev": true,
"requires": {
"lru-cache": "^6.0.0"
}
Update `npm` packages
2020-09-06 18:49:49 +09:00
}
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"@nodelib/fs.scandir": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"version": "2.1.5",
"resolved": "https://registry.npmjs.org/@nodelib/fs.scandir/-/fs.scandir-2.1.5.tgz",
"integrity": "sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true,
"requires": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"@nodelib/fs.stat": "2.0.5",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"run-parallel": "^1.1.9"
}
},
Update `npm` packages
2020-11-29 17:43:20 +09:00
"@nodelib/fs.stat": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/@nodelib/fs.stat/-/fs.stat-2.0.5.tgz",
"integrity": "sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==",
Update `npm` packages
2020-11-29 17:43:20 +09:00
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"@nodelib/fs.walk": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"version": "1.2.8",
"resolved": "https://registry.npmjs.org/@nodelib/fs.walk/-/fs.walk-1.2.8.tgz",
"integrity": "sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true,
"requires": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"@nodelib/fs.scandir": "2.1.5",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"fastq": "^1.6.0"
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@types/babel-types": {
Update packages
2018-11-25 05:00:22 +09:00
"version": "7.0.4",
"resolved": "https://registry.npmjs.org/@types/babel-types/-/babel-types-7.0.4.tgz",
"integrity": "sha512-WiZhq3SVJHFRgRYLXvpf65XnV6ipVHhnNaNvE8yCimejrGglkg38kEj0JcizqwSHxmPSjcTlig/6JouxLGEhGw==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true
},
"@types/babylon": {
Update packages
2018-11-25 05:00:22 +09:00
"version": "6.16.4",
"resolved": "https://registry.npmjs.org/@types/babylon/-/babylon-6.16.4.tgz",
"integrity": "sha512-8dZMcGPno3g7pJ/d0AyJERo+lXh9i1JhDuCUs+4lNIN9eUe5Yh6UCLrpgSEi05Ve2JMLauL2aozdvKwNL0px1Q==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@types/babel-types": "*"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"@types/eslint": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "8.4.1",
"resolved": "https://registry.npmjs.org/@types/eslint/-/eslint-8.4.1.tgz",
"integrity": "sha512-GE44+DNEyxxh2Kc6ro/VkIj+9ma0pO0bwv9+uHSyBrikYOHr8zYcdPvnBOp1aw8s+CjRvuSx7CyWqRrNFQ59mA==",
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"dev": true,
"requires": {
"@types/estree": "*",
"@types/json-schema": "*"
}
},
"@types/eslint-scope": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "3.7.3",
"resolved": "https://registry.npmjs.org/@types/eslint-scope/-/eslint-scope-3.7.3.tgz",
"integrity": "sha512-PB3ldyrcnAicT35TWPs5IcwKD8S333HMaa2VVv4+wdvebJkjWuW/xESoB8IwRcog8HYVYamb1g/R31Qv5Bx03g==",
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"dev": true,
"requires": {
"@types/eslint": "*",
"@types/estree": "*"
}
},
"@types/estree": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "0.0.51",
"resolved": "https://registry.npmjs.org/@types/estree/-/estree-0.0.51.tgz",
"integrity": "sha512-CuPgU6f3eT/XgKKPqKd/gLZV1Xmvf1a2R5POBOGQa6uv82xpls89HU5zKeVoyR8XzHd1RGNOlQlvUe3CFkjWNQ==",
Update npm packages
2021-05-02 16:30:09 +09:00
"dev": true
},
"@types/expect": {
"version": "1.20.4",
"resolved": "https://registry.npmjs.org/@types/expect/-/expect-1.20.4.tgz",
"integrity": "sha512-Q5Vn3yjTDyCMV50TB6VRIbQNxSE4OmZR86VSbGaNpfUolm0iePBB4KdEEHmxoY5sT2+2DIvXW0rvMDP2nHZ4Mg==",
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"dev": true
},
"@types/json-schema": {
Update npm packages
2021-10-31 17:38:18 +09:00
"version": "7.0.9",
"resolved": "https://registry.npmjs.org/@types/json-schema/-/json-schema-7.0.9.tgz",
"integrity": "sha512-qcUXuemtEu+E5wZSJHNxUXeCZhAfXKQ41D+duX+VYPde7xyEVZci+/oXKJL13tnRs9lR2pr4fod59GT6/X1/yQ==",
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"dev": true
},
Update npm packages
2021-09-05 16:47:57 +09:00
"@types/json5": {
"version": "0.0.29",
"resolved": "https://registry.npmjs.org/@types/json5/-/json5-0.0.29.tgz",
"integrity": "sha1-7ihweulOEdK4J7y+UnC86n8+ce4=",
"dev": true
},
Update npm packages
2022-01-23 18:58:15 +09:00
"@types/linkify-it": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/@types/linkify-it/-/linkify-it-3.0.2.tgz",
"integrity": "sha512-HZQYqbiFVWufzCwexrvh694SOim8z2d+xJl5UNamcvQFejLY/2YUtzXHYi3cHdI7PMlS8ejH2slRAOJQ32aNbA==",
"dev": true
},
"@types/markdown-it": {
"version": "12.2.3",
"resolved": "https://registry.npmjs.org/@types/markdown-it/-/markdown-it-12.2.3.tgz",
"integrity": "sha512-GKMHFfv3458yYy+v/N8gjufHO6MSZKCOXpZc5GXIWWy8uldwfmPn98vp81gZ5f9SVw8YYBctgfJ22a2d7AOMeQ==",
"dev": true,
"requires": {
"@types/linkify-it": "*",
"@types/mdurl": "*"
}
},
"@types/mdurl": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/@types/mdurl/-/mdurl-1.0.2.tgz",
"integrity": "sha512-eC4U9MlIcu2q0KQmXszyn5Akca/0jrQmwDRgpAMJai7qBWq4amIQhZyNau4VYGtCeALvW1/NtjzJJ567aZxfKA==",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"@types/minimist": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"version": "1.2.2",
"resolved": "https://registry.npmjs.org/@types/minimist/-/minimist-1.2.2.tgz",
"integrity": "sha512-jhuKLIRrhvCPLqwPcx6INqmKeiA5EWrsCOPhrlFSrbrmU4ZMPjj5Ul/oLCMDO98XRUIwVm78xICz4EPCektzeQ==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"@types/node": {
Update npm packages
2021-05-16 17:05:58 +09:00
"version": "14.14.45",
"resolved": "https://registry.npmjs.org/@types/node/-/node-14.14.45.tgz",
"integrity": "sha512-DssMqTV9UnnoxDWu959sDLZzfvqCF0qDNRjaWeYSui9xkFe61kKo4l1TWNTQONpuXEm+gLMRvdlzvNHBamzmEw==",
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"dev": true
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
},
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"@types/normalize-package-data": {
"version": "2.4.0",
"resolved": "https://registry.npmjs.org/@types/normalize-package-data/-/normalize-package-data-2.4.0.tgz",
"integrity": "sha512-f5j5b/Gf71L+dbqxIpQ4Z2WlmI/mPJ0fOkGGmFgtb6sAu97EPczzbS3/tJKxmcYDj55OX6ssqwDAWOHIYDRDGA==",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"@types/parse-json": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/@types/parse-json/-/parse-json-4.0.0.tgz",
"integrity": "sha512-//oorEZjL6sbPcKUaCdIGlIUeH26mgzimjBB77G6XRgnDl/L5wOnpyBGRe/Mmf5CVW3PwEBE1NjiMZ/ssFh4wA==",
"dev": true
},
Update npm packages
2021-05-02 16:30:09 +09:00
"@types/vinyl": {
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/@types/vinyl/-/vinyl-2.0.4.tgz",
"integrity": "sha512-2o6a2ixaVI2EbwBPg1QYLGQoHK56p/8X/sGfKbFC8N6sY9lfjsMf/GprtkQkSya0D4uRiutRZ2BWj7k3JvLsAQ==",
"dev": true,
"requires": {
"@types/expect": "^1.20.4",
"@types/node": "*"
}
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"@types/yauzl": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "2.9.2",
"resolved": "https://registry.npmjs.org/@types/yauzl/-/yauzl-2.9.2.tgz",
"integrity": "sha512-8uALY5LTvSuHgloDVUvWP3pIauILm+8/0pDMokuDYIoNsOkSwd5AiHBTSEJjKTDcZr5z8UpgOWZkxBF4iJftoA==",
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"dev": true,
"optional": true,
"requires": {
"@types/node": "*"
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@webassemblyjs/ast": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/ast/-/ast-1.11.1.tgz",
"integrity": "sha512-ukBh14qFLjxTQNTXocdyksN5QdM28S1CxHt2rdskFyL+xFV7VremuBLVbmCePj+URalXBENx/9Lm7lnhihtCSw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-07-11 19:14:47 +09:00
"@webassemblyjs/helper-numbers": "1.11.1",
"@webassemblyjs/helper-wasm-bytecode": "1.11.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@webassemblyjs/floating-point-hex-parser": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/floating-point-hex-parser/-/floating-point-hex-parser-1.11.1.tgz",
"integrity": "sha512-iGRfyc5Bq+NnNuX8b5hwBrRjzf0ocrJPI6GWFodBFzmFnyvrQ83SHKhmilCU/8Jv67i4GJZBMhEzltxzcNagtQ==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true
},
"@webassemblyjs/helper-api-error": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/helper-api-error/-/helper-api-error-1.11.1.tgz",
"integrity": "sha512-RlhS8CBCXfRUR/cwo2ho9bkheSXG0+NwooXcc3PAILALf2QLdFyj7KGsKRbVc95hZnhnERon4kW/D3SZpp6Tcg==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true
},
"@webassemblyjs/helper-buffer": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/helper-buffer/-/helper-buffer-1.11.1.tgz",
"integrity": "sha512-gwikF65aDNeeXa8JxXa2BAk+REjSyhrNC9ZwdT0f8jc4dQQeDQ7G4m0f2QCLPJiMTTO6wfDmRmj/pW0PsUvIcA==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true
},
Update `npm` packages
2021-01-24 16:34:00 +09:00
"@webassemblyjs/helper-numbers": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/helper-numbers/-/helper-numbers-1.11.1.tgz",
"integrity": "sha512-vDkbxiB8zfnPdNK9Rajcey5C0w+QJugEglN0of+kmO8l7lDb77AnlKYQF7aarZuCrv+l0UvqL+68gSDr3k9LPQ==",
Update `npm` packages
2021-01-24 16:34:00 +09:00
"dev": true,
"requires": {
Update npm packages
2021-07-11 19:14:47 +09:00
"@webassemblyjs/floating-point-hex-parser": "1.11.1",
"@webassemblyjs/helper-api-error": "1.11.1",
Update `npm` packages
2021-01-24 16:34:00 +09:00
"@xtuc/long": "4.2.2"
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@webassemblyjs/helper-wasm-bytecode": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/helper-wasm-bytecode/-/helper-wasm-bytecode-1.11.1.tgz",
"integrity": "sha512-PvpoOGiJwXeTrSf/qfudJhwlvDQxFgelbMqtq52WWiXC6Xgg1IREdngmPN3bs4RoO83PnL/nFrxucXj1+BX62Q==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true
},
"@webassemblyjs/helper-wasm-section": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/helper-wasm-section/-/helper-wasm-section-1.11.1.tgz",
"integrity": "sha512-10P9No29rYX1j7F3EVPX3JvGPQPae+AomuSTPiF9eBQeChHI6iqjMIwR9JmOJXwpnn/oVGDk7I5IlskuMwU/pg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-07-11 19:14:47 +09:00
"@webassemblyjs/ast": "1.11.1",
"@webassemblyjs/helper-buffer": "1.11.1",
"@webassemblyjs/helper-wasm-bytecode": "1.11.1",
"@webassemblyjs/wasm-gen": "1.11.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@webassemblyjs/ieee754": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/ieee754/-/ieee754-1.11.1.tgz",
"integrity": "sha512-hJ87QIPtAMKbFq6CGTkZYJivEwZDbQUgYd3qKSadTNOhVY7p+gfP6Sr0lLRVTaG1JjFj+r3YchoqRYxNH3M0GQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@xtuc/ieee754": "^1.2.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@webassemblyjs/leb128": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/leb128/-/leb128-1.11.1.tgz",
"integrity": "sha512-BJ2P0hNZ0u+Th1YZXJpzW6miwqQUGcIHT1G/sf72gLVD9DZ5AdYTqPNbHZh6K1M5VmKvFXwGSWZADz+qBWxeRw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update Webpack to the latest stable version (4.29.5)
2019-02-24 05:11:46 +09:00
"@xtuc/long": "4.2.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@webassemblyjs/utf8": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/utf8/-/utf8-1.11.1.tgz",
"integrity": "sha512-9kqcxAEdMhiwQkHpkNiorZzqpGrodQQ2IGrHHxCy+Ozng0ofyMA0lTqiLkVs1uzTRejX+/O0EOT7KxqVPuXosQ==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true
},
"@webassemblyjs/wasm-edit": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/wasm-edit/-/wasm-edit-1.11.1.tgz",
"integrity": "sha512-g+RsupUC1aTHfR8CDgnsVRVZFJqdkFHpsHMfJuWQzWU3tvnLC07UqHICfP+4XyL2tnr1amvl1Sdp06TnYCmVkA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-07-11 19:14:47 +09:00
"@webassemblyjs/ast": "1.11.1",
"@webassemblyjs/helper-buffer": "1.11.1",
"@webassemblyjs/helper-wasm-bytecode": "1.11.1",
"@webassemblyjs/helper-wasm-section": "1.11.1",
"@webassemblyjs/wasm-gen": "1.11.1",
"@webassemblyjs/wasm-opt": "1.11.1",
"@webassemblyjs/wasm-parser": "1.11.1",
"@webassemblyjs/wast-printer": "1.11.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@webassemblyjs/wasm-gen": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/wasm-gen/-/wasm-gen-1.11.1.tgz",
"integrity": "sha512-F7QqKXwwNlMmsulj6+O7r4mmtAlCWfO/0HdgOxSklZfQcDu0TpLiD1mRt/zF25Bk59FIjEuGAIyn5ei4yMfLhA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-07-11 19:14:47 +09:00
"@webassemblyjs/ast": "1.11.1",
"@webassemblyjs/helper-wasm-bytecode": "1.11.1",
"@webassemblyjs/ieee754": "1.11.1",
"@webassemblyjs/leb128": "1.11.1",
"@webassemblyjs/utf8": "1.11.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@webassemblyjs/wasm-opt": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/wasm-opt/-/wasm-opt-1.11.1.tgz",
"integrity": "sha512-VqnkNqnZlU5EB64pp1l7hdm3hmQw7Vgqa0KF/KCNO9sIpI6Fk6brDEiX+iCOYrvMuBWDws0NkTOxYEb85XQHHw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-07-11 19:14:47 +09:00
"@webassemblyjs/ast": "1.11.1",
"@webassemblyjs/helper-buffer": "1.11.1",
"@webassemblyjs/wasm-gen": "1.11.1",
"@webassemblyjs/wasm-parser": "1.11.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@webassemblyjs/wasm-parser": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/wasm-parser/-/wasm-parser-1.11.1.tgz",
"integrity": "sha512-rrBujw+dJu32gYB7/Lup6UhdkPx9S9SnobZzRVL7VcBH9Bt9bCBLEuX/YXOOtBsOZ4NQrRykKhffRWHvigQvOA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-07-11 19:14:47 +09:00
"@webassemblyjs/ast": "1.11.1",
"@webassemblyjs/helper-api-error": "1.11.1",
"@webassemblyjs/helper-wasm-bytecode": "1.11.1",
"@webassemblyjs/ieee754": "1.11.1",
"@webassemblyjs/leb128": "1.11.1",
"@webassemblyjs/utf8": "1.11.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@webassemblyjs/wast-printer": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/wast-printer/-/wast-printer-1.11.1.tgz",
"integrity": "sha512-IQboUWM4eKzWW+N/jij2sRatKMh99QEelo3Eb2q0qXkvPRISAj8Qxtmw5itwqK+TTkBuUIE45AxYPToqPtL5gg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-07-11 19:14:47 +09:00
"@webassemblyjs/ast": "1.11.1",
Update Webpack to the latest stable version (4.29.5)
2019-02-24 05:11:46 +09:00
"@xtuc/long": "4.2.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@xtuc/ieee754": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/@xtuc/ieee754/-/ieee754-1.2.0.tgz",
"integrity": "sha512-DX8nKgqcGwsc0eJSqYt5lwP4DH5FlHnmuWWBRy7X0NcaGR0ZtuyeESgMwTYVEtxmsNGY+qit4QYT/MIYTOTPeA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"@xtuc/long": {
Update Webpack to the latest stable version (4.29.5)
2019-02-24 05:11:46 +09:00
"version": "4.2.2",
"resolved": "https://registry.npmjs.org/@xtuc/long/-/long-4.2.2.tgz",
"integrity": "sha512-NuHqBY1PB/D8xU6s/thBgOAiAP7HOYDQ32+BFZILJ8ivkUkAHQnWfn6WhL79Owj1qmUnoN/YPhktdIoucipkAQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"abbrev": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/abbrev/-/abbrev-1.1.1.tgz",
"integrity": "sha512-nne9/IiQ/hzIhY6pdDnbBtz7DjPTKrY00P/zvPSm5pOFkl6xuGrGnXn/VtTNNfNtAfZ9/1RtehkszU9qcTii0Q==",
"dev": true
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"acorn": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "8.7.0",
"resolved": "https://registry.npmjs.org/acorn/-/acorn-8.7.0.tgz",
"integrity": "sha512-V/LGr1APy+PXIwKebEWrkZPwoeoF+w1jiOBUmuxuiUIaOHtob8Qc9BTrYo7VuI5fR8tqsy+buA2WFooR5olqvQ==",
Update Webpack to the latest stable version (4.29.5)
2019-02-24 05:11:46 +09:00
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"acorn-globals": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/acorn-globals/-/acorn-globals-3.1.0.tgz",
"integrity": "sha1-/YJw9x+7SZawBPqIDuXUZXOnMb8=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"acorn": "^4.0.4"
},
"dependencies": {
"acorn": {
"version": "4.0.13",
"resolved": "https://registry.npmjs.org/acorn/-/acorn-4.0.13.tgz",
"integrity": "sha1-EFSVrlNh1pe9GVyCUZLhrX8lN4c=",
"dev": true
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update npm packages
2021-08-08 17:45:36 +09:00
"acorn-import-assertions": {
Update npm packages
2021-10-17 18:33:19 +09:00
"version": "1.8.0",
"resolved": "https://registry.npmjs.org/acorn-import-assertions/-/acorn-import-assertions-1.8.0.tgz",
"integrity": "sha512-m7VZ3jwz4eK6A4Vtt8Ew1/mNbP24u0FhdyfA7fSvnJR6LMdfOYnmuIrrJAgrYfYJ10F/otaHTtrtrtmHdMNzEw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"requires": {}
Update npm packages
2021-08-08 17:45:36 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"acorn-jsx": {
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"version": "5.3.2",
"resolved": "https://registry.npmjs.org/acorn-jsx/-/acorn-jsx-5.3.2.tgz",
"integrity": "sha512-rq9s+JNhf0IChjtDXxllJ7g41oZk5SlXtp0LHwyA5cejwn7vKmKp4pPri6YEePv2PU65sAsegbXtIinmDFDXgQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"requires": {}
Update packages
2018-12-23 00:00:53 +09:00
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"agent-base": {
Update Puppeteer to version 6 (issue 12945) Please see https://github.com/puppeteer/puppeteer/releases/tag/v6.0.0
2021-02-02 21:18:22 +09:00
"version": "6.0.2",
"resolved": "https://registry.npmjs.org/agent-base/-/agent-base-6.0.2.tgz",
"integrity": "sha512-RZNwNclF7+MS/8bDg70amg32dyeZGZxiDuQmZxKLAlQjr3jGyLx+4Kkk58UO7D2QdgFIQCovuSuZESne6RG6XQ==",
"dev": true,
"requires": {
"debug": "4"
},
"dependencies": {
"debug": {
"version": "4.3.1",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.1.tgz",
"integrity": "sha512-doEwdvm4PCeK4K3RQN2ZC2BYUBaxwLARCqZmMjtF8a51J2Rb0xpVloFRnCODwqjpwnAoao4pelN8l3RJdv3gRQ==",
"dev": true,
"requires": {
"ms": "2.1.2"
}
},
"ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
}
}
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"ajv": {
Update npm packages
2021-10-31 17:38:18 +09:00
"version": "6.12.6",
"resolved": "https://registry.npmjs.org/ajv/-/ajv-6.12.6.tgz",
"integrity": "sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-07-26 18:15:21 +09:00
"fast-deep-equal": "^3.1.1",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"fast-json-stable-stringify": "^2.0.0",
"json-schema-traverse": "^0.4.1",
"uri-js": "^4.2.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"ajv-keywords": {
Update `npm` packages
2020-11-15 21:51:52 +09:00
"version": "3.5.2",
"resolved": "https://registry.npmjs.org/ajv-keywords/-/ajv-keywords-3.5.2.tgz",
"integrity": "sha512-5p6WTN0DdTGVQk6VjcEju19IgaHudalcfabD7yhDGeA6bcQnmL+CpveLJq/3hvfwd1aof6L386Ougkx6RfyMIQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"requires": {}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"align-text": {
"version": "0.1.4",
"resolved": "https://registry.npmjs.org/align-text/-/align-text-0.1.4.tgz",
"integrity": "sha1-DNkKVhCT810KmSVsIrcGlDP60Rc=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"kind-of": "^3.0.2",
"longest": "^1.0.1",
"repeat-string": "^1.5.2"
},
"dependencies": {
"kind-of": {
"version": "3.2.2",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz",
"integrity": "sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=",
"dev": true,
"requires": {
"is-buffer": "^1.1.5"
}
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"ansi-colors": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/ansi-colors/-/ansi-colors-1.1.0.tgz",
"integrity": "sha512-SFKX67auSNoVR38N3L+nvsPjOE0bybKTYbkf5tRvushrAPQ9V75huw0ZxBkKVeRU9kqH3d6HA4xTckbwZ4ixmA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"ansi-wrap": "^0.1.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"ansi-gray": {
"version": "0.1.1",
"resolved": "https://registry.npmjs.org/ansi-gray/-/ansi-gray-0.1.1.tgz",
"integrity": "sha1-KWLPVOyXksSFEKPetSRDaGHvclE=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"ansi-wrap": "0.1.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"ansi-regex": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.1.1.tgz",
"integrity": "sha1-w7M6te42DYbg5ijwRorn7yfWVN8=",
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"ansi-styles": {
"version": "3.2.1",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-3.2.1.tgz",
"integrity": "sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"color-convert": "^1.9.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"ansi-wrap": {
"version": "0.1.0",
"resolved": "https://registry.npmjs.org/ansi-wrap/-/ansi-wrap-0.1.0.tgz",
"integrity": "sha1-qCJQ3bABXponyoLoLqYDu/pF768=",
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"anymatch": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/anymatch/-/anymatch-2.0.0.tgz",
"integrity": "sha512-5teOsQWABXHHBFP9y3skS5P3d/WfWXpv3FUpy+LorMrNYaT9pI4oLMQX7jzQ2KklNpGpWHzdCXTDT2Y3XGlZBw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"micromatch": "^3.1.4",
"normalize-path": "^2.1.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"append-buffer": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/append-buffer/-/append-buffer-1.0.2.tgz",
"integrity": "sha1-2CIM9GYIFSXv6lBhTz3mUU36WPE=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"buffer-equal": "^1.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"aproba": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/aproba/-/aproba-1.2.0.tgz",
"integrity": "sha512-Y9J6ZjXtoYh8RnXVCMOU/ttDmk1aBjunq9vO0ta5x85WDQiQfUF9sIPBITdbiiIVcBo03Hi3jMxigBtsddlXRw==",
"dev": true
},
"archy": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/archy/-/archy-1.0.0.tgz",
"integrity": "sha1-+cjBN1fMHde8N5rHeyxipcKGjEA=",
"dev": true
},
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"are-we-there-yet": {
"version": "1.1.5",
"resolved": "https://registry.npmjs.org/are-we-there-yet/-/are-we-there-yet-1.1.5.tgz",
"integrity": "sha512-5hYdAkZlcG8tOLujVDTgCT+uPX0VnpAH28gWsLfzpXYm7wP6mp5Q/gYyR7YQ0cKVJcXJnl3j2kpBan13PtQf6w==",
"dev": true,
"requires": {
"delegates": "^1.0.0",
"readable-stream": "^2.0.6"
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"argparse": {
"version": "1.0.10",
"resolved": "https://registry.npmjs.org/argparse/-/argparse-1.0.10.tgz",
"integrity": "sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==",
Update eslint-plugin-mozilla to ^1.0.1
2018-11-23 22:40:05 +09:00
"dev": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"requires": {
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"sprintf-js": "~1.0.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"arr-diff": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/arr-diff/-/arr-diff-4.0.0.tgz",
"integrity": "sha1-1kYQdP6/7HHn4VI1dhoyml3HxSA=",
"dev": true
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"arr-filter": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/arr-filter/-/arr-filter-1.1.2.tgz",
"integrity": "sha1-Q/3d0JHo7xGqTEXZzcGOLf8XEe4=",
"dev": true,
"requires": {
"make-iterator": "^1.0.0"
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"arr-flatten": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/arr-flatten/-/arr-flatten-1.1.0.tgz",
"integrity": "sha512-L3hKV5R/p5o81R7O02IGnwpDmkp6E982XhtbuwSe3O4qOtMMMtodicASA1Cny2U+aCXcNpml+m4dPsvsJ3jatg==",
"dev": true
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"arr-map": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/arr-map/-/arr-map-2.0.2.tgz",
"integrity": "sha1-Onc0X/wc814qkYJWAfnljy4kysQ=",
"dev": true,
"requires": {
"make-iterator": "^1.0.0"
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"arr-union": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/arr-union/-/arr-union-3.1.0.tgz",
"integrity": "sha1-45sJrqne+Gao8gbiiK9jkZuuOcQ=",
"dev": true
},
"array-each": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/array-each/-/array-each-1.0.1.tgz",
"integrity": "sha1-p5SvDAWrF1KEbudTofIRoFugxE8=",
"dev": true
},
Update packages
2019-04-14 00:25:41 +09:00
"array-includes": {
Update npm packages
2021-10-17 18:33:19 +09:00
"version": "3.1.4",
"resolved": "https://registry.npmjs.org/array-includes/-/array-includes-3.1.4.tgz",
"integrity": "sha512-ZTNSQkmWumEbiHO2GF4GmWxYVTiQyJy2XOTa15sdQSrvKn7l+180egQMqlrMOUMCyLMD7pmyQe4mMDUT6Behrw==",
Update packages
2019-04-14 00:25:41 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-16 17:05:58 +09:00
"call-bind": "^1.0.2",
Update `npm` packages
2019-12-19 19:28:13 +09:00
"define-properties": "^1.1.3",
Update npm packages
2021-10-17 18:33:19 +09:00
"es-abstract": "^1.19.1",
Update npm packages
2021-05-16 17:05:58 +09:00
"get-intrinsic": "^1.1.1",
Update npm packages
2021-10-17 18:33:19 +09:00
"is-string": "^1.0.7"
Update `npm` packages
2019-12-19 19:28:13 +09:00
},
"dependencies": {
"define-properties": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.1.3.tgz",
"integrity": "sha512-3MqfYKj2lLzdMSf8ZIZE/V+Zuy+BgD6f164e8K2w7dgnpKArBDerGYpM46IYYcjnkdPNMjPk9A6VFB8+3SKlXQ==",
"dev": true,
"requires": {
"object-keys": "^1.0.12"
}
},
"object-keys": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz",
"integrity": "sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==",
"dev": true
}
Update packages
2019-04-14 00:25:41 +09:00
}
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"array-initial": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/array-initial/-/array-initial-1.1.0.tgz",
"integrity": "sha1-L6dLJnOTccOUe9enrcc74zSz15U=",
"dev": true,
"requires": {
"array-slice": "^1.0.0",
"is-number": "^4.0.0"
},
"dependencies": {
"is-number": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/is-number/-/is-number-4.0.0.tgz",
"integrity": "sha512-rSklcAIlf1OmFdyAqbnWTLVelsQ58uvZ66S/ZyawjWqIviTWCjg2PzVGw8WUA+nNuPTqb4wgA+NszrJ+08LlgQ==",
"dev": true
}
}
},
"array-last": {
"version": "1.3.0",
"resolved": "https://registry.npmjs.org/array-last/-/array-last-1.3.0.tgz",
"integrity": "sha512-eOCut5rXlI6aCOS7Z7kCplKRKyiFQ6dHFBem4PwlwKeNFk2/XxTrhRh5T9PyaEWGy/NHTZWbY+nsZlNFJu9rYg==",
"dev": true,
"requires": {
"is-number": "^4.0.0"
},
"dependencies": {
"is-number": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/is-number/-/is-number-4.0.0.tgz",
"integrity": "sha512-rSklcAIlf1OmFdyAqbnWTLVelsQ58uvZ66S/ZyawjWqIviTWCjg2PzVGw8WUA+nNuPTqb4wgA+NszrJ+08LlgQ==",
"dev": true
}
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"array-slice": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/array-slice/-/array-slice-1.1.0.tgz",
"integrity": "sha512-B1qMD3RBP7O8o0H2KbrXDyB0IccejMF15+87Lvlor12ONPRHP6gTjXMNkt/d3ZuOGbAe66hFmaCfECI24Ufp6w==",
"dev": true
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"array-sort": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/array-sort/-/array-sort-1.0.0.tgz",
"integrity": "sha512-ihLeJkonmdiAsD7vpgN3CRcx2J2S0TiYW+IS/5zHBI7mKUq3ySvBdzzBfD236ubDBQFiiyG3SWCPc+msQ9KoYg==",
"dev": true,
"requires": {
"default-compare": "^1.0.0",
"get-value": "^2.0.6",
"kind-of": "^5.0.2"
},
"dependencies": {
"kind-of": {
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-5.1.0.tgz",
"integrity": "sha512-NGEErnH6F2vUuXDh+OlbcKW7/wOcfdRHaZ7VWtqCztfHri/++YKmP51OdWeGPuqCOba6kk2OTe5d02VmTB80Pw==",
"dev": true
}
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"array-union": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/array-union/-/array-union-2.1.0.tgz",
"integrity": "sha512-HGyxoOTYUyCM6stUe6EJgnd4EoewAI7zMdfqO+kGjnlZmBDz/cR5pf8r/cR4Wq60sL/p0IkcjUEEPwS3GFrIyw==",
"dev": true
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"array-unique": {
"version": "0.3.2",
"resolved": "https://registry.npmjs.org/array-unique/-/array-unique-0.3.2.tgz",
"integrity": "sha1-qJS3XUvE9s1nnvMkSp/Y9Gri1Cg=",
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update `npm` packages
2019-12-19 19:28:13 +09:00
"array.prototype.flat": {
Update npm packages
2021-10-17 18:33:19 +09:00
"version": "1.2.5",
"resolved": "https://registry.npmjs.org/array.prototype.flat/-/array.prototype.flat-1.2.5.tgz",
"integrity": "sha512-KaYU+S+ndVqyUnignHftkwc58o3uVU1jzczILJ1tN2YaIZpFIKBiP/x/j97E5MVPsaCloPbqWLB/8qCTVvT2qg==",
Update `npm` packages
2019-12-19 19:28:13 +09:00
"dev": true,
"requires": {
Update npm packages
2021-10-17 18:33:19 +09:00
"call-bind": "^1.0.2",
Update `npm` packages
2019-12-19 19:28:13 +09:00
"define-properties": "^1.1.3",
Update npm packages
2021-10-17 18:33:19 +09:00
"es-abstract": "^1.19.0"
Update `npm` packages
2019-12-19 19:28:13 +09:00
},
"dependencies": {
"define-properties": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.1.3.tgz",
"integrity": "sha512-3MqfYKj2lLzdMSf8ZIZE/V+Zuy+BgD6f164e8K2w7dgnpKArBDerGYpM46IYYcjnkdPNMjPk9A6VFB8+3SKlXQ==",
"dev": true,
"requires": {
"object-keys": "^1.0.12"
}
},
"object-keys": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz",
"integrity": "sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==",
"dev": true
}
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"arrify": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/arrify/-/arrify-1.0.1.tgz",
"integrity": "sha1-iYUI2iIm84DfkEcoRWhJwVAaSw0=",
"dev": true
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"asap": {
"version": "2.0.6",
"resolved": "https://registry.npmjs.org/asap/-/asap-2.0.6.tgz",
"integrity": "sha1-5QNHYR1+aQlDIIu9r+vLwvuGbUY=",
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"assign-symbols": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/assign-symbols/-/assign-symbols-1.0.0.tgz",
"integrity": "sha1-WWZ/QfrdTyDMvCu5a41Pf3jsA2c=",
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update packages
2018-12-23 00:00:53 +09:00
"astral-regex": {
Update `npm` packages
2020-12-27 19:11:18 +09:00
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/astral-regex/-/astral-regex-2.0.0.tgz",
"integrity": "sha512-Z7tMw1ytTXt5jqMcOP+OQteU1VuNK9Y02uuJtKQ1Sv69jXQKKg5cibLwGJow8yzZP+eAc18EmLGPal0bp36rvQ==",
Update packages
2018-12-23 00:00:53 +09:00
"dev": true
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"async": {
"version": "0.2.10",
"resolved": "https://registry.npmjs.org/async/-/async-0.2.10.tgz",
"integrity": "sha1-trvgsGdLnXGXCMo43owjfLUmw9E=",
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"async-done": {
"version": "1.3.1",
"resolved": "https://registry.npmjs.org/async-done/-/async-done-1.3.1.tgz",
"integrity": "sha512-R1BaUeJ4PMoLNJuk+0tLJgjmEqVsdN118+Z8O+alhnQDQgy0kmD5Mqi0DNEmMx2LM0Ed5yekKu+ZXYvIHceicg==",
"dev": true,
"requires": {
"end-of-stream": "^1.1.0",
"once": "^1.3.2",
"process-nextick-args": "^1.0.7",
"stream-exhaust": "^1.0.1"
},
"dependencies": {
"process-nextick-args": {
"version": "1.0.7",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-1.0.7.tgz",
"integrity": "sha1-FQ4gt1ZZCtP5EJPyWk8q2L/zC6M=",
"dev": true
}
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"async-each": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/async-each/-/async-each-1.0.1.tgz",
"integrity": "sha1-GdOGodntxufByF04iu28xW0zYC0=",
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"async-settle": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/async-settle/-/async-settle-1.0.0.tgz",
"integrity": "sha1-HQqRS7Aldb7IqPOnTlCA9yssDGs=",
"dev": true,
"requires": {
"async-done": "^1.2.2"
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"atob": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/atob/-/atob-2.1.1.tgz",
"integrity": "sha1-ri1acpR38onWDdf5amMUoi3Wwio=",
"dev": true
Add support for `async`/`await` using Babel For proof-of-concept, this patch converts a couple of `Promise` returning methods to use `async` instead. Please note that the `generic` build, based on this patch, has been successfully testing in IE11 (i.e. the viewer loads and nothing is obviously broken). Being able to use modern JavaScript features like `async`/`await` is a huge plus, but there's one (obvious) side-effect: The size of the built files will increase slightly (unless `SKIP_BABEL == true`). That's unavoidable, but seems like a small price to pay in the grand scheme of things. Finally, note that the `chromium` build target was changed to no longer skip Babel translation, since the Chrome extension still supports version `49` of the browser (where native `async` support isn't available).
2018-07-30 20:58:09 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"autoprefixer": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "10.4.2",
"resolved": "https://registry.npmjs.org/autoprefixer/-/autoprefixer-10.4.2.tgz",
"integrity": "sha512-9fOPpHKuDW1w/0EKfRmVnxTDt8166MAnLI3mgZ1JCnhNtYWxcJ6Ud5CO/AVOZi/AvFa8DY9RTy3h3+tFBlrrdQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"browserslist": "^4.19.1",
"caniuse-lite": "^1.0.30001297",
"fraction.js": "^4.1.2",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"normalize-range": "^0.1.2",
Update npm packages
2021-10-31 17:38:18 +09:00
"picocolors": "^1.0.0",
Update npm packages
2022-01-09 18:05:52 +09:00
"postcss-value-parser": "^4.2.0"
Update `npm` packages
2020-04-02 19:13:14 +09:00
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"babel-loader": {
Update npm packages
2021-10-31 17:38:18 +09:00
"version": "8.2.3",
"resolved": "https://registry.npmjs.org/babel-loader/-/babel-loader-8.2.3.tgz",
"integrity": "sha512-n4Zeta8NC3QAsuyiizu0GkmRcQ6clkV9WFUnUf1iXP//IeSKbWjofW3UHyZVwlOB4y039YQKefawyTn64Zwbuw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-11-29 17:43:20 +09:00
"find-cache-dir": "^3.3.1",
Update `npm` packages
2020-04-02 19:13:14 +09:00
"loader-utils": "^1.4.0",
Update `npm` packages
2020-11-29 17:43:20 +09:00
"make-dir": "^3.1.0",
Update `npm` packages
2020-04-02 19:13:14 +09:00
"schema-utils": "^2.6.5"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2019-08-25 03:08:09 +09:00
"babel-plugin-dynamic-import-node": {
Update `npm` packages
2020-05-02 20:23:41 +09:00
"version": "2.3.3",
"resolved": "https://registry.npmjs.org/babel-plugin-dynamic-import-node/-/babel-plugin-dynamic-import-node-2.3.3.tgz",
"integrity": "sha512-jZVI+s9Zg3IqA/kdi0i6UDCybUI3aSBLnglhYbSSjKlV7yF1F/5LWv8MakQmvYpnbJDS6fcBL2KzHSxNCMtWSQ==",
Update packages
2019-08-25 03:08:09 +09:00
"dev": true,
"requires": {
"object.assign": "^4.1.0"
}
},
Update `npm` packages
2021-03-07 20:00:57 +09:00
"babel-plugin-polyfill-corejs2": {
Update npm packages
2021-11-28 18:40:29 +09:00
"version": "0.3.0",
"resolved": "https://registry.npmjs.org/babel-plugin-polyfill-corejs2/-/babel-plugin-polyfill-corejs2-0.3.0.tgz",
"integrity": "sha512-wMDoBJ6uG4u4PNFh72Ty6t3EgfA91puCuAwKIazbQlci+ENb/UU9A3xG5lutjUIiXCIn1CY5L15r9LimiJyrSA==",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"dev": true,
"requires": {
Update `npm` packages
2021-04-18 18:02:42 +09:00
"@babel/compat-data": "^7.13.11",
Update npm packages
2021-11-28 18:40:29 +09:00
"@babel/helper-define-polyfill-provider": "^0.3.0",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"semver": "^6.1.1"
},
"dependencies": {
"semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
"dev": true
}
}
},
"babel-plugin-polyfill-corejs3": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "0.5.1",
"resolved": "https://registry.npmjs.org/babel-plugin-polyfill-corejs3/-/babel-plugin-polyfill-corejs3-0.5.1.tgz",
"integrity": "sha512-TihqEe4sQcb/QcPJvxe94/9RZuLQuF1+To4WqQcRvc+3J3gLCPIPgDKzGLG6zmQLfH3nn25heRuDNkS2KR4I8A==",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/helper-define-polyfill-provider": "^0.3.1",
"core-js-compat": "^3.20.0"
Update `npm` packages
2021-03-07 20:00:57 +09:00
}
},
"babel-plugin-polyfill-regenerator": {
Update npm packages
2021-11-28 18:40:29 +09:00
"version": "0.3.0",
"resolved": "https://registry.npmjs.org/babel-plugin-polyfill-regenerator/-/babel-plugin-polyfill-regenerator-0.3.0.tgz",
"integrity": "sha512-dhAPTDLGoMW5/84wkgwiLRwMnio2i1fUe53EuvtKMv0pn2p3S8OCoV1xAzfJPl0KOX7IB89s2ib85vbYiea3jg==",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"dev": true,
"requires": {
Update npm packages
2021-11-28 18:40:29 +09:00
"@babel/helper-define-polyfill-provider": "^0.3.0"
Update `npm` packages
2021-03-07 20:00:57 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"babel-runtime": {
"version": "6.26.0",
"resolved": "https://registry.npmjs.org/babel-runtime/-/babel-runtime-6.26.0.tgz",
"integrity": "sha1-llxwWGaOgrVde/4E/yM3vItWR/4=",
"dev": true,
"requires": {
"core-js": "^2.4.0",
"regenerator-runtime": "^0.11.0"
Upgrade `core-js` to version 3.2.1 This only required changing the import paths. The `es` folder contains all polyfills we need now. If we want to import everything, we need to explicitly require the `index` file.
2019-09-15 23:29:46 +09:00
},
"dependencies": {
"core-js": {
"version": "2.6.9",
"resolved": "https://registry.npmjs.org/core-js/-/core-js-2.6.9.tgz",
"integrity": "sha512-HOpZf6eXmnl7la+cUdMnLvUxKNqLUzJvgIziQ0DiF3JwSImNphIqdGqzj6hIKyX04MmV0poclQ7+wjWvxQyR2A==",
"dev": true
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"babel-types": {
"version": "6.26.0",
"resolved": "https://registry.npmjs.org/babel-types/-/babel-types-6.26.0.tgz",
"integrity": "sha1-o7Bz+Uq0nrb6Vc1lInozQ4BjJJc=",
"dev": true,
"requires": {
"babel-runtime": "^6.26.0",
"esutils": "^2.0.2",
"lodash": "^4.17.4",
"to-fast-properties": "^1.0.3"
}
},
"babylon": {
"version": "6.18.0",
"resolved": "https://registry.npmjs.org/babylon/-/babylon-6.18.0.tgz",
"integrity": "sha512-q/UEjfGJ2Cm3oKV71DJz9d25TPnq5rhBVL2Q4fA5wcC3jcrdn7+SssEybFIxwAvvP+YCsCYNKughoF33GxgycQ==",
"dev": true
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"bach": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/bach/-/bach-1.2.0.tgz",
"integrity": "sha1-Szzpa/JxNPeaG0FKUcFONMO9mIA=",
"dev": true,
"requires": {
"arr-filter": "^1.1.1",
"arr-flatten": "^1.0.1",
"arr-map": "^2.0.0",
"array-each": "^1.0.0",
"array-initial": "^1.0.0",
"array-last": "^1.1.1",
"async-done": "^1.2.2",
"async-settle": "^1.0.0",
"now-and-later": "^2.0.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"balanced-match": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-1.0.0.tgz",
"integrity": "sha1-ibTRmasr7kneFk6gK4nORi1xt2c=",
"dev": true
},
"base": {
"version": "0.11.2",
"resolved": "https://registry.npmjs.org/base/-/base-0.11.2.tgz",
"integrity": "sha512-5T6P4xPgpp0YDFvSWwEZ4NoE3aM4QBQXDzmVbraCkFj8zHM+mba8SyqB5DbZWyR7mYHo6Y7BdQo3MoA4m0TeQg==",
"dev": true,
"requires": {
"cache-base": "^1.0.1",
"class-utils": "^0.3.5",
"component-emitter": "^1.2.1",
"define-property": "^1.0.0",
"isobject": "^3.0.1",
"mixin-deep": "^1.2.0",
"pascalcase": "^0.1.1"
},
"dependencies": {
"define-property": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-1.0.0.tgz",
"integrity": "sha1-dp66rz9KY6rTr56NMEybvnm/sOY=",
"dev": true,
"requires": {
"is-descriptor": "^1.0.0"
}
},
"is-accessor-descriptor": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-accessor-descriptor/-/is-accessor-descriptor-1.0.0.tgz",
"integrity": "sha512-m5hnHTkcVsPfqx3AKlyttIPb7J+XykHvJP2B9bZDjlhLIoEq4XoK64Vg7boZlVWYK6LUY94dYPEE7Lh0ZkZKcQ==",
"dev": true,
"requires": {
"kind-of": "^6.0.0"
}
},
"is-data-descriptor": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-data-descriptor/-/is-data-descriptor-1.0.0.tgz",
"integrity": "sha512-jbRXy1FmtAoCjQkVmIVYwuuqDFUbaOeDjmed1tOGPrsMhtJA4rD9tkgA0F1qJ3gRFRXcHYVkdeaP50Q5rE/jLQ==",
"dev": true,
"requires": {
"kind-of": "^6.0.0"
}
},
"is-descriptor": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/is-descriptor/-/is-descriptor-1.0.2.tgz",
"integrity": "sha512-2eis5WqQGV7peooDyLmNEPUrps9+SXX5c9pL3xEB+4e9HnGuDa7mB7kHxHw4CbqS9k1T2hOH3miL8n8WtiYVtg==",
"dev": true,
"requires": {
"is-accessor-descriptor": "^1.0.0",
"is-data-descriptor": "^1.0.0",
"kind-of": "^6.0.2"
}
}
}
},
"base64-js": {
Update npm packages
2021-10-03 15:21:01 +09:00
"version": "1.5.1",
"resolved": "https://registry.npmjs.org/base64-js/-/base64-js-1.5.1.tgz",
"integrity": "sha512-AKpaYlHn8t4SVbOHCy+b5+KKgvR4vrsD8vbvrbiQJps7fKDTkjkDry6ji0rUJjC0kzbNePLwzxq8iypo41qeWA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"big.js": {
Update `npm` packages
2020-04-02 19:13:14 +09:00
"version": "5.2.2",
"resolved": "https://registry.npmjs.org/big.js/-/big.js-5.2.2.tgz",
"integrity": "sha512-vyL2OymJxmarO8gxMr0mhChsO9QGwhynfuu4+MHTAW6czfq9humCB7rKpUjDd9YUiDPU4mzpyupFSvOClAwbmQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"binary-extensions": {
"version": "1.11.0",
"resolved": "https://registry.npmjs.org/binary-extensions/-/binary-extensions-1.11.0.tgz",
"integrity": "sha1-RqoXUftqL5PuXmibsQh9SxTGwgU=",
"dev": true
},
"binaryextensions": {
Update npm packages
2021-05-02 16:30:09 +09:00
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/binaryextensions/-/binaryextensions-2.3.0.tgz",
"integrity": "sha512-nAihlQsYGyc5Bwq6+EsubvANYGExeJKHDO3RjnvwU042fawQTQfM3Kxn7IHUXQOz4bzfwsGYYHGSvXyW4zOGLg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"bl": {
Update `npm` packages
2021-02-21 19:52:55 +09:00
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/bl/-/bl-4.1.0.tgz",
"integrity": "sha512-1W07cM9gS6DcLperZfFSj+bWLtaPGSOHWhPiGzXmvVJbRLdG82sH/Kn8EtW1VqWVA54AKf2h5k5BbnIbwF3h6w==",
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"dev": true,
"requires": {
"buffer": "^5.5.0",
"inherits": "^2.0.4",
"readable-stream": "^3.4.0"
},
"dependencies": {
"readable-stream": {
"version": "3.6.0",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-3.6.0.tgz",
"integrity": "sha512-BViHy7LKeTz4oNnkcLJ+lVSL6vpiFeX6/d3oSH8zCW7UxP2onchk+vTGB143xuFjHS3deTgkKoXXymXqymiIdA==",
"dev": true,
"requires": {
"inherits": "^2.0.3",
"string_decoder": "^1.1.1",
"util-deprecate": "^1.0.1"
}
}
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bluebird": {
Update `npm` packages
2020-05-02 20:23:41 +09:00
"version": "3.7.2",
"resolved": "https://registry.npmjs.org/bluebird/-/bluebird-3.7.2.tgz",
"integrity": "sha512-XpNj6GDQzdfW+r2Wnn7xiSAd7TM3jzkxGXBGTtWKuSXv1xUV+azxAm8jdWZN06QTQk+2N2XB9jRDkvbmQmcRtg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"brace-expansion": {
"version": "1.1.11",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz",
"integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==",
"dev": true,
"requires": {
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
}
},
"braces": {
"version": "2.3.2",
"resolved": "https://registry.npmjs.org/braces/-/braces-2.3.2.tgz",
"integrity": "sha512-aNdbnj9P8PjdXU4ybaWLK2IF3jc/EoDYbC7AazW6to3TRsfXxscC9UXOB5iDiEQrkyIbWp2SLQda4+QAa7nc3w==",
"dev": true,
"requires": {
"arr-flatten": "^1.1.0",
"array-unique": "^0.3.2",
"extend-shallow": "^2.0.1",
"fill-range": "^4.0.0",
"isobject": "^3.0.1",
"repeat-element": "^1.1.2",
"snapdragon": "^0.8.1",
"snapdragon-node": "^2.0.1",
"split-string": "^3.0.2",
"to-regex": "^3.0.1"
},
"dependencies": {
"extend-shallow": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/extend-shallow/-/extend-shallow-2.0.1.tgz",
"integrity": "sha1-Ua99YUrZqfYQ6huvu5idaxxWiQ8=",
"dev": true,
"requires": {
"is-extendable": "^0.1.0"
}
}
}
},
"browserslist": {
Update npm packages
2021-12-26 19:09:29 +09:00
"version": "4.19.1",
"resolved": "https://registry.npmjs.org/browserslist/-/browserslist-4.19.1.tgz",
"integrity": "sha512-u2tbbG5PdKRTUoctO3NBD8FQ5HdPh1ZXPHzp1rwaa5jTc+RV9/+RlWiAIKmjRPQF+xbGM9Kklj5bZQFa2s/38A==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-12-26 19:09:29 +09:00
"caniuse-lite": "^1.0.30001286",
"electron-to-chromium": "^1.4.17",
Update `npm` packages
2020-11-29 17:43:20 +09:00
"escalade": "^3.1.1",
Update npm packages
2021-12-26 19:09:29 +09:00
"node-releases": "^2.0.1",
"picocolors": "^1.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"buffer": {
Update Puppeteer to version 5.5.0
2020-11-22 22:26:32 +09:00
"version": "5.7.1",
"resolved": "https://registry.npmjs.org/buffer/-/buffer-5.7.1.tgz",
"integrity": "sha512-EHcyIPBQ4BSGlvjB16k5KgAJ27CIsHY/2JBmCRReo48y9rQ3MaUzWX3KVlBa4U7MyX02HdVj0K7C3WaB3ju7FQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-11-01 18:04:57 +09:00
"base64-js": "^1.3.1",
"ieee754": "^1.1.13"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"buffer-crc32": {
"version": "0.2.13",
"resolved": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.13.tgz",
"integrity": "sha1-DTM+PwDqxQqhRUq9MO+MKl2ackI=",
"dev": true
},
"buffer-equal": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/buffer-equal/-/buffer-equal-1.0.0.tgz",
"integrity": "sha1-WWFrSYME1Var1GaWayLu2j7KX74=",
"dev": true
},
"buffer-from": {
Update packages
2018-08-06 04:20:37 +09:00
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/buffer-from/-/buffer-from-1.1.1.tgz",
"integrity": "sha512-MQcXEUbCKtEo7bhqEs6560Hyd4XaovZlO/k9V3hjVUF/zwW7KBVdSK4gIt/bzwS9MbR5qob+F5jusZsb0YQK2A==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"builtin-modules": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-1.1.1.tgz",
"integrity": "sha1-Jw8HbFpywC9bZaR9+Uxf46J4iS8=",
"dev": true
},
"cache-base": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/cache-base/-/cache-base-1.0.1.tgz",
"integrity": "sha512-AKcdTnFSWATd5/GCPRxr2ChwIJ85CeyrEyjRHlKxQ56d4XJMGym0uAiKn0xbLOGOl3+yRpOTi484dVCEc5AUzQ==",
"dev": true,
"requires": {
"collection-visit": "^1.0.0",
"component-emitter": "^1.2.1",
"get-value": "^2.0.6",
"has-value": "^1.0.0",
"isobject": "^3.0.1",
"set-value": "^2.0.0",
"to-object-path": "^0.3.0",
"union-value": "^1.0.0",
"unset-value": "^1.0.0"
}
},
Update npm packages
2021-05-16 17:05:58 +09:00
"call-bind": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/call-bind/-/call-bind-1.0.2.tgz",
"integrity": "sha512-7O+FbCihrB5WGbFYesctwmTKae6rOiIzmz1icreWJ+0aA7LJfuqhEso2T9ncpcFtzMQtzXf2QGGueWJGTYsqrA==",
"dev": true,
"requires": {
"function-bind": "^1.1.1",
"get-intrinsic": "^1.0.2"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"callsites": {
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/callsites/-/callsites-3.1.0.tgz",
"integrity": "sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"camelcase": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz",
"integrity": "sha1-m7UwTS4LVmmLLHWLCKPqqdqlijk=",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"camelcase-keys": {
"version": "6.2.2",
"resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-6.2.2.tgz",
"integrity": "sha512-YrwaA0vEKazPBkn0ipTiMpSajYDSe+KjQfrjhcBMxJt/znbvlHd8Pw/Vamaz5EB4Wfhs3SUR3Z9mwRu/P3s3Yg==",
"dev": true,
"requires": {
"camelcase": "^5.3.1",
"map-obj": "^4.0.0",
"quick-lru": "^4.0.1"
},
"dependencies": {
"camelcase": {
"version": "5.3.1",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-5.3.1.tgz",
"integrity": "sha512-L28STB170nwWS63UjtlEOE3dldQApaJXZkOI1uMFfzf3rRuPegHaHesyee+YxQ+W6SvRDQV6UrdOdRiR153wJg==",
"dev": true
}
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"caniuse-lite": {
Add the `caniuse-lite` package Since the Autoprefixer plugin indirectly depends on this, it seems like a good idea to add this as a direct dependency in the PDF.js project to hopefully avoid having to manually update `caniuse-lite` in the future; see https://github.com/browserslist/browserslist#browsers-data-updating Also, slightly tweaks the Autoprefixer config for GENERIC-builds of the PDF.js library; note that this change doesn't affect the contents of the *built* `web/viewer.js` file.
2022-02-27 19:32:23 +09:00
"version": "1.0.30001312",
"resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001312.tgz",
"integrity": "sha512-Wiz1Psk2MEK0pX3rUzWaunLTZzqS2JYZFzNKqAiJGiuxIjRPLgV6+VDPOg6lQOUxmDwhTlh198JsTTi8Hzw6aQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"canvas": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "2.9.0",
"resolved": "https://registry.npmjs.org/canvas/-/canvas-2.9.0.tgz",
"integrity": "sha512-0l93g7uxp7rMyr7H+XRQ28A3ud0dKIUTIEkUe1Dxh4rjUYN7B93+SjC3r1PDKA18xcQN87OFGgUnyw7LSgNLSQ==",
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-30 14:43:13 +09:00
"@mapbox/node-pre-gyp": "^1.0.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"nan": "^2.15.0",
Update the `canvas` npm package to fix Travis CI builds (issue 10790)
2019-05-08 16:55:26 +09:00
"simple-get": "^3.0.3"
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"catharsis": {
Update npm packages
2021-05-16 17:05:58 +09:00
"version": "0.9.0",
"resolved": "https://registry.npmjs.org/catharsis/-/catharsis-0.9.0.tgz",
"integrity": "sha512-prMTQVpcns/tzFgFVkVp6ak6RykZyWb3gu8ckUpd6YkTlacOd3DXGJjIpD4Q6zJirizvaiAjSSHlOsA+6sNh2A==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-16 17:05:58 +09:00
"lodash": "^4.17.15"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"center-align": {
"version": "0.1.3",
"resolved": "https://registry.npmjs.org/center-align/-/center-align-0.1.3.tgz",
"integrity": "sha1-qg0yYptu6XIgBBHL1EYckHvCt60=",
"dev": true,
"requires": {
"align-text": "^0.1.3",
"lazy-cache": "^1.0.3"
}
},
Update packages
2018-12-23 00:00:53 +09:00
"cephes": {
Update packages
2019-09-15 22:35:32 +09:00
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/cephes/-/cephes-1.2.0.tgz",
"integrity": "sha512-twuUuJRrIrsELHz6foJtZlqrz6FC36zoHZJvvThsrM1UWPKxyoilw1Rka6Hk0AmPFKHKUoGwGfAtvNZNtNZu0g==",
"dev": true
Update packages
2018-12-23 00:00:53 +09:00
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"chalk": {
"version": "2.4.1",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-2.4.1.tgz",
"integrity": "sha512-ObN6h1v2fTJSmUXoS3nMQ92LbDK9be4TV+6G+omQlGJFdcUX5heKi1LZ1YnRMIgwTLEj3E24bT6tYni50rlCfQ==",
"dev": true,
"requires": {
"ansi-styles": "^3.2.1",
"escape-string-regexp": "^1.0.5",
"supports-color": "^5.3.0"
}
},
"character-parser": {
Update packages
2018-11-25 05:00:22 +09:00
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/character-parser/-/character-parser-2.2.0.tgz",
"integrity": "sha1-x84o821LzZdE5f/CxfzeHHMmH8A=",
"dev": true,
"requires": {
"is-regex": "^1.0.3"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"chokidar": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "2.1.8",
"resolved": "https://registry.npmjs.org/chokidar/-/chokidar-2.1.8.tgz",
"integrity": "sha512-ZmZUazfOzf0Nve7duiCKD23PFSCs4JPoYyccjUFF3aQkQadqBhfzhjkwBH2mNOG9cTBwhamM37EIsIkZw3nRgg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"anymatch": "^2.0.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"async-each": "^1.0.1",
"braces": "^2.3.2",
"fsevents": "^1.2.7",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"glob-parent": "^3.1.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"inherits": "^2.0.3",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"is-binary-path": "^1.0.0",
"is-glob": "^4.0.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"normalize-path": "^3.0.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"path-is-absolute": "^1.0.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"readdirp": "^2.2.1",
"upath": "^1.1.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
"is-glob": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.1.tgz",
"integrity": "sha512-5G0tKtBTFImOqDnLB2hG6Bp2qcKEFduo4tZu9MT/H6NQv/ghhy30o55ufafxJ/LdH79LLs2Kfrn85TLKyA7BUg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"is-extglob": "^2.1.1"
}
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"normalize-path": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/normalize-path/-/normalize-path-3.0.0.tgz",
"integrity": "sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==",
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
},
"chownr": {
Update npm packages
2021-10-03 15:21:01 +09:00
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/chownr/-/chownr-1.1.4.tgz",
"integrity": "sha512-jJ0bqzaylmJtVnNgzTeSOs8DPavpbYgEr/b0YL8/2GO3xJEhInFmhKMUnEJQjZumK7KXGFhUy89PrsJWlakBVg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"chrome-trace-event": {
Update npm packages
2021-09-19 16:31:42 +09:00
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/chrome-trace-event/-/chrome-trace-event-1.0.3.tgz",
"integrity": "sha512-p3KULyQg4S7NIHixdwbGX+nFHkoBiA4YQmyWtjb8XngSKV124nJmRysgAeujbUVb15vh+RvFUfCPqU7rXk+hZg==",
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"ci-info": {
Update the `eslint-plugin-unicorn` package to the latest version Please see https://github.com/sindresorhus/eslint-plugin-unicorn/releases/tag/v39.0.0
2021-11-28 18:44:22 +09:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/ci-info/-/ci-info-3.3.0.tgz",
"integrity": "sha512-riT/3vI5YpVH6/qomlDnJow6TBee2PBKSEpx3O32EGPYbWGIRsIlGRms3Sm74wYE1JMo8RnO04Hb12+v1J5ICw==",
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"class-utils": {
"version": "0.3.6",
"resolved": "https://registry.npmjs.org/class-utils/-/class-utils-0.3.6.tgz",
"integrity": "sha512-qOhPa/Fj7s6TY8H8esGu5QNpMMQxz79h+urzrNYN6mn+9BnxlDGf5QZ+XeCDsxSjPqsSR56XOZOJmpeurnLMeg==",
"dev": true,
"requires": {
"arr-union": "^3.1.0",
"define-property": "^0.2.5",
"isobject": "^3.0.0",
"static-extend": "^0.1.1"
},
"dependencies": {
"define-property": {
"version": "0.2.5",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-0.2.5.tgz",
"integrity": "sha1-w1se+RjsPJkPmlvFe+BKrOxcgRY=",
"dev": true,
"requires": {
"is-descriptor": "^0.1.0"
}
}
}
},
"clean-css": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "4.2.4",
"resolved": "https://registry.npmjs.org/clean-css/-/clean-css-4.2.4.tgz",
"integrity": "sha512-EJUDT7nDVFDvaQgAo2G/PJvxmp1o/c6iXLbswsBbUFXi1Nr+AjA2cKmfbKDMjMvzEe75g3P6JkaDDAKk96A85A==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"source-map": "~0.6.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Replace the remaining occurences of `instanceof Array` with `Array.isArray()` *Follow-up to PRs 8864 and 8813.* As explained in https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/isArray, `instanceof Array` can have inconsistent behavior. To ensure that only `Array.isArray` is used, an ESLint plugin/rule is added to enforce this.
2018-07-09 20:11:35 +09:00
"clean-regexp": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/clean-regexp/-/clean-regexp-1.0.0.tgz",
"integrity": "sha1-jffHquUf02h06PjQW5GAvBGj/tc=",
"dev": true,
"requires": {
"escape-string-regexp": "^1.0.5"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"cliui": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/cliui/-/cliui-2.1.0.tgz",
"integrity": "sha1-S0dXYP+AJkx2LDoXGQMukcf+oNE=",
"dev": true,
"requires": {
"center-align": "^0.1.1",
"right-align": "^0.1.1",
"wordwrap": "0.0.2"
}
},
Update `npm` packages
2020-10-04 20:49:28 +09:00
"clone": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/clone/-/clone-2.1.2.tgz",
"integrity": "sha1-G39Ln1kfHo+DZwQBYANFoCiHQ18=",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"clone-buffer": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/clone-buffer/-/clone-buffer-1.0.0.tgz",
"integrity": "sha1-4+JbIHrE5wGvch4staFnksrD3Fg=",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"clone-regexp": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/clone-regexp/-/clone-regexp-2.2.0.tgz",
"integrity": "sha512-beMpP7BOtTipFuW8hrJvREQ2DrRu3BE7by0ZpibtfBA+qfHYvMGTc2Yb1JMYPKg/JUw0CHYvpg796aNTSW9z7Q==",
"dev": true,
"requires": {
"is-regexp": "^2.0.0"
}
},
Update `npm` packages
2020-10-04 20:49:28 +09:00
"clone-stats": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-1.0.0.tgz",
"integrity": "sha1-s3gt/4u1R04Yuba/D9/ngvh3doA=",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"cloneable-readable": {
Update `npm` packages
2020-10-04 20:49:28 +09:00
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/cloneable-readable/-/cloneable-readable-1.1.3.tgz",
"integrity": "sha512-2EF8zTQOxYq70Y4XKtorQupqF0m49MBz2/yf5Bj+MHjvpG3Hy7sImifnqD6UA+TKYxeSV+u6qqQPawN5UvnpKQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"inherits": "^2.0.1",
"process-nextick-args": "^2.0.0",
"readable-stream": "^2.3.5"
}
},
"code-point-at": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/code-point-at/-/code-point-at-1.1.0.tgz",
"integrity": "sha1-DQcLTQQ6W+ozovGkDi7bPZpMz3c=",
"dev": true
},
"coffee-script": {
"version": "1.12.7",
"resolved": "https://registry.npmjs.org/coffee-script/-/coffee-script-1.12.7.tgz",
"integrity": "sha512-fLeEhqwymYat/MpTPUjSKHVYYl0ec2mOyALEMLmzr5i1isuG+6jfI2j2d5oBO3VIzgUXgBVIcOT9uH1TFxBckw==",
"dev": true
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"collection-map": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/collection-map/-/collection-map-1.0.0.tgz",
"integrity": "sha1-rqDwb40mx4DCt1SUOFVEsiVa8Yw=",
"dev": true,
"requires": {
"arr-map": "^2.0.2",
"for-own": "^1.0.0",
"make-iterator": "^1.0.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"collection-visit": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/collection-visit/-/collection-visit-1.0.0.tgz",
"integrity": "sha1-S8A3PBZLwykbTTaMgpzxqApZ3KA=",
"dev": true,
"requires": {
"map-visit": "^1.0.0",
"object-visit": "^1.0.0"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"color": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/color/-/color-3.0.0.tgz",
"integrity": "sha512-jCpd5+s0s0t7p3pHQKpnJ0TpQKKdleP71LWcA0aqiljpiuAkOSUFN/dyH8ZwF0hRmFlrIuRhufds1QyEP9EB+w==",
"dev": true,
"requires": {
"color-convert": "^1.9.1",
"color-string": "^1.5.2"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"color-convert": {
"version": "1.9.1",
"resolved": "https://registry.npmjs.org/color-convert/-/color-convert-1.9.1.tgz",
"integrity": "sha512-mjGanIiwQJskCC18rPR6OmrZ6fm2Lc7PeGFYwCmy5J34wC6F1PzdGL6xeMfmgicfYcNLGuVFA3WzXtIDCQSZxQ==",
"dev": true,
"requires": {
"color-name": "^1.1.1"
}
},
"color-name": {
Update npm packages
2021-12-26 19:09:29 +09:00
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz",
"integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"color-string": {
Bump color-string from 1.5.3 to 1.5.5 Bumps [color-string](https://github.com/Qix-/color-string) from 1.5.3 to 1.5.5. - [Release notes](https://github.com/Qix-/color-string/releases) - [Changelog](https://github.com/Qix-/color-string/blob/master/CHANGELOG.md) - [Commits](https://github.com/Qix-/color-string/commits/1.5.5) --- updated-dependencies: - dependency-name: color-string dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-06-22 16:59:39 +09:00
"version": "1.5.5",
"resolved": "https://registry.npmjs.org/color-string/-/color-string-1.5.5.tgz",
"integrity": "sha512-jgIoum0OfQfq9Whcfc2z/VhCNcmQjWbey6qBX0vqt7YICflUmBCh9E9CiQD5GSJ+Uehixm3NUwHVhqUAWRivZg==",
Update packages
2018-11-25 05:00:22 +09:00
"dev": true,
"requires": {
"color-name": "^1.0.0",
"simple-swizzle": "^0.2.2"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"color-support": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/color-support/-/color-support-1.1.3.tgz",
"integrity": "sha512-qiBjkpbMLO/HL68y+lh4q0/O1MZFj2RX6X/KmMa3+gJD3z+WwI1ZzDHysvqHGS3mP6mznPckpXmw1nI9cJjyRg==",
"dev": true
},
Update npm packages
2021-12-26 19:09:29 +09:00
"colord": {
"version": "2.9.2",
"resolved": "https://registry.npmjs.org/colord/-/colord-2.9.2.tgz",
"integrity": "sha512-Uqbg+J445nc1TKn4FoDPS6ZZqAvEDnwrH42yo8B40JSOgSLxMZ/gt3h4nmCtPLQeXhjJJkqBx7SCY35WnIixaQ==",
Update `npm` packages
2020-06-27 18:30:30 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"colornames": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/colornames/-/colornames-1.1.1.tgz",
"integrity": "sha1-+IiQMGhcfE/54qVZ9Qd+t2qBb5Y=",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"colors": {
Update packages
2018-11-25 05:00:22 +09:00
"version": "1.3.2",
"resolved": "https://registry.npmjs.org/colors/-/colors-1.3.2.tgz",
"integrity": "sha512-rhP0JSBGYvpcNQj4s5AdShMeE5ahMop96cTeDl/v9qQQm2fYClE2QXZRi8wLzc+GmXSxdIqqbOIAhyObEXDbfQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"colorspace": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/colorspace/-/colorspace-1.1.1.tgz",
"integrity": "sha512-pI3btWyiuz7Ken0BWh9Elzsmv2bM9AhA7psXib4anUXy/orfZ/E0MbQwhSOG/9L8hLlalqrU0UhOuqxW1YjmVw==",
"dev": true,
"requires": {
"color": "3.0.x",
"text-hex": "1.0.x"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"commander": {
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/commander/-/commander-1.0.5.tgz",
"integrity": "sha1-RXKVu5duOI6d0NtS3kMz4knz2Iw=",
"dev": true,
"requires": {
"keypress": "0.1.x"
}
},
"commondir": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/commondir/-/commondir-1.0.1.tgz",
"integrity": "sha1-3dgA2gxmEnOTzKWVDqloo6rxJTs=",
"dev": true
},
"component-emitter": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/component-emitter/-/component-emitter-1.2.1.tgz",
"integrity": "sha1-E3kY1teCg/ffemt8WmPhQOaUJeY=",
"dev": true
},
"concat-map": {
"version": "0.0.1",
"resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz",
"integrity": "sha1-2Klr13/Wjfd5OnMDajug1UBdR3s=",
"dev": true
},
"concat-stream": {
"version": "1.6.2",
"resolved": "https://registry.npmjs.org/concat-stream/-/concat-stream-1.6.2.tgz",
"integrity": "sha512-27HBghJxjiZtIk3Ycvn/4kbJk/1uZuJFfuPEns6LaEvpvG1f0hTea8lilrouyo9mVc2GWdcEZ8OLoGmSADlrCw==",
"dev": true,
"requires": {
"buffer-from": "^1.0.0",
"inherits": "^2.0.3",
"readable-stream": "^2.2.2",
"typedarray": "^0.0.6"
}
},
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"console-control-strings": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/console-control-strings/-/console-control-strings-1.1.0.tgz",
"integrity": "sha1-PXz0Rk22RG6mRL9LOVB/mFEAjo4=",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"constantinople": {
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/constantinople/-/constantinople-3.1.2.tgz",
"integrity": "sha512-yePcBqEFhLOqSBtwYOGGS1exHo/s1xjekXiinh4itpNQGCu4KA1euPh1fg07N2wMITZXQkBz75Ntdt1ctGZouw==",
"dev": true,
"requires": {
"@types/babel-types": "^7.0.0",
"@types/babylon": "^6.16.2",
"babel-types": "^6.26.0",
"babylon": "^6.18.0"
}
},
"convert-source-map": {
"version": "1.5.1",
"resolved": "https://registry.npmjs.org/convert-source-map/-/convert-source-map-1.5.1.tgz",
"integrity": "sha1-uCeAl7m8IpNl3lxiz1/K7YtVmeU=",
"dev": true
},
"copy-descriptor": {
"version": "0.1.1",
"resolved": "https://registry.npmjs.org/copy-descriptor/-/copy-descriptor-0.1.1.tgz",
"integrity": "sha1-Z29us8OZl8LuGsOpJP1hJHSPV40=",
"dev": true
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"copy-props": {
Bump copy-props from 2.0.4 to 2.0.5 Bumps [copy-props](https://github.com/gulpjs/copy-props) from 2.0.4 to 2.0.5. - [Release notes](https://github.com/gulpjs/copy-props/releases) - [Changelog](https://github.com/gulpjs/copy-props/blob/master/CHANGELOG.md) - [Commits](https://github.com/gulpjs/copy-props/compare/2.0.4...2.0.5) --- updated-dependencies: - dependency-name: copy-props dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-28 06:37:54 +09:00
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/copy-props/-/copy-props-2.0.5.tgz",
"integrity": "sha512-XBlx8HSqrT0ObQwmSzM7WE5k8FxTV75h1DX1Z3n6NhQ/UYYAvInWYmG06vFt7hQZArE2fuO62aihiWIVQwh1sw==",
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"dev": true,
"requires": {
Bump copy-props from 2.0.4 to 2.0.5 Bumps [copy-props](https://github.com/gulpjs/copy-props) from 2.0.4 to 2.0.5. - [Release notes](https://github.com/gulpjs/copy-props/releases) - [Changelog](https://github.com/gulpjs/copy-props/blob/master/CHANGELOG.md) - [Commits](https://github.com/gulpjs/copy-props/compare/2.0.4...2.0.5) --- updated-dependencies: - dependency-name: copy-props dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-28 06:37:54 +09:00
"each-props": "^1.3.2",
"is-plain-object": "^5.0.0"
},
"dependencies": {
"is-plain-object": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/is-plain-object/-/is-plain-object-5.0.0.tgz",
"integrity": "sha512-VRSzKkbMm5jMDoKLbltAkFQ5Qr7VDiTFGXxYFXXowVj387GeGNOCsOH6Msy00SGZ3Fp84b1Naa1psqgcCIEP5Q==",
"dev": true
}
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"core-js": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "3.21.1",
"resolved": "https://registry.npmjs.org/core-js/-/core-js-3.21.1.tgz",
"integrity": "sha512-FRq5b/VMrWlrmCzwRrpDYNxyHP9BcAZC+xHJaqTgIE5091ZV1NTmyh0sGOg5XqpnHvR0svdy0sv1gWA1zmhxig==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2019-03-31 02:59:52 +09:00
"core-js-compat": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "3.20.3",
"resolved": "https://registry.npmjs.org/core-js-compat/-/core-js-compat-3.20.3.tgz",
"integrity": "sha512-c8M5h0IkNZ+I92QhIpuSijOxGAcj3lgpsWdkCqmUTZNwidujF4r3pi6x1DCN+Vcs5qTS2XWWMfWSuCqyupX8gw==",
Update packages
2019-03-31 02:59:52 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-23 18:58:15 +09:00
"browserslist": "^4.19.1",
Update `npm` packages
2019-12-19 19:28:13 +09:00
"semver": "7.0.0"
Update packages
2019-03-31 02:59:52 +09:00
},
"dependencies": {
"semver": {
Update `npm` packages
2019-12-19 19:28:13 +09:00
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-7.0.0.tgz",
"integrity": "sha512-+GB6zVA9LWh6zovYQLALHwv5rb2PHGlJi3lfiqIHxR0uuwCgefcOJc59v9fv1w8GbStwxuuqqAjI9NMAOOgq1A==",
Update packages
2019-03-31 02:59:52 +09:00
"dev": true
}
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"core-util-is": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.2.tgz",
"integrity": "sha1-tf1UIgqivFq1eqtxQMlAdUUDwac=",
"dev": true
},
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"cosmiconfig": {
"version": "7.0.1",
"resolved": "https://registry.npmjs.org/cosmiconfig/-/cosmiconfig-7.0.1.tgz",
"integrity": "sha512-a1YWNUV2HwGimB7dU2s1wUMurNKjpx60HxBB6xUM8Re+2s1g1IIfJvFR0/iCF+XHdE0GMTKTuLR32UQff4TEyQ==",
"dev": true,
"requires": {
"@types/parse-json": "^4.0.0",
"import-fresh": "^3.2.1",
"parse-json": "^5.0.0",
"path-type": "^4.0.0",
"yaml": "^1.10.0"
},
"dependencies": {
"parse-json": {
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-5.2.0.tgz",
"integrity": "sha512-ayCKvm/phCGxOkYRSCM82iDwct8/EonSEgCSxWxD7ve6jHggsFl4fZVQBPRNgQoKiuV/odhFrGzQXZwbifC8Rg==",
"dev": true,
"requires": {
"@babel/code-frame": "^7.0.0",
"error-ex": "^1.3.1",
"json-parse-even-better-errors": "^2.3.0",
"lines-and-columns": "^1.1.6"
}
}
}
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"cross-env": {
Update `npm` packages
2020-12-13 19:38:37 +09:00
"version": "7.0.3",
"resolved": "https://registry.npmjs.org/cross-env/-/cross-env-7.0.3.tgz",
"integrity": "sha512-+/HKd6EgcQCJGh2PSjZuUitQBQynKor4wrFbRg4DtAgS1aWO+gU52xpH7M9ScGgXSYmAVS9bIJ8EzuaGw0oNAw==",
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"dev": true,
"requires": {
"cross-spawn": "^7.0.1"
}
},
Update npm packages
2022-02-20 18:08:23 +09:00
"cross-fetch": {
"version": "3.1.5",
"resolved": "https://registry.npmjs.org/cross-fetch/-/cross-fetch-3.1.5.tgz",
"integrity": "sha512-lvb1SBsI0Z7GDwmuid+mU3kWVBwTVUbe7S0H52yaaAdQOXq2YktTCZdlAcNKFzE6QtRz0snpw9bNiPeOIkkQvw==",
"dev": true,
"requires": {
"node-fetch": "2.6.7"
}
},
Update `npm` packages
2019-12-29 03:57:25 +09:00
"cross-spawn": {
Update `npm` packages
2020-05-30 17:58:10 +09:00
"version": "7.0.3",
"resolved": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.3.tgz",
"integrity": "sha512-iRDPJKUPVEND7dHPO8rkbOnPpyDygcDFtWjpeWNCgy8WP2rXcxXL8TskReQl6OrB2G7+UJrags1q15Fudc7G6w==",
Update `npm` packages
2019-12-29 03:57:25 +09:00
"dev": true,
"requires": {
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"path-key": "^3.1.0",
"shebang-command": "^2.0.0",
"which": "^2.0.1"
},
"dependencies": {
"path-key": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/path-key/-/path-key-3.1.1.tgz",
"integrity": "sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==",
"dev": true
},
"shebang-command": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/shebang-command/-/shebang-command-2.0.0.tgz",
"integrity": "sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==",
"dev": true,
"requires": {
"shebang-regex": "^3.0.0"
}
},
"shebang-regex": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/shebang-regex/-/shebang-regex-3.0.0.tgz",
"integrity": "sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==",
"dev": true
},
"which": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/which/-/which-2.0.2.tgz",
"integrity": "sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==",
"dev": true,
"requires": {
"isexe": "^2.0.0"
}
}
Update `npm` packages
2019-12-29 03:57:25 +09:00
}
},
Update npm packages
2022-02-20 18:08:23 +09:00
"css-functions-list": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/css-functions-list/-/css-functions-list-3.0.1.tgz",
"integrity": "sha512-PriDuifDt4u4rkDgnqRCLnjfMatufLmWNfQnGCq34xZwpY3oabwhB9SqRBmuvWUgndbemCFlKqg+nO7C2q0SBw==",
"dev": true
},
Update the left/right CSS calculation for the `sidebarContainer` HTML element to enable IE11 compatibility As gross as this hack is, it nonetheless seem necessary to allow using CSS variables; see also https://github.com/mozilla/pdf.js/pull/11567#issuecomment-582166160
2020-02-05 08:34:44 +09:00
"cssesc": {
Update `npm` packages
2020-02-22 01:38:22 +09:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/cssesc/-/cssesc-3.0.0.tgz",
"integrity": "sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==",
Update the left/right CSS calculation for the `sidebarContainer` HTML element to enable IE11 compatibility As gross as this hack is, it nonetheless seem necessary to allow using CSS variables; see also https://github.com/mozilla/pdf.js/pull/11567#issuecomment-582166160
2020-02-05 08:34:44 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"d": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/d/-/d-1.0.0.tgz",
"integrity": "sha1-dUu1v+VUUdpppYuU1F9MWwRi1Y8=",
"dev": true,
"requires": {
"es5-ext": "^0.10.9"
}
},
"debug": {
"version": "2.6.9",
"resolved": "https://registry.npmjs.org/debug/-/debug-2.6.9.tgz",
"integrity": "sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==",
"dev": true,
"requires": {
"ms": "2.0.0"
}
},
"decamelize": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/decamelize/-/decamelize-1.2.0.tgz",
"integrity": "sha1-9lNNFRSCabIDUue+4m9QH5oZEpA=",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"decamelize-keys": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/decamelize-keys/-/decamelize-keys-1.1.0.tgz",
"integrity": "sha1-0XGoeTMlKAfrPLYdwcFEXQeN8tk=",
"dev": true,
"requires": {
"decamelize": "^1.1.0",
"map-obj": "^1.0.0"
},
"dependencies": {
"map-obj": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-1.0.1.tgz",
"integrity": "sha1-2TPOuSBdgr3PSIb2dCvcK03qFG0=",
"dev": true
}
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"decode-uri-component": {
"version": "0.2.0",
"resolved": "https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz",
"integrity": "sha1-6zkTMzRYd1y4TNGh+uBiEGu4dUU=",
"dev": true
},
Update the `canvas` npm package to fix Travis CI builds (issue 10790)
2019-05-08 16:55:26 +09:00
"decompress-response": {
Update `npm` packages
2019-12-29 03:57:25 +09:00
"version": "4.2.1",
"resolved": "https://registry.npmjs.org/decompress-response/-/decompress-response-4.2.1.tgz",
"integrity": "sha512-jOSne2qbyE+/r8G1VU+G/82LBs2Fs4LAsTiLSHOCOMZQl2OKZ6i8i4IyHemTe+/yIXOtTcRQMzPcgyhoFlqPkw==",
Update the `canvas` npm package to fix Travis CI builds (issue 10790)
2019-05-08 16:55:26 +09:00
"dev": true,
"requires": {
Update `npm` packages
2019-12-29 03:57:25 +09:00
"mimic-response": "^2.0.0"
Update the `canvas` npm package to fix Travis CI builds (issue 10790)
2019-05-08 16:55:26 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"deep-is": {
"version": "0.1.3",
"resolved": "https://registry.npmjs.org/deep-is/-/deep-is-0.1.3.tgz",
"integrity": "sha1-s2nW+128E+7PUk+RsHD+7cNXzzQ=",
"dev": true
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"default-compare": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/default-compare/-/default-compare-1.0.0.tgz",
"integrity": "sha512-QWfXlM0EkAbqOCbD/6HjdwT19j7WCkMyiRhWilc4H9/5h/RzTF9gv5LYh1+CmDV5d1rki6KAWLtQale0xt20eQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"kind-of": "^5.0.2"
},
"dependencies": {
"kind-of": {
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-5.1.0.tgz",
"integrity": "sha512-NGEErnH6F2vUuXDh+OlbcKW7/wOcfdRHaZ7VWtqCztfHri/++YKmP51OdWeGPuqCOba6kk2OTe5d02VmTB80Pw==",
"dev": true
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"default-resolution": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/default-resolution/-/default-resolution-2.0.0.tgz",
"integrity": "sha1-vLgrqnKtebQmp2cy8aga1t8m1oQ=",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"define-properties": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.1.2.tgz",
"integrity": "sha1-g6c/L+pWmJj7c3GTyPhzyvbUXJQ=",
"dev": true,
"requires": {
"foreach": "^2.0.5",
"object-keys": "^1.0.8"
}
},
"define-property": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-2.0.2.tgz",
"integrity": "sha512-jwK2UV4cnPpbcG7+VRARKTZPUWowwXA8bzH5NP6ud0oeAxyYPuGZUAC7hMugpCdz4BeSZl2Dl9k66CHJ/46ZYQ==",
"dev": true,
"requires": {
"is-descriptor": "^1.0.2",
"isobject": "^3.0.1"
},
"dependencies": {
"is-accessor-descriptor": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-accessor-descriptor/-/is-accessor-descriptor-1.0.0.tgz",
"integrity": "sha512-m5hnHTkcVsPfqx3AKlyttIPb7J+XykHvJP2B9bZDjlhLIoEq4XoK64Vg7boZlVWYK6LUY94dYPEE7Lh0ZkZKcQ==",
"dev": true,
"requires": {
"kind-of": "^6.0.0"
}
},
"is-data-descriptor": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-data-descriptor/-/is-data-descriptor-1.0.0.tgz",
"integrity": "sha512-jbRXy1FmtAoCjQkVmIVYwuuqDFUbaOeDjmed1tOGPrsMhtJA4rD9tkgA0F1qJ3gRFRXcHYVkdeaP50Q5rE/jLQ==",
"dev": true,
"requires": {
"kind-of": "^6.0.0"
}
},
"is-descriptor": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/is-descriptor/-/is-descriptor-1.0.2.tgz",
"integrity": "sha512-2eis5WqQGV7peooDyLmNEPUrps9+SXX5c9pL3xEB+4e9HnGuDa7mB7kHxHw4CbqS9k1T2hOH3miL8n8WtiYVtg==",
"dev": true,
"requires": {
"is-accessor-descriptor": "^1.0.0",
"is-data-descriptor": "^1.0.0",
"kind-of": "^6.0.2"
}
}
}
},
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"delegates": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/delegates/-/delegates-1.0.0.tgz",
"integrity": "sha1-hMbhWbgZBP3KWaDvRM2HDTElD5o=",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"detect-file": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/detect-file/-/detect-file-1.0.0.tgz",
"integrity": "sha1-8NZtA2cqglyxtzvbP+YjEMjlUrc=",
"dev": true
},
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"detect-libc": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/detect-libc/-/detect-libc-1.0.3.tgz",
"integrity": "sha1-+hN8S9aY7fVc1c0CrFWfkaTEups=",
"dev": true
},
Upgrade Puppeteer to version 5.3.1
2020-10-04 06:06:31 +09:00
"devtools-protocol": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "0.0.960912",
"resolved": "https://registry.npmjs.org/devtools-protocol/-/devtools-protocol-0.0.960912.tgz",
"integrity": "sha512-I3hWmV9rWHbdnUdmMKHF2NuYutIM2kXz2mdXW8ha7TbRlGTVs+PF+PsB5QWvpCek4Fy9B+msiispCfwlhG5Sqg==",
Upgrade Puppeteer to version 5.3.1
2020-10-04 06:06:31 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"diagnostics": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/diagnostics/-/diagnostics-1.1.1.tgz",
"integrity": "sha512-8wn1PmdunLJ9Tqbx+Fx/ZEuHfJf4NKSN2ZBj7SJC/OWRWha843+WsTjqMe1B5E3p28jqBlp+mJ2fPVxPyNgYKQ==",
"dev": true,
"requires": {
"colorspace": "1.1.x",
"enabled": "1.0.x",
"kuler": "1.0.x"
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dir-glob": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/dir-glob/-/dir-glob-3.0.1.tgz",
"integrity": "sha512-WkrWp9GR4KXfKGYzOLmTuGVi1UWFfws377n9cc55/tb6DuqyF6pcQ5AbiHEshaDpY9v6oaSr2XCDidGmMwdzIA==",
"dev": true,
"requires": {
"path-type": "^4.0.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"distributions": {
Update packages
2019-09-15 22:35:32 +09:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/distributions/-/distributions-2.1.0.tgz",
"integrity": "sha512-4eov7WXRip5Tu0K7Y51W1oVt+DcvkoE0EzsvbLzgedC/n4PUpYXHqk6vo/OH1HteBHp5Vm6cmfnInf9NAXM4qQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-12-23 00:00:53 +09:00
"cephes": "^1.1.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"doctrine": {
Update packages
2019-02-18 00:44:36 +09:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/doctrine/-/doctrine-3.0.0.tgz",
"integrity": "sha512-yS+Q5i3hBf7GBkd4KG8a7eBNNWNGLTaEwwYWUijIYM7zrlYDM0BFXHjjPWlWZ1Rg7UaddZeIDmi9jF3HmqiQ2w==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"esutils": "^2.0.2"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"doctypes": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/doctypes/-/doctypes-1.1.0.tgz",
"integrity": "sha1-6oCxBqh1OHdOijpKWv4pPeSJ4Kk=",
"dev": true
},
Update the various ESLint packages to their latest versions
2018-07-09 19:52:55 +09:00
"domelementtype": {
Update `npm` packages
2020-08-09 18:03:07 +09:00
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-2.0.1.tgz",
"integrity": "sha512-5HOHUDsYZWV8FGWN0Njbr/Rn7f/eWSQi1v7+HsUVwXgn8nWWlL64zKDkS0n8ZmQ3mlWOMuXOnR+7Nx/5tMO5AQ==",
Update the various ESLint packages to their latest versions
2018-07-09 19:52:55 +09:00
"dev": true
},
"domhandler": {
Update npm packages
2021-10-03 15:21:01 +09:00
"version": "4.2.2",
"resolved": "https://registry.npmjs.org/domhandler/-/domhandler-4.2.2.tgz",
"integrity": "sha512-PzE9aBMsdZO8TK4BnuJwH0QT41wgMbRzuZrHUcpYncEjmQazq8QEaBWgLG7ZyC/DAZKEgglpIA6j4Qn/HmxS3w==",
Update the various ESLint packages to their latest versions
2018-07-09 19:52:55 +09:00
"dev": true,
"requires": {
Update npm packages
2021-10-03 15:21:01 +09:00
"domelementtype": "^2.2.0"
Update `npm` packages
2021-03-21 19:00:02 +09:00
},
"dependencies": {
"domelementtype": {
Update npm packages
2021-10-03 15:21:01 +09:00
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-2.2.0.tgz",
"integrity": "sha512-DtBMo82pv1dFtUmHyr48beiuq792Sxohr+8Hm9zoxklYPfa6n0Z3Byjj2IV7bmr2IyqClnqEQhfgHJJ5QF0R5A==",
Update `npm` packages
2021-03-21 19:00:02 +09:00
"dev": true
}
Update the various ESLint packages to their latest versions
2018-07-09 19:52:55 +09:00
}
},
Add a `DOMMatrix` polyfill for Node.js environments (PR 13361 follow-up) Given that `DOMMatrix` is, unsurprisingly, not supported in Node.js the `createMatrix` helper function in `src/display/pattern_helper.js` is most likely broken in Node.js environments. It will obviously try to fallback to the `DOMSVGFactory`, however that isn't intended for Node.js usage and errors will be thrown. Rather than trying to implement a `NodeSVGFactory`, this patch takes the easier route of just adding a `DOMMatrix` polyfill using: https://www.npmjs.com/package/dommatrix This isn't done only for simplicity, but it'll become necessary anyway since the `createMatrix` helper function is only temporary and will be removed in the future.
2021-06-10 17:50:35 +09:00
"dommatrix": {
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"version": "0.0.24",
"resolved": "https://registry.npmjs.org/dommatrix/-/dommatrix-0.0.24.tgz",
"integrity": "sha512-PatEhAW5pIHr28MvFQGV5iiHNloqvecQZlxs7/8s/eulLqZI3uVqPkrO7YDuqsebovr/9mmcWDSWzVG4amEZgQ==",
Update the `dommatrix` package to the latest version
2021-11-28 18:42:36 +09:00
"dev": true
Add a `DOMMatrix` polyfill for Node.js environments (PR 13361 follow-up) Given that `DOMMatrix` is, unsurprisingly, not supported in Node.js the `createMatrix` helper function in `src/display/pattern_helper.js` is most likely broken in Node.js environments. It will obviously try to fallback to the `DOMSVGFactory`, however that isn't intended for Node.js usage and errors will be thrown. Rather than trying to implement a `NodeSVGFactory`, this patch takes the easier route of just adding a `DOMMatrix` polyfill using: https://www.npmjs.com/package/dommatrix This isn't done only for simplicity, but it'll become necessary anyway since the `createMatrix` helper function is only temporary and will be removed in the future.
2021-06-10 17:50:35 +09:00
},
Update the various ESLint packages to their latest versions
2018-07-09 19:52:55 +09:00
"domutils": {
Update npm packages
2021-10-03 15:21:01 +09:00
"version": "2.8.0",
"resolved": "https://registry.npmjs.org/domutils/-/domutils-2.8.0.tgz",
"integrity": "sha512-w96Cjofp72M5IIhpjgobBimYEfoPjx1Vx0BSX9P30WBdZW2WIKU0T1Bd0kz2eNZ9ikjKgHbEyKx8BB6H1L3h3A==",
Update the various ESLint packages to their latest versions
2018-07-09 19:52:55 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-09-20 18:34:24 +09:00
"dom-serializer": "^1.0.1",
Update npm packages
2021-10-03 15:21:01 +09:00
"domelementtype": "^2.2.0",
"domhandler": "^4.2.0"
Update `npm` packages
2020-09-20 18:34:24 +09:00
},
"dependencies": {
"dom-serializer": {
Update npm packages
2021-10-03 15:21:01 +09:00
"version": "1.3.2",
"resolved": "https://registry.npmjs.org/dom-serializer/-/dom-serializer-1.3.2.tgz",
"integrity": "sha512-5c54Bk5Dw4qAxNOI1pFEizPSjVsx5+bpJKmL2kPn8JhBUq2q09tTCa3mjijun2NfK78NMouDYNMBkOrPZiS+ig==",
Update `npm` packages
2020-09-20 18:34:24 +09:00
"dev": true,
"requires": {
"domelementtype": "^2.0.1",
Update npm packages
2021-10-03 15:21:01 +09:00
"domhandler": "^4.2.0",
Update `npm` packages
2020-09-20 18:34:24 +09:00
"entities": "^2.0.0"
}
},
Update npm packages
2021-10-03 15:21:01 +09:00
"domelementtype": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-2.2.0.tgz",
"integrity": "sha512-DtBMo82pv1dFtUmHyr48beiuq792Sxohr+8Hm9zoxklYPfa6n0Z3Byjj2IV7bmr2IyqClnqEQhfgHJJ5QF0R5A==",
"dev": true
},
Update `npm` packages
2020-09-20 18:34:24 +09:00
"entities": {
Update `npm` packages
2021-03-21 19:00:02 +09:00
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/entities/-/entities-2.2.0.tgz",
"integrity": "sha512-p92if5Nz619I0w+akJrLZH0MX0Pb5DX39XOwQTtXSdQQOaYH03S1uIQp4mhOZtAXrxq4ViO67YTiLBo2638o9A==",
Update `npm` packages
2020-09-20 18:34:24 +09:00
"dev": true
}
Update the various ESLint packages to their latest versions
2018-07-09 19:52:55 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"duplexify": {
"version": "3.6.0",
"resolved": "https://registry.npmjs.org/duplexify/-/duplexify-3.6.0.tgz",
"integrity": "sha512-fO3Di4tBKJpYTFHAxTU00BcfWMY9w24r/x21a6rZRbsD/ToUgGxsMbiGRmB7uVAXeGKXD9MwiLZa5E97EVgIRQ==",
"dev": true,
"requires": {
"end-of-stream": "^1.0.0",
"inherits": "^2.0.1",
"readable-stream": "^2.0.0",
"stream-shift": "^1.0.0"
}
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"each-props": {
"version": "1.3.2",
"resolved": "https://registry.npmjs.org/each-props/-/each-props-1.3.2.tgz",
"integrity": "sha512-vV0Hem3zAGkJAyU7JSjixeU66rwdynTAa1vofCrSA5fEln+m67Az9CcnkVD776/fsN/UjIWmBDoNRS6t6G9RfA==",
"dev": true,
"requires": {
"is-plain-object": "^2.0.1",
"object.defaults": "^1.1.0"
}
},
Update npm packages
2021-08-22 17:38:52 +09:00
"electron-to-chromium": {
Update npm packages
2021-12-26 19:09:29 +09:00
"version": "1.4.28",
"resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.4.28.tgz",
"integrity": "sha512-Gzbf0wUtKfyPaqf0Plz+Ctinf9eQIzxEqBHwSvbGfeOm9GMNdLxyu1dNiCUfM+x6r4BE0xUJNh3Nmg9gfAtTmg==",
Update npm packages
2021-08-22 17:38:52 +09:00
"dev": true
},
Update packages
2019-02-18 00:44:36 +09:00
"emoji-regex": {
Update `npm` packages
2020-12-27 19:11:18 +09:00
"version": "8.0.0",
"resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-8.0.0.tgz",
"integrity": "sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==",
Update packages
2019-02-18 00:44:36 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"emojis-list": {
Update `npm` packages
2020-04-02 19:13:14 +09:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/emojis-list/-/emojis-list-3.0.0.tgz",
"integrity": "sha512-/kyM18EfinwXZbno9FyUGeFh87KC8HRQBQGildHZbEuRyWFOmv1U10o9BBp8XVZDVNNuQKyIGIu5ZYAAXJ0V2Q==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"enabled": {
"version": "1.0.2",
"resolved": "http://registry.npmjs.org/enabled/-/enabled-1.0.2.tgz",
"integrity": "sha1-ll9lE9LC0cX0ZStkouM5ZGf8L5M=",
"dev": true,
"requires": {
"env-variable": "0.0.x"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"end-of-stream": {
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"version": "1.4.1",
"resolved": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.4.1.tgz",
"integrity": "sha512-1MkrZNvWTKCaigbn+W15elq2BB/L22nqrSY5DKlo3X6+vclJm8Bb5djXJBmEX6fS3+zCh/F4VBK5Z2KxJt4s2Q==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"once": "^1.4.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"enhanced-resolve": {
Update npm packages
2021-10-03 15:21:01 +09:00
"version": "5.8.3",
"resolved": "https://registry.npmjs.org/enhanced-resolve/-/enhanced-resolve-5.8.3.tgz",
"integrity": "sha512-EGAbGvH7j7Xt2nc0E7D99La1OiEs8LnyimkRgwExpUMScN6O+3x9tIWs7PLQZVNx4YD+00skHXPXi1yQHpAmZA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"graceful-fs": "^4.2.4",
Update `npm` packages
2020-12-27 19:11:18 +09:00
"tapable": "^2.2.0"
Update `npm` packages
2020-06-27 18:30:30 +09:00
}
},
Update the various ESLint packages to their latest versions
2018-07-09 19:52:55 +09:00
"entities": {
Update eslint-plugin-mozilla to ^1.0.1
2018-11-23 22:40:05 +09:00
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/entities/-/entities-1.1.2.tgz",
"integrity": "sha512-f2LZMYl1Fzu7YSBKg+RoROelpOaNrcGmE9AZubeDfrCEia483oW4MI4VyFd5VNHIgQ/7qm1I0wUHK1eJnn2y2w==",
"dev": true
Update the various ESLint packages to their latest versions
2018-07-09 19:52:55 +09:00
},
Update packages
2018-11-25 05:00:22 +09:00
"env-variable": {
"version": "0.0.5",
"resolved": "https://registry.npmjs.org/env-variable/-/env-variable-0.0.5.tgz",
"integrity": "sha512-zoB603vQReOFvTg5xMl9I1P2PnHsHQQKTEowsKKD7nseUfJq6UWzK+4YtlWUO1nhiQUxe6XMkk+JleSZD1NZFA==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"errno": {
Update `npm` packages
2021-02-07 19:55:03 +09:00
"version": "0.1.8",
"resolved": "https://registry.npmjs.org/errno/-/errno-0.1.8.tgz",
"integrity": "sha512-dJ6oBr5SQ1VSd9qkk7ByRgb/1SH4JZjCHSW/mr63/QcXO9zLVxvJ6Oy13nio03rxpSnVDDjFor75SjVeZWPW/A==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"prr": "~1.0.1"
}
},
"error-ex": {
"version": "1.3.1",
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.3.1.tgz",
"integrity": "sha1-+FWobOYa3E6GIcPNoh56dhLDqNw=",
"dev": true,
"requires": {
"is-arrayish": "^0.2.1"
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"es-abstract": {
Update npm packages
2021-10-17 18:33:19 +09:00
"version": "1.19.1",
"resolved": "https://registry.npmjs.org/es-abstract/-/es-abstract-1.19.1.tgz",
"integrity": "sha512-2vJ6tjA/UfqLm2MPs7jxVybLoB8i1t1Jd9R3kISld20sIxPcTbLuggQOUxeWeAvIUkduv/CfMjuh4WmiXr2v9w==",
Update npm packages
2021-05-16 17:05:58 +09:00
"dev": true,
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"requires": {
Update npm packages
2021-05-16 17:05:58 +09:00
"call-bind": "^1.0.2",
Update `npm` packages
2019-12-19 19:28:13 +09:00
"es-to-primitive": "^1.2.1",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"function-bind": "^1.1.1",
Update npm packages
2021-05-16 17:05:58 +09:00
"get-intrinsic": "^1.1.1",
Update npm packages
2021-10-17 18:33:19 +09:00
"get-symbol-description": "^1.0.0",
Update packages
2019-01-05 22:27:47 +09:00
"has": "^1.0.3",
Update npm packages
2021-05-16 17:05:58 +09:00
"has-symbols": "^1.0.2",
Update npm packages
2021-08-22 17:38:52 +09:00
"internal-slot": "^1.0.3",
Update npm packages
2021-10-17 18:33:19 +09:00
"is-callable": "^1.2.4",
Update npm packages
2021-05-16 17:05:58 +09:00
"is-negative-zero": "^2.0.1",
Update npm packages
2021-10-17 18:33:19 +09:00
"is-regex": "^1.1.4",
"is-shared-array-buffer": "^1.0.1",
"is-string": "^1.0.7",
"is-weakref": "^1.0.1",
Update npm packages
2021-08-22 17:38:52 +09:00
"object-inspect": "^1.11.0",
Update `npm` packages
2019-12-19 19:28:13 +09:00
"object-keys": "^1.1.1",
Update npm packages
2021-05-16 17:05:58 +09:00
"object.assign": "^4.1.2",
"string.prototype.trimend": "^1.0.4",
"string.prototype.trimstart": "^1.0.4",
Update npm packages
2021-05-30 14:43:13 +09:00
"unbox-primitive": "^1.0.1"
Update packages
2019-01-05 22:27:47 +09:00
},
"dependencies": {
Update `npm` packages
2020-10-04 20:49:28 +09:00
"define-properties": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.1.3.tgz",
"integrity": "sha512-3MqfYKj2lLzdMSf8ZIZE/V+Zuy+BgD6f164e8K2w7dgnpKArBDerGYpM46IYYcjnkdPNMjPk9A6VFB8+3SKlXQ==",
Update npm packages
2021-05-16 17:05:58 +09:00
"dev": true,
Update `npm` packages
2020-10-04 20:49:28 +09:00
"requires": {
"object-keys": "^1.0.12"
}
},
Update `npm` packages
2019-12-19 19:28:13 +09:00
"has-symbols": {
Update npm packages
2021-05-16 17:05:58 +09:00
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.2.tgz",
"integrity": "sha512-chXa79rL/UC2KlX17jo3vRGz0azaWEx5tGqZg5pO3NUyEJVB17dMruQlzCCOfUvElghKcm5194+BCRvi2Rv/Gw==",
"dev": true
Update `npm` packages
2019-12-19 19:28:13 +09:00
},
Update packages
2019-01-05 22:27:47 +09:00
"object-keys": {
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz",
Update npm packages
2021-05-16 17:05:58 +09:00
"integrity": "sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==",
"dev": true
Update `npm` packages
2020-10-04 20:49:28 +09:00
},
"object.assign": {
Update npm packages
2021-05-16 17:05:58 +09:00
"version": "4.1.2",
"resolved": "https://registry.npmjs.org/object.assign/-/object.assign-4.1.2.tgz",
"integrity": "sha512-ixT2L5THXsApyiUPYKmW+2EHpXXe5Ii3M+f4e+aJFAHao5amFRW6J0OO6c/LU8Be47utCx2GL89hxGB6XSmKuQ==",
"dev": true,
Update `npm` packages
2020-10-04 20:49:28 +09:00
"requires": {
Update npm packages
2021-05-16 17:05:58 +09:00
"call-bind": "^1.0.0",
Update `npm` packages
2020-10-04 20:49:28 +09:00
"define-properties": "^1.1.3",
"has-symbols": "^1.0.1",
"object-keys": "^1.1.1"
}
Update packages
2019-01-05 22:27:47 +09:00
}
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
},
Update `npm` packages
2021-01-24 16:34:00 +09:00
"es-module-lexer": {
Update npm packages
2021-10-17 18:33:19 +09:00
"version": "0.9.3",
"resolved": "https://registry.npmjs.org/es-module-lexer/-/es-module-lexer-0.9.3.tgz",
"integrity": "sha512-1HQ2M2sPtxwnvOvT1ZClHyQDiggdNjURWpY2we6aMKCQiUVxTmVs2UYPLIrD84sS+kMdUwfBSylbJPwNnBrnHQ==",
Update `npm` packages
2021-01-24 16:34:00 +09:00
"dev": true
},
Reduce usage of SystemJS, in the development viewer, even further With these changes SystemJS is now only used, during development, on the worker-thread and in the unit/font-tests, since Firefox is currently missing support for worker modules; please see https://bugzilla.mozilla.org/show_bug.cgi?id=1247687 Hence all the JavaScript files in the `web/` and `src/display/` folders are now loaded *natively* by the browser (during development) using standard `import` statements/calls, thanks to a nice `import-maps` polyfill. *Please note:* As soon as https://bugzilla.mozilla.org/show_bug.cgi?id=1247687 is fixed in Firefox, we should be able to remove all traces of SystemJS and thus finally be able to use every possible modern JavaScript feature.
2020-05-20 01:00:23 +09:00
"es-module-shims": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "1.4.6",
"resolved": "https://registry.npmjs.org/es-module-shims/-/es-module-shims-1.4.6.tgz",
"integrity": "sha512-uXuuv+98O227v1pD8HPAeG0ggqyDj6JnRcMBp+A6K7/pTgbdwyNGH4eOk9L9xifZoNbsXZ8Z2y1J9fKjr1v4KQ==",
Update npm packages
2021-10-17 18:33:19 +09:00
"dev": true
Reduce usage of SystemJS, in the development viewer, even further With these changes SystemJS is now only used, during development, on the worker-thread and in the unit/font-tests, since Firefox is currently missing support for worker modules; please see https://bugzilla.mozilla.org/show_bug.cgi?id=1247687 Hence all the JavaScript files in the `web/` and `src/display/` folders are now loaded *natively* by the browser (during development) using standard `import` statements/calls, thanks to a nice `import-maps` polyfill. *Please note:* As soon as https://bugzilla.mozilla.org/show_bug.cgi?id=1247687 is fixed in Firefox, we should be able to remove all traces of SystemJS and thus finally be able to use every possible modern JavaScript feature.
2020-05-20 01:00:23 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"es-to-primitive": {
Update `npm` packages
2019-12-19 19:28:13 +09:00
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/es-to-primitive/-/es-to-primitive-1.2.1.tgz",
"integrity": "sha512-QCOllgZJtaUo9miYBcLChTUaHNjJF3PYs1VidD7AwiEj1kYxKeQTctLAezAOH5ZKRH0g2IgPn6KwB4IT8iRpvA==",
Update npm packages
2021-05-16 17:05:58 +09:00
"dev": true,
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"requires": {
"is-callable": "^1.1.4",
"is-date-object": "^1.0.1",
"is-symbol": "^1.0.2"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"es5-ext": {
"version": "0.10.44",
"resolved": "https://registry.npmjs.org/es5-ext/-/es5-ext-0.10.44.tgz",
"integrity": "sha512-TO4Vt9IhW3FzDKLDOpoA8VS9BCV4b9WTf6BqvMOgfoa8wX73F3Kh3y2J7yTstTaXlQ0k1vq4DH2vw6RSs42z+g==",
"dev": true,
"requires": {
"es6-iterator": "~2.0.3",
"es6-symbol": "~3.1.1",
"next-tick": "1"
}
},
"es6-iterator": {
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/es6-iterator/-/es6-iterator-2.0.3.tgz",
"integrity": "sha1-p96IkUGgWpSwhUQDstCg+/qY87c=",
"dev": true,
"requires": {
"d": "1",
"es5-ext": "^0.10.35",
"es6-symbol": "^3.1.1"
}
},
"es6-symbol": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/es6-symbol/-/es6-symbol-3.1.1.tgz",
"integrity": "sha1-vwDvT9q2uhtG7Le2KbTH7VcVzHc=",
"dev": true,
"requires": {
"d": "1",
"es5-ext": "~0.10.14"
}
},
"es6-weak-map": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/es6-weak-map/-/es6-weak-map-2.0.2.tgz",
"integrity": "sha1-XjqzIlH/0VOKH45f+hNXdy+S2W8=",
"dev": true,
"requires": {
"d": "1",
"es5-ext": "^0.10.14",
"es6-iterator": "^2.0.1",
"es6-symbol": "^3.1.1"
}
},
Update `npm` packages
2020-06-27 18:30:30 +09:00
"escalade": {
Update `npm` packages
2020-11-29 17:43:20 +09:00
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/escalade/-/escalade-3.1.1.tgz",
"integrity": "sha512-k0er2gUkLf8O0zKJiAhmkTnJlTvINGv7ygDNPbeIsX/TJjGJZHuh9B2UxbsaEkmlEo9MfhrSzmhIlhRlI2GXnw==",
Update `npm` packages
2020-06-27 18:30:30 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"escape-string-regexp": {
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz",
"integrity": "sha1-G2HAViGQqN/2rjuyzwIAyhMLhtQ=",
"dev": true
},
"eslint": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "8.9.0",
"resolved": "https://registry.npmjs.org/eslint/-/eslint-8.9.0.tgz",
"integrity": "sha512-PB09IGwv4F4b0/atrbcMFboF/giawbBLVC7fyDamk5Wtey4Jh2K+rYaBhCAbUyEI4QzB1ly09Uglc9iCtFaG2Q==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-02-20 18:08:23 +09:00
"@eslint/eslintrc": "^1.1.0",
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"@humanwhocodes/config-array": "^0.9.2",
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
"ajv": "^6.10.0",
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"chalk": "^4.0.0",
"cross-spawn": "^7.0.2",
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"debug": "^4.3.2",
Update packages
2019-02-18 00:44:36 +09:00
"doctrine": "^3.0.0",
Update npm packages
2021-05-30 14:43:13 +09:00
"escape-string-regexp": "^4.0.0",
Update npm packages
2022-02-20 18:08:23 +09:00
"eslint-scope": "^7.1.1",
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"eslint-utils": "^3.0.0",
Update npm packages
2022-02-20 18:08:23 +09:00
"eslint-visitor-keys": "^3.3.0",
"espree": "^9.3.1",
Update `npm` packages
2021-02-21 19:52:55 +09:00
"esquery": "^1.4.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"esutils": "^2.0.2",
Update npm packages
2021-05-30 14:43:13 +09:00
"fast-deep-equal": "^3.1.3",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"file-entry-cache": "^6.0.1",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"functional-red-black-tree": "^1.0.1",
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"glob-parent": "^6.0.1",
Update `npm` packages
2021-03-21 19:00:02 +09:00
"globals": "^13.6.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"ignore": "^5.2.0",
Update packages
2019-01-05 22:27:47 +09:00
"import-fresh": "^3.0.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"imurmurhash": "^0.1.4",
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
"is-glob": "^4.0.0",
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"js-yaml": "^4.1.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"json-stable-stringify-without-jsonify": "^1.0.1",
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"levn": "^0.4.1",
Update npm packages
2021-05-30 14:43:13 +09:00
"lodash.merge": "^4.6.2",
Update the various ESLint packages to their latest versions
2018-07-09 19:52:55 +09:00
"minimatch": "^3.0.4",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"natural-compare": "^1.4.0",
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"optionator": "^0.9.1",
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"regexpp": "^3.2.0",
Update npm packages
2021-11-14 18:17:30 +09:00
"strip-ansi": "^6.0.1",
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"strip-json-comments": "^3.1.0",
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
"text-table": "^0.2.0",
"v8-compile-cache": "^2.0.3"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"ansi-regex": {
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
"integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
"dev": true
Update `npm` packages
2021-02-21 19:52:55 +09:00
},
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"ansi-styles": {
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz",
"integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==",
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"dev": true,
"requires": {
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"color-convert": "^2.0.1"
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
}
},
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"argparse": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/argparse/-/argparse-2.0.1.tgz",
"integrity": "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==",
Update `npm` packages
2021-02-21 19:52:55 +09:00
"dev": true
},
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"chalk": {
Update npm packages
2021-08-08 17:45:36 +09:00
"version": "4.1.2",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz",
"integrity": "sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==",
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"dev": true,
"requires": {
"ansi-styles": "^4.1.0",
"supports-color": "^7.1.0"
}
},
"color-convert": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz",
"integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==",
"dev": true,
"requires": {
"color-name": "~1.1.4"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"debug": {
Update npm packages
2021-11-28 18:40:29 +09:00
"version": "4.3.3",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.3.tgz",
"integrity": "sha512-/zxw5+vh1Tfv+4Qn7a5nsbcJKPaSvCDhojn6FEl9vupwK2VCSDtEiEtqr8DFtzYFOdz63LBkxec7DYuc2jon6Q==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-09-20 18:34:24 +09:00
"ms": "2.1.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update npm packages
2021-05-30 14:43:13 +09:00
"escape-string-regexp": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-4.0.0.tgz",
"integrity": "sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA==",
"dev": true
},
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"eslint-scope": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "7.1.1",
"resolved": "https://registry.npmjs.org/eslint-scope/-/eslint-scope-7.1.1.tgz",
"integrity": "sha512-QKQM/UXpIiHcLqJ5AOyIW7XZmzjkzQXYE54n1++wb0u9V/abW3l9uQnxX8Z5Xd18xyKIMTUAyQ0k1e8pz6LUrw==",
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"dev": true,
"requires": {
"esrecurse": "^4.3.0",
"estraverse": "^5.2.0"
}
},
"eslint-visitor-keys": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-3.3.0.tgz",
"integrity": "sha512-mQ+suqKJVyeuwGYHAdjMFqjCyfl8+Ldnxuyp3ldiMBFKkvytrXUZWaiPCEav8qDHKty44bD+qV1IP4T+w+xXRA==",
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"dev": true
},
"estraverse": {
Update npm packages
2021-10-31 17:38:18 +09:00
"version": "5.3.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz",
"integrity": "sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==",
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"dev": true
},
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
"glob-parent": {
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"version": "6.0.2",
"resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-6.0.2.tgz",
"integrity": "sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==",
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
"dev": true,
"requires": {
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"is-glob": "^4.0.3"
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
}
},
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"has-flag": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz",
"integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==",
"dev": true
},
Update npm packages
2022-01-23 18:58:15 +09:00
"ignore": {
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/ignore/-/ignore-5.2.0.tgz",
"integrity": "sha512-CmxgYGiEPCLhfLnpPp1MoRmifwEIOgjcHXxOBjv7mY96c+eWScsOP9c112ZyLdWHi0FxHjI+4uVhKYp/gcdRmQ==",
"dev": true
},
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
"is-glob": {
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"version": "4.0.3",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz",
"integrity": "sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==",
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
"dev": true,
"requires": {
"is-extglob": "^2.1.1"
}
},
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"js-yaml": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.0.tgz",
"integrity": "sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==",
"dev": true,
"requires": {
"argparse": "^2.0.1"
}
},
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"levn": {
"version": "0.4.1",
"resolved": "https://registry.npmjs.org/levn/-/levn-0.4.1.tgz",
"integrity": "sha512-+bT2uH4E5LGE7h/n3evcS/sQlJXCpIp6ym8OWJ5eV6+67Dsql/LaaT7qJBAt2rzfoa/5QBGBhxDix1dMt2kQKQ==",
Update the `mkdirp` package, since its major version was increased
2020-04-02 19:18:23 +09:00
"dev": true,
"requires": {
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"prelude-ls": "^1.2.1",
"type-check": "~0.4.0"
Update the `mkdirp` package, since its major version was increased
2020-04-02 19:18:23 +09:00
}
},
Update packages
2018-09-21 22:16:30 +09:00
"ms": {
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
Update packages
2018-09-21 22:16:30 +09:00
"dev": true
},
Update `npm` packages
2019-11-23 19:25:24 +09:00
"optionator": {
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"version": "0.9.1",
"resolved": "https://registry.npmjs.org/optionator/-/optionator-0.9.1.tgz",
"integrity": "sha512-74RlY5FCnhq4jRxVUPKDaRwrVNXMqsGsiW6AJw4XK8hmtm10wC0ypZBLw5IIp85NZMr91+qd1RvvENwg7jjRFw==",
Update `npm` packages
2019-11-23 19:25:24 +09:00
"dev": true,
"requires": {
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"deep-is": "^0.1.3",
"fast-levenshtein": "^2.0.6",
"levn": "^0.4.1",
"prelude-ls": "^1.2.1",
"type-check": "^0.4.0",
"word-wrap": "^1.2.3"
Update `npm` packages
2019-11-23 19:25:24 +09:00
}
},
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"prelude-ls": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.2.1.tgz",
"integrity": "sha512-vkcDPrRZo1QZLbn5RLGPpg/WmIQ65qoWWhcGKf/b5eplkkarX0m9z8ppCat4mlOqUsWpyNuYgO3VRyrYHSzX5g==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"strip-ansi": {
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"version": "6.0.1",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
"integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
"dev": true,
"requires": {
"ansi-regex": "^5.0.1"
}
},
"supports-color": {
"version": "7.2.0",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-7.2.0.tgz",
"integrity": "sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"has-flag": "^4.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
},
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"type-check": {
"version": "0.4.0",
"resolved": "https://registry.npmjs.org/type-check/-/type-check-0.4.0.tgz",
"integrity": "sha512-XleUoc9uwGXqjWwXaUTZAmzMcFZ5858QA2vvx1Ur5xIcixXIP+8LnFDgRplU30us6teqdlskFfu+ae4K79Ooew==",
"dev": true,
"requires": {
"prelude-ls": "^1.2.1"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
},
Update the `eslint-plugin-mozilla` to the latest version (PR 10905 follow-up) This required adding a number of additional dependencies, based on https://dxr.mozilla.org/mozilla-central/rev/4aed8e10318f38571712350856bf9e61c5f84e1f/tools/lint/eslint/eslint-plugin-mozilla/package.json#32-37 Since this, implicitly, enabled "prettier"[1] for the `extensions/firefox` directory a couple of small code changes were necessary as well. --- [1] Generally speaking I'm wondering if that name is deliberately ironic, since the style it enforces is often times extremely weird and ugly :-P
2019-09-07 19:37:13 +09:00
"eslint-config-prettier": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "8.4.0",
"resolved": "https://registry.npmjs.org/eslint-config-prettier/-/eslint-config-prettier-8.4.0.tgz",
"integrity": "sha512-CFotdUcMY18nGRo5KGsnNxpznzhkopOcOo0InID+sgQssPrzjvsyKZPvOgymTFeHrFuC3Tzdf2YndhXtULK9Iw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"requires": {}
Update the `eslint-plugin-mozilla` to the latest version (PR 10905 follow-up) This required adding a number of additional dependencies, based on https://dxr.mozilla.org/mozilla-central/rev/4aed8e10318f38571712350856bf9e61c5f84e1f/tools/lint/eslint/eslint-plugin-mozilla/package.json#32-37 Since this, implicitly, enabled "prettier"[1] for the `extensions/firefox` directory a couple of small code changes were necessary as well. --- [1] Generally speaking I'm wondering if that name is deliberately ironic, since the style it enforces is often times extremely weird and ugly :-P
2019-09-07 19:37:13 +09:00
},
Enable eslint-plugin-import to prevent unresolved paths
2018-11-23 21:50:28 +09:00
"eslint-import-resolver-node": {
Update npm packages
2021-08-22 17:38:52 +09:00
"version": "0.3.6",
"resolved": "https://registry.npmjs.org/eslint-import-resolver-node/-/eslint-import-resolver-node-0.3.6.tgz",
"integrity": "sha512-0En0w03NRVMn9Uiyn8YRPDKvWjxCWkslUEhGNTdGx15RvPJYQ+lbOlqrlNI2vEAs4pDYK4f/HN2TbDmk5TP0iw==",
Enable eslint-plugin-import to prevent unresolved paths
2018-11-23 21:50:28 +09:00
"dev": true,
"requires": {
Update npm packages
2021-08-22 17:38:52 +09:00
"debug": "^3.2.7",
"resolve": "^1.20.0"
Update `npm` packages
2020-01-31 22:04:49 +09:00
},
"dependencies": {
Update npm packages
2021-08-22 17:38:52 +09:00
"debug": {
"version": "3.2.7",
"resolved": "https://registry.npmjs.org/debug/-/debug-3.2.7.tgz",
"integrity": "sha512-CFjzYYAi4ThfiQvizrFQevTTXHtnCqWfe7x1AhgEscTz6ZbLbfoLRLPugTQyBth6f8ZERVUSyWHFD/7Wu4t1XQ==",
"dev": true,
"requires": {
"ms": "^2.1.1"
}
},
"ms": {
"version": "2.1.3",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.3.tgz",
"integrity": "sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==",
"dev": true
},
Update `npm` packages
2020-01-31 22:04:49 +09:00
"resolve": {
Update npm packages
2021-05-16 17:05:58 +09:00
"version": "1.20.0",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.20.0.tgz",
"integrity": "sha512-wENBPt4ySzg4ybFQW2TT1zMQucPK95HSh/nq2CFTZVOGut2+pQvSsgtda4d26YrYcr067wjbmzOG8byDPBX63A==",
Update `npm` packages
2020-01-31 22:04:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-16 17:05:58 +09:00
"is-core-module": "^2.2.0",
Update `npm` packages
2020-01-31 22:04:49 +09:00
"path-parse": "^1.0.6"
}
}
Enable eslint-plugin-import to prevent unresolved paths
2018-11-23 21:50:28 +09:00
}
},
"eslint-module-utils": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "2.7.2",
"resolved": "https://registry.npmjs.org/eslint-module-utils/-/eslint-module-utils-2.7.2.tgz",
"integrity": "sha512-zquepFnWCY2ISMFwD/DqzaM++H+7PDzOpUvotJWm/y1BAFt5R4oeULgdrTejKqLkz7MA/tgstsUMNYc7wNdTrg==",
Enable eslint-plugin-import to prevent unresolved paths
2018-11-23 21:50:28 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-16 17:05:58 +09:00
"debug": "^3.2.7",
Update npm packages
2022-01-09 18:05:52 +09:00
"find-up": "^2.1.0"
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
},
"dependencies": {
Update npm packages
2021-05-16 17:05:58 +09:00
"debug": {
"version": "3.2.7",
"resolved": "https://registry.npmjs.org/debug/-/debug-3.2.7.tgz",
"integrity": "sha512-CFjzYYAi4ThfiQvizrFQevTTXHtnCqWfe7x1AhgEscTz6ZbLbfoLRLPugTQyBth6f8ZERVUSyWHFD/7Wu4t1XQ==",
"dev": true,
"requires": {
"ms": "^2.1.1"
}
},
"ms": {
"version": "2.1.3",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.3.tgz",
"integrity": "sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==",
"dev": true
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
}
Enable eslint-plugin-import to prevent unresolved paths
2018-11-23 21:50:28 +09:00
}
},
Update the `eslint-plugin-mozilla` to the latest version (PR 10905 follow-up) This required adding a number of additional dependencies, based on https://dxr.mozilla.org/mozilla-central/rev/4aed8e10318f38571712350856bf9e61c5f84e1f/tools/lint/eslint/eslint-plugin-mozilla/package.json#32-37 Since this, implicitly, enabled "prettier"[1] for the `extensions/firefox` directory a couple of small code changes were necessary as well. --- [1] Generally speaking I'm wondering if that name is deliberately ironic, since the style it enforces is often times extremely weird and ugly :-P
2019-09-07 19:37:13 +09:00
"eslint-plugin-fetch-options": {
"version": "0.0.5",
"resolved": "https://registry.npmjs.org/eslint-plugin-fetch-options/-/eslint-plugin-fetch-options-0.0.5.tgz",
"integrity": "sha512-ZMxrccsOAZ7uMQ4nMvPJLqLg6oyLF96YOEwTKWAIbDHpwWUp1raXALZom8ikKucaEnhqWSRuBWI8jBXveFwkJg==",
"dev": true
},
"eslint-plugin-html": {
Update npm packages
2021-10-03 15:21:01 +09:00
"version": "6.2.0",
"resolved": "https://registry.npmjs.org/eslint-plugin-html/-/eslint-plugin-html-6.2.0.tgz",
"integrity": "sha512-vi3NW0E8AJombTvt8beMwkL1R/fdRWl4QSNRNMhVQKWm36/X0KF0unGNAY4mqUF06mnwVWZcIcerrCnfn9025g==",
Update the `eslint-plugin-mozilla` to the latest version (PR 10905 follow-up) This required adding a number of additional dependencies, based on https://dxr.mozilla.org/mozilla-central/rev/4aed8e10318f38571712350856bf9e61c5f84e1f/tools/lint/eslint/eslint-plugin-mozilla/package.json#32-37 Since this, implicitly, enabled "prettier"[1] for the `extensions/firefox` directory a couple of small code changes were necessary as well. --- [1] Generally speaking I'm wondering if that name is deliberately ironic, since the style it enforces is often times extremely weird and ugly :-P
2019-09-07 19:37:13 +09:00
"dev": true,
"requires": {
Update npm packages
2021-10-03 15:21:01 +09:00
"htmlparser2": "^7.1.2"
Update the `eslint-plugin-mozilla` to the latest version (PR 10905 follow-up) This required adding a number of additional dependencies, based on https://dxr.mozilla.org/mozilla-central/rev/4aed8e10318f38571712350856bf9e61c5f84e1f/tools/lint/eslint/eslint-plugin-mozilla/package.json#32-37 Since this, implicitly, enabled "prettier"[1] for the `extensions/firefox` directory a couple of small code changes were necessary as well. --- [1] Generally speaking I'm wondering if that name is deliberately ironic, since the style it enforces is often times extremely weird and ugly :-P
2019-09-07 19:37:13 +09:00
}
},
Enable eslint-plugin-import to prevent unresolved paths
2018-11-23 21:50:28 +09:00
"eslint-plugin-import": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "2.25.4",
"resolved": "https://registry.npmjs.org/eslint-plugin-import/-/eslint-plugin-import-2.25.4.tgz",
"integrity": "sha512-/KJBASVFxpu0xg1kIBn9AUa8hQVnszpwgE7Ld0lKAlx7Ie87yzEzCgSkekt+le/YVhiaosO4Y14GDAOc41nfxA==",
Enable eslint-plugin-import to prevent unresolved paths
2018-11-23 21:50:28 +09:00
"dev": true,
"requires": {
Update npm packages
2021-10-17 18:33:19 +09:00
"array-includes": "^3.1.4",
"array.prototype.flat": "^1.2.5",
Update packages
2019-02-18 00:44:36 +09:00
"debug": "^2.6.9",
Update npm packages
2021-05-16 17:05:58 +09:00
"doctrine": "^2.1.0",
Update npm packages
2021-08-22 17:38:52 +09:00
"eslint-import-resolver-node": "^0.3.6",
Update npm packages
2022-01-09 18:05:52 +09:00
"eslint-module-utils": "^2.7.2",
Update packages
2019-02-18 00:44:36 +09:00
"has": "^1.0.3",
Update npm packages
2021-11-14 18:17:30 +09:00
"is-core-module": "^2.8.0",
Update npm packages
2021-10-17 18:33:19 +09:00
"is-glob": "^4.0.3",
Update packages
2019-02-18 00:44:36 +09:00
"minimatch": "^3.0.4",
Update npm packages
2021-10-17 18:33:19 +09:00
"object.values": "^1.1.5",
Update npm packages
2021-05-16 17:05:58 +09:00
"resolve": "^1.20.0",
Update npm packages
2022-01-09 18:05:52 +09:00
"tsconfig-paths": "^3.12.0"
Enable eslint-plugin-import to prevent unresolved paths
2018-11-23 21:50:28 +09:00
},
"dependencies": {
"doctrine": {
Update npm packages
2021-05-16 17:05:58 +09:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/doctrine/-/doctrine-2.1.0.tgz",
"integrity": "sha512-35mSku4ZXK0vfCuHEDAwt55dg2jNajHZ1odvF+8SSr82EsZY4QmXfuWso8oEd8zRhVObSN18aM0CjSdoBX7zIw==",
Enable eslint-plugin-import to prevent unresolved paths
2018-11-23 21:50:28 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-16 17:05:58 +09:00
"esutils": "^2.0.2"
}
},
"is-core-module": {
Update npm packages
2021-10-17 18:33:19 +09:00
"version": "2.8.0",
"resolved": "https://registry.npmjs.org/is-core-module/-/is-core-module-2.8.0.tgz",
"integrity": "sha512-vd15qHsaqrRL7dtH6QNuy0ndJmRDrS9HAM1CAiSifNUFv4x1a0CCVsj18hJ1mShxIG6T2i1sO78MkP56r0nYRw==",
Update npm packages
2021-05-16 17:05:58 +09:00
"dev": true,
"requires": {
"has": "^1.0.3"
Enable eslint-plugin-import to prevent unresolved paths
2018-11-23 21:50:28 +09:00
}
Update packages
2019-02-18 00:44:36 +09:00
},
Update npm packages
2021-10-17 18:33:19 +09:00
"is-glob": {
"version": "4.0.3",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz",
"integrity": "sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==",
"dev": true,
"requires": {
"is-extglob": "^2.1.1"
}
},
Update packages
2019-02-18 00:44:36 +09:00
"resolve": {
Update npm packages
2021-05-16 17:05:58 +09:00
"version": "1.20.0",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.20.0.tgz",
"integrity": "sha512-wENBPt4ySzg4ybFQW2TT1zMQucPK95HSh/nq2CFTZVOGut2+pQvSsgtda4d26YrYcr067wjbmzOG8byDPBX63A==",
Update packages
2019-02-18 00:44:36 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-16 17:05:58 +09:00
"is-core-module": "^2.2.0",
Update packages
2019-02-18 00:44:36 +09:00
"path-parse": "^1.0.6"
}
Enable eslint-plugin-import to prevent unresolved paths
2018-11-23 21:50:28 +09:00
}
}
},
Add basic linting of JSON files using `eslint-plugin-json` By adding basic linting of JSON files, we can ensure that they're actually valid and prevent e.g. test-failures caused by *accidental* errors when editing the `test/test_manifest.json` file (something that I've done *many* times myself). For now this simply uses the `recommended` configuration, but we can obviously tweak this later if/when needed. Please find additional information at https://github.com/azeemba/eslint-plugin-json
2021-06-15 18:59:47 +09:00
"eslint-plugin-json": {
Update npm packages
2021-08-08 17:45:36 +09:00
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/eslint-plugin-json/-/eslint-plugin-json-3.1.0.tgz",
"integrity": "sha512-MrlG2ynFEHe7wDGwbUuFPsaT2b1uhuEFhJ+W1f1u+1C2EkXmTYJp4B1aAdQQ8M+CC3t//N/oRKiIVw14L2HR1g==",
Add basic linting of JSON files using `eslint-plugin-json` By adding basic linting of JSON files, we can ensure that they're actually valid and prevent e.g. test-failures caused by *accidental* errors when editing the `test/test_manifest.json` file (something that I've done *many* times myself). For now this simply uses the `recommended` configuration, but we can obviously tweak this later if/when needed. Please find additional information at https://github.com/azeemba/eslint-plugin-json
2021-06-15 18:59:47 +09:00
"dev": true,
"requires": {
"lodash": "^4.17.21",
Update npm packages
2021-08-08 17:45:36 +09:00
"vscode-json-languageservice": "^4.1.6"
Add basic linting of JSON files using `eslint-plugin-json` By adding basic linting of JSON files, we can ensure that they're actually valid and prevent e.g. test-failures caused by *accidental* errors when editing the `test/test_manifest.json` file (something that I've done *many* times myself). For now this simply uses the `recommended` configuration, but we can obviously tweak this later if/when needed. Please find additional information at https://github.com/azeemba/eslint-plugin-json
2021-06-15 18:59:47 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"eslint-plugin-mozilla": {
Update npm packages
2021-10-03 15:21:01 +09:00
"version": "2.11.1",
"resolved": "https://registry.npmjs.org/eslint-plugin-mozilla/-/eslint-plugin-mozilla-2.11.1.tgz",
"integrity": "sha512-4kd2+ABYvnUzYwCHJVwhwRGUPlJLXG7DKlOjA/wGeQF3A1j7KA/Oal6+tuFh4yhL7XiHcBsn8pvla0CuB3253g==",
Update `npm` packages
2021-04-18 18:02:42 +09:00
"dev": true,
"requires": {
Update npm packages
2021-10-03 15:21:01 +09:00
"@babel/core": "^7.15.0",
"@babel/eslint-parser": "^7.15.0",
Update `npm` packages
2021-04-18 18:02:42 +09:00
"eslint-scope": "^5.1.1",
Update npm packages
2021-10-03 15:21:01 +09:00
"eslint-visitor-keys": "^2.1.0",
Update `npm` packages
2021-04-18 18:02:42 +09:00
"estraverse": "^4.3.0",
"htmlparser2": "^6.0.1",
"multi-ini": "^2.1.2",
"sax": "^1.2.4"
Update `npm` packages
2020-04-02 19:13:14 +09:00
},
"dependencies": {
Update npm packages
2021-10-03 15:21:01 +09:00
"entities": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/entities/-/entities-2.2.0.tgz",
"integrity": "sha512-p92if5Nz619I0w+akJrLZH0MX0Pb5DX39XOwQTtXSdQQOaYH03S1uIQp4mhOZtAXrxq4ViO67YTiLBo2638o9A==",
Update `npm` packages
2020-07-26 18:15:21 +09:00
"dev": true
},
Update `npm` packages
2020-04-02 19:13:14 +09:00
"estraverse": {
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-4.3.0.tgz",
"integrity": "sha512-39nnKffWz8xN1BU/2c79n9nB9HDzo0niYUqx6xyqUnyoAnQyyWpOTdZEeiCch8BBu515t4wp9ZmgVfVhn9EBpw==",
"dev": true
Update npm packages
2021-10-03 15:21:01 +09:00
},
"htmlparser2": {
"version": "6.1.0",
"resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-6.1.0.tgz",
"integrity": "sha512-gyyPk6rgonLFEDGoeRgQNaEUvdJ4ktTmmUh/h2t7s+M8oPpIPxgNACWa+6ESR57kXstwqPiCut0V8NRpcwgU7A==",
"dev": true,
"requires": {
"domelementtype": "^2.0.1",
"domhandler": "^4.0.0",
"domutils": "^2.5.2",
"entities": "^2.0.0"
}
Update `npm` packages
2020-04-02 19:13:14 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"eslint-plugin-no-unsanitized": {
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/eslint-plugin-no-unsanitized/-/eslint-plugin-no-unsanitized-4.0.1.tgz",
"integrity": "sha512-y/lAMWnPPC7RYuUdxlEL/XiCL8FehN9h9s3Kjqbp/Kv0i9NZs+IXSC2kS546Fa4Bumwy31HlVS/OdWX0Kxb5Xg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"requires": {}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update the `eslint-plugin-mozilla` to the latest version (PR 10905 follow-up) This required adding a number of additional dependencies, based on https://dxr.mozilla.org/mozilla-central/rev/4aed8e10318f38571712350856bf9e61c5f84e1f/tools/lint/eslint/eslint-plugin-mozilla/package.json#32-37 Since this, implicitly, enabled "prettier"[1] for the `extensions/firefox` directory a couple of small code changes were necessary as well. --- [1] Generally speaking I'm wondering if that name is deliberately ironic, since the style it enforces is often times extremely weird and ugly :-P
2019-09-07 19:37:13 +09:00
"eslint-plugin-prettier": {
Update the `eslint-plugin-prettier` package to the latest version Please refer to https://github.com/prettier/eslint-plugin-prettier/blob/master/CHANGELOG.md#v400-2021-08-30
2021-09-05 16:54:18 +09:00
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/eslint-plugin-prettier/-/eslint-plugin-prettier-4.0.0.tgz",
"integrity": "sha512-98MqmCJ7vJodoQK359bqQWaxOE0CS8paAz/GgjaZLyex4TTk3g9HugoO89EqWCrFiOqn9EVvcoo7gZzONCWVwQ==",
Update the `eslint-plugin-mozilla` to the latest version (PR 10905 follow-up) This required adding a number of additional dependencies, based on https://dxr.mozilla.org/mozilla-central/rev/4aed8e10318f38571712350856bf9e61c5f84e1f/tools/lint/eslint/eslint-plugin-mozilla/package.json#32-37 Since this, implicitly, enabled "prettier"[1] for the `extensions/firefox` directory a couple of small code changes were necessary as well. --- [1] Generally speaking I'm wondering if that name is deliberately ironic, since the style it enforces is often times extremely weird and ugly :-P
2019-09-07 19:37:13 +09:00
"dev": true,
"requires": {
"prettier-linter-helpers": "^1.0.0"
}
},
Use ESLint to ensure that `export`s are sorted alphabetically There's built-in ESLint rule, see `sort-imports`, to ensure that all `import`-statements are sorted alphabetically, since that often helps with readability. Unfortunately there's no corresponding rule to sort `export`-statements alphabetically, however there's an ESLint plugin which does this; please see https://www.npmjs.com/package/eslint-plugin-sort-exports The only downside here is that it's not automatically fixable, but the re-ordering is a one-time "cost" and the plugin will help maintain a *consistent* ordering of `export`-statements in the future. *Note:* To reduce the possibility of introducing any errors here, the re-ordering was done by simply selecting the relevant lines and then using the built-in sort-functionality of my editor.
2021-01-09 23:37:44 +09:00
"eslint-plugin-sort-exports": {
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"version": "0.6.0",
"resolved": "https://registry.npmjs.org/eslint-plugin-sort-exports/-/eslint-plugin-sort-exports-0.6.0.tgz",
"integrity": "sha512-NMFUDPL6jVkTiGR698sv6nNEM/cA7CzSJaeIDdBnzkyj8ZYe7eFvcaxLSSSSouikQaxZQukVd74CIQ2sggbrtg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"requires": {}
Use ESLint to ensure that `export`s are sorted alphabetically There's built-in ESLint rule, see `sort-imports`, to ensure that all `import`-statements are sorted alphabetically, since that often helps with readability. Unfortunately there's no corresponding rule to sort `export`-statements alphabetically, however there's an ESLint plugin which does this; please see https://www.npmjs.com/package/eslint-plugin-sort-exports The only downside here is that it's not automatically fixable, but the re-ordering is a one-time "cost" and the plugin will help maintain a *consistent* ordering of `export`-statements in the future. *Note:* To reduce the possibility of introducing any errors here, the re-ordering was done by simply selecting the relevant lines and then using the built-in sort-functionality of my editor.
2021-01-09 23:37:44 +09:00
},
Replace the remaining occurences of `instanceof Array` with `Array.isArray()` *Follow-up to PRs 8864 and 8813.* As explained in https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/isArray, `instanceof Array` can have inconsistent behavior. To ensure that only `Array.isArray` is used, an ESLint plugin/rule is added to enforce this.
2018-07-09 20:11:35 +09:00
"eslint-plugin-unicorn": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "41.0.0",
"resolved": "https://registry.npmjs.org/eslint-plugin-unicorn/-/eslint-plugin-unicorn-41.0.0.tgz",
"integrity": "sha512-xoJCaRc1uy5REg9DkVga1BkZV57jJxoqOcrU28QHZB89Lk5LdSqdVyTIt9JQVfHNKaiyJ7X+3iLlIn+VEHWEzA==",
Replace the remaining occurences of `instanceof Array` with `Array.isArray()` *Follow-up to PRs 8864 and 8813.* As explained in https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/isArray, `instanceof Array` can have inconsistent behavior. To ensure that only `Array.isArray` is used, an ESLint plugin/rule is added to enforce this.
2018-07-09 20:11:35 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/helper-validator-identifier": "^7.15.7",
"ci-info": "^3.3.0",
Replace the remaining occurences of `instanceof Array` with `Array.isArray()` *Follow-up to PRs 8864 and 8813.* As explained in https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/isArray, `instanceof Array` can have inconsistent behavior. To ensure that only `Array.isArray` is used, an ESLint plugin/rule is added to enforce this.
2018-07-09 20:11:35 +09:00
"clean-regexp": "^1.0.0",
Update the `eslint-plugin-unicorn` package to the latest version
2021-06-13 17:03:08 +09:00
"eslint-utils": "^3.0.0",
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"esquery": "^1.4.0",
Update npm packages
2022-01-09 18:05:52 +09:00
"indent-string": "^4.0.0",
Update the `eslint-plugin-unicorn` package to the latest version
2021-05-02 16:31:44 +09:00
"is-builtin-module": "^3.1.0",
Update Puppeteer to version 9 (#13282) * Update Puppeteer to version 9 Hopefully the updated Chromium-version might help reduce the number of intermittent test failures. Please find additional information at https://github.com/puppeteer/puppeteer/releases/tag/v9.0.0 * Update the `eslint-plugin-sort-exports`/`eslint-plugin-unicorn"` packages to their latest versions Both of these ESLint plugins have increased their version numbers, however `npm update` doesn't handle this automatically. https://www.npmjs.com/package/eslint-plugin-sort-exports https://www.npmjs.com/package/eslint-plugin-unicorn
2021-04-22 18:35:16 +09:00
"lodash": "^4.17.21",
Update `npm` packages
2020-05-30 17:58:10 +09:00
"pluralize": "^8.0.0",
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"read-pkg-up": "^7.0.1",
Update npm packages
2022-01-09 18:05:52 +09:00
"regexp-tree": "^0.1.24",
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"safe-regex": "^2.1.1",
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"semver": "^7.3.5",
"strip-indent": "^3.0.0"
Update packages
2019-02-18 00:44:36 +09:00
},
"dependencies": {
Update the `eslint-plugin-unicorn` package to the latest version
2021-05-02 16:31:44 +09:00
"builtin-modules": {
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-3.2.0.tgz",
"integrity": "sha512-lGzLKcioL90C7wMczpkY0n/oART3MbBa8R9OFGE1rJxoVI86u4WAGfEk8Wjv10eKSyTHVGkSo3bvBylCEtk7LA==",
"dev": true
},
"is-builtin-module": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-3.1.0.tgz",
"integrity": "sha512-OV7JjAgOTfAFJmHZLvpSTb4qi0nIILDV1gWPYDnDJUTNFM5aGlRAhk4QcT8i7TuAleeEV5Fdkqn3t4mS+Q11fg==",
"dev": true,
"requires": {
"builtin-modules": "^3.0.0"
}
},
Update packages
2019-02-18 00:44:36 +09:00
"safe-regex": {
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/safe-regex/-/safe-regex-2.1.1.tgz",
"integrity": "sha512-rx+x8AMzKb5Q5lQ95Zoi6ZbJqwCLkqi3XuJXp5P3rT8OEc6sZCJG5AE5dU3lsgRr/F4Bs31jSlVN+j5KrsGu9A==",
Update packages
2019-02-18 00:44:36 +09:00
"dev": true,
"requires": {
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
"regexp-tree": "~0.1.1"
Update packages
2019-02-18 00:44:36 +09:00
}
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
},
"semver": {
Update `eslint-config-prettier`/`eslint-plugin-unicorn` packages to their latest versions Both of these ESLint "helpers" has increased their *major* version numbers, which `npm update` doesn't handle automatically (since that could cause errors), hence this patch which updates them manually. https://www.npmjs.com/package/eslint-config-prettier https://www.npmjs.com/package/eslint-plugin-unicorn
2021-04-14 19:39:19 +09:00
"version": "7.3.5",
"resolved": "https://registry.npmjs.org/semver/-/semver-7.3.5.tgz",
"integrity": "sha512-PoeGJYh8HK4BTO/a9Tf6ZG3veo/A7ZVsYrSA6J8ny9nb3B1VrpkuN+z9OE5wfE5p6H4LchYZsegiQgbJD94ZFQ==",
Update the `eslint-plugin-unicorn` package to the latest version Please see https://github.com/sindresorhus/eslint-plugin-unicorn/releases/tag/v25.0.0 for additional details.
2021-01-10 19:29:27 +09:00
"dev": true,
"requires": {
"lru-cache": "^6.0.0"
}
Update packages
2019-02-18 00:44:36 +09:00
}
Replace the remaining occurences of `instanceof Array` with `Array.isArray()` *Follow-up to PRs 8864 and 8813.* As explained in https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/isArray, `instanceof Array` can have inconsistent behavior. To ensure that only `Array.isArray` is used, an ESLint plugin/rule is added to enforce this.
2018-07-09 20:11:35 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"eslint-scope": {
Update `npm` packages
2020-11-29 17:43:20 +09:00
"version": "5.1.1",
"resolved": "https://registry.npmjs.org/eslint-scope/-/eslint-scope-5.1.1.tgz",
"integrity": "sha512-2NxwbF/hZ0KpepYN0cNbo+FN6XoK7GaHlQhgx/hIZl6Va0bF45RQOOwhLIy8lQDbuCiadSLCBnH2CFYquit5bw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-11-29 17:43:20 +09:00
"esrecurse": "^4.3.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"estraverse": "^4.1.1"
}
},
Update the various ESLint packages to their latest versions
2018-07-09 19:52:55 +09:00
"eslint-utils": {
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/eslint-utils/-/eslint-utils-3.0.0.tgz",
"integrity": "sha512-uuQC43IGctw68pJA1RgbQS8/NP7rch6Cwd4j3ZBtgo4/8Flj4eGE7ZYSZRN3iq5pVUv6GPdW5Z1RFleo84uLDA==",
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
"dev": true,
"requires": {
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"eslint-visitor-keys": "^2.0.0"
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
}
Update the various ESLint packages to their latest versions
2018-07-09 19:52:55 +09:00
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"eslint-visitor-keys": {
Update npm packages
2021-06-27 17:25:40 +09:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-2.1.0.tgz",
"integrity": "sha512-0rSmRBzXgDzIsD6mGdJgevzgezI534Cer5L/vyMX0kHzT/jiB43jRhd9YUlMGYLQy2zprNmoT8qasCGtY+QaKw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update `npm` packages
2020-10-18 17:57:52 +09:00
"espree": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "9.3.1",
"resolved": "https://registry.npmjs.org/espree/-/espree-9.3.1.tgz",
"integrity": "sha512-bvdyLmJMfwkV3NCRl5ZhJf22zBFo1y8bYh3VYb+bfzqNB4Je68P2sSuXyuFquzWLebHpNd2/d5uv7yoP9ISnGQ==",
Update `npm` packages
2020-10-18 17:57:52 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-09 18:05:52 +09:00
"acorn": "^8.7.0",
Update `npm` packages
2020-12-13 19:38:37 +09:00
"acorn-jsx": "^5.3.1",
Update npm packages
2022-02-20 18:08:23 +09:00
"eslint-visitor-keys": "^3.3.0"
Update `npm` packages
2020-10-18 17:57:52 +09:00
},
"dependencies": {
"eslint-visitor-keys": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-3.3.0.tgz",
"integrity": "sha512-mQ+suqKJVyeuwGYHAdjMFqjCyfl8+Ldnxuyp3ldiMBFKkvytrXUZWaiPCEav8qDHKty44bD+qV1IP4T+w+xXRA==",
Update `npm` packages
2020-10-18 17:57:52 +09:00
"dev": true
}
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"esprima": {
Update `npm` packages
2020-01-31 22:04:49 +09:00
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/esprima/-/esprima-4.0.1.tgz",
"integrity": "sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"esquery": {
Update `eslint-config-prettier`/`eslint-plugin-unicorn` packages to their latest versions Both of these ESLint "helpers" has increased their *major* version numbers, which `npm update` doesn't handle automatically (since that could cause errors), hence this patch which updates them manually. https://www.npmjs.com/package/eslint-config-prettier https://www.npmjs.com/package/eslint-plugin-unicorn
2021-04-14 19:39:19 +09:00
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/esquery/-/esquery-1.4.0.tgz",
"integrity": "sha512-cCDispWt5vHHtwMY2YrAQ4ibFkAL8RbH5YGBnZBc90MolvvfkkQcJro/aZiAQUlQ3qgrYS6D6v8Gc5G5CQsc9w==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"estraverse": "^5.1.0"
},
"dependencies": {
"estraverse": {
Update `npm` packages
2020-08-09 18:03:07 +09:00
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-5.2.0.tgz",
"integrity": "sha512-BxbNGGNm0RyRYvUdHpIwv9IWzeM9XClbOxwoATuFdOE7ZE6wHL+HQ5T8hoPM+zHvmKzzsEqhgy0GrQ5X13afiQ==",
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"dev": true
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"esrecurse": {
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/esrecurse/-/esrecurse-4.3.0.tgz",
"integrity": "sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag==",
"dev": true,
"requires": {
"estraverse": "^5.2.0"
},
"dependencies": {
"estraverse": {
Update npm packages
2021-10-31 17:38:18 +09:00
"version": "5.3.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz",
"integrity": "sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==",
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"dev": true
}
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"estraverse": {
"version": "4.2.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-4.2.0.tgz",
"integrity": "sha1-De4/7TH81GlhjOc0IJn8GvoL2xM=",
"dev": true
},
"esutils": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/esutils/-/esutils-2.0.2.tgz",
"integrity": "sha1-Cr9PHKpbyx96nYrMbepPqqBLrJs=",
"dev": true
},
Update `npm` packages
2019-12-29 03:57:25 +09:00
"events": {
Update npm packages
2021-09-19 16:31:42 +09:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/events/-/events-3.3.0.tgz",
"integrity": "sha512-mQw+2fkQbALzQ7V0MY0IqdnXNOeTtP4r0lN9z7AAawCXgqea7bDii20AYrIBrFd/Hx0M2Ocz6S111CaFkUcb0Q==",
Update `npm` packages
2019-12-29 03:57:25 +09:00
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"execall": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/execall/-/execall-2.0.0.tgz",
"integrity": "sha512-0FU2hZ5Hh6iQnarpRtQurM/aAvp3RIbfvgLHrcqJYzhXyV2KFruhuChf9NC6waAhiUR7FFtlugkI4p7f2Fqlow==",
"dev": true,
"requires": {
"clone-regexp": "^2.1.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"expand-brackets": {
"version": "2.1.4",
"resolved": "https://registry.npmjs.org/expand-brackets/-/expand-brackets-2.1.4.tgz",
"integrity": "sha1-t3c14xXOMPa27/D4OwQVGiJEliI=",
"dev": true,
"requires": {
"debug": "^2.3.3",
"define-property": "^0.2.5",
"extend-shallow": "^2.0.1",
"posix-character-classes": "^0.1.0",
"regex-not": "^1.0.0",
"snapdragon": "^0.8.1",
"to-regex": "^3.0.1"
},
"dependencies": {
"define-property": {
"version": "0.2.5",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-0.2.5.tgz",
"integrity": "sha1-w1se+RjsPJkPmlvFe+BKrOxcgRY=",
"dev": true,
"requires": {
"is-descriptor": "^0.1.0"
}
},
"extend-shallow": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/extend-shallow/-/extend-shallow-2.0.1.tgz",
"integrity": "sha1-Ua99YUrZqfYQ6huvu5idaxxWiQ8=",
"dev": true,
"requires": {
"is-extendable": "^0.1.0"
}
}
}
},
"expand-tilde": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/expand-tilde/-/expand-tilde-2.0.2.tgz",
"integrity": "sha1-l+gBqgUt8CRU3kawK/YhZCzchQI=",
"dev": true,
"requires": {
"homedir-polyfill": "^1.0.1"
}
},
"extend": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/extend/-/extend-3.0.2.tgz",
"integrity": "sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"extend-shallow": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/extend-shallow/-/extend-shallow-3.0.2.tgz",
"integrity": "sha1-Jqcarwc7OfshJxcnRhMcJwQCjbg=",
"dev": true,
"requires": {
"assign-symbols": "^1.0.0",
"is-extendable": "^1.0.1"
},
"dependencies": {
"is-extendable": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/is-extendable/-/is-extendable-1.0.1.tgz",
"integrity": "sha512-arnXMxT1hhoKo9k1LZdmlNyJdDDfy2v0fXjFlmok4+i8ul/6WlbVge9bhM74OpNPQPMGUToDtz+KXa1PneJxOA==",
"dev": true,
"requires": {
"is-plain-object": "^2.0.4"
}
}
}
},
"extglob": {
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/extglob/-/extglob-2.0.4.tgz",
"integrity": "sha512-Nmb6QXkELsuBr24CJSkilo6UHHgbekK5UiZgfE6UHD3Eb27YC6oD+bhcT+tJ6cl8dmsgdQxnWlcry8ksBIBLpw==",
"dev": true,
"requires": {
"array-unique": "^0.3.2",
"define-property": "^1.0.0",
"expand-brackets": "^2.1.4",
"extend-shallow": "^2.0.1",
"fragment-cache": "^0.2.1",
"regex-not": "^1.0.0",
"snapdragon": "^0.8.1",
"to-regex": "^3.0.1"
},
"dependencies": {
"define-property": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-1.0.0.tgz",
"integrity": "sha1-dp66rz9KY6rTr56NMEybvnm/sOY=",
"dev": true,
"requires": {
"is-descriptor": "^1.0.0"
}
},
"extend-shallow": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/extend-shallow/-/extend-shallow-2.0.1.tgz",
"integrity": "sha1-Ua99YUrZqfYQ6huvu5idaxxWiQ8=",
"dev": true,
"requires": {
"is-extendable": "^0.1.0"
}
},
"is-accessor-descriptor": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-accessor-descriptor/-/is-accessor-descriptor-1.0.0.tgz",
"integrity": "sha512-m5hnHTkcVsPfqx3AKlyttIPb7J+XykHvJP2B9bZDjlhLIoEq4XoK64Vg7boZlVWYK6LUY94dYPEE7Lh0ZkZKcQ==",
"dev": true,
"requires": {
"kind-of": "^6.0.0"
}
},
"is-data-descriptor": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-data-descriptor/-/is-data-descriptor-1.0.0.tgz",
"integrity": "sha512-jbRXy1FmtAoCjQkVmIVYwuuqDFUbaOeDjmed1tOGPrsMhtJA4rD9tkgA0F1qJ3gRFRXcHYVkdeaP50Q5rE/jLQ==",
"dev": true,
"requires": {
"kind-of": "^6.0.0"
}
},
"is-descriptor": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/is-descriptor/-/is-descriptor-1.0.2.tgz",
"integrity": "sha512-2eis5WqQGV7peooDyLmNEPUrps9+SXX5c9pL3xEB+4e9HnGuDa7mB7kHxHw4CbqS9k1T2hOH3miL8n8WtiYVtg==",
"dev": true,
"requires": {
"is-accessor-descriptor": "^1.0.0",
"is-data-descriptor": "^1.0.0",
"kind-of": "^6.0.2"
}
}
}
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"extract-zip": {
Update `npm` packages
2020-06-13 17:36:11 +09:00
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/extract-zip/-/extract-zip-2.0.1.tgz",
"integrity": "sha512-GDhU9ntwuKyGXdZBUgTIe+vXnWj0fppUEtMDL0+idd5Sta8TGpHssn/eusA9mrPr9qNDym6SxAYZjNvCn/9RBg==",
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"dev": true,
"requires": {
"@types/yauzl": "^2.9.1",
"debug": "^4.1.1",
"get-stream": "^5.1.0",
"yauzl": "^2.10.0"
},
"dependencies": {
"debug": {
Update npm packages
2021-07-11 19:14:47 +09:00
"version": "4.3.2",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.2.tgz",
"integrity": "sha512-mOp8wKcvj7XxC78zLgw/ZA+6TSgkoE2C/ienthhRD298T7UNwAg9diBpLRxC0mOezLl4B0xV7M0cCO6P/O0Xhw==",
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-11-29 17:43:20 +09:00
"ms": "2.1.2"
}
},
"ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
}
}
},
"fancy-log": {
"version": "1.3.3",
"resolved": "https://registry.npmjs.org/fancy-log/-/fancy-log-1.3.3.tgz",
"integrity": "sha512-k9oEhlyc0FrVh25qYuSELjr8oxsCoc4/LEZfg2iJJrfEk/tZL9bCoJE47gqAvI2m/AUjluCS4+3I0eTx8n3AEw==",
"dev": true,
"requires": {
"ansi-gray": "^0.1.1",
"color-support": "^1.1.3",
"parse-node-version": "^1.0.0",
"time-stamp": "^1.0.0"
}
},
"fast-deep-equal": {
"version": "3.1.3",
"resolved": "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz",
"integrity": "sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==",
"dev": true
},
"fast-diff": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/fast-diff/-/fast-diff-1.2.0.tgz",
"integrity": "sha512-xJuoT5+L99XlZ8twedaRf6Ax2TgQVxvgZOYoPKqZufmJib0tL2tegPBOZb1pVNgIhlqDlA0eO0c3wBvQcmzx4w==",
"dev": true
},
"fast-glob": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "3.2.11",
"resolved": "https://registry.npmjs.org/fast-glob/-/fast-glob-3.2.11.tgz",
"integrity": "sha512-xrO3+1bxSo3ZVHAnqzyuewYT6aMFHRAd4Kcs92MAonjwQZLsK9d0SF1IyQ3k5PoirxTW0Oe/RqFgMQ6TcNE5Ew==",
Update `npm` packages
2020-11-29 17:43:20 +09:00
"dev": true,
"requires": {
"@nodelib/fs.stat": "^2.0.2",
"@nodelib/fs.walk": "^1.2.3",
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"glob-parent": "^5.1.2",
Update `npm` packages
2020-11-29 17:43:20 +09:00
"merge2": "^1.3.0",
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"micromatch": "^4.0.4"
Update `npm` packages
2020-11-29 17:43:20 +09:00
},
"dependencies": {
"braces": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/braces/-/braces-3.0.2.tgz",
"integrity": "sha512-b8um+L1RzM3WDSzvhm6gIz1yfTbBt6YTlcEKAvsmqCZZFw46z626lVj9j1yEPW33H5H+lBQpZMP1k8l+78Ha0A==",
"dev": true,
"requires": {
"fill-range": "^7.0.1"
}
},
"fill-range": {
"version": "7.0.1",
"resolved": "https://registry.npmjs.org/fill-range/-/fill-range-7.0.1.tgz",
"integrity": "sha512-qOo9F+dMUmC2Lcb4BbVvnKJxTPjCm+RRpe4gDuGrzkL7mEVl/djYSu2OdQ2Pa302N4oqkSg9ir6jaLWJ2USVpQ==",
"dev": true,
"requires": {
"to-regex-range": "^5.0.1"
}
},
"glob-parent": {
Update `npm` packages
2021-03-07 20:00:57 +09:00
"version": "5.1.2",
"resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz",
"integrity": "sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==",
Update `npm` packages
2020-11-29 17:43:20 +09:00
"dev": true,
"requires": {
"is-glob": "^4.0.1"
}
},
"is-glob": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"version": "4.0.3",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz",
"integrity": "sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==",
Update `npm` packages
2020-11-29 17:43:20 +09:00
"dev": true,
"requires": {
"is-extglob": "^2.1.1"
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
}
},
Update `npm` packages
2020-11-29 17:43:20 +09:00
"is-number": {
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/is-number/-/is-number-7.0.0.tgz",
"integrity": "sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==",
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"dev": true
Update `npm` packages
2020-11-29 17:43:20 +09:00
},
"micromatch": {
Update npm packages
2021-05-02 16:30:09 +09:00
"version": "4.0.4",
"resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.4.tgz",
"integrity": "sha512-pRmzw/XUcwXGpD9aI9q/0XOwLNygjETJ8y0ao0wdqprrzDa4YnxLcz7fQRZr8voh8V10kGhABbNcHVk5wHgWwg==",
Update `npm` packages
2020-11-29 17:43:20 +09:00
"dev": true,
"requires": {
"braces": "^3.0.1",
Update npm packages
2021-05-02 16:30:09 +09:00
"picomatch": "^2.2.3"
Update `npm` packages
2020-11-29 17:43:20 +09:00
}
},
"to-regex-range": {
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/to-regex-range/-/to-regex-range-5.0.1.tgz",
"integrity": "sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==",
"dev": true,
"requires": {
"is-number": "^7.0.0"
}
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
}
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"fast-json-stable-stringify": {
Update `npm` packages
2019-12-29 03:57:25 +09:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/fast-json-stable-stringify/-/fast-json-stable-stringify-2.1.0.tgz",
"integrity": "sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"fast-levenshtein": {
"version": "2.0.6",
"resolved": "https://registry.npmjs.org/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz",
"integrity": "sha1-PYpcZog6FqMMqGQ+hR8Zuqd5eRc=",
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"fast-safe-stringify": {
"version": "2.0.6",
"resolved": "https://registry.npmjs.org/fast-safe-stringify/-/fast-safe-stringify-2.0.6.tgz",
"integrity": "sha512-q8BZ89jjc+mz08rSxROs8VsrBBcn1SIw1kq9NjolL509tkABRk9io01RAjSaEv1Xb2uFLt8VtRiZbGp5H8iDtg==",
"dev": true
},
Update `npm` packages
2020-09-06 18:49:49 +09:00
"fastest-levenshtein": {
"version": "1.0.12",
"resolved": "https://registry.npmjs.org/fastest-levenshtein/-/fastest-levenshtein-1.0.12.tgz",
"integrity": "sha512-On2N+BpYJ15xIC974QNVuYGMOlEVt4s0EOI3wwMqOmK1fdDY+FN/zltPV8vosq4ad4c/gJ1KHScUn/6AWIgiow==",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"fastq": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"version": "1.13.0",
"resolved": "https://registry.npmjs.org/fastq/-/fastq-1.13.0.tgz",
"integrity": "sha512-YpkpUnK8od0o1hmeSc7UUs/eB/vIPWJYjKck2QKIzAf71Vm1AAQ3EbuZB3g2JIy+pg+ERD0vqI79KyZiB2e2Nw==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true,
"requires": {
"reusify": "^1.0.4"
}
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"fd-slicer": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/fd-slicer/-/fd-slicer-1.1.0.tgz",
"integrity": "sha1-JcfInLH5B3+IkbvmHY85Dq4lbx4=",
"dev": true,
"requires": {
"pend": "~1.2.0"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"fecha": {
"version": "2.3.3",
"resolved": "http://registry.npmjs.org/fecha/-/fecha-2.3.3.tgz",
"integrity": "sha512-lUGBnIamTAwk4znq5BcqsDaxSmZ9nDVJaij6NvRt/Tg4R69gERA+otPKbS86ROw9nxVMw2/mp1fnaiWqbs6Sdg==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"file-entry-cache": {
Update `npm` packages
2021-02-21 19:52:55 +09:00
"version": "6.0.1",
"resolved": "https://registry.npmjs.org/file-entry-cache/-/file-entry-cache-6.0.1.tgz",
"integrity": "sha512-7Gps/XWymbLk2QLYK4NzpMOrYjMhdIxXuIvy2QBsLE6ljuodKvdkWs/cpyJJ3CVIVpH0Oi1Hvg1ovbMzLdFBBg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-12-13 19:38:37 +09:00
"flat-cache": "^3.0.4"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"fill-range": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/fill-range/-/fill-range-4.0.0.tgz",
"integrity": "sha1-1USBHUKPmOsGpj3EAtJAPDKMOPc=",
"dev": true,
"requires": {
"extend-shallow": "^2.0.1",
"is-number": "^3.0.0",
"repeat-string": "^1.6.1",
"to-regex-range": "^2.1.0"
},
"dependencies": {
"extend-shallow": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/extend-shallow/-/extend-shallow-2.0.1.tgz",
"integrity": "sha1-Ua99YUrZqfYQ6huvu5idaxxWiQ8=",
"dev": true,
"requires": {
"is-extendable": "^0.1.0"
}
}
}
},
Update npm packages
2021-10-31 17:38:18 +09:00
"find-cache-dir": {
"version": "3.3.2",
"resolved": "https://registry.npmjs.org/find-cache-dir/-/find-cache-dir-3.3.2.tgz",
"integrity": "sha512-wXZV5emFEjrridIgED11OoUKLxiYjAcqot/NJdAkOhlJ+vGzwhOAfcG5OX1jP+S0PcjEn8bdMJv+g2jwQ3Onig==",
"dev": true,
"requires": {
"commondir": "^1.0.1",
"make-dir": "^3.0.2",
"pkg-dir": "^4.1.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"find-up": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-2.1.0.tgz",
"integrity": "sha1-RdG35QbHF93UgndaK3eSCjwMV6c=",
"dev": true,
"requires": {
"locate-path": "^2.0.0"
}
},
"findup-sync": {
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/findup-sync/-/findup-sync-3.0.0.tgz",
"integrity": "sha512-YbffarhcicEhOrm4CtrwdKBdCuz576RLdhJDsIfvNtxUuhdRet1qZcsMjqbePtAseKdAnDyM/IyXbu7PRPRLYg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"detect-file": "^1.0.0",
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"is-glob": "^4.0.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"micromatch": "^3.0.4",
"resolve-dir": "^1.0.1"
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
},
"dependencies": {
"is-glob": {
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.1.tgz",
"integrity": "sha512-5G0tKtBTFImOqDnLB2hG6Bp2qcKEFduo4tZu9MT/H6NQv/ghhy30o55ufafxJ/LdH79LLs2Kfrn85TLKyA7BUg==",
"dev": true,
"requires": {
"is-extglob": "^2.1.1"
}
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"fined": {
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/fined/-/fined-1.2.0.tgz",
"integrity": "sha512-ZYDqPLGxDkDhDZBjZBb+oD1+j0rA4E0pXY50eplAAOPg2N/gUBSSk5IM1/QhPfyVo19lJ+CvXpqfvk+b2p/8Ng==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"expand-tilde": "^2.0.2",
"is-plain-object": "^2.0.3",
"object.defaults": "^1.1.0",
"object.pick": "^1.2.0",
"parse-filepath": "^1.0.1"
}
},
"flagged-respawn": {
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/flagged-respawn/-/flagged-respawn-1.0.1.tgz",
"integrity": "sha512-lNaHNVymajmk0OJMBn8fVUAU1BtDeKIqKoVhk4xAALB57aALg6b4W0MfJ/cUE0g9YBXy5XhSlPIpYIJ7HaY/3Q==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"flat-cache": {
Update `npm` packages
2020-12-13 19:38:37 +09:00
"version": "3.0.4",
"resolved": "https://registry.npmjs.org/flat-cache/-/flat-cache-3.0.4.tgz",
"integrity": "sha512-dm9s5Pw7Jc0GvMYbshN6zchCA9RgQlzzEZX3vylR9IqFfS8XciblUXOKfW6SiuJ0e13eDYZoZV5wdrev7P3Nwg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-12-13 19:38:37 +09:00
"flatted": "^3.1.0",
"rimraf": "^3.0.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2019-02-18 00:44:36 +09:00
"flatted": {
Update `npm` packages
2021-01-24 16:34:00 +09:00
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/flatted/-/flatted-3.1.1.tgz",
"integrity": "sha512-zAoAQiudy+r5SvnSw3KJy5os/oRJYHzrzja/tBDqrZtNhUw8bt6y8OBzMWcjWr+8liV8Eb6yOhw8WZ7VFZ5ZzA==",
Update packages
2019-02-18 00:44:36 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"flush-write-stream": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/flush-write-stream/-/flush-write-stream-1.0.3.tgz",
"integrity": "sha512-calZMC10u0FMUqoiunI2AiGIIUtUIvifNwkHhNupZH4cbNnW1Itkoh/Nf5HFYmDrwWPjrUxpkZT0KhuCq0jmGw==",
"dev": true,
"requires": {
"inherits": "^2.0.1",
"readable-stream": "^2.0.4"
}
},
"for-in": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/for-in/-/for-in-1.0.2.tgz",
"integrity": "sha1-gQaNKVqBQuwKxybG4iAMMPttXoA=",
"dev": true
},
"for-own": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/for-own/-/for-own-1.0.0.tgz",
"integrity": "sha1-xjMy9BXO3EsE2/5wz4NklMU8tEs=",
"dev": true,
"requires": {
"for-in": "^1.0.1"
}
},
"foreach": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/foreach/-/foreach-2.0.5.tgz",
"integrity": "sha1-C+4AUBiusmDQo6865ljdATbsG5k=",
"dev": true
},
Update `npm` packages
2020-12-13 19:38:37 +09:00
"fraction.js": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "4.1.2",
"resolved": "https://registry.npmjs.org/fraction.js/-/fraction.js-4.1.2.tgz",
"integrity": "sha512-o2RiJQ6DZaR/5+Si0qJUIy637QMRudSi9kU/FFzx9EZazrIdnBgpU+3sEWCxAVhH2RtxW2Oz+T4p2o8uOPVcgA==",
Update `npm` packages
2020-12-13 19:38:37 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"fragment-cache": {
"version": "0.2.1",
"resolved": "https://registry.npmjs.org/fragment-cache/-/fragment-cache-0.2.1.tgz",
"integrity": "sha1-QpD60n8T6Jvn8zeZxrxaCr//DRk=",
"dev": true,
"requires": {
"map-cache": "^0.2.2"
}
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"fs-constants": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/fs-constants/-/fs-constants-1.0.0.tgz",
"integrity": "sha512-y6OAwoSIf7FyjMIv94u+b5rdheZEjzR63GTyZJm5qh4Bi+2YgwLCcI/fPFZkL5PSixOt6ZNKm+w+Hfp/Bciwow==",
"dev": true
},
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"fs-minipass": {
Update npm packages
2021-05-30 14:43:13 +09:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/fs-minipass/-/fs-minipass-2.1.0.tgz",
"integrity": "sha512-V/JgOLFCS+R6Vcq0slCuaeWEdNC3ouDlJMNIsacH2VtALiu9mV4LPrHc5cDl8k5aw6J8jwgWWpiTo5RYhmIzvg==",
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-30 14:43:13 +09:00
"minipass": "^3.0.0"
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"fs-mkdirp-stream": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/fs-mkdirp-stream/-/fs-mkdirp-stream-1.0.0.tgz",
"integrity": "sha1-C3gV/DIBxqaeFNuYzgmMFpNSWes=",
"dev": true,
"requires": {
"graceful-fs": "^4.1.11",
"through2": "^2.0.3"
added transform function added depedencies removed gulp-transform dependency removed dependencies removed gulptransform dependency
2019-11-13 11:51:31 +09:00
},
"dependencies": {
"through2": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.5.tgz",
"integrity": "sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==",
"dev": true,
"requires": {
"readable-stream": "~2.3.6",
"xtend": "~4.0.1"
}
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"fs.realpath": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/fs.realpath/-/fs.realpath-1.0.0.tgz",
"integrity": "sha1-FQStJSMVjKpA20onh8sBQRmU6k8=",
"dev": true
},
"fsevents": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "1.2.9",
"resolved": "https://registry.npmjs.org/fsevents/-/fsevents-1.2.9.tgz",
"integrity": "sha512-oeyj2H3EjjonWcFjD5NvZNE9Rqe4UW+nQBU2HNeKw0koVLEFIhtyETyAakeAM3de7Z/SW5kcA+fZUait9EApnw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"optional": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"nan": "^2.12.1",
"node-pre-gyp": "^0.12.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
"abbrev": {
"version": "1.1.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-nne9/IiQ/hzIhY6pdDnbBtz7DjPTKrY00P/zvPSm5pOFkl6xuGrGnXn/VtTNNfNtAfZ9/1RtehkszU9qcTii0Q==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"ansi-regex": {
"version": "2.1.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-w7M6te42DYbg5ijwRorn7yfWVN8=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"dev": true,
"optional": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"aproba": {
"version": "1.2.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-Y9J6ZjXtoYh8RnXVCMOU/ttDmk1aBjunq9vO0ta5x85WDQiQfUF9sIPBITdbiiIVcBo03Hi3jMxigBtsddlXRw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"are-we-there-yet": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "1.1.5",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-5hYdAkZlcG8tOLujVDTgCT+uPX0VnpAH28gWsLfzpXYm7wP6mp5Q/gYyR7YQ0cKVJcXJnl3j2kpBan13PtQf6w==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
"delegates": "^1.0.0",
"readable-stream": "^2.0.6"
}
},
"balanced-match": {
"version": "1.0.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-ibTRmasr7kneFk6gK4nORi1xt2c=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"dev": true,
"optional": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"brace-expansion": {
"version": "1.1.11",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"optional": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"requires": {
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
}
},
"code-point-at": {
"version": "1.1.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-DQcLTQQ6W+ozovGkDi7bPZpMz3c=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"dev": true,
"optional": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"concat-map": {
"version": "0.0.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-2Klr13/Wjfd5OnMDajug1UBdR3s=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"dev": true,
"optional": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"console-control-strings": {
"version": "1.1.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-PXz0Rk22RG6mRL9LOVB/mFEAjo4=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"dev": true,
"optional": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"core-util-is": {
"version": "1.0.2",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-tf1UIgqivFq1eqtxQMlAdUUDwac=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"debug": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "4.1.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-pYAIzeRo8J6KPEaJ0VWOh5Pzkbw/RetuzehGM7QRRX5he4fPHx2rdKMB256ehJCkX+XRQm16eZLqLNS8RSZXZw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"ms": "^2.1.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"deep-extend": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "0.6.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-LOHxIOaPYdHlJRtCQfDIVZtfw/ufM8+rVj649RIHzcm/vGwQRXFt6OPqIFWsm2XEMrNIEtWR64sY1LEKD2vAOA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"delegates": {
"version": "1.0.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-hMbhWbgZBP3KWaDvRM2HDTElD5o=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"detect-libc": {
"version": "1.0.3",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-+hN8S9aY7fVc1c0CrFWfkaTEups=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"fs.realpath": {
"version": "1.0.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-FQStJSMVjKpA20onh8sBQRmU6k8=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"gauge": {
"version": "2.7.4",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-LANAXHU4w51+s3sxcCLjJfsBi/c=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
"aproba": "^1.0.3",
"console-control-strings": "^1.0.0",
"has-unicode": "^2.0.0",
"object-assign": "^4.1.0",
"signal-exit": "^3.0.0",
"string-width": "^1.0.1",
"strip-ansi": "^3.0.1",
"wide-align": "^1.1.0"
}
},
"glob": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "7.1.3",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-vcfuiIxogLV4DlGBHIUOwI0IbrJ8HWPc4MU7HzviGeNho/UJDfi6B5p3sHeWIQ0KGIU0Jpxi5ZHxemQfLkkAwQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
"minimatch": "^3.0.4",
"once": "^1.3.0",
"path-is-absolute": "^1.0.0"
}
},
"has-unicode": {
"version": "2.0.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-4Ob+aijPUROIVeCG0Wkedx3iqLk=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"iconv-lite": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "0.4.24",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-v3MXnZAcvnywkTUEZomIActle7RXXeedOR31wwl7VlyoXO4Qi9arvSenNQWne1TcRwhCL1HwLI21bEqdpj8/rA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"safer-buffer": ">= 2.1.2 < 3"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"ignore-walk": {
"version": "3.0.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-DTVlMx3IYPe0/JJcYP7Gxg7ttZZu3IInhuEhbchuqneY9wWe5Ojy2mXLBaQFUQmo0AW2r3qG7m1mg86js+gnlQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
"minimatch": "^3.0.4"
}
},
"inflight": {
"version": "1.0.6",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-Sb1jMdfQLQwJvJEKEHW6gWW1bfk=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
"once": "^1.3.0",
"wrappy": "1"
}
},
"inherits": {
"version": "2.0.3",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-Yzwsg+PaQqUC9SRmAiSA9CCCYd4=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"dev": true,
"optional": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"is-fullwidth-code-point": {
"version": "1.0.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-754xOG8DGn8NZDr4L95QxFfvAMs=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"optional": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"requires": {
"number-is-nan": "^1.0.0"
}
},
"isarray": {
"version": "1.0.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"minimatch": {
"version": "3.0.4",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-yJHVQEhyqPLUTgt9B83PXu6W3rx4MvvHvSUvToogpwoGDOUQ+yDrR0HRot+yOCdCO7u4hX3pWft6kWBBcqh0UA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"optional": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"requires": {
"brace-expansion": "^1.1.7"
}
},
"minimist": {
"version": "0.0.8",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-hX/Kv8M5fSYluCKCYuhqp6ARsF0=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"dev": true,
"optional": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"mkdirp": {
"version": "0.5.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-MAV0OOrGz3+MR2fzhkjWaX11yQM=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"optional": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"requires": {
"minimist": "0.0.8"
}
},
"ms": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "2.1.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-tgp+dl5cGk28utYktBsrFqA7HKgrhgPsg6Z/EfhWI4gl1Hwq8B/GmY/0oXZ6nF8hDVesS/FpnYaD/kOWhYQvyg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"needle": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "2.3.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-QBZu7aAFR0522EyaXZM0FZ9GLpq6lvQ3uq8gteiDUp7wKdy0lSd2hPlgFwVuW1CBkfEs9PfDQsQzZghLs/psdg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"debug": "^4.1.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"iconv-lite": "^0.4.4",
"sax": "^1.2.4"
}
},
"node-pre-gyp": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "0.12.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-4KghwV8vH5k+g2ylT+sLTjy5wmUOb9vPhnM8NHvRf9dHmnW/CndrFXy2aRPaPST6dugXSdHXfeaHQm77PIz/1A==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
"detect-libc": "^1.0.2",
"mkdirp": "^0.5.1",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"needle": "^2.2.1",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"nopt": "^4.0.1",
"npm-packlist": "^1.1.6",
"npmlog": "^4.0.2",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"rc": "^1.2.7",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"rimraf": "^2.6.1",
"semver": "^5.3.0",
"tar": "^4"
}
},
"nopt": {
"version": "4.0.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-0NRoWv1UFRk8jHUFYC0NF81kR00=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
"abbrev": "1",
"osenv": "^0.1.4"
}
},
"npm-bundled": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "1.0.6",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-8/JCaftHwbd//k6y2rEWp6k1wxVfpFzB6t1p825+cUb7Ym2XQfhwIC5KwhrvzZRJu+LtDE585zVaS32+CGtf0g==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"npm-packlist": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "1.4.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-+TcdO7HJJ8peiiYhvPxsEDhF3PJFGUGRcFsGve3vxvxdcpO2Z4Z7rkosRM0kWj6LfbK/P0gu3dzk5RU1ffvFcw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
"ignore-walk": "^3.0.1",
"npm-bundled": "^1.0.1"
}
},
"npmlog": {
"version": "4.1.2",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-2uUqazuKlTaSI/dC8AzicUck7+IrEaOnN/e0jd3Xtt1KcGpwx30v50mL7oPyr/h9bL3E4aZccVwpwP+5W9Vjkg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
"are-we-there-yet": "~1.1.2",
"console-control-strings": "~1.1.0",
"gauge": "~2.7.3",
"set-blocking": "~2.0.0"
}
},
"number-is-nan": {
"version": "1.0.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-CXtgK1NCKlIsGvuHkDGDNpQaAR0=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"dev": true,
"optional": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"object-assign": {
"version": "4.1.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-IQmtx5ZYh8/AXLvUQsrIv7s2CGM=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"once": {
"version": "1.4.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-WDsap3WWHUsROsF9nFC6753Xa9E=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"optional": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"requires": {
"wrappy": "1"
}
},
"os-homedir": {
"version": "1.0.2",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-/7xJiDNuDoM94MFox+8VISGqf7M=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"os-tmpdir": {
"version": "1.0.2",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-u+Z0BseaqFxc/sdm/lc0VV36EnQ=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"osenv": {
"version": "0.1.5",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-0CWcCECdMVc2Rw3U5w9ZjqX6ga6ubk1xDVKxtBQPK7wis/0F2r9T6k4ydGYhecl7YUBxBVxhL5oisPsNxAPe2g==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
"os-homedir": "^1.0.0",
"os-tmpdir": "^1.0.0"
}
},
"path-is-absolute": {
"version": "1.0.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-F0uSaHNVNP+8es5r9TpanhtcX18=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"process-nextick-args": {
"version": "2.0.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-MtEC1TqN0EU5nephaJ4rAtThHtC86dNN9qCuEhtshvpVBkAW5ZO7BASN9REnF9eoXGcRub+pFuKEpOHE+HbEMw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"rc": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "1.2.8",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-y3bGgqKj3QBdxLbLkomlohkvsA8gdAiUQlSBJnBhfn+BPxg4bc62d8TcBW15wavDfgexCgccckhcZvywyQYPOw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"deep-extend": "^0.6.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"ini": "~1.3.0",
"minimist": "^1.2.0",
"strip-json-comments": "~2.0.1"
},
"dependencies": {
"minimist": {
"version": "1.2.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-o1AIsg9BOD7sH7kU9M1d95omQoQ=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
}
}
},
"readable-stream": {
"version": "2.3.6",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-tQtKA9WIAhBF3+VLAseyMqZeBjW0AHJoxOtYqSUZNJxauErmLbVm2FW1y+J/YA9dUrAC39ITejlZWhVIwawkKw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"rimraf": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "2.6.3",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-mwqeW5XsA2qAejG46gYdENaxXjx9onRNCfn7L0duuP4hCuTIi/QO7PDK07KJfp1d+izWPrzEJDcSqBa0OZQriA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"glob": "^7.1.3"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"safe-buffer": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "5.1.2",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"bundled": true,
"dev": true,
"optional": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"safer-buffer": {
"version": "2.1.2",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"sax": {
"version": "1.2.4",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-NqVDv9TpANUjFm0N8uM5GxL36UgKi9/atZw+x7YFnQ8ckwFGKrl4xX4yWtrey3UJm5nP1kUbnYgLopqWNSRhWw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"semver": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "5.7.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-Ya52jSX2u7QKghxeoFGpLwCtGlt7j0oY9DYb5apt9nPlJ42ID+ulTXESnt/qAQcoSERyZ5sl3LDIOw0nAn/5DA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"set-blocking": {
"version": "2.0.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-BF+XgtARrppoA93TgrJDkrPYkPc=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"signal-exit": {
"version": "3.0.2",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-tf3AjxKH6hF4Yo5BXiUTK3NkbG0=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"string_decoder": {
"version": "1.1.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"optional": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"requires": {
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"safe-buffer": "~5.1.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"string-width": {
"version": "1.0.2",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-EYvfW4zcUaKn5w0hHgfisLmxB9M=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"code-point-at": "^1.0.0",
"is-fullwidth-code-point": "^1.0.0",
"strip-ansi": "^3.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"strip-ansi": {
"version": "3.0.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-ajhfuIU9lS1f8F0Oiq+UJ43GPc8=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"optional": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"requires": {
"ansi-regex": "^2.0.0"
}
},
"strip-json-comments": {
"version": "2.0.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-PFMZQukIwml8DsNEhYwobHygpgo=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"tar": {
Bump tar from 4.4.15 to 4.4.19 Bumps [tar](https://github.com/npm/node-tar) from 4.4.15 to 4.4.19. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.15...v4.4.19) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-01 01:39:41 +09:00
"version": "4.4.19",
"resolved": "https://registry.npmjs.org/tar/-/tar-4.4.19.tgz",
"integrity": "sha512-a20gEsvHnWe0ygBY8JbxoM4w3SJdhc7ZAuxkLqh+nvNQN2IOt0B5lLgM490X5Hl8FF0dl0tOf2ewFYAlIFgzVA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"optional": true,
"requires": {
Bump tar from 4.4.15 to 4.4.19 Bumps [tar](https://github.com/npm/node-tar) from 4.4.15 to 4.4.19. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.15...v4.4.19) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-01 01:39:41 +09:00
"chownr": "^1.1.4",
"fs-minipass": "^1.2.7",
"minipass": "^2.9.0",
"minizlib": "^1.3.3",
"mkdirp": "^0.5.5",
"safe-buffer": "^5.2.1",
"yallist": "^3.1.1"
Bump tar from 4.4.8 to 4.4.15 Bumps [tar](https://github.com/npm/node-tar) from 4.4.8 to 4.4.15. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.8...v4.4.15) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-04 04:41:11 +09:00
},
"dependencies": {
Bump tar from 4.4.15 to 4.4.19 Bumps [tar](https://github.com/npm/node-tar) from 4.4.15 to 4.4.19. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.15...v4.4.19) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-01 01:39:41 +09:00
"chownr": {
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/chownr/-/chownr-1.1.4.tgz",
"integrity": "sha512-jJ0bqzaylmJtVnNgzTeSOs8DPavpbYgEr/b0YL8/2GO3xJEhInFmhKMUnEJQjZumK7KXGFhUy89PrsJWlakBVg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"bundled": true,
Bump tar from 4.4.15 to 4.4.19 Bumps [tar](https://github.com/npm/node-tar) from 4.4.15 to 4.4.19. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.15...v4.4.19) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-01 01:39:41 +09:00
"dev": true,
"optional": true
},
"fs-minipass": {
"version": "1.2.7",
"resolved": "https://registry.npmjs.org/fs-minipass/-/fs-minipass-1.2.7.tgz",
"integrity": "sha512-GWSSJGFy4e9GUeCcbIkED+bgAoFyj7XF1mV8rma3QW4NIqX9Kyx79N/PF61H5udOV3aY1IaMLs6pGbH71nlCTA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"bundled": true,
Bump tar from 4.4.15 to 4.4.19 Bumps [tar](https://github.com/npm/node-tar) from 4.4.15 to 4.4.19. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.15...v4.4.19) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-01 01:39:41 +09:00
"dev": true,
"optional": true,
"requires": {
"minipass": "^2.6.0"
}
},
"minimist": {
"version": "1.2.5",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz",
"integrity": "sha512-FM9nNUYrRBAELZQT3xeZQ7fmMOBg6nWNmJKTcgsJeaLstP/UODVpGsr5OhXhhXg6f+qtJ8uiZ+PUxkDWcgIXLw==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"bundled": true,
Bump tar from 4.4.15 to 4.4.19 Bumps [tar](https://github.com/npm/node-tar) from 4.4.15 to 4.4.19. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.15...v4.4.19) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-01 01:39:41 +09:00
"dev": true,
"optional": true
},
Bump tar from 4.4.8 to 4.4.15 Bumps [tar](https://github.com/npm/node-tar) from 4.4.8 to 4.4.15. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.8...v4.4.15) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-04 04:41:11 +09:00
"minipass": {
"version": "2.9.0",
"resolved": "https://registry.npmjs.org/minipass/-/minipass-2.9.0.tgz",
"integrity": "sha512-wxfUjg9WebH+CUDX/CdbRlh5SmfZiy/hpkxaRI16Y9W56Pa75sWgd/rvFilSgrauD9NyFymP/+JFV3KwzIsJeg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"bundled": true,
Bump tar from 4.4.8 to 4.4.15 Bumps [tar](https://github.com/npm/node-tar) from 4.4.8 to 4.4.15. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.8...v4.4.15) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-04 04:41:11 +09:00
"dev": true,
"optional": true,
"requires": {
"safe-buffer": "^5.1.2",
"yallist": "^3.0.0"
}
Bump tar from 4.4.15 to 4.4.19 Bumps [tar](https://github.com/npm/node-tar) from 4.4.15 to 4.4.19. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.15...v4.4.19) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-01 01:39:41 +09:00
},
"minizlib": {
"version": "1.3.3",
"resolved": "https://registry.npmjs.org/minizlib/-/minizlib-1.3.3.tgz",
"integrity": "sha512-6ZYMOEnmVsdCeTJVE0W9ZD+pVnE8h9Hma/iOwwRDsdQoePpoX56/8B6z3P9VNwppJuBKNRuFDRNRqRWexT9G9Q==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"bundled": true,
Bump tar from 4.4.15 to 4.4.19 Bumps [tar](https://github.com/npm/node-tar) from 4.4.15 to 4.4.19. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.15...v4.4.19) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-01 01:39:41 +09:00
"dev": true,
"optional": true,
"requires": {
"minipass": "^2.9.0"
}
},
"mkdirp": {
"version": "0.5.5",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.5.tgz",
"integrity": "sha512-NKmAlESf6jMGym1++R0Ra7wvhV+wFW63FaSOFPwRahvea0gMUcGUhVeAg/0BC0wiv9ih5NYPB1Wn1UEI1/L+xQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"bundled": true,
Bump tar from 4.4.15 to 4.4.19 Bumps [tar](https://github.com/npm/node-tar) from 4.4.15 to 4.4.19. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.15...v4.4.19) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-01 01:39:41 +09:00
"dev": true,
"optional": true,
"requires": {
"minimist": "^1.2.5"
}
},
"safe-buffer": {
"version": "5.2.1",
"resolved": "https://registry.npmjs.org/safe-buffer/-/safe-buffer-5.2.1.tgz",
"integrity": "sha512-rp3So07KcdmmKbGvgaNxQSJr7bGVSVk5S9Eq1F+ppbRo70+YeaDxkw5Dd8NPN+GD6bjnYm2VuPuCXmpuYvmCXQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"bundled": true,
Bump tar from 4.4.15 to 4.4.19 Bumps [tar](https://github.com/npm/node-tar) from 4.4.15 to 4.4.19. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.15...v4.4.19) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-01 01:39:41 +09:00
"dev": true,
"optional": true
},
"yallist": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/yallist/-/yallist-3.1.1.tgz",
"integrity": "sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"bundled": true,
Bump tar from 4.4.15 to 4.4.19 Bumps [tar](https://github.com/npm/node-tar) from 4.4.15 to 4.4.19. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.15...v4.4.19) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-01 01:39:41 +09:00
"dev": true,
"optional": true
Bump tar from 4.4.8 to 4.4.15 Bumps [tar](https://github.com/npm/node-tar) from 4.4.8 to 4.4.15. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.8...v4.4.15) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-04 04:41:11 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"util-deprecate": {
"version": "1.0.2",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-RQ1Nyfpw3nMnYvvS1KKJgUGaDM8=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true
},
"wide-align": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "1.1.3",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha512-QGkOQc8XL6Bt5PwnsExKBPuMKBxnGxWWW3fU55Xt4feHozMUhdUMaBCk290qpm/wG5u/RSKzwdAC4i51YigihA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
"dev": true,
"optional": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"string-width": "^1.0.2 || 2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"wrappy": {
"version": "1.0.2",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"integrity": "sha1-tSQ9jz7BqjXxNkYFvA0QNuMKtp8=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bundled": true,
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"dev": true,
"optional": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
},
"function-bind": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/function-bind/-/function-bind-1.1.1.tgz",
Update npm packages
2021-05-16 17:05:58 +09:00
"integrity": "sha512-yIovAzMX49sF8Yl58fSCWJ5svSLuaibPxXQJFLmBObTuCr0Mf1KiPopGM9NiFjiYBCbfaa2Fh6breQ6ANVTI0A==",
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"functional-red-black-tree": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/functional-red-black-tree/-/functional-red-black-tree-1.0.1.tgz",
"integrity": "sha1-GwqzvVU7Kg1jmdKcDj6gslIHgyc=",
"dev": true
},
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"gauge": {
"version": "2.7.4",
"resolved": "https://registry.npmjs.org/gauge/-/gauge-2.7.4.tgz",
"integrity": "sha1-LANAXHU4w51+s3sxcCLjJfsBi/c=",
"dev": true,
"requires": {
"aproba": "^1.0.3",
"console-control-strings": "^1.0.0",
"has-unicode": "^2.0.0",
"object-assign": "^4.1.0",
"signal-exit": "^3.0.0",
"string-width": "^1.0.1",
"strip-ansi": "^3.0.1",
"wide-align": "^1.1.0"
}
},
Update `npm` packages
2020-01-31 22:04:49 +09:00
"gensync": {
Update `npm` packages
2020-11-29 17:43:20 +09:00
"version": "1.0.0-beta.2",
"resolved": "https://registry.npmjs.org/gensync/-/gensync-1.0.0-beta.2.tgz",
"integrity": "sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg==",
Update `npm` packages
2020-01-31 22:04:49 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"get-caller-file": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/get-caller-file/-/get-caller-file-1.0.2.tgz",
"integrity": "sha1-9wLmMSfn4jHBYKgMFVSstw1QR+U=",
"dev": true
},
Update npm packages
2021-05-16 17:05:58 +09:00
"get-intrinsic": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/get-intrinsic/-/get-intrinsic-1.1.1.tgz",
"integrity": "sha512-kWZrnVM42QCiEA2Ig1bG8zjoIMOgxWwYCEeNdwY6Tv/cOSeGpcoX4pXHfKUxNKVoArnrEr2e9srnAxxGIraS9Q==",
"dev": true,
"requires": {
"function-bind": "^1.1.1",
"has": "^1.0.3",
"has-symbols": "^1.0.1"
},
"dependencies": {
"has-symbols": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.2.tgz",
"integrity": "sha512-chXa79rL/UC2KlX17jo3vRGz0azaWEx5tGqZg5pO3NUyEJVB17dMruQlzCCOfUvElghKcm5194+BCRvi2Rv/Gw==",
"dev": true
}
}
},
Update npm packages
2021-05-02 16:30:09 +09:00
"get-stdin": {
"version": "8.0.0",
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-8.0.0.tgz",
"integrity": "sha512-sY22aA6xchAzprjyqmSEQv4UbAAzRN0L2dQB0NlN5acTTK9Don6nhoc3eAbUnpZiCANAMfd/+40kVdKfFygohg==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"get-stream": {
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/get-stream/-/get-stream-5.2.0.tgz",
"integrity": "sha512-nBF+F1rAZVCu/p7rjzgA+Yb4lfYXrpl7a6VmJrU8wF9I1CKvP/QwPNZHnOlwbTkY6dvtFIzFMSyQXbLoTQPRpA==",
"dev": true,
"requires": {
"pump": "^3.0.0"
},
"dependencies": {
"pump": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/pump/-/pump-3.0.0.tgz",
"integrity": "sha512-LwZy+p3SFs1Pytd/jYct4wpv49HiYCqd9Rlc5ZVdk0V+8Yzv6jR5Blk3TRmPL1ft69TxP0IMZGJ+WPFU2BFhww==",
"dev": true,
"requires": {
"end-of-stream": "^1.1.0",
"once": "^1.3.1"
}
}
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update npm packages
2021-10-17 18:33:19 +09:00
"get-symbol-description": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/get-symbol-description/-/get-symbol-description-1.0.0.tgz",
"integrity": "sha512-2EmdH1YvIQiZpltCNgkuiUnyukzxM/R6NDJX31Ke3BG1Nq5b0S2PhX59UKi9vZpPDQVdqn+1IcaAwnzTT5vCjw==",
"dev": true,
"requires": {
"call-bind": "^1.0.2",
"get-intrinsic": "^1.1.1"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"get-value": {
"version": "2.0.6",
"resolved": "https://registry.npmjs.org/get-value/-/get-value-2.0.6.tgz",
"integrity": "sha1-3BXKHGcjh8p2vTesCjlbogQqLCg=",
"dev": true
},
"glob": {
"version": "7.1.2",
"resolved": "https://registry.npmjs.org/glob/-/glob-7.1.2.tgz",
"integrity": "sha512-MJTUg1kjuLeQCJ+ccE4Vpa6kKVXkPYJ2mOCQyUuKLcLQsdrMCpBPUi8qVE6+YuaJkozeA9NusTAw3hLr8Xe5EQ==",
"dev": true,
"requires": {
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
"minimatch": "^3.0.4",
"once": "^1.3.0",
"path-is-absolute": "^1.0.0"
}
},
"glob-parent": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz",
"integrity": "sha1-nmr2KZ2NO9K9QEMIMr0RPfkGxa4=",
"dev": true,
"requires": {
"is-glob": "^3.1.0",
"path-dirname": "^1.0.0"
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"glob-stream": {
"version": "6.1.0",
"resolved": "https://registry.npmjs.org/glob-stream/-/glob-stream-6.1.0.tgz",
"integrity": "sha1-cEXJlBOz65SIjYOrRtC0BMx73eQ=",
"dev": true,
"requires": {
"extend": "^3.0.0",
"glob": "^7.1.1",
"glob-parent": "^3.1.0",
"is-negated-glob": "^1.0.0",
"ordered-read-streams": "^1.0.0",
"pumpify": "^1.3.5",
"readable-stream": "^2.1.5",
"remove-trailing-separator": "^1.0.1",
"to-absolute-glob": "^2.0.0",
"unique-stream": "^2.0.2"
}
},
Update Jasmine to version 3.6.1 This is possible now that most intermittent unit test failures have been resolved by other patches. There is only one remaining, but it's very rare and doesn't have to block this update anymore.
2020-08-02 04:11:32 +09:00
"glob-to-regexp": {
Update `npm` packages
2020-10-18 17:57:52 +09:00
"version": "0.4.1",
"resolved": "https://registry.npmjs.org/glob-to-regexp/-/glob-to-regexp-0.4.1.tgz",
"integrity": "sha512-lkX1HJXwyMcprw/5YUZc2s7DrpAiHB21/V+E1rHUrVNokkvB6bqMzT0VfV6/86ZNabt1k14YOIaT7nDvOX3Iiw==",
Update Jasmine to version 3.6.1 This is possible now that most intermittent unit test failures have been resolved by other patches. There is only one remaining, but it's very rare and doesn't have to block this update anymore.
2020-08-02 04:11:32 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"glob-watcher": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "5.0.5",
"resolved": "https://registry.npmjs.org/glob-watcher/-/glob-watcher-5.0.5.tgz",
"integrity": "sha512-zOZgGGEHPklZNjZQaZ9f41i7F2YwE+tS5ZHrDhbBCk3stwahn5vQxnFmBJZHoYdusR6R1bLSXeGUy/BhctwKzw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"anymatch": "^2.0.0",
"async-done": "^1.2.0",
"chokidar": "^2.0.0",
"is-negated-glob": "^1.0.0",
"just-debounce": "^1.0.0",
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"normalize-path": "^3.0.0",
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"object.defaults": "^1.1.0"
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
},
"dependencies": {
"normalize-path": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/normalize-path/-/normalize-path-3.0.0.tgz",
"integrity": "sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==",
"dev": true
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"global-modules": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/global-modules/-/global-modules-1.0.0.tgz",
"integrity": "sha512-sKzpEkf11GpOFuw0Zzjzmt4B4UZwjOcG757PPvrfhxcLFbq0wpsgpOqxpxtxFiCG4DtG93M6XRVbF2oGdev7bg==",
"dev": true,
"requires": {
"global-prefix": "^1.0.1",
"is-windows": "^1.0.1",
"resolve-dir": "^1.0.0"
}
},
"global-prefix": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/global-prefix/-/global-prefix-1.0.2.tgz",
"integrity": "sha1-2/dDxsFJklk8ZVVoy2btMsASLr4=",
"dev": true,
"requires": {
"expand-tilde": "^2.0.2",
"homedir-polyfill": "^1.0.1",
"ini": "^1.3.4",
"is-windows": "^1.0.1",
"which": "^1.2.14"
}
},
"globals": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "13.12.1",
"resolved": "https://registry.npmjs.org/globals/-/globals-13.12.1.tgz",
"integrity": "sha512-317dFlgY2pdJZ9rspXDks7073GpDmXdfbM3vYYp0HAMKGDh1FfWPleI2ljVNLQX5M5lXcAslTcPTrOrMEFOjyw==",
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-12-27 19:11:18 +09:00
"type-fest": "^0.20.2"
},
"dependencies": {
"type-fest": {
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.20.2.tgz",
"integrity": "sha512-Ne+eE4r0/iWnpAxD852z3A+N0Bt5RN//NjJwRd2VFHEmrywxf5vsZlh4R6lixl6B+wz/8d+maTSAkN1FIkI3LQ==",
"dev": true
}
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"globby": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "11.1.0",
"resolved": "https://registry.npmjs.org/globby/-/globby-11.1.0.tgz",
"integrity": "sha512-jhIXaOzy1sb8IyocaruWSn1TjmnBVs8Ayhcy83rmxNJ8q2uWKCAj3CnJY+KpGSXCueAPc0i05kVvVKtP1t9S3g==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true,
"requires": {
"array-union": "^2.1.0",
"dir-glob": "^3.0.1",
Update npm packages
2022-02-06 19:24:14 +09:00
"fast-glob": "^3.2.9",
"ignore": "^5.2.0",
"merge2": "^1.4.1",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"slash": "^3.0.0"
},
"dependencies": {
"ignore": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/ignore/-/ignore-5.2.0.tgz",
"integrity": "sha512-CmxgYGiEPCLhfLnpPp1MoRmifwEIOgjcHXxOBjv7mY96c+eWScsOP9c112ZyLdWHi0FxHjI+4uVhKYp/gcdRmQ==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true
}
}
},
"globjoin": {
"version": "0.1.4",
"resolved": "https://registry.npmjs.org/globjoin/-/globjoin-0.1.4.tgz",
"integrity": "sha1-L0SUrIkZ43Z8XLtpHp9GMyQoXUM=",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"glogg": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/glogg/-/glogg-1.0.1.tgz",
"integrity": "sha512-ynYqXLoluBKf9XGR1gA59yEJisIL7YHEH4xr3ZziHB5/yl4qWfaK8Js9jGe6gBGCSCKVqiyO30WnRZADvemUNw==",
"dev": true,
"requires": {
"sparkles": "^1.0.0"
}
},
"graceful-fs": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "4.2.9",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.9.tgz",
"integrity": "sha512-NtNxqUcXgpW2iMrfqSfR73Glt39K+BLwWsPs94yR63v45T0Wbej7eRmL5cWfwEgqXnmjQp3zaJTshdRW/qC2ZQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"gulp": {
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"version": "4.0.2",
"resolved": "https://registry.npmjs.org/gulp/-/gulp-4.0.2.tgz",
"integrity": "sha512-dvEs27SCZt2ibF29xYgmnwwCYZxdxhQ/+LFWlbAW8y7jt68L/65402Lz3+CKy0Ov4rOs+NERmDq7YlZaDqUIfA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"glob-watcher": "^5.0.3",
"gulp-cli": "^2.2.0",
"undertaker": "^1.2.1",
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"vinyl-fs": "^3.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"camelcase": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-3.0.0.tgz",
"integrity": "sha1-MvxLn82vhF/N9+c7uXysImHwqwo=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"cliui": {
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/cliui/-/cliui-3.2.0.tgz",
"integrity": "sha1-EgYBU3qRbSmUD5NNo7SNWFo5IT0=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"string-width": "^1.0.1",
"strip-ansi": "^3.0.1",
"wrap-ansi": "^2.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"find-up": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-1.1.2.tgz",
"integrity": "sha1-ay6YIrGizgpgq2TWEOzK1TyyTQ8=",
"dev": true,
"requires": {
"path-exists": "^2.0.0",
"pinkie-promise": "^2.0.0"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"gulp-cli": {
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/gulp-cli/-/gulp-cli-2.2.0.tgz",
"integrity": "sha512-rGs3bVYHdyJpLqR0TUBnlcZ1O5O++Zs4bA0ajm+zr3WFCfiSLjGwoCBqFs18wzN+ZxahT9DkOK5nDf26iDsWjA==",
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"dev": true,
"requires": {
"ansi-colors": "^1.0.1",
"archy": "^1.0.0",
"array-sort": "^1.0.0",
"color-support": "^1.1.3",
"concat-stream": "^1.6.0",
"copy-props": "^2.0.1",
"fancy-log": "^1.3.2",
"gulplog": "^1.0.0",
"interpret": "^1.1.0",
"isobject": "^3.0.1",
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"liftoff": "^3.1.0",
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"matchdep": "^2.0.0",
"mute-stdout": "^1.0.0",
"pretty-hrtime": "^1.0.0",
"replace-homedir": "^1.0.0",
"semver-greatest-satisfied-range": "^1.1.0",
"v8flags": "^3.0.1",
"yargs": "^7.1.0"
}
},
"load-json-file": {
"version": "1.1.0",
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-1.1.0.tgz",
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"integrity": "sha1-lWkFcI1YtLq0wiYbBPWfMcmTdMA=",
"dev": true,
"requires": {
"graceful-fs": "^4.1.2",
"parse-json": "^2.2.0",
"pify": "^2.0.0",
"pinkie-promise": "^2.0.0",
"strip-bom": "^2.0.0"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"os-locale": {
"version": "1.4.0",
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"resolved": "https://registry.npmjs.org/os-locale/-/os-locale-1.4.0.tgz",
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"integrity": "sha1-IPnxeuKe00XoveWDsT0gCYA8FNk=",
"dev": true,
"requires": {
"lcid": "^1.0.0"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"path-exists": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-2.1.0.tgz",
"integrity": "sha1-D+tsZPD8UY2adU3V77YscCJ2H0s=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"pinkie-promise": "^2.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"path-type": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-1.1.0.tgz",
"integrity": "sha1-WcRPfuSR2nBNpBXaWkBwuk+P5EE=",
"dev": true,
"requires": {
"graceful-fs": "^4.1.2",
"pify": "^2.0.0",
"pinkie-promise": "^2.0.0"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"pify": {
"version": "2.3.0",
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"integrity": "sha1-7RQaasBDqEnqWISY59yosVMw6Qw=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"read-pkg": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-1.1.0.tgz",
"integrity": "sha1-9f+qXs0pyzHAR0vKfXVra7KePyg=",
"dev": true,
"requires": {
"load-json-file": "^1.0.0",
"normalize-package-data": "^2.3.2",
"path-type": "^1.0.0"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"read-pkg-up": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-1.0.1.tgz",
"integrity": "sha1-nWPBMnbAZZGNV/ACpX9AobZD+wI=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"find-up": "^1.0.0",
"read-pkg": "^1.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"which-module": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/which-module/-/which-module-1.0.0.tgz",
"integrity": "sha1-u6Y8qGGUiZT/MHc2CJ47lgJsKk8=",
"dev": true
},
"yargs": {
"version": "7.1.0",
"resolved": "https://registry.npmjs.org/yargs/-/yargs-7.1.0.tgz",
"integrity": "sha1-a6MY6xaWFyf10oT46gA+jWFU0Mg=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"camelcase": "^3.0.0",
"cliui": "^3.2.0",
"decamelize": "^1.1.1",
"get-caller-file": "^1.0.1",
"os-locale": "^1.4.0",
"read-pkg-up": "^1.0.1",
"require-directory": "^2.1.1",
"require-main-filename": "^1.0.1",
"set-blocking": "^2.0.0",
"string-width": "^1.0.2",
"which-module": "^1.0.0",
"y18n": "^3.2.1",
"yargs-parser": "^5.0.0"
}
},
"yargs-parser": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-5.0.1.tgz",
"integrity": "sha512-wpav5XYiddjXxirPoCTUPbqM0PXvJ9hiBMvuJgInvo4/lAOTZzUprArw17q2O1P2+GHhbBr18/iQwjL5Z9BqfA==",
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"dev": true,
"requires": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"camelcase": "^3.0.0",
"object.assign": "^4.1.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
}
},
"gulp-postcss": {
Update npm packages
2021-09-05 16:47:57 +09:00
"version": "9.0.1",
"resolved": "https://registry.npmjs.org/gulp-postcss/-/gulp-postcss-9.0.1.tgz",
"integrity": "sha512-9QUHam5JyXwGUxaaMvoFQVT44tohpEFpM8xBdPfdwTYGM0AItS1iTQz0MpsF8Jroh7GF5Jt2GVPaYgvy8qD2Fw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"fancy-log": "^1.3.3",
Update packages
2018-12-23 00:00:53 +09:00
"plugin-error": "^1.0.1",
Update npm packages
2021-09-05 16:47:57 +09:00
"postcss-load-config": "^3.0.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"vinyl-sourcemaps-apply": "^0.2.1"
}
},
"gulp-rename": {
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/gulp-rename/-/gulp-rename-2.0.0.tgz",
"integrity": "sha512-97Vba4KBzbYmR5VBs9mWmK+HwIf5mj+/zioxfZhOKeXtx5ZjBk57KFlePf5nxq9QsTtFl0ejnHE3zTC9MHXqyQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"gulp-replace": {
Update npm packages
2021-05-16 17:05:58 +09:00
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/gulp-replace/-/gulp-replace-1.1.3.tgz",
"integrity": "sha512-HcPHpWY4XdF8zxYkDODHnG2+7a3nD/Y8Mfu3aBgMiCFDW3X2GiOKXllsAmILcxe3KZT2BXoN18WrpEFm48KfLQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-02 16:30:09 +09:00
"@types/node": "^14.14.41",
"@types/vinyl": "^2.0.4",
"istextorbinary": "^3.0.0",
"replacestream": "^4.0.3",
"yargs-parser": ">=5.0.0-security.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"gulp-zip": {
Update `npm` packages
2021-03-21 19:00:02 +09:00
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/gulp-zip/-/gulp-zip-5.1.0.tgz",
"integrity": "sha512-XZr/y91IliK/SpR74g3TkZejGkGEmK7CSDjSghT1jXshgO+dFvpLIz9w9fpuwkew6i7k4F+G24TubNgq1ISzEw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2021-03-21 19:00:02 +09:00
"get-stream": "^5.2.0",
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"plugin-error": "^1.0.1",
"through2": "^3.0.1",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"vinyl": "^2.1.0",
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"yazl": "^2.5.1"
added transform function added depedencies removed gulp-transform dependency removed dependencies removed gulptransform dependency
2019-11-13 11:51:31 +09:00
},
"dependencies": {
"through2": {
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/through2/-/through2-3.0.2.tgz",
"integrity": "sha512-enaDQ4MUyP2W6ZyT6EsMzqBPZaM/avg8iuo+l2d3QCs0J+6RaqkHV/2/lOwDTueBHeJ/2LG9lrLW3d5rWPucuQ==",
added transform function added depedencies removed gulp-transform dependency removed dependencies removed gulptransform dependency
2019-11-13 11:51:31 +09:00
"dev": true,
"requires": {
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"inherits": "^2.0.4",
"readable-stream": "2 || 3"
added transform function added depedencies removed gulp-transform dependency removed dependencies removed gulptransform dependency
2019-11-13 11:51:31 +09:00
}
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"gulplog": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/gulplog/-/gulplog-1.0.0.tgz",
"integrity": "sha1-4oxNRdBey77YGDY86PnFkmIp/+U=",
"dev": true,
"requires": {
"glogg": "^1.0.0"
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"hard-rejection": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/hard-rejection/-/hard-rejection-2.1.0.tgz",
"integrity": "sha512-VIZB+ibDhx7ObhAe7OVtoEbuP4h/MuOTHJ+J8h/eBXotJYl0fBgR72xDFCKgIh22OJZIOVNxBMWuhAr10r8HdA==",
"dev": true
},
Enable eslint-plugin-import to prevent unresolved paths
2018-11-23 21:50:28 +09:00
"has": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/has/-/has-1.0.3.tgz",
"integrity": "sha512-f2dvO0VU6Oej7RkWJGrehjbzMAjFp5/VKPp5tTpWIV4JHHZK1/BxbFRtf/siA2SWTe09caDmVtYYzWEIbBS4zw==",
Update npm packages
2021-05-16 17:05:58 +09:00
"dev": true,
Enable eslint-plugin-import to prevent unresolved paths
2018-11-23 21:50:28 +09:00
"requires": {
"function-bind": "^1.1.1"
}
},
Update npm packages
2021-05-16 17:05:58 +09:00
"has-bigints": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/has-bigints/-/has-bigints-1.0.1.tgz",
"integrity": "sha512-LSBS2LjbNBTf6287JEbEzvJgftkF5qFkmCo9hDRpAzKhUOlJ+hx8dd4USs00SgsUNwc4617J9ki5YtEClM2ffA==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"has-flag": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/has-flag/-/has-flag-3.0.0.tgz",
"integrity": "sha1-tdRU3CGZriJWmfNGfloH87lVuv0=",
"dev": true
},
"has-symbols": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.0.tgz",
"integrity": "sha1-uhqPGvKg/DllD1yFA2dwQSIGO0Q=",
"dev": true
},
Update npm packages
2021-08-22 17:38:52 +09:00
"has-tostringtag": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/has-tostringtag/-/has-tostringtag-1.0.0.tgz",
"integrity": "sha512-kFjcSNhnlGV1kyoGk7OXKSawH5JOb/LzUc5w9B02hOTO0dfFRjbHQKvg1d6cf3HbeUmtU9VbbV3qzZ2Teh97WQ==",
"dev": true,
"requires": {
"has-symbols": "^1.0.2"
},
"dependencies": {
"has-symbols": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.2.tgz",
"integrity": "sha512-chXa79rL/UC2KlX17jo3vRGz0azaWEx5tGqZg5pO3NUyEJVB17dMruQlzCCOfUvElghKcm5194+BCRvi2Rv/Gw==",
"dev": true
}
}
},
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"has-unicode": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/has-unicode/-/has-unicode-2.0.1.tgz",
"integrity": "sha1-4Ob+aijPUROIVeCG0Wkedx3iqLk=",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"has-value": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/has-value/-/has-value-1.0.0.tgz",
"integrity": "sha1-GLKB2lhbHFxR3vJMkw7SmgvmsXc=",
"dev": true,
"requires": {
"get-value": "^2.0.6",
"has-values": "^1.0.0",
"isobject": "^3.0.0"
}
},
"has-values": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/has-values/-/has-values-1.0.0.tgz",
"integrity": "sha1-lbC2P+whRmGab+V/51Yo1aOe/k8=",
"dev": true,
"requires": {
"is-number": "^3.0.0",
"kind-of": "^4.0.0"
},
"dependencies": {
"kind-of": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-4.0.0.tgz",
"integrity": "sha1-IIE989cSkosgc3hpGkUGb65y3Vc=",
"dev": true,
"requires": {
"is-buffer": "^1.1.5"
}
}
}
},
"highlight.js": {
Bump highlight.js from 9.13.1 to 9.18.5 Bumps [highlight.js](https://github.com/highlightjs/highlight.js) from 9.13.1 to 9.18.5. - [Release notes](https://github.com/highlightjs/highlight.js/releases) - [Changelog](https://github.com/highlightjs/highlight.js/blob/9.18.5/CHANGES.md) - [Commits](https://github.com/highlightjs/highlight.js/compare/9.13.1...9.18.5) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-25 08:29:33 +09:00
"version": "9.18.5",
"resolved": "https://registry.npmjs.org/highlight.js/-/highlight.js-9.18.5.tgz",
"integrity": "sha512-a5bFyofd/BHCX52/8i8uJkjr9DYwXIPnM/plwI6W7ezItLGqzt7X2G2nXuYSfsIJdkwwj/g9DG1LkcGJI/dDoA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"homedir-polyfill": {
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/homedir-polyfill/-/homedir-polyfill-1.0.3.tgz",
"integrity": "sha512-eSmmWE5bZTK2Nou4g0AI3zZ9rswp7GRKoKXS1BLUkvPviOqs4YTN1djQIqrXy9k5gEtdLPy86JjRwsNM9tnDcA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"parse-passwd": "^1.0.0"
}
},
"hosted-git-info": {
Bump hosted-git-info from 2.6.0 to 2.8.9 Bumps [hosted-git-info](https://github.com/npm/hosted-git-info) from 2.6.0 to 2.8.9. - [Release notes](https://github.com/npm/hosted-git-info/releases) - [Changelog](https://github.com/npm/hosted-git-info/blob/v2.8.9/CHANGELOG.md) - [Commits](https://github.com/npm/hosted-git-info/compare/v2.6.0...v2.8.9) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-08 03:43:06 +09:00
"version": "2.8.9",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.9.tgz",
"integrity": "sha512-mxIDAb9Lsm6DoOJ7xH+5+X4y1LU/4Hi50L9C5sIswK3JzULS4bwk1FvjdBgvYR4bzT4tuUQiC15FE2f5HbLvYw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"html-tags": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/html-tags/-/html-tags-3.1.0.tgz",
"integrity": "sha512-1qYz89hW3lFDEazhjW0yVAV87lw8lVkrJocr72XmBkMKsoSVJCQx3W8BXsC7hO2qAt8BoVjYjtAcZ9perqGnNg==",
"dev": true
},
Update the various ESLint packages to their latest versions
2018-07-09 19:52:55 +09:00
"htmlparser2": {
Update npm packages
2021-10-03 15:21:01 +09:00
"version": "7.1.2",
"resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-7.1.2.tgz",
"integrity": "sha512-d6cqsbJba2nRdg8WW2okyD4ceonFHn9jLFxhwlNcLhQWcFPdxXeJulgOLjLKtAK9T6ahd+GQNZwG9fjmGW7lyg==",
Update the various ESLint packages to their latest versions
2018-07-09 19:52:55 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-08-09 18:03:07 +09:00
"domelementtype": "^2.0.1",
Update npm packages
2021-10-03 15:21:01 +09:00
"domhandler": "^4.2.2",
"domutils": "^2.8.0",
"entities": "^3.0.1"
Update packages
2019-02-18 00:44:36 +09:00
},
"dependencies": {
Update `npm` packages
2020-08-09 18:03:07 +09:00
"entities": {
Update npm packages
2021-10-03 15:21:01 +09:00
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/entities/-/entities-3.0.1.tgz",
"integrity": "sha512-WiyBqoomrwMdFG1e0kqvASYfnlb0lp8M5o5Fw2OFq1hNZxxcNk8Ik0Xm7LxzBhuidnZB/UtBqVCgUz3kBOP51Q==",
Update `npm` packages
2020-08-09 18:03:07 +09:00
"dev": true
Update packages
2019-02-18 00:44:36 +09:00
}
Update the various ESLint packages to their latest versions
2018-07-09 19:52:55 +09:00
}
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"https-proxy-agent": {
Update Puppeteer to version 6 (issue 12945) Please see https://github.com/puppeteer/puppeteer/releases/tag/v6.0.0
2021-02-02 21:18:22 +09:00
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/https-proxy-agent/-/https-proxy-agent-5.0.0.tgz",
"integrity": "sha512-EkYm5BcKUGiduxzSt3Eppko+PiNWNEpa4ySk9vTC6wDsQJW9rHSa+UhGNJoRYp7bz6Ht1eaRIa6QaJqO5rCFbA==",
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"dev": true,
"requires": {
Update Puppeteer to version 6 (issue 12945) Please see https://github.com/puppeteer/puppeteer/releases/tag/v6.0.0
2021-02-02 21:18:22 +09:00
"agent-base": "6",
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"debug": "4"
},
"dependencies": {
"debug": {
Update Puppeteer to version 5.5.0
2020-11-22 22:26:32 +09:00
"version": "4.3.1",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.1.tgz",
"integrity": "sha512-doEwdvm4PCeK4K3RQN2ZC2BYUBaxwLARCqZmMjtF8a51J2Rb0xpVloFRnCODwqjpwnAoao4pelN8l3RJdv3gRQ==",
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"dev": true,
"requires": {
Upgrade Puppeteer to version 5.3.1
2020-10-04 06:06:31 +09:00
"ms": "2.1.2"
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
}
},
"ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
}
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"iconv-lite": {
Update packages
2018-09-10 00:54:24 +09:00
"version": "0.4.24",
"resolved": "https://registry.npmjs.org/iconv-lite/-/iconv-lite-0.4.24.tgz",
"integrity": "sha512-v3MXnZAcvnywkTUEZomIActle7RXXeedOR31wwl7VlyoXO4Qi9arvSenNQWne1TcRwhCL1HwLI21bEqdpj8/rA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"safer-buffer": ">= 2.1.2 < 3"
}
},
"ieee754": {
Update npm packages
2021-10-03 15:21:01 +09:00
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/ieee754/-/ieee754-1.2.1.tgz",
"integrity": "sha512-dcyqhDvX1C46lXZcVqCpK+FtMRQVdIMN6/Df5js2zouUsqG7I6sFxitIC+7KYK29KdXOLHdu9zL4sFnoVQnqaA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"ignore": {
Update packages
2018-08-19 23:16:41 +09:00
"version": "4.0.6",
"resolved": "https://registry.npmjs.org/ignore/-/ignore-4.0.6.tgz",
"integrity": "sha512-cyFDKrqc/YdcWFniJhzI42+AzS+gNwmUzOSFcRCQYwySuBBBy/KjuxWLZ/FHEH6Moq1NizMOBWyTcv8O4OZIMg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-12-23 00:00:53 +09:00
"import-cwd": {
Update npm packages
2021-09-05 16:47:57 +09:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/import-cwd/-/import-cwd-3.0.0.tgz",
"integrity": "sha512-4pnzH16plW+hgvRECbDWpQl3cqtvSofHWh44met7ESfZ8UZOWWddm8hEyDTqREJ9RbYHY8gi8DqmaelApoOGMg==",
Update packages
2018-12-23 00:00:53 +09:00
"dev": true,
"requires": {
Update npm packages
2021-09-05 16:47:57 +09:00
"import-from": "^3.0.0"
Update packages
2018-12-23 00:00:53 +09:00
}
},
Update packages
2019-01-05 22:27:47 +09:00
"import-fresh": {
Update `npm` packages
2021-01-24 16:34:00 +09:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/import-fresh/-/import-fresh-3.3.0.tgz",
"integrity": "sha512-veYYhQa+D1QBKznvhUHxb8faxlrwUnxseDAbAp457E0wLNio2bOSKnjYDhMj+YiAq61xrMGhQk9iXVk5FzgQMw==",
Update packages
2019-01-05 22:27:47 +09:00
"dev": true,
"requires": {
"parent-module": "^1.0.0",
"resolve-from": "^4.0.0"
}
},
Update packages
2018-12-23 00:00:53 +09:00
"import-from": {
Update npm packages
2021-09-05 16:47:57 +09:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/import-from/-/import-from-3.0.0.tgz",
"integrity": "sha512-CiuXOFFSzkU5x/CR0+z7T91Iht4CXgfCxVOFRhh2Zyhg5wOpWvvDLQUsWl+gcN+QscYBjez8hDCt85O7RLDttQ==",
Update packages
2018-12-23 00:00:53 +09:00
"dev": true,
"requires": {
Update npm packages
2021-09-05 16:47:57 +09:00
"resolve-from": "^5.0.0"
Update packages
2018-12-23 00:00:53 +09:00
},
"dependencies": {
"resolve-from": {
Update npm packages
2021-09-05 16:47:57 +09:00
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-5.0.0.tgz",
"integrity": "sha512-qYg9KP24dD5qka9J47d0aVky0N+b4fTU89LN9iDnjB5waksiC49rvMB0PrUJQGoTmH50XPiqOvAjDfaijGxYZw==",
Update packages
2018-12-23 00:00:53 +09:00
"dev": true
}
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"import-lazy": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/import-lazy/-/import-lazy-4.0.0.tgz",
"integrity": "sha512-rKtvo6a868b5Hu3heneU+L4yEQ4jYKLtjpnPeUdK7h0yzXGmyBTypknlkCvHFBqfX9YlorEiMM6Dnq/5atfHkw==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"imurmurhash": {
"version": "0.1.4",
"resolved": "https://registry.npmjs.org/imurmurhash/-/imurmurhash-0.1.4.tgz",
"integrity": "sha1-khi5srkoojixPcT7a21XbyMUU+o=",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"indent-string": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/indent-string/-/indent-string-4.0.0.tgz",
"integrity": "sha512-EdDDZu4A2OyIK7Lr/2zG+w5jmbuk1DVBnEwREQvBzspBJkCEbRa8GxU1lghYcaGJCnRWibjDXlq779X1/y5xwg==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"inflight": {
"version": "1.0.6",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.6.tgz",
"integrity": "sha1-Sb1jMdfQLQwJvJEKEHW6gWW1bfk=",
"dev": true,
"requires": {
"once": "^1.3.0",
"wrappy": "1"
}
},
"inherits": {
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.4.tgz",
"integrity": "sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"ini": {
Bump ini from 1.3.5 to 1.3.7 Bumps [ini](https://github.com/isaacs/ini) from 1.3.5 to 1.3.7. - [Release notes](https://github.com/isaacs/ini/releases) - [Commits](https://github.com/isaacs/ini/compare/v1.3.5...v1.3.7) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-11 05:48:56 +09:00
"version": "1.3.7",
"resolved": "https://registry.npmjs.org/ini/-/ini-1.3.7.tgz",
"integrity": "sha512-iKpRpXP+CrP2jyrxvg1kMUpXDyRUFDWurxbnVT1vQPx+Wz9uCYsMIqYuSBLV+PAaZG/d7kRLKRFc9oDMsH+mFQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update npm packages
2021-08-22 17:38:52 +09:00
"internal-slot": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/internal-slot/-/internal-slot-1.0.3.tgz",
"integrity": "sha512-O0DB1JC/sPyZl7cIo78n5dR7eUSwwpYPiXRhTzNxZVAMUuB8vlnRFyLxdrVToks6XPLVnFfbzaVd5WLjhgg+vA==",
"dev": true,
"requires": {
"get-intrinsic": "^1.1.0",
"has": "^1.0.3",
"side-channel": "^1.0.4"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"interpret": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/interpret/-/interpret-1.1.0.tgz",
"integrity": "sha1-ftGxQQxqDg94z5XTuEQMY/eLhhQ=",
"dev": true
},
"invert-kv": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/invert-kv/-/invert-kv-1.0.0.tgz",
"integrity": "sha1-EEqOSqym09jNFXqO+L+rLXo//bY=",
"dev": true
},
"is-absolute": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-absolute/-/is-absolute-1.0.0.tgz",
"integrity": "sha512-dOWoqflvcydARa360Gvv18DZ/gRuHKi2NU/wU5X1ZFzdYfH29nkiNZsF3mp4OJ3H4yo9Mx8A/uAGNzpzPN3yBA==",
"dev": true,
"requires": {
"is-relative": "^1.0.0",
"is-windows": "^1.0.1"
}
},
"is-accessor-descriptor": {
"version": "0.1.6",
"resolved": "https://registry.npmjs.org/is-accessor-descriptor/-/is-accessor-descriptor-0.1.6.tgz",
"integrity": "sha1-qeEss66Nh2cn7u84Q/igiXtcmNY=",
"dev": true,
"requires": {
"kind-of": "^3.0.2"
},
"dependencies": {
"kind-of": {
"version": "3.2.2",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz",
"integrity": "sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=",
"dev": true,
"requires": {
"is-buffer": "^1.1.5"
}
}
}
},
"is-arrayish": {
"version": "0.2.1",
"resolved": "https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.2.1.tgz",
"integrity": "sha1-d8mYQFJ6qOyxqLppe4BkWnqSap0=",
"dev": true
},
Update npm packages
2021-05-16 17:05:58 +09:00
"is-bigint": {
Update npm packages
2021-08-22 17:38:52 +09:00
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/is-bigint/-/is-bigint-1.0.4.tgz",
"integrity": "sha512-zB9CruMamjym81i2JZ3UMn54PKGsQzsJeo6xvN3HJJ4CAsQNB6iRutp2To77OfCNuoxspsIhzaPoO1zyCEhFOg==",
"dev": true,
"requires": {
"has-bigints": "^1.0.1"
}
Update npm packages
2021-05-16 17:05:58 +09:00
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"is-binary-path": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/is-binary-path/-/is-binary-path-1.0.1.tgz",
"integrity": "sha1-dfFmQrSA8YenEcgUFh/TpKdlWJg=",
"dev": true,
"requires": {
"binary-extensions": "^1.0.0"
}
},
Update npm packages
2021-05-16 17:05:58 +09:00
"is-boolean-object": {
Update npm packages
2021-08-22 17:38:52 +09:00
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/is-boolean-object/-/is-boolean-object-1.1.2.tgz",
"integrity": "sha512-gDYaKHJmnj4aWxyj6YHyXVpdQawtVLHU5cb+eztPGczf6cjuTdwve5ZIEfgXqH4e57An1D1AKf8CZ3kYrQRqYA==",
Update npm packages
2021-05-16 17:05:58 +09:00
"dev": true,
"requires": {
Update npm packages
2021-08-22 17:38:52 +09:00
"call-bind": "^1.0.2",
"has-tostringtag": "^1.0.0"
Update npm packages
2021-05-16 17:05:58 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"is-buffer": {
"version": "1.1.6",
"resolved": "https://registry.npmjs.org/is-buffer/-/is-buffer-1.1.6.tgz",
"integrity": "sha512-NcdALwpXkTm5Zvvbk7owOUSvVvBKDgKP5/ewfXEznmQFfs4ZRmanOeKBTjRVjka3QFoN6XJ+9F3USqfHqTaU5w==",
"dev": true
},
"is-builtin-module": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-1.0.0.tgz",
"integrity": "sha1-VAVy0096wxGfj3bDDLwbHgN6/74=",
"dev": true,
"requires": {
"builtin-modules": "^1.0.0"
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"is-callable": {
Update npm packages
2021-08-22 17:38:52 +09:00
"version": "1.2.4",
"resolved": "https://registry.npmjs.org/is-callable/-/is-callable-1.2.4.tgz",
"integrity": "sha512-nsuwtxZfMX67Oryl9LCQ+upnC0Z0BgpwntpS89m1H/TLF0zNfzfLMV/9Wa/6MZsj0acpEjAO0KF1xT6ZdLl95w==",
Update npm packages
2021-05-16 17:05:58 +09:00
"dev": true
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
},
Update `npm` packages
2020-11-29 17:43:20 +09:00
"is-core-module": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/is-core-module/-/is-core-module-2.2.0.tgz",
"integrity": "sha512-XRAfAdyyY5F5cOXn7hYQDqh2Xmii+DEfIcQGxK/uNwMHhIkPWO0g8msXcbzLe+MpGoR951MlqM/2iIlU4vKDdQ==",
"dev": true,
"requires": {
"has": "^1.0.3"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"is-data-descriptor": {
"version": "0.1.4",
"resolved": "https://registry.npmjs.org/is-data-descriptor/-/is-data-descriptor-0.1.4.tgz",
"integrity": "sha1-C17mSDiOLIYCgueT8YVv7D8wG1Y=",
"dev": true,
"requires": {
"kind-of": "^3.0.2"
},
"dependencies": {
"kind-of": {
"version": "3.2.2",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz",
"integrity": "sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=",
"dev": true,
"requires": {
"is-buffer": "^1.1.5"
}
}
}
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"is-date-object": {
Update npm packages
2021-08-22 17:38:52 +09:00
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/is-date-object/-/is-date-object-1.0.5.tgz",
"integrity": "sha512-9YQaSxsAiSwcvS33MBk3wTCVnWK+HhF8VZR2jRxehM16QcVOdHqPn4VPHmRK4lSr38n9JriurInLcP90xsYNfQ==",
"dev": true,
"requires": {
"has-tostringtag": "^1.0.0"
}
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"is-descriptor": {
"version": "0.1.6",
"resolved": "https://registry.npmjs.org/is-descriptor/-/is-descriptor-0.1.6.tgz",
"integrity": "sha512-avDYr0SB3DwO9zsMov0gKCESFYqCnE4hq/4z3TdUlukEy5t9C0YRq7HLrsN52NAcqXKaepeCD0n+B0arnVG3Hg==",
"dev": true,
"requires": {
"is-accessor-descriptor": "^0.1.6",
"is-data-descriptor": "^0.1.4",
"kind-of": "^5.0.0"
},
"dependencies": {
"kind-of": {
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-5.1.0.tgz",
"integrity": "sha512-NGEErnH6F2vUuXDh+OlbcKW7/wOcfdRHaZ7VWtqCztfHri/++YKmP51OdWeGPuqCOba6kk2OTe5d02VmTB80Pw==",
"dev": true
}
}
},
Update packages
2018-11-25 05:00:22 +09:00
"is-expression": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/is-expression/-/is-expression-3.0.0.tgz",
"integrity": "sha1-Oayqa+f9HzRx3ELHQW5hwkMXrJ8=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"acorn": "~4.0.2",
"object-assign": "^4.0.1"
},
"dependencies": {
"acorn": {
"version": "4.0.13",
"resolved": "https://registry.npmjs.org/acorn/-/acorn-4.0.13.tgz",
"integrity": "sha1-EFSVrlNh1pe9GVyCUZLhrX8lN4c=",
"dev": true
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"is-extendable": {
"version": "0.1.1",
"resolved": "https://registry.npmjs.org/is-extendable/-/is-extendable-0.1.1.tgz",
"integrity": "sha1-YrEQ4omkcUGOPsNqYX1HLjAd/Ik=",
"dev": true
},
"is-extglob": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/is-extglob/-/is-extglob-2.1.1.tgz",
"integrity": "sha1-qIwCU1eR8C7TfHahueqXc8gz+MI=",
"dev": true
},
"is-fullwidth-code-point": {
Update npm packages
2021-05-30 14:43:13 +09:00
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-1.0.0.tgz",
"integrity": "sha1-754xOG8DGn8NZDr4L95QxFfvAMs=",
"dev": true,
"requires": {
"number-is-nan": "^1.0.0"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"is-glob": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-3.1.0.tgz",
"integrity": "sha1-e6WuJCF4BKxwcHuWkiVnSGzD6Eo=",
"dev": true,
"requires": {
"is-extglob": "^2.1.0"
}
},
"is-negated-glob": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-negated-glob/-/is-negated-glob-1.0.0.tgz",
"integrity": "sha1-aRC8pdqMleeEtXUbl2z1oQ/uNtI=",
"dev": true
},
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-10-04 20:50:37 +09:00
"is-negative-zero": {
Update npm packages
2021-05-16 17:05:58 +09:00
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/is-negative-zero/-/is-negative-zero-2.0.1.tgz",
"integrity": "sha512-2z6JzQvZRa9A2Y7xC6dQQm4FSTSTNWjKIYYTt4246eMTJmIo0Q+ZyOsU66X8lxK1AbB92dFeglPLrhwpeRKO6w==",
"dev": true
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-10-04 20:50:37 +09:00
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"is-number": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/is-number/-/is-number-3.0.0.tgz",
"integrity": "sha1-JP1iAaR4LPUFYcgQJ2r8fRLXEZU=",
"dev": true,
"requires": {
"kind-of": "^3.0.2"
},
"dependencies": {
"kind-of": {
"version": "3.2.2",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz",
"integrity": "sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=",
"dev": true,
"requires": {
"is-buffer": "^1.1.5"
}
}
}
},
Update npm packages
2021-05-16 17:05:58 +09:00
"is-number-object": {
Update npm packages
2021-08-22 17:38:52 +09:00
"version": "1.0.6",
"resolved": "https://registry.npmjs.org/is-number-object/-/is-number-object-1.0.6.tgz",
"integrity": "sha512-bEVOqiRcvo3zO1+G2lVMy+gkkEm9Yh7cDMRusKKu5ZJKPUYSJwICTKZrNKHA2EbSP0Tu0+6B/emsYNHZyn6K8g==",
"dev": true,
"requires": {
"has-tostringtag": "^1.0.0"
}
Update npm packages
2021-05-16 17:05:58 +09:00
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"is-odd": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/is-odd/-/is-odd-2.0.0.tgz",
"integrity": "sha512-OTiixgpZAT1M4NHgS5IguFp/Vz2VI3U7Goh4/HA1adtwyLtSBrxYlcSYkhpAE07s4fKEcjrFxyvtQBND4vFQyQ==",
"dev": true,
"requires": {
"is-number": "^4.0.0"
},
"dependencies": {
"is-number": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/is-number/-/is-number-4.0.0.tgz",
"integrity": "sha512-rSklcAIlf1OmFdyAqbnWTLVelsQ58uvZ66S/ZyawjWqIviTWCjg2PzVGw8WUA+nNuPTqb4wgA+NszrJ+08LlgQ==",
"dev": true
}
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"is-plain-obj": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/is-plain-obj/-/is-plain-obj-1.1.0.tgz",
"integrity": "sha1-caUMhCnfync8kqOQpKA7OfzVHT4=",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"is-plain-object": {
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/is-plain-object/-/is-plain-object-2.0.4.tgz",
"integrity": "sha512-h5PpgXkWitc38BBMYawTYMWJHFZJVnBquFE57xFpjB8pJFiF6gZ+bU+WyI/yqXiFR5mdLsgYNaPe8uao6Uv9Og==",
"dev": true,
"requires": {
"isobject": "^3.0.1"
}
},
"is-promise": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "2.2.2",
"resolved": "https://registry.npmjs.org/is-promise/-/is-promise-2.2.2.tgz",
"integrity": "sha512-+lP4/6lKUBfQjZ2pdxThZvLUAafmZb8OAxFb8XXtiQmS35INgr85hdOGoEs124ez1FCnZJt6jau/T+alh58QFQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"is-regex": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/is-regex/-/is-regex-1.1.4.tgz",
"integrity": "sha512-kvRdxDsxZjhzUX07ZnLydzS1TU/TJlTUHHY4YLL87e37oUA49DfkLqgy+VjFocowy29cKvcSiu+kIv728jTTVg==",
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"dev": true,
"requires": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"call-bind": "^1.0.2",
"has-tostringtag": "^1.0.0"
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"is-regexp": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/is-regexp/-/is-regexp-2.1.0.tgz",
"integrity": "sha512-OZ4IlER3zmRIoB9AqNhEggVxqIH4ofDns5nRrPS6yQxXE1TPCUpFznBfRQmQa8uC+pXqjMnukiJBxCisIxiLGA==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"is-relative": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-relative/-/is-relative-1.0.0.tgz",
"integrity": "sha512-Kw/ReK0iqwKeu0MITLFuj0jbPAmEiOsIwyIXvvbfa6QfmN9pkD1M+8pdk7Rl/dTKbH34/XBFMbgD4iMJhLQbGA==",
"dev": true,
"requires": {
"is-unc-path": "^1.0.0"
}
},
Update npm packages
2021-10-17 18:33:19 +09:00
"is-shared-array-buffer": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/is-shared-array-buffer/-/is-shared-array-buffer-1.0.1.tgz",
"integrity": "sha512-IU0NmyknYZN0rChcKhRO1X8LYz5Isj/Fsqh8NJOSf+N/hCOTwy29F32Ik7a+QszE63IdvmwdTPDd6cZ5pg4cwA==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"is-stream": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/is-stream/-/is-stream-1.1.0.tgz",
"integrity": "sha1-EtSj3U5o4Lec6428hBc66A2RykQ=",
"dev": true
},
Update `npm` packages
2020-01-31 22:04:49 +09:00
"is-string": {
Update npm packages
2021-08-22 17:38:52 +09:00
"version": "1.0.7",
"resolved": "https://registry.npmjs.org/is-string/-/is-string-1.0.7.tgz",
"integrity": "sha512-tE2UXzivje6ofPW7l23cjDOMa09gb7xlAqG6jG5ej6uPV32TlWP3NKPigtaGeHNu9fohccRYvIiZMfOOnOYUtg==",
"dev": true,
"requires": {
"has-tostringtag": "^1.0.0"
}
Update `npm` packages
2020-01-31 22:04:49 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"is-symbol": {
Update npm packages
2021-05-16 17:05:58 +09:00
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/is-symbol/-/is-symbol-1.0.4.tgz",
"integrity": "sha512-C/CPBqKWnvdcxqIARxyOh4v1UUEOCHpgDa0WYgpKDFMszcrPcffg5uhwSgPCLD2WWxmq6isisz87tzT01tuGhg==",
"dev": true,
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"requires": {
Update npm packages
2021-05-16 17:05:58 +09:00
"has-symbols": "^1.0.2"
Update `npm` packages
2019-12-19 19:28:13 +09:00
},
"dependencies": {
"has-symbols": {
Update npm packages
2021-05-16 17:05:58 +09:00
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.2.tgz",
"integrity": "sha512-chXa79rL/UC2KlX17jo3vRGz0azaWEx5tGqZg5pO3NUyEJVB17dMruQlzCCOfUvElghKcm5194+BCRvi2Rv/Gw==",
"dev": true
Update `npm` packages
2019-12-19 19:28:13 +09:00
}
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"is-unc-path": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-unc-path/-/is-unc-path-1.0.0.tgz",
"integrity": "sha512-mrGpVd0fs7WWLfVsStvgF6iEJnbjDFZh9/emhRDcGWTduTfNHd9CHeUwH3gYIjdbwo4On6hunkztwOaAw0yllQ==",
"dev": true,
"requires": {
"unc-path-regex": "^0.1.2"
}
},
"is-utf8": {
"version": "0.2.1",
"resolved": "https://registry.npmjs.org/is-utf8/-/is-utf8-0.2.1.tgz",
"integrity": "sha1-Sw2hRCEE0bM2NA6AeX6GXPOffXI=",
"dev": true
},
"is-valid-glob": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-valid-glob/-/is-valid-glob-1.0.0.tgz",
"integrity": "sha1-Kb8+/3Ab4tTTFdusw5vDn+j2Aao=",
"dev": true
},
Update npm packages
2021-10-17 18:33:19 +09:00
"is-weakref": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/is-weakref/-/is-weakref-1.0.1.tgz",
"integrity": "sha512-b2jKc2pQZjaeFYWEf7ScFj+Be1I+PXmlu572Q8coTXZ+LD/QQZ7ShPMst8h16riVgyXTQwUsFEl74mDvc/3MHQ==",
"dev": true,
"requires": {
"call-bind": "^1.0.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"is-windows": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/is-windows/-/is-windows-1.0.2.tgz",
"integrity": "sha512-eXK1UInq2bPmjyX6e3VHIzMLobc4J94i4AWn+Hpq3OU5KkrRC96OAcR3PRJ/pGu6m8TRnBHP9dkXQVsT/COVIA==",
"dev": true
},
"isarray": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz",
"integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=",
"dev": true
},
"isexe": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz",
"integrity": "sha1-6PvzdNxVb/iUehDcsFctYz8s+hA=",
"dev": true
},
"isobject": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/isobject/-/isobject-3.0.1.tgz",
"integrity": "sha1-TkMekrEalzFjaqH5yNHMvP2reN8=",
"dev": true
},
"isstream": {
"version": "0.1.2",
"resolved": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz",
"integrity": "sha1-R+Y/evVa+m+S4VAOaQ64uFKcCZo=",
"dev": true
},
"istextorbinary": {
Update npm packages
2021-05-02 16:30:09 +09:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/istextorbinary/-/istextorbinary-3.3.0.tgz",
"integrity": "sha512-Tvq1W6NAcZeJ8op+Hq7tdZ434rqnMx4CCZ7H0ff83uEloDvVbqAwaMTZcafKGJT0VHkYzuXUiCY4hlXQg6WfoQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-02 16:30:09 +09:00
"binaryextensions": "^2.2.0",
"textextensions": "^3.2.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"jasmine": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "4.0.2",
"resolved": "https://registry.npmjs.org/jasmine/-/jasmine-4.0.2.tgz",
"integrity": "sha512-YsrgxJQEggxzByYe4j68eQLOiQeSrPDYGv4sHhGBp3c6HHdq+uPXeAQ73kOAQpdLZ3/0zN7x/TZTloqeE1/qIA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-10-18 17:57:52 +09:00
"glob": "^7.1.6",
Update Jasmine to version 4 For the unit-tests that were updated in this patch, note that I settled on simply using `toEqual` comparisons rather than updating the custom matchers (since those don't seem necessary any more). Please refer to the following resources for additional information: - https://github.com/jasmine/jasmine/blob/main/release_notes/4.0.0.md - https://github.com/jasmine/jasmine-npm/blob/main/release_notes/4.0.0.md - https://jasmine.github.io/tutorials/upgrading_to_Jasmine_4.0
2022-01-09 18:27:06 +09:00
"jasmine-core": "^4.0.0"
Update `npm` packages
2020-10-18 17:57:52 +09:00
},
"dependencies": {
"glob": {
Update npm packages
2021-10-17 18:33:19 +09:00
"version": "7.2.0",
"resolved": "https://registry.npmjs.org/glob/-/glob-7.2.0.tgz",
"integrity": "sha512-lmLf6gtyrPq8tTjSmrO94wBeQbFR3HbLHbuyD69wuyQkImp2hWqMGB47OX65FBkPffO641IP9jWa1z4ivqG26Q==",
Update `npm` packages
2020-10-18 17:57:52 +09:00
"dev": true,
"requires": {
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
"minimatch": "^3.0.4",
"once": "^1.3.0",
"path-is-absolute": "^1.0.0"
}
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"jasmine-core": {
Update Jasmine to version 4 For the unit-tests that were updated in this patch, note that I settled on simply using `toEqual` comparisons rather than updating the custom matchers (since those don't seem necessary any more). Please refer to the following resources for additional information: - https://github.com/jasmine/jasmine/blob/main/release_notes/4.0.0.md - https://github.com/jasmine/jasmine-npm/blob/main/release_notes/4.0.0.md - https://jasmine.github.io/tutorials/upgrading_to_Jasmine_4.0
2022-01-09 18:27:06 +09:00
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/jasmine-core/-/jasmine-core-4.0.0.tgz",
"integrity": "sha512-tq24OCqHElgU9KDpb/8O21r1IfotgjIzalfW9eCmRR40LZpvwXT68iariIyayMwi0m98RDt16aljdbwK0sBMmQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"jest-worker": {
Update npm packages
2021-10-31 17:38:18 +09:00
"version": "27.3.1",
"resolved": "https://registry.npmjs.org/jest-worker/-/jest-worker-27.3.1.tgz",
"integrity": "sha512-ks3WCzsiZaOPJl/oMsDjaf0TRiSv7ctNgs0FqRr2nARsovz6AWWy4oLElwcquGSz692DzgZQrCLScPNs5YlC4g==",
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"dev": true,
"requires": {
"@types/node": "*",
"merge-stream": "^2.0.0",
Update npm packages
2021-06-27 17:25:40 +09:00
"supports-color": "^8.0.0"
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
},
"dependencies": {
"has-flag": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz",
"integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==",
"dev": true
},
"supports-color": {
Update npm packages
2021-06-27 17:25:40 +09:00
"version": "8.1.1",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-8.1.1.tgz",
"integrity": "sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q==",
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"dev": true,
"requires": {
"has-flag": "^4.0.0"
}
}
}
},
Update packages
2018-11-25 05:00:22 +09:00
"js-stringify": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/js-stringify/-/js-stringify-1.0.2.tgz",
"integrity": "sha1-Fzb939lyTyijaCrcYjCufk6Weds=",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"js-tokens": {
Update packages
2018-12-23 00:00:53 +09:00
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/js-tokens/-/js-tokens-4.0.0.tgz",
"integrity": "sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"js-yaml": {
Bump js-yaml from 3.12.0 to 3.13.1 Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 3.12.0 to 3.13.1. - [Release notes](https://github.com/nodeca/js-yaml/releases) - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](https://github.com/nodeca/js-yaml/compare/3.12.0...3.13.1) Signed-off-by: dependabot[bot] <support@github.com>
2019-07-19 09:04:03 +09:00
"version": "3.13.1",
"resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.13.1.tgz",
"integrity": "sha512-YfbcO7jXDdyj0DGxYVSlSeQNHbD7XPWvrVWeVUujrQEoZzWJIRrCPoyk6kL6IAjAG2IolMK4T0hNUe0HOUs5Jw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"argparse": "^1.0.7",
"esprima": "^4.0.0"
}
},
"js2xmlparser": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "4.0.2",
"resolved": "https://registry.npmjs.org/js2xmlparser/-/js2xmlparser-4.0.2.tgz",
"integrity": "sha512-6n4D8gLlLf1n5mNLQPRfViYzu9RATblzPEtm1SthMX1Pjao0r9YI9nw7ZIfRxQMERS87mcswrg+r/OYrPRX6jA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-23 18:58:15 +09:00
"xmlcreate": "^2.0.4"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"jsdoc": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "3.6.10",
"resolved": "https://registry.npmjs.org/jsdoc/-/jsdoc-3.6.10.tgz",
"integrity": "sha512-IdQ8ppSo5LKZ9o3M+LKIIK8i00DIe5msDvG3G81Km+1dhy0XrOWD0Ji8H61ElgyEj/O9KRLokgKbAM9XX9CJAg==",
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-04-18 18:08:46 +09:00
"@babel/parser": "^7.9.4",
Update npm packages
2022-01-23 18:58:15 +09:00
"@types/markdown-it": "^12.2.3",
Update `npm` packages
2020-04-18 18:08:46 +09:00
"bluebird": "^3.7.2",
Update npm packages
2021-05-16 17:05:58 +09:00
"catharsis": "^0.9.0",
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"escape-string-regexp": "^2.0.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"js2xmlparser": "^4.0.2",
"klaw": "^4.0.1",
"markdown-it": "^12.3.2",
"markdown-it-anchor": "^8.4.1",
"marked": "^4.0.10",
Update `npm` packages
2020-04-18 18:08:46 +09:00
"mkdirp": "^1.0.4",
Update packages
2019-08-25 03:08:09 +09:00
"requizzle": "^0.2.3",
Update `npm` packages
2020-04-18 18:08:46 +09:00
"strip-json-comments": "^3.1.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"taffydb": "2.6.2",
Update npm packages
2022-01-23 18:58:15 +09:00
"underscore": "~1.13.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
Update npm packages
2022-01-23 18:58:15 +09:00
"argparse": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/argparse/-/argparse-2.0.1.tgz",
"integrity": "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==",
"dev": true
},
Update `npm` packages
2020-04-18 18:08:46 +09:00
"entities": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/entities/-/entities-2.1.0.tgz",
"integrity": "sha512-hCx1oky9PFrJ611mf0ifBLBRW8lUUVRlFolb5gWRfIELabBlbp9xZvrqZLZAs+NxFnbfQoeGd8wDkygjg7U85w==",
Update `npm` packages
2020-04-18 18:08:46 +09:00
"dev": true
},
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"escape-string-regexp": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-2.0.0.tgz",
"integrity": "sha512-UpzcLCXolUWcNu5HtVMHYdXJjArjsF9C0aNnquZYY4uW/Vu0miy5YoWvbV345HauVvcAUnpRuhMMcqTcGOY2+w==",
"dev": true
},
Update npm packages
2022-01-23 18:58:15 +09:00
"linkify-it": {
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/linkify-it/-/linkify-it-3.0.3.tgz",
"integrity": "sha512-ynTsyrFSdE5oZ/O9GEf00kPngmOfVwazR5GKDq6EYfhlpFug3J2zybX56a2PRRpc9P+FuSoGNAwjlbDs9jJBPQ==",
"dev": true,
"requires": {
"uc.micro": "^1.0.1"
}
},
Update `npm` packages
2020-04-18 18:08:46 +09:00
"markdown-it": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "12.3.2",
"resolved": "https://registry.npmjs.org/markdown-it/-/markdown-it-12.3.2.tgz",
"integrity": "sha512-TchMembfxfNVpHkbtriWltGWc+m3xszaRD0CZup7GFFhzIgQqxIfn3eGj1yZpfuflzPvfkt611B2Q/Bsk1YnGg==",
Update the `mkdirp` package, since its major version was increased
2020-04-02 19:18:23 +09:00
"dev": true,
"requires": {
Update npm packages
2022-01-23 18:58:15 +09:00
"argparse": "^2.0.1",
"entities": "~2.1.0",
"linkify-it": "^3.0.1",
Update `npm` packages
2020-04-18 18:08:46 +09:00
"mdurl": "^1.0.1",
"uc.micro": "^1.0.5"
Update the `mkdirp` package, since its major version was increased
2020-04-02 19:18:23 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
},
Update packages
2018-12-23 00:00:53 +09:00
"jsesc": {
"version": "2.5.2",
"resolved": "https://registry.npmjs.org/jsesc/-/jsesc-2.5.2.tgz",
"integrity": "sha512-OYu7XEzjkCQ3C5Ps3QIZsQfNpqoJyZZA99wd9aWd05NCtC5pWOkShK2mkL6HXQR6/Cy2lbNdPlZBpuQHXE63gA==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"json-parse-better-errors": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/json-parse-better-errors/-/json-parse-better-errors-1.0.2.tgz",
"integrity": "sha512-mrqyZKfX5EhL7hvqcV6WG1yYjnjeuYDzDhhcAAUrq8Po85NBQBJP+ZDUT75qZQ98IkUoBqdkExkukOU7Ts2wrw==",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"json-parse-even-better-errors": {
Update `npm` packages
2020-09-06 18:49:49 +09:00
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/json-parse-even-better-errors/-/json-parse-even-better-errors-2.3.1.tgz",
"integrity": "sha512-xyFwyhro/JEof6Ghe2iz2NcXoj2sloNsWr/XsERDK/oiPCfaNhl5ONfp+jQdAZRQQ0IJWNzH9zIZF7li91kh2w==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true
},
Update `npm` packages
2019-12-29 03:57:25 +09:00
"json-schema-traverse": {
"version": "0.4.1",
"resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz",
"integrity": "sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"json-stable-stringify-without-jsonify": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/json-stable-stringify-without-jsonify/-/json-stable-stringify-without-jsonify-1.0.1.tgz",
"integrity": "sha1-nbe1lJatPzz+8wp1FC0tkwrXJlE=",
"dev": true
},
"json5": {
Update `npm` packages
2021-04-18 18:02:42 +09:00
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/json5/-/json5-2.2.0.tgz",
"integrity": "sha512-f+8cldu7X/y7RAJurMEJmdoKXGB/X550w2Nr3tTbezL6RwEE/iMcm+tZnXeoZtKuOq6ft8+CqzEkrIgx1fPoQA==",
Update `npm` packages
2020-04-02 19:13:14 +09:00
"dev": true,
"requires": {
"minimist": "^1.2.5"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Add basic linting of JSON files using `eslint-plugin-json` By adding basic linting of JSON files, we can ensure that they're actually valid and prevent e.g. test-failures caused by *accidental* errors when editing the `test/test_manifest.json` file (something that I've done *many* times myself). For now this simply uses the `recommended` configuration, but we can obviously tweak this later if/when needed. Please find additional information at https://github.com/azeemba/eslint-plugin-json
2021-06-15 18:59:47 +09:00
"jsonc-parser": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/jsonc-parser/-/jsonc-parser-3.0.0.tgz",
"integrity": "sha512-fQzRfAbIBnR0IQvftw9FJveWiHp72Fg20giDrHz6TdfB12UH/uue0D3hm57UB5KgAVuniLMCaS8P1IMj9NR7cA==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"jstransformer": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/jstransformer/-/jstransformer-1.0.0.tgz",
"integrity": "sha1-7Yvwkh4vPx7U1cGkT2hwntJHIsM=",
"dev": true,
"requires": {
"is-promise": "^2.0.0",
"promise": "^7.0.1"
}
},
Include forgotten changes after Wintersmith update This should have been part of the previous commit that updated the Wintersmith dependency. Markdown support is no longer included in Pug itself and should be done by a transformer instead.
2018-11-25 05:39:54 +09:00
"jstransformer-markdown-it": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/jstransformer-markdown-it/-/jstransformer-markdown-it-2.1.0.tgz",
"integrity": "sha1-aewwzkUYvtWZezjwJ2SOjChekvc=",
Update eslint-plugin-mozilla to ^1.0.1
2018-11-23 22:40:05 +09:00
"dev": true,
Include forgotten changes after Wintersmith update This should have been part of the previous commit that updated the Wintersmith dependency. Markdown support is no longer included in Pug itself and should be done by a transformer instead.
2018-11-25 05:39:54 +09:00
"requires": {
"markdown-it": "^8.0.0"
}
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"just-debounce": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/just-debounce/-/just-debounce-1.0.0.tgz",
"integrity": "sha1-h/zPrv/AtozRnVX2cilD+SnqNeo=",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"keypress": {
"version": "0.1.0",
"resolved": "https://registry.npmjs.org/keypress/-/keypress-0.1.0.tgz",
"integrity": "sha1-SjGI1CkbZrT2XtuZ+AaqmuKTWSo=",
"dev": true
},
"kind-of": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "6.0.3",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-6.0.3.tgz",
"integrity": "sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"klaw": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/klaw/-/klaw-4.0.1.tgz",
"integrity": "sha512-pgsE40/SvC7st04AHiISNewaIMUbY5V/K8b21ekiPiFoYs/EYSdsGa+FJArB1d441uq4Q8zZyIxvAzkGNlBdRw==",
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"known-css-properties": {
Update npm packages
2021-12-26 19:09:29 +09:00
"version": "0.24.0",
"resolved": "https://registry.npmjs.org/known-css-properties/-/known-css-properties-0.24.0.tgz",
"integrity": "sha512-RTSoaUAfLvpR357vWzAz/50Q/BmHfmE6ETSWfutT0AJiw10e6CmcdYRQJlLRd95B53D0Y2aD1jSxD3V3ySF+PA==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"kuler": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/kuler/-/kuler-1.0.1.tgz",
"integrity": "sha512-J9nVUucG1p/skKul6DU3PUZrhs0LPulNaeUOox0IyXDi8S4CztTHs1gQphhuZmzXG7VOQSf6NJfKuzteQLv9gQ==",
"dev": true,
"requires": {
"colornames": "^1.1.1"
}
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"last-run": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/last-run/-/last-run-1.1.1.tgz",
"integrity": "sha1-RblpQsF7HHnHchmCWbqUO+v4yls=",
"dev": true,
"requires": {
"default-resolution": "^2.0.0",
"es6-weak-map": "^2.0.1"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"lazy-cache": {
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/lazy-cache/-/lazy-cache-1.0.4.tgz",
"integrity": "sha1-odePw6UEdMuAhF07O24dpJpEbo4=",
"dev": true
},
"lazystream": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/lazystream/-/lazystream-1.0.0.tgz",
"integrity": "sha1-9plf4PggOS9hOWvolGJAe7dxaOQ=",
"dev": true,
"requires": {
"readable-stream": "^2.0.5"
}
},
"lcid": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/lcid/-/lcid-1.0.0.tgz",
"integrity": "sha1-MIrMr6C8SDo4Z7S28rlQYlHRuDU=",
"dev": true,
"requires": {
"invert-kv": "^1.0.0"
}
},
"lead": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/lead/-/lead-1.0.0.tgz",
"integrity": "sha1-bxT5mje+Op3XhPVJVpDlkDRm7kI=",
"dev": true,
"requires": {
"flush-write-stream": "^1.0.2"
}
},
"levn": {
"version": "0.3.0",
"resolved": "https://registry.npmjs.org/levn/-/levn-0.3.0.tgz",
"integrity": "sha1-OwmSTt+fCDwEkP3UwLxEIeBHZO4=",
"dev": true,
"requires": {
"prelude-ls": "~1.1.2",
"type-check": "~0.3.2"
}
},
"liftoff": {
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/liftoff/-/liftoff-3.1.0.tgz",
"integrity": "sha512-DlIPlJUkCV0Ips2zf2pJP0unEoT1kwYhiiPUGF3s/jtxTCjziNLoiVVh+jqWOWeFi6mmwQ5fNxvAUyPad4Dfog==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"extend": "^3.0.0",
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"findup-sync": "^3.0.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"fined": "^1.0.1",
"flagged-respawn": "^1.0.0",
"is-plain-object": "^2.0.4",
"object.map": "^1.0.0",
"rechoir": "^0.6.2",
"resolve": "^1.1.7"
}
},
Update npm packages
2021-09-05 16:47:57 +09:00
"lilconfig": {
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/lilconfig/-/lilconfig-2.0.3.tgz",
"integrity": "sha512-EHKqr/+ZvdKCifpNrJCKxBTgk5XupZA3y/aCPY9mxfgBzmgh93Mt/WqjjQ38oMxXuvDokaKiM3lAgvSH2sjtHg==",
"dev": true
},
Update ESLint to version 7 Please see https://eslint.org/blog/2020/05/eslint-v7.0.0-released for a list of notable changes.
2020-05-10 18:32:46 +09:00
"lines-and-columns": {
"version": "1.1.6",
"resolved": "https://registry.npmjs.org/lines-and-columns/-/lines-and-columns-1.1.6.tgz",
"integrity": "sha1-HADHQ7QzzQpOgHWPe2SldEDZ/wA=",
"dev": true
},
Include forgotten changes after Wintersmith update This should have been part of the previous commit that updated the Wintersmith dependency. Markdown support is no longer included in Pug itself and should be done by a transformer instead.
2018-11-25 05:39:54 +09:00
"linkify-it": {
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/linkify-it/-/linkify-it-2.0.3.tgz",
"integrity": "sha1-2UpGSPmxwXnWT6lykSaL22zpQ08=",
Update eslint-plugin-mozilla to ^1.0.1
2018-11-23 22:40:05 +09:00
"dev": true,
Include forgotten changes after Wintersmith update This should have been part of the previous commit that updated the Wintersmith dependency. Markdown support is no longer included in Pug itself and should be done by a transformer instead.
2018-11-25 05:39:54 +09:00
"requires": {
"uc.micro": "^1.0.1"
}
},
Update `npm` packages
2019-12-29 03:57:25 +09:00
"loader-runner": {
Update `npm` packages
2021-01-10 19:25:47 +09:00
"version": "4.2.0",
"resolved": "https://registry.npmjs.org/loader-runner/-/loader-runner-4.2.0.tgz",
"integrity": "sha512-92+huvxMvYlMzMt0iIOukcwYBFpkYJdpl2xsZ7LrlayO7E8SOv+JJUEK17B/dJIHAOLMfh2dZZ/Y18WgmGtYNw==",
Update `npm` packages
2019-12-29 03:57:25 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"loader-utils": {
Update `npm` packages
2020-04-02 19:13:14 +09:00
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/loader-utils/-/loader-utils-1.4.0.tgz",
"integrity": "sha512-qH0WSMBtn/oHuwjy/NucEgbx5dbxxnxup9s4PVXJUDHZBQY+s0NWA9rJf53RBnQZxfch7euUui7hpoAPvALZdA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-04-02 19:13:14 +09:00
"big.js": "^5.2.2",
"emojis-list": "^3.0.0",
"json5": "^1.0.1"
},
"dependencies": {
"json5": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/json5/-/json5-1.0.1.tgz",
"integrity": "sha512-aKS4WQjPenRxiQsC93MNfjx+nbF4PAdYzmd/1JIj8HYzqfbu86beTuNgXDzPknWk0n0uARlyewZo4s++ES36Ow==",
"dev": true,
"requires": {
"minimist": "^1.2.0"
}
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"locate-path": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/locate-path/-/locate-path-2.0.0.tgz",
"integrity": "sha1-K1aLJl7slExtnA3pw9u7ygNUzY4=",
"dev": true,
"requires": {
"p-locate": "^2.0.0",
"path-exists": "^3.0.0"
}
},
"lodash": {
Bump lodash from 4.17.19 to 4.17.21 Bumps [lodash](https://github.com/lodash/lodash) from 4.17.19 to 4.17.21. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](https://github.com/lodash/lodash/compare/4.17.19...4.17.21) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-07 19:54:18 +09:00
"version": "4.17.21",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz",
"integrity": "sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"lodash.clone": {
"version": "4.5.0",
"resolved": "https://registry.npmjs.org/lodash.clone/-/lodash.clone-4.5.0.tgz",
"integrity": "sha1-GVhwRQ9aExkkeN9Lw9I9LeoZB7Y=",
"dev": true
},
Update `npm` packages
2021-03-07 20:00:57 +09:00
"lodash.debounce": {
"version": "4.0.8",
"resolved": "https://registry.npmjs.org/lodash.debounce/-/lodash.debounce-4.0.8.tgz",
"integrity": "sha1-gteb/zCmfEAF/9XiUVMArZyk168=",
"dev": true
},
Update npm packages
2021-05-30 14:43:13 +09:00
"lodash.merge": {
"version": "4.6.2",
"resolved": "https://registry.npmjs.org/lodash.merge/-/lodash.merge-4.6.2.tgz",
"integrity": "sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"lodash.some": {
"version": "4.6.0",
"resolved": "https://registry.npmjs.org/lodash.some/-/lodash.some-4.6.0.tgz",
"integrity": "sha1-G7nzFO9ri63tE7VJFpsqlF62jk0=",
"dev": true
},
Update npm packages
2021-05-02 16:30:09 +09:00
"lodash.truncate": {
"version": "4.4.2",
"resolved": "https://registry.npmjs.org/lodash.truncate/-/lodash.truncate-4.4.2.tgz",
"integrity": "sha1-WjUNoLERO4N+z//VgSy+WNbq4ZM=",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"logform": {
"version": "1.10.0",
"resolved": "https://registry.npmjs.org/logform/-/logform-1.10.0.tgz",
"integrity": "sha512-em5ojIhU18fIMOw/333mD+ZLE2fis0EzXl1ZwHx4iQzmpQi6odNiY/t+ITNr33JZhT9/KEaH+UPIipr6a9EjWg==",
"dev": true,
"requires": {
"colors": "^1.2.1",
"fast-safe-stringify": "^2.0.4",
"fecha": "^2.3.3",
"ms": "^2.1.1",
"triple-beam": "^1.2.0"
},
"dependencies": {
"ms": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.1.tgz",
"integrity": "sha512-tgp+dl5cGk28utYktBsrFqA7HKgrhgPsg6Z/EfhWI4gl1Hwq8B/GmY/0oXZ6nF8hDVesS/FpnYaD/kOWhYQvyg==",
"dev": true
}
}
},
"longest": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/longest/-/longest-1.0.1.tgz",
"integrity": "sha1-MKCy2jj3N3DoKUoNIuZiXtd9AJc=",
"dev": true
},
Update `npm` packages
2020-11-15 21:51:52 +09:00
"lru-cache": {
Update `npm` packages
2021-02-07 19:55:03 +09:00
"version": "6.0.0",
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-6.0.0.tgz",
"integrity": "sha512-Jo6dJ04CmSjuznwJSS3pUeWmd/H0ffTlkXXgwZi+eq1UCmqQwCh+eLsYOYCwY991i2Fah4h1BEMCx4qThGbsiA==",
Update `npm` packages
2020-11-15 21:51:52 +09:00
"dev": true,
"requires": {
Update `npm` packages
2021-02-07 19:55:03 +09:00
"yallist": "^4.0.0"
},
"dependencies": {
"yallist": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/yallist/-/yallist-4.0.0.tgz",
"integrity": "sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A==",
"dev": true
}
Update `npm` packages
2020-11-15 21:51:52 +09:00
}
},
Update npm packages
2021-10-31 17:38:18 +09:00
"make-dir": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/make-dir/-/make-dir-3.1.0.tgz",
"integrity": "sha512-g3FeP20LNwhALb/6Cz6Dd4F2ngze0jz7tbzrD2wAV+o9FeNHe4rL+yK2md0J/fiSf1sa1ADhXqi5+oVwOM/eGw==",
"dev": true,
"requires": {
"semver": "^6.0.0"
},
"dependencies": {
"semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
"dev": true
}
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"make-iterator": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/make-iterator/-/make-iterator-1.0.1.tgz",
"integrity": "sha512-pxiuXh0iVEq7VM7KMIhs5gxsfxCux2URptUQaXo4iZZJxBAzTPOLE2BumO5dbfVYq/hBJFBR/a1mFDmOx5AGmw==",
"dev": true,
"requires": {
"kind-of": "^6.0.2"
}
},
"map-cache": {
"version": "0.2.2",
"resolved": "https://registry.npmjs.org/map-cache/-/map-cache-0.2.2.tgz",
"integrity": "sha1-wyq9C9ZSXZsFFkW7TyasXcmKDb8=",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"map-obj": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/map-obj/-/map-obj-4.3.0.tgz",
"integrity": "sha512-hdN1wVrZbb29eBGiGjJbeP8JbKjq1urkHJ/LIP/NY48MZ1QVXUsQBV1G1zvYFHn1XE06cwjBsOI2K3Ulnj1YXQ==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"map-visit": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/map-visit/-/map-visit-1.0.0.tgz",
"integrity": "sha1-7Nyo8TFE5mDxtb1B8S80edmN+48=",
"dev": true,
"requires": {
"object-visit": "^1.0.0"
}
},
Include forgotten changes after Wintersmith update This should have been part of the previous commit that updated the Wintersmith dependency. Markdown support is no longer included in Pug itself and should be done by a transformer instead.
2018-11-25 05:39:54 +09:00
"markdown-it": {
"version": "8.4.2",
"resolved": "https://registry.npmjs.org/markdown-it/-/markdown-it-8.4.2.tgz",
"integrity": "sha512-GcRz3AWTqSUphY3vsUqQSFMbgR38a4Lh3GWlHRh/7MRwz8mcu9n2IO7HOh+bXHrR9kOPDl5RNCaEsrneb+xhHQ==",
Update eslint-plugin-mozilla to ^1.0.1
2018-11-23 22:40:05 +09:00
"dev": true,
Include forgotten changes after Wintersmith update This should have been part of the previous commit that updated the Wintersmith dependency. Markdown support is no longer included in Pug itself and should be done by a transformer instead.
2018-11-25 05:39:54 +09:00
"requires": {
"argparse": "^1.0.7",
"entities": "~1.1.1",
"linkify-it": "^2.0.0",
"mdurl": "^1.0.1",
"uc.micro": "^1.0.5"
}
},
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"markdown-it-anchor": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "8.4.1",
"resolved": "https://registry.npmjs.org/markdown-it-anchor/-/markdown-it-anchor-8.4.1.tgz",
"integrity": "sha512-sLODeRetZ/61KkKLJElaU3NuU2z7MhXf12Ml1WJMSdwpngeofneCRF+JBbat8HiSqhniOMuTemXMrsI7hA6XyA==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"requires": {}
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"marked": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "4.0.10",
"resolved": "https://registry.npmjs.org/marked/-/marked-4.0.10.tgz",
"integrity": "sha512-+QvuFj0nGgO970fySghXGmuw+Fd0gD2x3+MqCWLIPf5oxdv1Ka6b2q+z9RP01P/IaKPMEramy+7cNy/Lw8c3hw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"matchdep": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/matchdep/-/matchdep-2.0.0.tgz",
"integrity": "sha1-xvNINKDY28OzfCfui7yyfHd1WC4=",
"dev": true,
"requires": {
"findup-sync": "^2.0.0",
"micromatch": "^3.0.4",
"resolve": "^1.4.0",
"stack-trace": "0.0.10"
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
},
"dependencies": {
"findup-sync": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/findup-sync/-/findup-sync-2.0.0.tgz",
"integrity": "sha1-kyaxSIwi0aYIhlCoaQGy2akKLLw=",
"dev": true,
"requires": {
"detect-file": "^1.0.0",
"is-glob": "^3.1.0",
"micromatch": "^3.0.4",
"resolve-dir": "^1.0.1"
}
}
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"mathml-tag-names": {
"version": "2.1.3",
"resolved": "https://registry.npmjs.org/mathml-tag-names/-/mathml-tag-names-2.1.3.tgz",
"integrity": "sha512-APMBEanjybaPzUrfqU0IMU5I0AswKMH7k8OTLs0vvV4KZpExkTkY87nR/zpbuTPj+gARop7aGUbl11pnDfW6xg==",
"dev": true
},
Include forgotten changes after Wintersmith update This should have been part of the previous commit that updated the Wintersmith dependency. Markdown support is no longer included in Pug itself and should be done by a transformer instead.
2018-11-25 05:39:54 +09:00
"mdurl": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/mdurl/-/mdurl-1.0.1.tgz",
Update eslint-plugin-mozilla to ^1.0.1
2018-11-23 22:40:05 +09:00
"integrity": "sha1-/oWy7HWlkDfyrf7BAP1sYBdhFS4=",
"dev": true
Include forgotten changes after Wintersmith update This should have been part of the previous commit that updated the Wintersmith dependency. Markdown support is no longer included in Pug itself and should be done by a transformer instead.
2018-11-25 05:39:54 +09:00
},
Update `npm` packages
2020-11-15 21:51:52 +09:00
"memory-fs": {
"version": "0.5.0",
"resolved": "https://registry.npmjs.org/memory-fs/-/memory-fs-0.5.0.tgz",
"integrity": "sha512-jA0rdU5KoQMC0e6ppoNRtpp6vjFq6+NY7r8hywnC7V+1Xj/MtHwGIbB1QaK/dunyjWteJzmkpd7ooeWg10T7GA==",
"dev": true,
"requires": {
"errno": "^0.1.3",
"readable-stream": "^2.0.1"
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"meow": {
Update `npm` packages
2021-01-24 16:34:00 +09:00
"version": "9.0.0",
"resolved": "https://registry.npmjs.org/meow/-/meow-9.0.0.tgz",
"integrity": "sha512-+obSblOQmRhcyBt62furQqRAQpNyWXo8BuQ5bN7dG8wmwQ+vwHKp/rCFD4CrTP8CsDQD1sjoZ94K417XEUk8IQ==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true,
"requires": {
"@types/minimist": "^1.2.0",
"camelcase-keys": "^6.2.2",
Update `npm` packages
2021-01-24 16:34:00 +09:00
"decamelize": "^1.2.0",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"decamelize-keys": "^1.1.0",
"hard-rejection": "^2.1.0",
"minimist-options": "4.1.0",
Update `npm` packages
2020-11-29 17:43:20 +09:00
"normalize-package-data": "^3.0.0",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"read-pkg-up": "^7.0.1",
"redent": "^3.0.0",
"trim-newlines": "^3.0.0",
Update `npm` packages
2020-11-29 17:43:20 +09:00
"type-fest": "^0.18.0",
"yargs-parser": "^20.2.3"
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
},
"dependencies": {
Update `npm` packages
2020-11-29 17:43:20 +09:00
"hosted-git-info": {
Update npm packages
2021-05-02 16:30:09 +09:00
"version": "4.0.2",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-4.0.2.tgz",
"integrity": "sha512-c9OGXbZ3guC/xOlCg1Ci/VgWlwsqDv1yMQL1CWqXDL0hDjXuNcq0zuR4xqPSuasI3kqFDhqSyTjREz5gzq0fXg==",
Update `npm` packages
2020-11-29 17:43:20 +09:00
"dev": true,
"requires": {
"lru-cache": "^6.0.0"
}
},
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"is-core-module": {
"version": "2.8.0",
"resolved": "https://registry.npmjs.org/is-core-module/-/is-core-module-2.8.0.tgz",
"integrity": "sha512-vd15qHsaqrRL7dtH6QNuy0ndJmRDrS9HAM1CAiSifNUFv4x1a0CCVsj18hJ1mShxIG6T2i1sO78MkP56r0nYRw==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true,
"requires": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"has": "^1.0.3"
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
}
},
"normalize-package-data": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-3.0.3.tgz",
"integrity": "sha512-p2W1sgqij3zMMyRC067Dg16bfzVH+w7hyegmpIvZ4JNjqtGOVAIvLmjBx3yP7YTe9vKJgkoNOPjwQGogDoMXFA==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-02 16:30:09 +09:00
"hosted-git-info": "^4.0.1",
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"is-core-module": "^2.5.0",
Update npm packages
2021-05-02 16:30:09 +09:00
"semver": "^7.3.4",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"validate-npm-package-license": "^3.0.1"
}
},
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"semver": {
"version": "7.3.5",
"resolved": "https://registry.npmjs.org/semver/-/semver-7.3.5.tgz",
"integrity": "sha512-PoeGJYh8HK4BTO/a9Tf6ZG3veo/A7ZVsYrSA6J8ny9nb3B1VrpkuN+z9OE5wfE5p6H4LchYZsegiQgbJD94ZFQ==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true,
"requires": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"lru-cache": "^6.0.0"
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
}
},
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"type-fest": {
"version": "0.18.1",
"resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.18.1.tgz",
"integrity": "sha512-OIAYXk8+ISY+qTOwkHtKqzAuxchoMiD9Udx+FSGQDuiRR+PJKJHc2NJAXlbhkGwTt/4/nKZxELY1w3ReWOL8mw==",
Update `npm` packages
2020-11-29 17:43:20 +09:00
"dev": true
}
}
},
"merge-stream": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/merge-stream/-/merge-stream-2.0.0.tgz",
"integrity": "sha512-abv/qOcuPfk3URPfDzmZU1LKmuw8kT+0nIHvKrKgFrwifol/doWcdA4ZqsWQ8ENrFKkd67Mfpo/LovbIUsbt3w==",
"dev": true
},
"merge2": {
"version": "1.4.1",
"resolved": "https://registry.npmjs.org/merge2/-/merge2-1.4.1.tgz",
"integrity": "sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"micromatch": {
"version": "3.1.10",
"resolved": "https://registry.npmjs.org/micromatch/-/micromatch-3.1.10.tgz",
"integrity": "sha512-MWikgl9n9M3w+bpsY3He8L+w9eF9338xRl8IAO5viDizwSzziFEyUzo2xrrloB64ADbTf8uA8vRqqttDTOmccg==",
"dev": true,
"requires": {
"arr-diff": "^4.0.0",
"array-unique": "^0.3.2",
"braces": "^2.3.1",
"define-property": "^2.0.2",
"extend-shallow": "^3.0.2",
"extglob": "^2.0.4",
"fragment-cache": "^0.2.1",
"kind-of": "^6.0.2",
"nanomatch": "^1.2.9",
"object.pick": "^1.3.0",
"regex-not": "^1.0.0",
"snapdragon": "^0.8.1",
"to-regex": "^3.0.2"
}
},
"mime": {
Update packages
2018-11-25 05:00:22 +09:00
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/mime/-/mime-2.3.1.tgz",
"integrity": "sha512-OEUllcVoydBHGN1z84yfQDimn58pZNNNXgZlHXSboxMlFvgI6MXSWpWKpFRra7H1HxpVhHTkrghfRW49k6yjeg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"mime-db": {
Update npm packages
2021-11-14 18:17:30 +09:00
"version": "1.51.0",
"resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.51.0.tgz",
"integrity": "sha512-5y8A56jg7XVQx2mbv1lu49NR4dokRnhZYTtL+KGfaa27uq4pSTXkwQkFJl4pkRMyNFz/EtYDSkiiEHx3F7UN6g==",
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"dev": true
},
"mime-types": {
Update npm packages
2021-11-14 18:17:30 +09:00
"version": "2.1.34",
"resolved": "https://registry.npmjs.org/mime-types/-/mime-types-2.1.34.tgz",
"integrity": "sha512-6cP692WwGIs9XXdOO4++N+7qjqv0rqxxVvJ3VHPh/Sc9mVZcQP+ZGhkKiTvWMQRr2tbHkJP/Yn7Y0npb3ZBs4A==",
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"dev": true,
"requires": {
Update npm packages
2021-11-14 18:17:30 +09:00
"mime-db": "1.51.0"
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
}
},
Update the `canvas` npm package to fix Travis CI builds (issue 10790)
2019-05-08 16:55:26 +09:00
"mimic-response": {
Update `npm` packages
2021-03-07 20:00:57 +09:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/mimic-response/-/mimic-response-2.1.0.tgz",
"integrity": "sha512-wXqjST+SLt7R009ySCglWBCFpjUygmCIfD790/kVbiGmUgfYGuB14PiTd5DwVxSV4NcYHjzMkoj5LjQZwTQLEA==",
Update the `canvas` npm package to fix Travis CI builds (issue 10790)
2019-05-08 16:55:26 +09:00
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"min-indent": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/min-indent/-/min-indent-1.0.1.tgz",
"integrity": "sha512-I9jwMn07Sy/IwOj3zVkVik2JTvgpaykDZEigL6Rx6N9LbMywwUSMtxET+7lVoDLLd3O3IXwJwvuuns8UB/HeAg==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"minimatch": {
"version": "3.0.4",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz",
"integrity": "sha512-yJHVQEhyqPLUTgt9B83PXu6W3rx4MvvHvSUvToogpwoGDOUQ+yDrR0HRot+yOCdCO7u4hX3pWft6kWBBcqh0UA==",
"dev": true,
"requires": {
"brace-expansion": "^1.1.7"
}
},
"minimist": {
Update `npm` packages
2020-03-19 17:55:14 +09:00
"version": "1.2.5",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz",
"integrity": "sha512-FM9nNUYrRBAELZQT3xeZQ7fmMOBg6nWNmJKTcgsJeaLstP/UODVpGsr5OhXhhXg6f+qtJ8uiZ+PUxkDWcgIXLw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"minimist-options": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/minimist-options/-/minimist-options-4.1.0.tgz",
"integrity": "sha512-Q4r8ghd80yhO/0j1O3B2BjweX3fiHg9cdOwjJd2J76Q135c+NDxGCqdYKQ1SKBuFfgWbAUzBfvYjPUEeNgqN1A==",
"dev": true,
"requires": {
"arrify": "^1.0.1",
"is-plain-obj": "^1.1.0",
"kind-of": "^6.0.3"
}
},
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"minipass": {
Update npm packages
2021-05-30 14:43:13 +09:00
"version": "3.1.3",
"resolved": "https://registry.npmjs.org/minipass/-/minipass-3.1.3.tgz",
"integrity": "sha512-Mgd2GdMVzY+x3IJ+oHnVM+KG3lA5c8tnabyJKmHSaG2kAGpudxuOf8ToDkhumF7UzME7DecbQE9uOZhNm7PuJg==",
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-30 14:43:13 +09:00
"yallist": "^4.0.0"
},
"dependencies": {
"yallist": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/yallist/-/yallist-4.0.0.tgz",
"integrity": "sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A==",
"dev": true
}
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
}
},
"minizlib": {
Update npm packages
2021-05-30 14:43:13 +09:00
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/minizlib/-/minizlib-2.1.2.tgz",
"integrity": "sha512-bAxsR8BVfj60DWXHE3u30oHzfl4G7khkSuPW+qvpd7jFRHm7dLxOjUk1EHACJ/hxLY8phGJ0YhYHZo7jil7Qdg==",
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-30 14:43:13 +09:00
"minipass": "^3.0.0",
"yallist": "^4.0.0"
},
"dependencies": {
"yallist": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/yallist/-/yallist-4.0.0.tgz",
"integrity": "sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A==",
"dev": true
}
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"mixin-deep": {
Bump mixin-deep from 1.3.1 to 1.3.2 Bumps [mixin-deep](https://github.com/jonschlinkert/mixin-deep) from 1.3.1 to 1.3.2. - [Release notes](https://github.com/jonschlinkert/mixin-deep/releases) - [Commits](https://github.com/jonschlinkert/mixin-deep/compare/1.3.1...1.3.2) Signed-off-by: dependabot[bot] <support@github.com>
2019-08-28 09:33:12 +09:00
"version": "1.3.2",
"resolved": "https://registry.npmjs.org/mixin-deep/-/mixin-deep-1.3.2.tgz",
"integrity": "sha512-WRoDn//mXBiJ1H40rqa3vH0toePwSsGb45iInWlTySa+Uu4k3tYUSxa2v1KqAiLtvlrSzaExqS1gtk96A9zvEA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"for-in": "^1.0.2",
"is-extendable": "^1.0.1"
},
"dependencies": {
"is-extendable": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/is-extendable/-/is-extendable-1.0.1.tgz",
"integrity": "sha512-arnXMxT1hhoKo9k1LZdmlNyJdDDfy2v0fXjFlmok4+i8ul/6WlbVge9bhM74OpNPQPMGUToDtz+KXa1PneJxOA==",
"dev": true,
"requires": {
"is-plain-object": "^2.0.4"
}
}
}
},
"mkdirp": {
Update `npm` packages
2020-04-18 18:08:46 +09:00
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-1.0.4.tgz",
"integrity": "sha512-vVqVZQyf3WLx2Shd0qJ9xuvqgAyKPLAiqITEtqW0oIUjzo3PePDd6fW9iFz30ef7Ysp/oiWqbhszeGWW2T6Gzw==",
Update the `mkdirp` package, since its major version was increased
2020-04-02 19:18:23 +09:00
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"mkdirp-classic": {
"version": "0.5.3",
"resolved": "https://registry.npmjs.org/mkdirp-classic/-/mkdirp-classic-0.5.3.tgz",
"integrity": "sha512-gKLcREMhtuZRwRAfqP3RFW+TK4JqApVBtOIftVgjuABpAtpxhPGaDcfvbhNvD0B8iD1oUr/txX35NjcaY6Ns/A==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"ms": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.0.0.tgz",
"integrity": "sha1-VgiurfwAvmwpAd9fmGF4jeDVl8g=",
"dev": true
},
Update `npm` packages
2020-07-26 18:15:21 +09:00
"multi-ini": {
Update `npm` packages
2021-04-18 18:02:42 +09:00
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/multi-ini/-/multi-ini-2.1.2.tgz",
"integrity": "sha512-m7G4SF3bo/VM+iyeiIlCvBVD0GY2NQ/PHh+H6y3sEYaRJ3fFeKo5/6e0O15B17+KpqDZ9ia+JBo8d7ZUYiEucw==",
Update `npm` packages
2020-07-26 18:15:21 +09:00
"dev": true,
"requires": {
"lodash": "^4.0.0"
}
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"mute-stdout": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/mute-stdout/-/mute-stdout-1.0.1.tgz",
"integrity": "sha512-kDcwXR4PS7caBpuRYYBUz9iVixUk3anO3f5OYFiIPwK/20vCzKCHyKoulbiDY1S53zD2bxUpxN/IJ+TnXjfvxg==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"nan": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "2.15.0",
"resolved": "https://registry.npmjs.org/nan/-/nan-2.15.0.tgz",
"integrity": "sha512-8ZtvEnA2c5aYCZYd1cvgdnU6cqwixRoYg70xPLWUws5ORTa/lnw+u4amixRS/Ac5U5mQVgp9pnlSUnbNWFaWZQ==",
Update `npm` packages
2019-12-29 03:57:25 +09:00
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"nanoid": {
Bump nanoid from 3.1.30 to 3.2.0 Bumps [nanoid](https://github.com/ai/nanoid) from 3.1.30 to 3.2.0. - [Release notes](https://github.com/ai/nanoid/releases) - [Changelog](https://github.com/ai/nanoid/blob/main/CHANGELOG.md) - [Commits](https://github.com/ai/nanoid/compare/3.1.30...3.2.0) --- updated-dependencies: - dependency-name: nanoid dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-28 06:38:28 +09:00
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.2.0.tgz",
"integrity": "sha512-fmsZYa9lpn69Ad5eDn7FMcnnSR+8R34W9qJEijxYhTbfOWzr22n1QxCMzXLK+ODyW2973V3Fux959iQoUxzUIA==",
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"nanomatch": {
"version": "1.2.9",
"resolved": "https://registry.npmjs.org/nanomatch/-/nanomatch-1.2.9.tgz",
"integrity": "sha512-n8R9bS8yQ6eSXaV6jHUpKzD8gLsin02w1HSFiegwrs9E098Ylhw5jdyKPaYqvHknHaSCKTPp7C8dGCQ0q9koXA==",
"dev": true,
"requires": {
"arr-diff": "^4.0.0",
"array-unique": "^0.3.2",
"define-property": "^2.0.2",
"extend-shallow": "^3.0.2",
"fragment-cache": "^0.2.1",
"is-odd": "^2.0.0",
"is-windows": "^1.0.2",
"kind-of": "^6.0.2",
"object.pick": "^1.3.0",
"regex-not": "^1.0.0",
"snapdragon": "^0.8.1",
"to-regex": "^3.0.1"
}
},
"natural-compare": {
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/natural-compare/-/natural-compare-1.4.0.tgz",
"integrity": "sha1-Sr6/7tdUHywnrPspvbvRXI1bpPc=",
"dev": true
},
"ncp": {
"version": "2.0.0",
Update eslint-plugin-mozilla to ^1.0.1
2018-11-23 22:40:05 +09:00
"resolved": "https://registry.npmjs.org/ncp/-/ncp-2.0.0.tgz",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"integrity": "sha1-GVoh1sRuNh0vsSgbo4uR6d9727M=",
"dev": true
},
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"needle": {
Update the `needle` package to the latest version
2021-09-05 16:56:50 +09:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/needle/-/needle-3.0.0.tgz",
"integrity": "sha512-eGr0qnfHxAjr+Eptl1zr2lgUQUPC1SZfTkg2kFi0kxr1ChJonHUVYobkug8siBKMlyUVVp56MSkp6CSeXH/jgw==",
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"dev": true,
"requires": {
Update packages
2019-08-25 03:08:09 +09:00
"debug": "^3.2.6",
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"iconv-lite": "^0.4.4",
"sax": "^1.2.4"
Update the `canvas` npm package to fix Travis CI builds (issue 10790)
2019-05-08 16:55:26 +09:00
},
"dependencies": {
"debug": {
Update `npm` packages
2021-01-10 19:25:47 +09:00
"version": "3.2.7",
"resolved": "https://registry.npmjs.org/debug/-/debug-3.2.7.tgz",
"integrity": "sha512-CFjzYYAi4ThfiQvizrFQevTTXHtnCqWfe7x1AhgEscTz6ZbLbfoLRLPugTQyBth6f8ZERVUSyWHFD/7Wu4t1XQ==",
Update the `canvas` npm package to fix Travis CI builds (issue 10790)
2019-05-08 16:55:26 +09:00
"dev": true,
"requires": {
"ms": "^2.1.1"
}
},
"ms": {
Update `npm` packages
2021-01-10 19:25:47 +09:00
"version": "2.1.3",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.3.tgz",
"integrity": "sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==",
Update the `canvas` npm package to fix Travis CI builds (issue 10790)
2019-05-08 16:55:26 +09:00
"dev": true
}
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"neo-async": {
Update `npm` packages
2020-07-26 18:15:21 +09:00
"version": "2.6.2",
"resolved": "https://registry.npmjs.org/neo-async/-/neo-async-2.6.2.tgz",
"integrity": "sha512-Yd3UES5mWCSqR+qNT93S3UoYUkqAZ9lLg8a7g9rimsWmYGK8cVToA4/sF3RrshdyV3sAGMXVUmpMYOw+dLpOuw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"next-tick": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/next-tick/-/next-tick-1.0.0.tgz",
"integrity": "sha1-yobR/ogoFpsBICCOPchCS524NCw=",
"dev": true
},
Update `npm` packages
2020-11-01 18:04:57 +09:00
"node-fetch": {
Update Puppeteer to version `13.1.2` Note in particular https://github.com/puppeteer/puppeteer/releases/tag/v13.1.0 which includes an update to Chromium 98, which adds support for `structuredClone` in the browser.
2022-01-18 20:23:22 +09:00
"version": "2.6.7",
"resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.7.tgz",
"integrity": "sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"dev": true,
"requires": {
"whatwg-url": "^5.0.0"
}
Update `npm` packages
2020-11-01 18:04:57 +09:00
},
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
"node-releases": {
Update npm packages
2021-12-26 19:09:29 +09:00
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/node-releases/-/node-releases-2.0.1.tgz",
"integrity": "sha512-CqyzN6z7Q6aMeF/ktcMVTzhAHCEpf8SOarwpzpf8pNBY2k5/oM34UHldUwp8VKI7uxct2HxSRdJjBaZeESzcxA==",
Update `npm` packages
2020-04-02 19:13:14 +09:00
"dev": true
Update Babel to 7.x Update configuration to work with Babel 7 Explicitly require globals - eslint-plugin-mozilla needs it, but doesn't require it on its own. Fix Regexp to match Babel 7's inlined _interopRequireDefault
2018-11-23 20:52:29 +09:00
},
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"nopt": {
Update npm packages
2021-05-30 14:43:13 +09:00
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/nopt/-/nopt-5.0.0.tgz",
"integrity": "sha512-Tbj67rffqceeLpcRXrT7vKAN8CwfPeIBgM7E6iBkmKLV7bEMwpGgYLGv0jACUsECaa/vuxP0IjEont6umdMgtQ==",
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-30 14:43:13 +09:00
"abbrev": "1"
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"normalize-package-data": {
"version": "2.4.0",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.4.0.tgz",
"integrity": "sha512-9jjUFbTPfEy3R/ad/2oNbKtW9Hgovl5O1FvFWKkKblNXoN/Oou6+9+KKohPK13Yc3/TyunyWhJp6gvRNR/PPAw==",
"dev": true,
"requires": {
"hosted-git-info": "^2.1.4",
"is-builtin-module": "^1.0.0",
"semver": "2 || 3 || 4 || 5",
"validate-npm-package-license": "^3.0.1"
}
},
"normalize-path": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/normalize-path/-/normalize-path-2.1.1.tgz",
"integrity": "sha1-GrKLVW4Zg2Oowab35vogE3/mrtk=",
"dev": true,
"requires": {
"remove-trailing-separator": "^1.0.1"
}
},
"normalize-range": {
"version": "0.1.2",
"resolved": "https://registry.npmjs.org/normalize-range/-/normalize-range-0.1.2.tgz",
"integrity": "sha1-LRDAa9/TEuqXd2laTShDlFa3WUI=",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"normalize-selector": {
"version": "0.2.0",
"resolved": "https://registry.npmjs.org/normalize-selector/-/normalize-selector-0.2.0.tgz",
"integrity": "sha1-0LFF62kRicY6eNIB3E/bEpPvDAM=",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"now-and-later": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/now-and-later/-/now-and-later-2.0.0.tgz",
"integrity": "sha1-vGHLtFbXnLMiB85HygUTb/Ln1u4=",
"dev": true,
"requires": {
"once": "^1.3.2"
}
},
"npm": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "6.14.15",
"resolved": "https://registry.npmjs.org/npm/-/npm-6.14.15.tgz",
"integrity": "sha512-dkcQc4n+DiJAMYG2haNAMyJbmuvevjXz+WC9dCUzodw8EovwTIc6CATSsTEplCY6c0jG4OshxFGFJsrnKJguWA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"abbrev": "~1.1.1",
"ansicolors": "~0.3.2",
"ansistyles": "~0.1.3",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"aproba": "^2.0.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"archy": "~1.0.0",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"bin-links": "^1.1.8",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"bluebird": "^3.5.5",
"byte-size": "^5.0.1",
"cacache": "^12.0.3",
"call-limit": "^1.1.1",
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"chownr": "^1.1.4",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"ci-info": "^2.0.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"cli-columns": "^3.1.2",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"cli-table3": "^0.5.1",
"cmd-shim": "^3.0.3",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"columnify": "~1.5.4",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"config-chain": "^1.1.12",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"debuglog": "*",
"detect-indent": "~5.0.0",
"detect-newline": "^2.1.0",
"dezalgo": "~1.0.3",
"editor": "~1.0.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"figgy-pudding": "^3.5.1",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"find-npm-prefix": "^1.0.2",
"fs-vacuum": "~1.2.10",
"fs-write-stream-atomic": "~1.0.10",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"gentle-fs": "^2.3.1",
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"glob": "^7.1.6",
"graceful-fs": "^4.2.4",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"has-unicode": "~2.0.1",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2021-04-18 18:05:52 +09:00
"hosted-git-info": "^2.8.9",
Update packages
2018-11-25 05:00:22 +09:00
"iferr": "^1.0.2",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"imurmurhash": "*",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"infer-owner": "^1.0.4",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"inflight": "~1.0.6",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"inherits": "^2.0.4",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2021-04-18 18:05:52 +09:00
"ini": "^1.3.8",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"init-package-json": "^1.10.3",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"is-cidr": "^3.0.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"json-parse-better-errors": "^1.0.2",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"JSONStream": "^1.3.5",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"lazy-property": "~1.0.0",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"libcipm": "^4.0.8",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"libnpm": "^3.0.1",
"libnpmaccess": "^3.0.2",
"libnpmhook": "^5.0.3",
"libnpmorg": "^1.0.1",
"libnpmsearch": "^2.0.2",
"libnpmteam": "^1.0.2",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"libnpx": "^10.2.4",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"lock-verify": "^2.1.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"lockfile": "^1.0.4",
"lodash._baseindexof": "*",
"lodash._baseuniq": "~4.6.0",
"lodash._bindcallback": "*",
"lodash._cacheindexof": "*",
"lodash._createcache": "*",
"lodash._getnative": "*",
"lodash.clonedeep": "~4.5.0",
"lodash.restparam": "*",
"lodash.union": "~4.6.0",
"lodash.uniq": "~4.5.0",
"lodash.without": "~4.4.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"lru-cache": "^5.1.1",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"meant": "^1.0.2",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"mississippi": "^3.0.0",
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"mkdirp": "^0.5.5",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"move-concurrently": "^1.0.1",
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"node-gyp": "^5.1.0",
"nopt": "^4.0.3",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"normalize-package-data": "^2.5.0",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"npm-audit-report": "^1.3.3",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"npm-cache-filename": "~1.0.2",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"npm-install-checks": "^3.0.2",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"npm-lifecycle": "^3.1.5",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"npm-package-arg": "^6.1.1",
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"npm-packlist": "^1.4.8",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"npm-pick-manifest": "^3.0.2",
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"npm-profile": "^4.0.4",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"npm-registry-fetch": "^4.0.7",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-11-29 17:47:33 +09:00
"npm-user-validate": "^1.0.1",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"npmlog": "~4.1.2",
"once": "~1.4.0",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2021-04-18 18:05:52 +09:00
"opener": "^1.5.2",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"osenv": "^0.1.5",
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"pacote": "^9.5.12",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"path-is-inside": "~1.0.2",
"promise-inflight": "~1.0.1",
"qrcode-terminal": "^0.12.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"query-string": "^6.8.2",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"qw": "~1.0.1",
"read": "~1.0.7",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2019-11-11 19:23:17 +09:00
"read-cmd-shim": "^1.0.5",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"read-installed": "~4.0.3",
Bump npm from 6.13.0 to 6.13.4 Bumps [npm](https://github.com/npm/cli) from 6.13.0 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.13.0...v6.13.4) Signed-off-by: dependabot[bot] <support@github.com>
2019-12-14 02:30:33 +09:00
"read-package-json": "^2.1.1",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"read-package-tree": "^5.3.1",
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"readable-stream": "^3.6.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"readdir-scoped-modules": "^1.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"request": "^2.88.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"retry": "^0.12.0",
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"rimraf": "^2.7.1",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"safe-buffer": "^5.1.2",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"semver": "^5.7.1",
"sha": "^3.0.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"slide": "~1.1.6",
"sorted-object": "~2.0.1",
"sorted-union-stream": "~2.1.3",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2021-04-18 18:05:52 +09:00
"ssri": "^6.0.2",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"stringify-package": "^1.0.1",
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"tar": "^4.4.19",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"text-table": "~0.2.0",
"tiny-relative-date": "^1.3.0",
"uid-number": "0.0.6",
"umask": "~1.1.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"unique-filename": "^1.1.1",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"unpipe": "~1.0.0",
"update-notifier": "^2.5.0",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2019-11-11 19:23:17 +09:00
"uuid": "^3.3.3",
Update packages
2018-11-25 05:00:22 +09:00
"validate-npm-package-license": "^3.0.4",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"validate-npm-package-name": "~3.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"which": "^1.3.1",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"worker-farm": "^1.7.0",
"write-file-atomic": "^2.4.3"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
"abbrev": {
"version": "1.1.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"agent-base": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "4.3.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
"es6-promisify": "^5.0.0"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update packages
2018-11-25 05:00:22 +09:00
"agentkeepalive": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "3.5.2",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
"humanize-ms": "^1.2.1"
}
},
"ansi-align": {
"version": "2.0.0",
"bundled": true,
"dev": true,
"requires": {
"string-width": "^2.0.0"
}
},
"ansi-regex": {
"version": "2.1.1",
"bundled": true,
"dev": true
},
"ansi-styles": {
"version": "3.2.1",
"bundled": true,
"dev": true,
"requires": {
"color-convert": "^1.9.0"
}
},
"ansicolors": {
"version": "0.3.2",
"bundled": true,
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"ansistyles": {
"version": "0.1.3",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"aproba": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "2.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"archy": {
"version": "1.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"are-we-there-yet": {
"version": "1.1.4",
"bundled": true,
"dev": true,
"requires": {
"delegates": "^1.0.0",
"readable-stream": "^2.0.6"
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"dependencies": {
"readable-stream": {
"version": "2.3.6",
"bundled": true,
"dev": true,
"requires": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"string_decoder": {
"version": "1.1.1",
"bundled": true,
"dev": true,
"requires": {
"safe-buffer": "~5.1.0"
}
}
Update packages
2018-11-25 05:00:22 +09:00
}
},
"asap": {
"version": "2.0.6",
"bundled": true,
"dev": true
},
"asn1": {
"version": "0.2.4",
"bundled": true,
"dev": true,
"requires": {
"safer-buffer": "~2.1.0"
}
},
"assert-plus": {
"version": "1.0.0",
"bundled": true,
"dev": true
},
"asynckit": {
"version": "0.4.0",
"bundled": true,
"dev": true
},
"aws-sign2": {
"version": "0.7.0",
"bundled": true,
"dev": true
},
"aws4": {
"version": "1.8.0",
"bundled": true,
"dev": true
},
"balanced-match": {
"version": "1.0.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"bcrypt-pbkdf": {
"version": "1.0.2",
"bundled": true,
"dev": true,
"optional": true,
"requires": {
"tweetnacl": "^0.14.3"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bin-links": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "1.1.8",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"bluebird": "^3.5.3",
"cmd-shim": "^3.0.0",
Bump npm from 6.13.0 to 6.13.4 Bumps [npm](https://github.com/npm/cli) from 6.13.0 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.13.0...v6.13.4) Signed-off-by: dependabot[bot] <support@github.com>
2019-12-14 02:30:33 +09:00
"gentle-fs": "^2.3.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"graceful-fs": "^4.1.15",
Bump npm from 6.13.0 to 6.13.4 Bumps [npm](https://github.com/npm/cli) from 6.13.0 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.13.0...v6.13.4) Signed-off-by: dependabot[bot] <support@github.com>
2019-12-14 02:30:33 +09:00
"npm-normalize-package-bin": "^1.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"write-file-atomic": "^2.3.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"bluebird": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "3.5.5",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"boxen": {
"version": "1.3.0",
"bundled": true,
"dev": true,
"requires": {
"ansi-align": "^2.0.0",
"camelcase": "^4.0.0",
"chalk": "^2.0.1",
"cli-boxes": "^1.0.0",
"string-width": "^2.0.0",
"term-size": "^1.2.0",
"widest-line": "^2.0.0"
}
},
"brace-expansion": {
"version": "1.1.11",
"bundled": true,
"dev": true,
"requires": {
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
}
},
"buffer-from": {
"version": "1.0.0",
"bundled": true,
"dev": true
},
"builtins": {
"version": "1.0.3",
"bundled": true,
"dev": true
},
"byline": {
"version": "5.0.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"byte-size": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "5.0.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"cacache": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "12.0.3",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"bluebird": "^3.5.5",
"chownr": "^1.1.1",
"figgy-pudding": "^3.5.1",
"glob": "^7.1.4",
"graceful-fs": "^4.1.15",
"infer-owner": "^1.0.3",
"lru-cache": "^5.1.1",
Update packages
2018-11-25 05:00:22 +09:00
"mississippi": "^3.0.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"mkdirp": "^0.5.1",
"move-concurrently": "^1.0.1",
"promise-inflight": "^1.0.1",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"rimraf": "^2.6.3",
"ssri": "^6.0.1",
"unique-filename": "^1.1.1",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"y18n": "^4.0.0"
}
},
"call-limit": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "1.1.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"camelcase": {
"version": "4.1.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"capture-stack-trace": {
"version": "1.0.0",
"bundled": true,
"dev": true
},
"caseless": {
"version": "0.12.0",
"bundled": true,
"dev": true
},
"chalk": {
"version": "2.4.1",
"bundled": true,
"dev": true,
"requires": {
"ansi-styles": "^3.2.1",
"escape-string-regexp": "^1.0.5",
"supports-color": "^5.3.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"chownr": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "1.1.4",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"ci-info": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "2.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"cidr-regex": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "2.0.10",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
"ip-regex": "^2.1.0"
}
},
"cli-boxes": {
"version": "1.0.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"cli-columns": {
"version": "3.1.2",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"string-width": "^2.0.0",
"strip-ansi": "^3.0.1"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"cli-table3": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "0.5.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
"colors": "^1.1.2",
"object-assign": "^4.1.0",
"string-width": "^2.1.1"
}
},
"cliui": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "5.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"string-width": "^3.1.0",
"strip-ansi": "^5.2.0",
"wrap-ansi": "^5.1.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
Update packages
2018-11-25 05:00:22 +09:00
"ansi-regex": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "4.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"is-fullwidth-code-point": {
"version": "2.0.0",
"bundled": true,
"dev": true
},
"string-width": {
"version": "3.1.0",
"bundled": true,
"dev": true,
"requires": {
"emoji-regex": "^7.0.1",
"is-fullwidth-code-point": "^2.0.0",
"strip-ansi": "^5.1.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"strip-ansi": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "5.2.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"ansi-regex": "^4.1.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
}
},
Update packages
2018-11-25 05:00:22 +09:00
"clone": {
"version": "1.0.4",
"bundled": true,
"dev": true
},
"cmd-shim": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "3.0.3",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"graceful-fs": "^4.1.2",
"mkdirp": "~0.5.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"code-point-at": {
"version": "1.1.0",
"bundled": true,
"dev": true
},
"color-convert": {
"version": "1.9.1",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"color-name": "^1.1.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"color-name": {
"version": "1.1.3",
"bundled": true,
"dev": true
},
"colors": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "1.3.3",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"optional": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"columnify": {
"version": "1.5.4",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"strip-ansi": "^3.0.0",
"wcwidth": "^1.0.0"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"combined-stream": {
"version": "1.0.6",
"bundled": true,
"dev": true,
"requires": {
"delayed-stream": "~1.0.0"
}
},
"concat-map": {
"version": "0.0.1",
"bundled": true,
"dev": true
},
"concat-stream": {
"version": "1.6.2",
"bundled": true,
"dev": true,
"requires": {
"buffer-from": "^1.0.0",
"inherits": "^2.0.3",
"readable-stream": "^2.2.2",
"typedarray": "^0.0.6"
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"dependencies": {
"readable-stream": {
"version": "2.3.6",
"bundled": true,
"dev": true,
"requires": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"string_decoder": {
"version": "1.1.1",
"bundled": true,
"dev": true,
"requires": {
"safe-buffer": "~5.1.0"
}
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"config-chain": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "1.1.12",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"ini": "^1.3.4",
"proto-list": "~1.2.1"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"configstore": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "3.1.5",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"dot-prop": "^4.2.1",
Update packages
2018-11-25 05:00:22 +09:00
"graceful-fs": "^4.1.2",
"make-dir": "^1.0.0",
"unique-string": "^1.0.0",
"write-file-atomic": "^2.0.0",
"xdg-basedir": "^3.0.0"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update packages
2018-11-25 05:00:22 +09:00
"console-control-strings": {
"version": "1.1.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"copy-concurrently": {
"version": "1.0.5",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"aproba": "^1.1.1",
"fs-write-stream-atomic": "^1.0.8",
"iferr": "^0.1.5",
"mkdirp": "^0.5.1",
"rimraf": "^2.5.4",
"run-queue": "^1.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"aproba": {
"version": "1.2.0",
"bundled": true,
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"iferr": {
"version": "0.1.5",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
}
}
},
Update packages
2018-11-25 05:00:22 +09:00
"core-util-is": {
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"version": "1.0.2",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"create-error-class": {
"version": "3.0.2",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"capture-stack-trace": "^1.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"cross-spawn": {
"version": "5.1.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"lru-cache": "^4.0.1",
"shebang-command": "^1.2.0",
"which": "^1.2.9"
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"dependencies": {
"lru-cache": {
"version": "4.1.5",
"bundled": true,
"dev": true,
"requires": {
"pseudomap": "^1.0.2",
"yallist": "^2.1.2"
}
},
"yallist": {
"version": "2.1.2",
"bundled": true,
"dev": true
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"crypto-random-string": {
"version": "1.0.0",
"bundled": true,
"dev": true
},
"cyclist": {
"version": "0.2.2",
"bundled": true,
"dev": true
},
"dashdash": {
"version": "1.14.1",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"assert-plus": "^1.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"debug": {
"version": "3.1.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"ms": "2.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
Update packages
2018-11-25 05:00:22 +09:00
"ms": {
"version": "2.0.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
}
}
},
Update packages
2018-11-25 05:00:22 +09:00
"debuglog": {
"version": "1.0.1",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"decamelize": {
"version": "1.2.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"decode-uri-component": {
"version": "0.2.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"deep-extend": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "0.6.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"defaults": {
"version": "1.0.3",
"bundled": true,
"dev": true,
"requires": {
"clone": "^1.0.2"
}
},
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"define-properties": {
"version": "1.1.3",
"bundled": true,
"dev": true,
"requires": {
"object-keys": "^1.0.12"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"delayed-stream": {
"version": "1.0.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"delegates": {
"version": "1.0.0",
"bundled": true,
"dev": true
},
"detect-indent": {
"version": "5.0.0",
"bundled": true,
"dev": true
},
"detect-newline": {
"version": "2.1.0",
"bundled": true,
"dev": true
},
"dezalgo": {
"version": "1.0.3",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"asap": "^2.0.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"wrappy": "1"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"dot-prop": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "4.2.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
"is-obj": "^1.0.0"
}
},
"dotenv": {
"version": "5.0.1",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"duplexer3": {
"version": "0.1.4",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"duplexify": {
"version": "3.6.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"end-of-stream": "^1.0.0",
"inherits": "^2.0.1",
"readable-stream": "^2.0.0",
"stream-shift": "^1.0.0"
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"dependencies": {
"readable-stream": {
"version": "2.3.6",
"bundled": true,
"dev": true,
"requires": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"string_decoder": {
"version": "1.1.1",
"bundled": true,
"dev": true,
"requires": {
"safe-buffer": "~5.1.0"
}
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"ecc-jsbn": {
"version": "0.1.2",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
Update packages
2018-11-25 05:00:22 +09:00
"optional": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"jsbn": "~0.1.0",
"safer-buffer": "^2.1.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"editor": {
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"version": "1.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"emoji-regex": {
"version": "7.0.3",
"bundled": true,
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"encoding": {
"version": "0.1.12",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"iconv-lite": "~0.4.13"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"end-of-stream": {
"version": "1.4.1",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"once": "^1.4.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"env-paths": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "2.2.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"bundled": true,
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"err-code": {
"version": "1.1.2",
"bundled": true,
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update packages
2018-11-25 05:00:22 +09:00
"errno": {
"version": "0.1.7",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"prr": "~1.0.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"es-abstract": {
"version": "1.12.0",
"bundled": true,
"dev": true,
"requires": {
"es-to-primitive": "^1.1.1",
"function-bind": "^1.1.1",
"has": "^1.0.1",
"is-callable": "^1.1.3",
"is-regex": "^1.0.4"
}
},
"es-to-primitive": {
"version": "1.2.0",
"bundled": true,
"dev": true,
"requires": {
"is-callable": "^1.1.4",
"is-date-object": "^1.0.1",
"is-symbol": "^1.0.2"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"es6-promise": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "4.2.8",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"es6-promisify": {
"version": "5.0.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"es6-promise": "^4.0.3"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"escape-string-regexp": {
"version": "1.0.5",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"execa": {
"version": "0.7.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"cross-spawn": "^5.0.1",
"get-stream": "^3.0.0",
"is-stream": "^1.1.0",
"npm-run-path": "^2.0.0",
"p-finally": "^1.0.0",
"signal-exit": "^3.0.0",
"strip-eof": "^1.0.0"
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"dependencies": {
"get-stream": {
"version": "3.0.0",
"bundled": true,
"dev": true
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"extend": {
"version": "3.0.2",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"extsprintf": {
"version": "1.3.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"fast-json-stable-stringify": {
"version": "2.0.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"figgy-pudding": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "3.5.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"find-npm-prefix": {
"version": "1.0.2",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"flush-write-stream": {
"version": "1.0.3",
"bundled": true,
"dev": true,
"requires": {
"inherits": "^2.0.1",
"readable-stream": "^2.0.4"
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"dependencies": {
"readable-stream": {
"version": "2.3.6",
"bundled": true,
"dev": true,
"requires": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"string_decoder": {
"version": "1.1.1",
"bundled": true,
"dev": true,
"requires": {
"safe-buffer": "~5.1.0"
}
}
Update packages
2018-11-25 05:00:22 +09:00
}
},
"forever-agent": {
"version": "0.6.1",
"bundled": true,
"dev": true
},
"form-data": {
"version": "2.3.2",
"bundled": true,
"dev": true,
"requires": {
"asynckit": "^0.4.0",
"combined-stream": "1.0.6",
"mime-types": "^2.1.12"
}
},
"from2": {
"version": "2.3.0",
"bundled": true,
"dev": true,
"requires": {
"inherits": "^2.0.1",
"readable-stream": "^2.0.0"
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"dependencies": {
"readable-stream": {
"version": "2.3.6",
"bundled": true,
"dev": true,
"requires": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"string_decoder": {
"version": "1.1.1",
"bundled": true,
"dev": true,
"requires": {
"safe-buffer": "~5.1.0"
}
}
Update packages
2018-11-25 05:00:22 +09:00
}
},
"fs-minipass": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "1.2.7",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"minipass": "^2.6.0"
},
"dependencies": {
"minipass": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2019-11-11 19:23:17 +09:00
"version": "2.9.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"bundled": true,
"dev": true,
"requires": {
"safe-buffer": "^5.1.2",
"yallist": "^3.0.0"
}
}
Update packages
2018-11-25 05:00:22 +09:00
}
},
"fs-vacuum": {
"version": "1.2.10",
"bundled": true,
"dev": true,
"requires": {
"graceful-fs": "^4.1.2",
"path-is-inside": "^1.0.1",
"rimraf": "^2.5.2"
}
},
"fs-write-stream-atomic": {
"version": "1.0.10",
"bundled": true,
"dev": true,
"requires": {
"graceful-fs": "^4.1.2",
"iferr": "^0.1.5",
"imurmurhash": "^0.1.4",
"readable-stream": "1 || 2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
Update packages
2018-11-25 05:00:22 +09:00
"iferr": {
"version": "0.1.5",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"readable-stream": {
"version": "2.3.6",
"bundled": true,
"dev": true,
"requires": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"string_decoder": {
"version": "1.1.1",
"bundled": true,
"dev": true,
"requires": {
"safe-buffer": "~5.1.0"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
},
Update packages
2018-11-25 05:00:22 +09:00
"fs.realpath": {
"version": "1.0.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"function-bind": {
"version": "1.1.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"dev": true
Update packages
2018-11-25 05:00:22 +09:00
},
"gauge": {
"version": "2.7.4",
"bundled": true,
"dev": true,
"requires": {
"aproba": "^1.0.3",
"console-control-strings": "^1.0.0",
"has-unicode": "^2.0.0",
"object-assign": "^4.1.0",
"signal-exit": "^3.0.0",
"string-width": "^1.0.1",
"strip-ansi": "^3.0.1",
"wide-align": "^1.1.0"
},
"dependencies": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"aproba": {
"version": "1.2.0",
"bundled": true,
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"string-width": {
"version": "1.0.2",
"bundled": true,
"dev": true,
"requires": {
"code-point-at": "^1.0.0",
"is-fullwidth-code-point": "^1.0.0",
"strip-ansi": "^3.0.0"
}
}
}
},
"genfun": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "5.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"gentle-fs": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "2.3.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
"aproba": "^1.1.2",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"chownr": "^1.1.2",
Bump npm from 6.13.0 to 6.13.4 Bumps [npm](https://github.com/npm/cli) from 6.13.0 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.13.0...v6.13.4) Signed-off-by: dependabot[bot] <support@github.com>
2019-12-14 02:30:33 +09:00
"cmd-shim": "^3.0.3",
Update packages
2018-11-25 05:00:22 +09:00
"fs-vacuum": "^1.2.10",
"graceful-fs": "^4.1.11",
"iferr": "^0.1.5",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"infer-owner": "^1.0.4",
Update packages
2018-11-25 05:00:22 +09:00
"mkdirp": "^0.5.1",
"path-is-inside": "^1.0.2",
"read-cmd-shim": "^1.0.1",
"slide": "^1.1.6"
},
"dependencies": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"aproba": {
"version": "1.2.0",
"bundled": true,
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"iferr": {
"version": "0.1.5",
"bundled": true,
"dev": true
}
}
},
"get-caller-file": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "2.0.5",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"get-stream": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "4.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"dev": true,
"requires": {
"pump": "^3.0.0"
}
Update packages
2018-11-25 05:00:22 +09:00
},
"getpass": {
"version": "0.1.7",
"bundled": true,
"dev": true,
"requires": {
"assert-plus": "^1.0.0"
}
},
"glob": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "7.1.6",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
"minimatch": "^3.0.4",
"once": "^1.3.0",
"path-is-absolute": "^1.0.0"
}
},
"global-dirs": {
"version": "0.1.1",
"bundled": true,
"dev": true,
"requires": {
"ini": "^1.3.4"
}
},
"got": {
"version": "6.7.1",
"bundled": true,
"dev": true,
"requires": {
"create-error-class": "^3.0.0",
"duplexer3": "^0.1.4",
"get-stream": "^3.0.0",
"is-redirect": "^1.0.0",
"is-retry-allowed": "^1.0.0",
"is-stream": "^1.0.0",
"lowercase-keys": "^1.0.0",
"safe-buffer": "^5.0.1",
"timed-out": "^4.0.0",
"unzip-response": "^2.0.1",
"url-parse-lax": "^1.0.0"
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"dependencies": {
"get-stream": {
"version": "3.0.0",
"bundled": true,
"dev": true
}
Update packages
2018-11-25 05:00:22 +09:00
}
},
"graceful-fs": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "4.2.4",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"har-schema": {
"version": "2.0.0",
"bundled": true,
"dev": true
},
"har-validator": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-11-29 17:47:33 +09:00
"version": "5.1.5",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-11-29 17:47:33 +09:00
"ajv": "^6.12.3",
Update packages
2018-11-25 05:00:22 +09:00
"har-schema": "^2.0.0"
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-11-29 17:47:33 +09:00
},
"dependencies": {
"ajv": {
"version": "6.12.6",
"bundled": true,
"dev": true,
"requires": {
"fast-deep-equal": "^3.1.1",
"fast-json-stable-stringify": "^2.0.0",
"json-schema-traverse": "^0.4.1",
"uri-js": "^4.2.2"
}
},
"fast-deep-equal": {
"version": "3.1.3",
"bundled": true,
"dev": true
},
"json-schema-traverse": {
"version": "0.4.1",
"bundled": true,
"dev": true
}
Update packages
2018-11-25 05:00:22 +09:00
}
},
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"has": {
"version": "1.0.3",
"bundled": true,
"dev": true,
"requires": {
"function-bind": "^1.1.1"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"has-flag": {
"version": "3.0.0",
"bundled": true,
"dev": true
},
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"has-symbols": {
"version": "1.0.0",
"bundled": true,
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"has-unicode": {
"version": "2.0.1",
"bundled": true,
"dev": true
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"hosted-git-info": {
"version": "2.8.9",
"bundled": true,
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"http-cache-semantics": {
"version": "3.8.1",
"bundled": true,
"dev": true
},
"http-proxy-agent": {
"version": "2.1.0",
"bundled": true,
"dev": true,
"requires": {
"agent-base": "4",
"debug": "3.1.0"
}
},
"http-signature": {
"version": "1.2.0",
"bundled": true,
"dev": true,
"requires": {
"assert-plus": "^1.0.0",
"jsprim": "^1.2.2",
"sshpk": "^1.7.0"
}
},
"https-proxy-agent": {
Bump npm from 6.13.0 to 6.13.4 Bumps [npm](https://github.com/npm/cli) from 6.13.0 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.13.0...v6.13.4) Signed-off-by: dependabot[bot] <support@github.com>
2019-12-14 02:30:33 +09:00
"version": "2.2.4",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"agent-base": "^4.3.0",
Update packages
2018-11-25 05:00:22 +09:00
"debug": "^3.1.0"
}
},
"humanize-ms": {
"version": "1.2.1",
"bundled": true,
"dev": true,
"requires": {
"ms": "^2.0.0"
}
},
"iconv-lite": {
"version": "0.4.23",
"bundled": true,
"dev": true,
"requires": {
"safer-buffer": ">= 2.1.2 < 3"
}
},
"iferr": {
"version": "1.0.2",
"bundled": true,
"dev": true
},
"ignore-walk": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2019-11-11 19:23:17 +09:00
"version": "3.0.3",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
"minimatch": "^3.0.4"
}
},
"import-lazy": {
"version": "2.1.0",
"bundled": true,
"dev": true
},
"imurmurhash": {
"version": "0.1.4",
"bundled": true,
"dev": true
},
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"infer-owner": {
"version": "1.0.4",
"bundled": true,
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"inflight": {
"version": "1.0.6",
"bundled": true,
"dev": true,
"requires": {
"once": "^1.3.0",
"wrappy": "1"
}
},
"inherits": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "2.0.4",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2021-04-18 18:05:52 +09:00
"ini": {
"version": "1.3.8",
"bundled": true,
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"init-package-json": {
"version": "1.10.3",
"bundled": true,
"dev": true,
"requires": {
"glob": "^7.1.1",
"npm-package-arg": "^4.0.0 || ^5.0.0 || ^6.0.0",
"promzard": "^0.3.0",
"read": "~1.0.1",
"read-package-json": "1 || 2",
"semver": "2.x || 3.x || 4 || 5",
"validate-npm-package-license": "^3.0.1",
"validate-npm-package-name": "^3.0.0"
}
},
"ip": {
"version": "1.1.5",
"bundled": true,
"dev": true
},
"ip-regex": {
"version": "2.1.0",
"bundled": true,
"dev": true
},
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"is-callable": {
"version": "1.1.4",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"dev": true
Update packages
2018-11-25 05:00:22 +09:00
},
"is-ci": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "1.2.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"ci-info": "^1.5.0"
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"dependencies": {
"ci-info": {
"version": "1.6.0",
"bundled": true,
"dev": true
}
Update packages
2018-11-25 05:00:22 +09:00
}
},
"is-cidr": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "3.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"cidr-regex": "^2.0.10"
Update packages
2018-11-25 05:00:22 +09:00
}
},
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"is-date-object": {
"version": "1.0.1",
"bundled": true,
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"is-fullwidth-code-point": {
"version": "1.0.0",
"bundled": true,
"dev": true,
"requires": {
"number-is-nan": "^1.0.0"
}
},
"is-installed-globally": {
"version": "0.1.0",
"bundled": true,
"dev": true,
"requires": {
"global-dirs": "^0.1.0",
"is-path-inside": "^1.0.0"
}
},
"is-npm": {
"version": "1.0.0",
"bundled": true,
"dev": true
},
"is-obj": {
"version": "1.0.1",
"bundled": true,
"dev": true
},
"is-path-inside": {
"version": "1.0.1",
"bundled": true,
"dev": true,
"requires": {
"path-is-inside": "^1.0.1"
}
},
"is-redirect": {
"version": "1.0.0",
"bundled": true,
"dev": true
},
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"is-regex": {
"version": "1.0.4",
"bundled": true,
"dev": true,
"requires": {
"has": "^1.0.1"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"is-retry-allowed": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "1.2.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"is-stream": {
"version": "1.1.0",
"bundled": true,
"dev": true
},
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"is-symbol": {
"version": "1.0.2",
"bundled": true,
"dev": true,
"requires": {
"has-symbols": "^1.0.0"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"is-typedarray": {
"version": "1.0.0",
"bundled": true,
"dev": true
},
"isarray": {
"version": "1.0.0",
"bundled": true,
"dev": true
},
"isexe": {
"version": "2.0.0",
"bundled": true,
"dev": true
},
"isstream": {
"version": "0.1.2",
"bundled": true,
"dev": true
},
"jsbn": {
"version": "0.1.1",
"bundled": true,
"dev": true,
"optional": true
},
"json-parse-better-errors": {
"version": "1.0.2",
"bundled": true,
"dev": true
},
"json-schema": {
"version": "0.2.3",
"bundled": true,
"dev": true
},
"json-stringify-safe": {
"version": "5.0.1",
"bundled": true,
"dev": true
},
"jsonparse": {
"version": "1.3.1",
"bundled": true,
"dev": true
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"JSONStream": {
"version": "1.3.5",
"bundled": true,
"dev": true,
"requires": {
"jsonparse": "^1.2.0",
"through": ">=2.2.7 <3"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"jsprim": {
"version": "1.4.1",
"bundled": true,
"dev": true,
"requires": {
"assert-plus": "1.0.0",
"extsprintf": "1.3.0",
"json-schema": "0.2.3",
"verror": "1.10.0"
}
},
"latest-version": {
"version": "3.1.0",
"bundled": true,
"dev": true,
"requires": {
"package-json": "^4.0.0"
}
},
"lazy-property": {
"version": "1.0.0",
"bundled": true,
"dev": true
},
"libcipm": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "4.0.8",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
"bin-links": "^1.1.2",
"bluebird": "^3.5.1",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"figgy-pudding": "^3.5.1",
Update packages
2018-11-25 05:00:22 +09:00
"find-npm-prefix": "^1.0.2",
"graceful-fs": "^4.1.11",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"ini": "^1.3.5",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"lock-verify": "^2.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"mkdirp": "^0.5.1",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"npm-lifecycle": "^3.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"npm-logical-tree": "^1.2.1",
"npm-package-arg": "^6.1.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"pacote": "^9.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"read-package-json": "^2.0.13",
"rimraf": "^2.6.2",
"worker-farm": "^1.6.0"
}
},
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"libnpm": {
"version": "3.0.1",
"bundled": true,
"dev": true,
"requires": {
"bin-links": "^1.1.2",
"bluebird": "^3.5.3",
"find-npm-prefix": "^1.0.2",
"libnpmaccess": "^3.0.2",
"libnpmconfig": "^1.2.1",
"libnpmhook": "^5.0.3",
"libnpmorg": "^1.0.1",
"libnpmpublish": "^1.1.2",
"libnpmsearch": "^2.0.2",
"libnpmteam": "^1.0.2",
"lock-verify": "^2.0.2",
"npm-lifecycle": "^3.0.0",
"npm-logical-tree": "^1.2.1",
"npm-package-arg": "^6.1.0",
"npm-profile": "^4.0.2",
"npm-registry-fetch": "^4.0.0",
"npmlog": "^4.1.2",
"pacote": "^9.5.3",
"read-package-json": "^2.0.13",
"stringify-package": "^1.0.0"
}
},
"libnpmaccess": {
"version": "3.0.2",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"aproba": "^2.0.0",
"get-stream": "^4.0.0",
"npm-package-arg": "^6.1.0",
"npm-registry-fetch": "^4.0.0"
}
},
"libnpmconfig": {
"version": "1.2.1",
"bundled": true,
"dev": true,
"requires": {
"figgy-pudding": "^3.5.1",
"find-up": "^3.0.0",
"ini": "^1.3.5"
Update packages
2018-11-25 05:00:22 +09:00
},
"dependencies": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"find-up": {
"version": "3.0.0",
"bundled": true,
"dev": true,
"requires": {
"locate-path": "^3.0.0"
}
},
"locate-path": {
"version": "3.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"p-locate": "^3.0.0",
"path-exists": "^3.0.0"
Update packages
2018-11-25 05:00:22 +09:00
}
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"p-limit": {
"version": "2.2.0",
"bundled": true,
"dev": true,
"requires": {
"p-try": "^2.0.0"
}
},
"p-locate": {
"version": "3.0.0",
"bundled": true,
"dev": true,
"requires": {
"p-limit": "^2.0.0"
}
},
"p-try": {
"version": "2.2.0",
"bundled": true,
"dev": true
Update packages
2018-11-25 05:00:22 +09:00
}
}
},
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"libnpmhook": {
"version": "5.0.3",
"bundled": true,
"dev": true,
"requires": {
"aproba": "^2.0.0",
"figgy-pudding": "^3.4.1",
"get-stream": "^4.0.0",
"npm-registry-fetch": "^4.0.0"
}
},
"libnpmorg": {
"version": "1.0.1",
"bundled": true,
"dev": true,
"requires": {
"aproba": "^2.0.0",
"figgy-pudding": "^3.4.1",
"get-stream": "^4.0.0",
"npm-registry-fetch": "^4.0.0"
}
},
"libnpmpublish": {
"version": "1.1.2",
"bundled": true,
"dev": true,
"requires": {
"aproba": "^2.0.0",
"figgy-pudding": "^3.5.1",
"get-stream": "^4.0.0",
"lodash.clonedeep": "^4.5.0",
"normalize-package-data": "^2.4.0",
"npm-package-arg": "^6.1.0",
"npm-registry-fetch": "^4.0.0",
"semver": "^5.5.1",
"ssri": "^6.0.1"
}
},
"libnpmsearch": {
"version": "2.0.2",
"bundled": true,
"dev": true,
"requires": {
"figgy-pudding": "^3.5.1",
"get-stream": "^4.0.0",
"npm-registry-fetch": "^4.0.0"
}
},
"libnpmteam": {
"version": "1.0.2",
"bundled": true,
"dev": true,
"requires": {
"aproba": "^2.0.0",
"figgy-pudding": "^3.4.1",
"get-stream": "^4.0.0",
"npm-registry-fetch": "^4.0.0"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"libnpx": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "10.2.4",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
"dotenv": "^5.0.1",
"npm-package-arg": "^6.0.0",
"rimraf": "^2.6.2",
"safe-buffer": "^5.1.0",
"update-notifier": "^2.3.0",
"which": "^1.3.0",
"y18n": "^4.0.0",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"yargs": "^14.2.3"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"lock-verify": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "2.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"npm-package-arg": "^6.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"semver": "^5.4.1"
}
},
"lockfile": {
"version": "1.0.4",
"bundled": true,
"dev": true,
"requires": {
"signal-exit": "^3.0.2"
}
},
"lodash._baseindexof": {
"version": "3.1.0",
Update the `@javascript-obfuscator/escodegen` package to the latest version The only changes are support for [Class static initialization blocks](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Class_static_initialization_blocks), and the diff for the `node_modules\@javascript-obfuscator\escodegen\escodegen.js` file contains only: ```diff @@ -1506,6 +1506,13 @@ return result; }, + StaticBlock: function (stmt, flags) { + return [ + 'static' + space, + this.BlockStatement(stmt, flags) + ]; + }, + ThrowStatement: function (stmt, flags) { return [join( 'throw', ```
2022-02-06 19:26:07 +09:00
"bundled": true,
Add the `caniuse-lite` package Since the Autoprefixer plugin indirectly depends on this, it seems like a good idea to add this as a direct dependency in the PDF.js project to hopefully avoid having to manually update `caniuse-lite` in the future; see https://github.com/browserslist/browserslist#browsers-data-updating Also, slightly tweaks the Autoprefixer config for GENERIC-builds of the PDF.js library; note that this change doesn't affect the contents of the *built* `web/viewer.js` file.
2022-02-27 19:32:23 +09:00
"dev": true
Update packages
2018-11-25 05:00:22 +09:00
},
"lodash._baseuniq": {
"version": "4.6.0",
"bundled": true,
"dev": true,
"requires": {
"lodash._createset": "~4.0.0",
"lodash._root": "~3.0.0"
}
},
"lodash._bindcallback": {
"version": "3.0.1",
Update the `@javascript-obfuscator/escodegen` package to the latest version The only changes are support for [Class static initialization blocks](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Class_static_initialization_blocks), and the diff for the `node_modules\@javascript-obfuscator\escodegen\escodegen.js` file contains only: ```diff @@ -1506,6 +1506,13 @@ return result; }, + StaticBlock: function (stmt, flags) { + return [ + 'static' + space, + this.BlockStatement(stmt, flags) + ]; + }, + ThrowStatement: function (stmt, flags) { return [join( 'throw', ```
2022-02-06 19:26:07 +09:00
"bundled": true,
Add the `caniuse-lite` package Since the Autoprefixer plugin indirectly depends on this, it seems like a good idea to add this as a direct dependency in the PDF.js project to hopefully avoid having to manually update `caniuse-lite` in the future; see https://github.com/browserslist/browserslist#browsers-data-updating Also, slightly tweaks the Autoprefixer config for GENERIC-builds of the PDF.js library; note that this change doesn't affect the contents of the *built* `web/viewer.js` file.
2022-02-27 19:32:23 +09:00
"dev": true
Update packages
2018-11-25 05:00:22 +09:00
},
"lodash._cacheindexof": {
"version": "3.0.2",
Update the `@javascript-obfuscator/escodegen` package to the latest version The only changes are support for [Class static initialization blocks](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Class_static_initialization_blocks), and the diff for the `node_modules\@javascript-obfuscator\escodegen\escodegen.js` file contains only: ```diff @@ -1506,6 +1506,13 @@ return result; }, + StaticBlock: function (stmt, flags) { + return [ + 'static' + space, + this.BlockStatement(stmt, flags) + ]; + }, + ThrowStatement: function (stmt, flags) { return [join( 'throw', ```
2022-02-06 19:26:07 +09:00
"bundled": true,
Add the `caniuse-lite` package Since the Autoprefixer plugin indirectly depends on this, it seems like a good idea to add this as a direct dependency in the PDF.js project to hopefully avoid having to manually update `caniuse-lite` in the future; see https://github.com/browserslist/browserslist#browsers-data-updating Also, slightly tweaks the Autoprefixer config for GENERIC-builds of the PDF.js library; note that this change doesn't affect the contents of the *built* `web/viewer.js` file.
2022-02-27 19:32:23 +09:00
"dev": true
Update packages
2018-11-25 05:00:22 +09:00
},
"lodash._createcache": {
"version": "3.1.2",
"bundled": true,
Add the `caniuse-lite` package Since the Autoprefixer plugin indirectly depends on this, it seems like a good idea to add this as a direct dependency in the PDF.js project to hopefully avoid having to manually update `caniuse-lite` in the future; see https://github.com/browserslist/browserslist#browsers-data-updating Also, slightly tweaks the Autoprefixer config for GENERIC-builds of the PDF.js library; note that this change doesn't affect the contents of the *built* `web/viewer.js` file.
2022-02-27 19:32:23 +09:00
"dev": true,
Update packages
2018-11-25 05:00:22 +09:00
"requires": {
"lodash._getnative": "^3.0.0"
}
},
"lodash._createset": {
"version": "4.0.3",
"bundled": true,
"dev": true
},
"lodash._getnative": {
"version": "3.9.1",
Update the `@javascript-obfuscator/escodegen` package to the latest version The only changes are support for [Class static initialization blocks](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Class_static_initialization_blocks), and the diff for the `node_modules\@javascript-obfuscator\escodegen\escodegen.js` file contains only: ```diff @@ -1506,6 +1506,13 @@ return result; }, + StaticBlock: function (stmt, flags) { + return [ + 'static' + space, + this.BlockStatement(stmt, flags) + ]; + }, + ThrowStatement: function (stmt, flags) { return [join( 'throw', ```
2022-02-06 19:26:07 +09:00
"bundled": true,
Add the `caniuse-lite` package Since the Autoprefixer plugin indirectly depends on this, it seems like a good idea to add this as a direct dependency in the PDF.js project to hopefully avoid having to manually update `caniuse-lite` in the future; see https://github.com/browserslist/browserslist#browsers-data-updating Also, slightly tweaks the Autoprefixer config for GENERIC-builds of the PDF.js library; note that this change doesn't affect the contents of the *built* `web/viewer.js` file.
2022-02-27 19:32:23 +09:00
"dev": true
Update packages
2018-11-25 05:00:22 +09:00
},
"lodash._root": {
"version": "3.0.1",
"bundled": true,
"dev": true
},
"lodash.clonedeep": {
"version": "4.5.0",
"bundled": true,
"dev": true
},
"lodash.restparam": {
"version": "3.6.1",
Update the `@javascript-obfuscator/escodegen` package to the latest version The only changes are support for [Class static initialization blocks](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Class_static_initialization_blocks), and the diff for the `node_modules\@javascript-obfuscator\escodegen\escodegen.js` file contains only: ```diff @@ -1506,6 +1506,13 @@ return result; }, + StaticBlock: function (stmt, flags) { + return [ + 'static' + space, + this.BlockStatement(stmt, flags) + ]; + }, + ThrowStatement: function (stmt, flags) { return [join( 'throw', ```
2022-02-06 19:26:07 +09:00
"bundled": true,
Add the `caniuse-lite` package Since the Autoprefixer plugin indirectly depends on this, it seems like a good idea to add this as a direct dependency in the PDF.js project to hopefully avoid having to manually update `caniuse-lite` in the future; see https://github.com/browserslist/browserslist#browsers-data-updating Also, slightly tweaks the Autoprefixer config for GENERIC-builds of the PDF.js library; note that this change doesn't affect the contents of the *built* `web/viewer.js` file.
2022-02-27 19:32:23 +09:00
"dev": true
Update packages
2018-11-25 05:00:22 +09:00
},
"lodash.union": {
"version": "4.6.0",
"bundled": true,
"dev": true
},
"lodash.uniq": {
"version": "4.5.0",
"bundled": true,
"dev": true
},
"lodash.without": {
"version": "4.4.0",
"bundled": true,
"dev": true
},
"lowercase-keys": {
"version": "1.0.1",
"bundled": true,
"dev": true
},
"lru-cache": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "5.1.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"yallist": "^3.0.2"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"make-dir": {
"version": "1.3.0",
"bundled": true,
"dev": true,
"requires": {
"pify": "^3.0.0"
}
},
"make-fetch-happen": {
Bump npm from 6.13.0 to 6.13.4 Bumps [npm](https://github.com/npm/cli) from 6.13.0 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.13.0...v6.13.4) Signed-off-by: dependabot[bot] <support@github.com>
2019-12-14 02:30:33 +09:00
"version": "5.0.2",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
"agentkeepalive": "^3.4.1",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"cacache": "^12.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"http-cache-semantics": "^3.8.1",
"http-proxy-agent": "^2.1.0",
Bump npm from 6.13.0 to 6.13.4 Bumps [npm](https://github.com/npm/cli) from 6.13.0 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.13.0...v6.13.4) Signed-off-by: dependabot[bot] <support@github.com>
2019-12-14 02:30:33 +09:00
"https-proxy-agent": "^2.2.3",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"lru-cache": "^5.1.1",
Update packages
2018-11-25 05:00:22 +09:00
"mississippi": "^3.0.0",
"node-fetch-npm": "^2.0.2",
"promise-retry": "^1.1.1",
"socks-proxy-agent": "^4.0.0",
"ssri": "^6.0.0"
}
},
"meant": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "1.0.2",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"mime-db": {
"version": "1.35.0",
"bundled": true,
"dev": true
},
"mime-types": {
"version": "2.1.19",
"bundled": true,
"dev": true,
"requires": {
"mime-db": "~1.35.0"
}
},
"minimatch": {
"version": "3.0.4",
"bundled": true,
"dev": true,
"requires": {
"brace-expansion": "^1.1.7"
}
},
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"minimist": {
"version": "1.2.5",
"bundled": true,
"dev": true
},
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2019-11-11 19:23:17 +09:00
"minizlib": {
"version": "1.3.3",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2019-11-11 19:23:17 +09:00
"minipass": "^2.9.0"
Update packages
2018-11-25 05:00:22 +09:00
},
"dependencies": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2019-11-11 19:23:17 +09:00
"minipass": {
"version": "2.9.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2019-11-11 19:23:17 +09:00
"dev": true,
"requires": {
"safe-buffer": "^5.1.2",
"yallist": "^3.0.0"
}
Update packages
2018-11-25 05:00:22 +09:00
}
}
},
"mississippi": {
"version": "3.0.0",
"bundled": true,
"dev": true,
"requires": {
"concat-stream": "^1.5.0",
"duplexify": "^3.4.2",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"end-of-stream": "^1.1.0",
"flush-write-stream": "^1.0.0",
"from2": "^2.1.0",
"parallel-transform": "^1.1.0",
"pump": "^3.0.0",
"pumpify": "^1.3.3",
"stream-each": "^1.1.0",
"through2": "^2.0.0"
}
},
"mkdirp": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "0.5.5",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"minimist": "^1.2.5"
},
"dependencies": {
"minimist": {
"version": "1.2.5",
"bundled": true,
"dev": true
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"move-concurrently": {
"version": "1.0.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"aproba": "^1.1.1",
"copy-concurrently": "^1.0.0",
"fs-write-stream-atomic": "^1.0.8",
"mkdirp": "^0.5.1",
"rimraf": "^2.5.4",
"run-queue": "^1.0.3"
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"dependencies": {
"aproba": {
"version": "1.2.0",
"bundled": true,
"dev": true
}
Update packages
2018-11-25 05:00:22 +09:00
}
},
"ms": {
"version": "2.1.1",
"bundled": true,
"dev": true
},
"mute-stream": {
"version": "0.0.7",
"bundled": true,
"dev": true
},
"node-fetch-npm": {
"version": "2.0.2",
"bundled": true,
"dev": true,
"requires": {
"encoding": "^0.1.11",
"json-parse-better-errors": "^1.0.0",
"safe-buffer": "^5.1.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"node-gyp": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "5.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"env-paths": "^2.2.0",
"glob": "^7.1.4",
"graceful-fs": "^4.2.2",
"mkdirp": "^0.5.1",
"nopt": "^4.0.1",
"npmlog": "^4.1.2",
"request": "^2.88.0",
"rimraf": "^2.6.3",
"semver": "^5.7.1",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"tar": "^4.4.12",
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"which": "^1.3.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"nopt": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "4.0.3",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"abbrev": "1",
"osenv": "^0.1.4"
}
},
"normalize-package-data": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "2.5.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"hosted-git-info": "^2.1.4",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"resolve": "^1.10.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"semver": "2 || 3 || 4 || 5",
"validate-npm-package-license": "^3.0.1"
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"dependencies": {
"resolve": {
"version": "1.10.0",
"bundled": true,
"dev": true,
"requires": {
"path-parse": "^1.0.6"
}
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"npm-audit-report": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "1.3.3",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"cli-table3": "^0.5.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"console-control-strings": "^1.1.0"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"npm-bundled": {
Bump npm from 6.13.0 to 6.13.4 Bumps [npm](https://github.com/npm/cli) from 6.13.0 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.13.0...v6.13.4) Signed-off-by: dependabot[bot] <support@github.com>
2019-12-14 02:30:33 +09:00
"version": "1.1.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Bump npm from 6.13.0 to 6.13.4 Bumps [npm](https://github.com/npm/cli) from 6.13.0 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.13.0...v6.13.4) Signed-off-by: dependabot[bot] <support@github.com>
2019-12-14 02:30:33 +09:00
"dev": true,
"requires": {
"npm-normalize-package-bin": "^1.0.1"
}
Update packages
2018-11-25 05:00:22 +09:00
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"npm-cache-filename": {
"version": "1.0.2",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"npm-install-checks": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "3.0.2",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"semver": "^2.3.0 || 3.x || 4 || 5"
}
},
"npm-lifecycle": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "3.1.5",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"byline": "^5.0.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"graceful-fs": "^4.1.15",
"node-gyp": "^5.0.2",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"resolve-from": "^4.0.0",
"slide": "^1.1.6",
"uid-number": "0.0.6",
"umask": "^1.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"which": "^1.3.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"npm-logical-tree": {
"version": "1.2.1",
"bundled": true,
"dev": true
},
Bump npm from 6.13.0 to 6.13.4 Bumps [npm](https://github.com/npm/cli) from 6.13.0 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.13.0...v6.13.4) Signed-off-by: dependabot[bot] <support@github.com>
2019-12-14 02:30:33 +09:00
"npm-normalize-package-bin": {
"version": "1.0.1",
"bundled": true,
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"npm-package-arg": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "6.1.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"hosted-git-info": "^2.7.1",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"osenv": "^0.1.5",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"semver": "^5.6.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"validate-npm-package-name": "^3.0.0"
}
},
"npm-packlist": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "1.4.8",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"ignore-walk": "^3.0.1",
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"npm-bundled": "^1.0.1",
"npm-normalize-package-bin": "^1.0.1"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"npm-pick-manifest": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "3.0.2",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"figgy-pudding": "^3.5.1",
Update packages
2018-11-25 05:00:22 +09:00
"npm-package-arg": "^6.0.0",
"semver": "^5.4.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"npm-profile": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "4.0.4",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"aproba": "^1.1.2 || 2",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"figgy-pudding": "^3.4.1",
"npm-registry-fetch": "^4.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"npm-registry-fetch": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "4.0.7",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"bluebird": "^3.5.1",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"figgy-pudding": "^3.4.1",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"JSONStream": "^1.3.4",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"lru-cache": "^5.1.1",
"make-fetch-happen": "^5.0.0",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2019-11-11 19:23:17 +09:00
"npm-package-arg": "^6.1.0",
"safe-buffer": "^5.2.0"
},
"dependencies": {
"safe-buffer": {
Bump npm from 6.14.5 to 6.14.6 Bumps [npm](https://github.com/npm/cli) from 6.14.5 to 6.14.6. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.14.5...v6.14.6) Signed-off-by: dependabot[bot] <support@github.com>
2020-07-08 04:25:19 +09:00
"version": "5.2.1",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2019-11-11 19:23:17 +09:00
"bundled": true,
"dev": true
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"npm-run-path": {
"version": "2.0.2",
"bundled": true,
"dev": true,
"requires": {
"path-key": "^2.0.0"
}
},
"npm-user-validate": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-11-29 17:47:33 +09:00
"version": "1.0.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"npmlog": {
"version": "4.1.2",
"bundled": true,
"dev": true,
"requires": {
"are-we-there-yet": "~1.1.2",
"console-control-strings": "~1.1.0",
"gauge": "~2.7.3",
"set-blocking": "~2.0.0"
}
},
"number-is-nan": {
"version": "1.0.1",
"bundled": true,
"dev": true
},
"oauth-sign": {
"version": "0.9.0",
"bundled": true,
"dev": true
},
"object-assign": {
"version": "4.1.1",
"bundled": true,
"dev": true
},
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"object-keys": {
"version": "1.0.12",
"bundled": true,
"dev": true
},
"object.getownpropertydescriptors": {
"version": "2.0.3",
"bundled": true,
"dev": true,
"requires": {
"define-properties": "^1.1.2",
"es-abstract": "^1.5.1"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"once": {
"version": "1.4.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"wrappy": "1"
}
},
"opener": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2021-04-18 18:05:52 +09:00
"version": "1.5.2",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"os-homedir": {
"version": "1.0.2",
"bundled": true,
"dev": true
},
"os-tmpdir": {
"version": "1.0.2",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"osenv": {
"version": "0.1.5",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"os-homedir": "^1.0.0",
"os-tmpdir": "^1.0.0"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"p-finally": {
"version": "1.0.0",
"bundled": true,
"dev": true
},
"package-json": {
"version": "4.0.1",
"bundled": true,
"dev": true,
"requires": {
"got": "^6.7.1",
"registry-auth-token": "^3.0.1",
"registry-url": "^3.0.3",
"semver": "^5.1.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"pacote": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "9.5.12",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"bluebird": "^3.5.3",
"cacache": "^12.0.2",
"chownr": "^1.1.2",
"figgy-pudding": "^3.5.1",
"get-stream": "^4.1.0",
"glob": "^7.1.3",
"infer-owner": "^1.0.4",
"lru-cache": "^5.1.1",
"make-fetch-happen": "^5.0.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"minimatch": "^3.0.4",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"minipass": "^2.3.5",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"mississippi": "^3.0.0",
"mkdirp": "^0.5.1",
"normalize-package-data": "^2.4.0",
Bump npm from 6.13.0 to 6.13.4 Bumps [npm](https://github.com/npm/cli) from 6.13.0 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.13.0...v6.13.4) Signed-off-by: dependabot[bot] <support@github.com>
2019-12-14 02:30:33 +09:00
"npm-normalize-package-bin": "^1.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"npm-package-arg": "^6.1.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"npm-packlist": "^1.1.12",
"npm-pick-manifest": "^3.0.0",
"npm-registry-fetch": "^4.0.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"osenv": "^0.1.5",
"promise-inflight": "^1.0.1",
"promise-retry": "^1.1.1",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"protoduck": "^5.0.1",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"rimraf": "^2.6.2",
Update packages
2018-11-25 05:00:22 +09:00
"safe-buffer": "^5.1.2",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"semver": "^5.6.0",
"ssri": "^6.0.1",
"tar": "^4.4.10",
"unique-filename": "^1.1.1",
"which": "^1.3.1"
},
"dependencies": {
"minipass": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2019-11-11 19:23:17 +09:00
"version": "2.9.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"bundled": true,
"dev": true,
"requires": {
"safe-buffer": "^5.1.2",
"yallist": "^3.0.0"
}
}
Update packages
2018-11-25 05:00:22 +09:00
}
},
"parallel-transform": {
"version": "1.1.0",
"bundled": true,
"dev": true,
"requires": {
"cyclist": "~0.2.2",
"inherits": "^2.0.3",
"readable-stream": "^2.1.5"
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"dependencies": {
"readable-stream": {
"version": "2.3.6",
"bundled": true,
"dev": true,
"requires": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"string_decoder": {
"version": "1.1.1",
"bundled": true,
"dev": true,
"requires": {
"safe-buffer": "~5.1.0"
}
}
Update packages
2018-11-25 05:00:22 +09:00
}
},
"path-exists": {
"version": "3.0.0",
"bundled": true,
"dev": true
},
"path-is-absolute": {
"version": "1.0.1",
"bundled": true,
"dev": true
},
"path-is-inside": {
"version": "1.0.2",
"bundled": true,
"dev": true
},
"path-key": {
"version": "2.0.1",
"bundled": true,
"dev": true
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"path-parse": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "1.0.7",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"bundled": true,
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"performance-now": {
"version": "2.1.0",
"bundled": true,
"dev": true
},
"pify": {
"version": "3.0.0",
"bundled": true,
"dev": true
},
"prepend-http": {
"version": "1.0.4",
"bundled": true,
"dev": true
},
"process-nextick-args": {
"version": "2.0.0",
"bundled": true,
"dev": true
},
"promise-inflight": {
"version": "1.0.1",
"bundled": true,
"dev": true
},
"promise-retry": {
"version": "1.1.1",
"bundled": true,
"dev": true,
"requires": {
"err-code": "^1.0.0",
"retry": "^0.10.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
Update packages
2018-11-25 05:00:22 +09:00
"retry": {
"version": "0.10.1",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
Update packages
2018-11-25 05:00:22 +09:00
}
}
},
"promzard": {
"version": "0.3.0",
"bundled": true,
"dev": true,
"requires": {
"read": "1"
}
},
"proto-list": {
"version": "1.2.4",
"bundled": true,
"dev": true
},
"protoduck": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "5.0.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"genfun": "^5.0.0"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"prr": {
"version": "1.0.1",
"bundled": true,
"dev": true
},
"pseudomap": {
"version": "1.0.2",
"bundled": true,
"dev": true
},
"psl": {
"version": "1.1.29",
"bundled": true,
"dev": true
},
"pump": {
"version": "3.0.0",
"bundled": true,
"dev": true,
"requires": {
"end-of-stream": "^1.1.0",
"once": "^1.3.1"
}
},
"pumpify": {
"version": "1.5.1",
"bundled": true,
"dev": true,
"requires": {
"duplexify": "^3.6.0",
"inherits": "^2.0.3",
"pump": "^2.0.0"
},
"dependencies": {
"pump": {
"version": "2.0.1",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"end-of-stream": "^1.1.0",
"once": "^1.3.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
}
},
Update packages
2018-11-25 05:00:22 +09:00
"punycode": {
"version": "1.4.1",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"qrcode-terminal": {
"version": "0.12.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"qs": {
"version": "6.5.2",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"query-string": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "6.8.2",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"decode-uri-component": "^0.2.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"split-on-first": "^1.0.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"strict-uri-encode": "^2.0.0"
}
},
"qw": {
"version": "1.0.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"rc": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "1.2.8",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"deep-extend": "^0.6.0",
Update packages
2018-11-25 05:00:22 +09:00
"ini": "~1.3.0",
"minimist": "^1.2.0",
"strip-json-comments": "~2.0.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"read": {
"version": "1.0.7",
"bundled": true,
"dev": true,
"requires": {
"mute-stream": "~0.0.4"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"read-cmd-shim": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2019-11-11 19:23:17 +09:00
"version": "1.0.5",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"graceful-fs": "^4.1.2"
}
},
"read-installed": {
"version": "4.0.3",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"debuglog": "^1.0.1",
"graceful-fs": "^4.1.2",
"read-package-json": "^2.0.0",
"readdir-scoped-modules": "^1.0.0",
"semver": "2 || 3 || 4 || 5",
"slide": "~1.1.3",
"util-extend": "^1.0.1"
}
},
"read-package-json": {
Bump npm from 6.13.0 to 6.13.4 Bumps [npm](https://github.com/npm/cli) from 6.13.0 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.13.0...v6.13.4) Signed-off-by: dependabot[bot] <support@github.com>
2019-12-14 02:30:33 +09:00
"version": "2.1.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"glob": "^7.1.1",
"graceful-fs": "^4.1.2",
"json-parse-better-errors": "^1.0.1",
"normalize-package-data": "^2.0.0",
Bump npm from 6.13.0 to 6.13.4 Bumps [npm](https://github.com/npm/cli) from 6.13.0 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.13.0...v6.13.4) Signed-off-by: dependabot[bot] <support@github.com>
2019-12-14 02:30:33 +09:00
"npm-normalize-package-bin": "^1.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"read-package-tree": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "5.3.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"read-package-json": "^2.0.0",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"readdir-scoped-modules": "^1.0.0",
"util-promisify": "^2.1.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"readable-stream": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "3.6.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"inherits": "^2.0.3",
"string_decoder": "^1.1.1",
"util-deprecate": "^1.0.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"readdir-scoped-modules": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "1.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"debuglog": "^1.0.1",
"dezalgo": "^1.0.0",
"graceful-fs": "^4.1.2",
"once": "^1.3.0"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"registry-auth-token": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "3.4.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
"rc": "^1.1.6",
"safe-buffer": "^5.0.1"
}
},
"registry-url": {
"version": "3.1.0",
"bundled": true,
"dev": true,
"requires": {
"rc": "^1.0.1"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"request": {
Update packages
2018-11-25 05:00:22 +09:00
"version": "2.88.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"aws-sign2": "~0.7.0",
Update packages
2018-11-25 05:00:22 +09:00
"aws4": "^1.8.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"caseless": "~0.12.0",
Update packages
2018-11-25 05:00:22 +09:00
"combined-stream": "~1.0.6",
"extend": "~3.0.2",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"forever-agent": "~0.6.1",
Update packages
2018-11-25 05:00:22 +09:00
"form-data": "~2.3.2",
"har-validator": "~5.1.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"http-signature": "~1.2.0",
"is-typedarray": "~1.0.0",
"isstream": "~0.1.2",
"json-stringify-safe": "~5.0.1",
Update packages
2018-11-25 05:00:22 +09:00
"mime-types": "~2.1.19",
"oauth-sign": "~0.9.0",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"performance-now": "^2.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"qs": "~6.5.2",
"safe-buffer": "^5.1.2",
"tough-cookie": "~2.4.3",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"tunnel-agent": "^0.6.0",
Update packages
2018-11-25 05:00:22 +09:00
"uuid": "^3.3.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"require-directory": {
"version": "2.1.1",
"bundled": true,
"dev": true
},
"require-main-filename": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "2.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"resolve-from": {
"version": "4.0.0",
"bundled": true,
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"retry": {
"version": "0.12.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"rimraf": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "2.7.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"glob": "^7.1.3"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"run-queue": {
"version": "1.0.3",
"bundled": true,
"dev": true,
"requires": {
"aproba": "^1.1.1"
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"dependencies": {
"aproba": {
"version": "1.2.0",
"bundled": true,
"dev": true
}
Update packages
2018-11-25 05:00:22 +09:00
}
},
"safe-buffer": {
"version": "5.1.2",
"bundled": true,
"dev": true
},
"safer-buffer": {
"version": "2.1.2",
"bundled": true,
"dev": true
},
"semver": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "5.7.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"semver-diff": {
"version": "2.1.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"semver": "^5.0.3"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"set-blocking": {
"version": "2.0.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"sha": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "3.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"graceful-fs": "^4.1.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"shebang-command": {
"version": "1.2.0",
"bundled": true,
"dev": true,
"requires": {
"shebang-regex": "^1.0.0"
}
},
"shebang-regex": {
"version": "1.0.0",
"bundled": true,
"dev": true
},
"signal-exit": {
"version": "3.0.2",
"bundled": true,
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"slide": {
"version": "1.1.6",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"smart-buffer": {
Bump npm from 6.13.0 to 6.13.4 Bumps [npm](https://github.com/npm/cli) from 6.13.0 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.13.0...v6.13.4) Signed-off-by: dependabot[bot] <support@github.com>
2019-12-14 02:30:33 +09:00
"version": "4.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"socks": {
Bump npm from 6.13.0 to 6.13.4 Bumps [npm](https://github.com/npm/cli) from 6.13.0 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.13.0...v6.13.4) Signed-off-by: dependabot[bot] <support@github.com>
2019-12-14 02:30:33 +09:00
"version": "2.3.3",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Bump npm from 6.13.0 to 6.13.4 Bumps [npm](https://github.com/npm/cli) from 6.13.0 to 6.13.4. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.13.0...v6.13.4) Signed-off-by: dependabot[bot] <support@github.com>
2019-12-14 02:30:33 +09:00
"ip": "1.1.5",
"smart-buffer": "^4.1.0"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"socks-proxy-agent": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "4.0.2",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"agent-base": "~4.2.1",
"socks": "~2.3.2"
},
"dependencies": {
"agent-base": {
"version": "4.2.1",
"bundled": true,
"dev": true,
"requires": {
"es6-promisify": "^5.0.0"
}
}
Update packages
2018-11-25 05:00:22 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"sorted-object": {
"version": "2.0.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"sorted-union-stream": {
"version": "2.1.3",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"from2": "^1.3.0",
"stream-iterate": "^1.1.0"
},
"dependencies": {
"from2": {
"version": "1.3.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"inherits": "~2.0.1",
"readable-stream": "~1.1.10"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"isarray": {
"version": "0.0.1",
"bundled": true,
"dev": true
},
"readable-stream": {
"version": "1.1.14",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"core-util-is": "~1.0.0",
"inherits": "~2.0.1",
"isarray": "0.0.1",
"string_decoder": "~0.10.x"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
Update packages
2018-11-25 05:00:22 +09:00
},
"string_decoder": {
"version": "0.10.31",
"bundled": true,
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
},
Update packages
2018-11-25 05:00:22 +09:00
"spdx-correct": {
"version": "3.0.0",
"bundled": true,
"dev": true,
"requires": {
"spdx-expression-parse": "^3.0.0",
"spdx-license-ids": "^3.0.0"
}
},
"spdx-exceptions": {
"version": "2.1.0",
"bundled": true,
"dev": true
},
"spdx-expression-parse": {
"version": "3.0.0",
"bundled": true,
"dev": true,
"requires": {
"spdx-exceptions": "^2.1.0",
"spdx-license-ids": "^3.0.0"
}
},
"spdx-license-ids": {
Bump npm from 6.14.5 to 6.14.6 Bumps [npm](https://github.com/npm/cli) from 6.14.5 to 6.14.6. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](https://github.com/npm/cli/compare/v6.14.5...v6.14.6) Signed-off-by: dependabot[bot] <support@github.com>
2020-07-08 04:25:19 +09:00
"version": "3.0.5",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"bundled": true,
"dev": true
},
"split-on-first": {
"version": "1.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"sshpk": {
"version": "1.14.2",
"bundled": true,
"dev": true,
"requires": {
"asn1": "~0.2.3",
"assert-plus": "^1.0.0",
"bcrypt-pbkdf": "^1.0.0",
"dashdash": "^1.12.0",
"ecc-jsbn": "~0.1.1",
"getpass": "^0.1.1",
"jsbn": "~0.1.0",
"safer-buffer": "^2.0.2",
"tweetnacl": "~0.14.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"ssri": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2021-04-18 18:05:52 +09:00
"version": "6.0.2",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"dev": true,
"requires": {
"figgy-pudding": "^3.5.1"
}
Update packages
2018-11-25 05:00:22 +09:00
},
"stream-each": {
"version": "1.2.2",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"end-of-stream": "^1.1.0",
"stream-shift": "^1.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"stream-iterate": {
"version": "1.2.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"readable-stream": "^2.1.5",
"stream-shift": "^1.0.0"
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"dependencies": {
"readable-stream": {
"version": "2.3.6",
"bundled": true,
"dev": true,
"requires": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"string_decoder": {
"version": "1.1.1",
"bundled": true,
"dev": true,
"requires": {
"safe-buffer": "~5.1.0"
}
}
Update packages
2018-11-25 05:00:22 +09:00
}
},
"stream-shift": {
"version": "1.0.0",
"bundled": true,
"dev": true
},
"strict-uri-encode": {
"version": "2.0.0",
"bundled": true,
"dev": true
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"string_decoder": {
"version": "1.3.0",
"bundled": true,
"dev": true,
"requires": {
"safe-buffer": "~5.2.0"
},
"dependencies": {
"safe-buffer": {
"version": "5.2.0",
"bundled": true,
"dev": true
}
}
},
Update packages
2018-11-25 05:00:22 +09:00
"string-width": {
"version": "2.1.1",
"bundled": true,
"dev": true,
"requires": {
"is-fullwidth-code-point": "^2.0.0",
"strip-ansi": "^4.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
"ansi-regex": {
"version": "3.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"is-fullwidth-code-point": {
"version": "2.0.0",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
Update packages
2018-11-25 05:00:22 +09:00
},
"strip-ansi": {
"version": "4.0.0",
"bundled": true,
"dev": true,
"requires": {
"ansi-regex": "^3.0.0"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
},
Update packages
2018-11-25 05:00:22 +09:00
"stringify-package": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "1.0.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"strip-ansi": {
"version": "3.0.1",
"bundled": true,
"dev": true,
"requires": {
"ansi-regex": "^2.0.0"
}
},
"strip-eof": {
"version": "1.0.0",
"bundled": true,
"dev": true
},
"strip-json-comments": {
"version": "2.0.1",
"bundled": true,
"dev": true
},
"supports-color": {
"version": "5.4.0",
"bundled": true,
"dev": true,
"requires": {
"has-flag": "^3.0.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"tar": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "4.4.19",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"bundled": true,
Bump tar from 4.4.15 to 4.4.19 Bumps [tar](https://github.com/npm/node-tar) from 4.4.15 to 4.4.19. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.15...v4.4.19) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-01 01:39:41 +09:00
"dev": true,
"requires": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"chownr": "^1.1.4",
"fs-minipass": "^1.2.7",
"minipass": "^2.9.0",
"minizlib": "^1.3.3",
"mkdirp": "^0.5.5",
"safe-buffer": "^5.2.1",
"yallist": "^3.1.1"
Bump tar from 4.4.15 to 4.4.19 Bumps [tar](https://github.com/npm/node-tar) from 4.4.15 to 4.4.19. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.15...v4.4.19) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-01 01:39:41 +09:00
},
"dependencies": {
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"minipass": {
"version": "2.9.0",
"bundled": true,
"dev": true,
"requires": {
"safe-buffer": "^5.1.2",
"yallist": "^3.0.0"
}
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
},
"safe-buffer": {
"version": "5.2.1",
"bundled": true,
"dev": true
},
"yallist": {
"version": "3.1.1",
"bundled": true,
"dev": true
Bump tar from 4.4.15 to 4.4.19 Bumps [tar](https://github.com/npm/node-tar) from 4.4.15 to 4.4.19. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.15...v4.4.19) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-01 01:39:41 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"term-size": {
"version": "1.2.0",
"bundled": true,
"dev": true,
"requires": {
"execa": "^0.7.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"text-table": {
"version": "0.2.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"through": {
"version": "2.3.8",
"bundled": true,
"dev": true
},
"through2": {
"version": "2.0.3",
"bundled": true,
"dev": true,
"requires": {
"readable-stream": "^2.1.5",
"xtend": "~4.0.1"
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
},
"dependencies": {
"readable-stream": {
"version": "2.3.6",
"bundled": true,
"dev": true,
"requires": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"string_decoder": {
"version": "1.1.1",
"bundled": true,
"dev": true,
"requires": {
"safe-buffer": "~5.1.0"
}
}
Update packages
2018-11-25 05:00:22 +09:00
}
},
"timed-out": {
"version": "4.0.1",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"tiny-relative-date": {
"version": "1.3.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"tough-cookie": {
"version": "2.4.3",
"bundled": true,
"dev": true,
"requires": {
"psl": "^1.1.24",
"punycode": "^1.4.1"
}
},
"tunnel-agent": {
"version": "0.6.0",
"bundled": true,
"dev": true,
"requires": {
"safe-buffer": "^5.0.1"
}
},
"tweetnacl": {
"version": "0.14.5",
"bundled": true,
"dev": true,
"optional": true
},
"typedarray": {
"version": "0.0.6",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"uid-number": {
"version": "0.0.6",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"umask": {
"version": "1.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"unique-filename": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "1.1.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"unique-slug": "^2.0.0"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"unique-slug": {
"version": "2.0.0",
"bundled": true,
"dev": true,
"requires": {
"imurmurhash": "^0.1.4"
}
},
"unique-string": {
"version": "1.0.0",
"bundled": true,
"dev": true,
"requires": {
"crypto-random-string": "^1.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"unpipe": {
"version": "1.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"unzip-response": {
"version": "2.0.1",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"update-notifier": {
"version": "2.5.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"boxen": "^1.2.1",
"chalk": "^2.0.1",
"configstore": "^3.0.0",
"import-lazy": "^2.1.0",
"is-ci": "^1.0.10",
"is-installed-globally": "^0.1.0",
"is-npm": "^1.0.0",
"latest-version": "^3.0.0",
"semver-diff": "^2.0.0",
"xdg-basedir": "^3.0.0"
}
},
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-11-29 17:47:33 +09:00
"uri-js": {
"version": "4.4.0",
"bundled": true,
"dev": true,
"requires": {
"punycode": "^2.1.0"
},
"dependencies": {
"punycode": {
"version": "2.1.1",
"bundled": true,
"dev": true
}
}
},
Update packages
2018-11-25 05:00:22 +09:00
"url-parse-lax": {
"version": "1.0.0",
"bundled": true,
"dev": true,
"requires": {
"prepend-http": "^1.0.1"
}
},
"util-deprecate": {
"version": "1.0.2",
"bundled": true,
"dev": true
},
"util-extend": {
"version": "1.0.3",
"bundled": true,
"dev": true
},
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"util-promisify": {
"version": "2.1.0",
"bundled": true,
"dev": true,
"requires": {
"object.getownpropertydescriptors": "^2.0.3"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"uuid": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2019-11-11 19:23:17 +09:00
"version": "3.3.3",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"validate-npm-package-license": {
Update packages
2018-11-25 05:00:22 +09:00
"version": "3.0.4",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"spdx-correct": "^3.0.0",
"spdx-expression-parse": "^3.0.0"
}
},
"validate-npm-package-name": {
"version": "3.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"builtins": "^1.0.3"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"verror": {
"version": "1.10.0",
"bundled": true,
"dev": true,
"requires": {
"assert-plus": "^1.0.0",
"core-util-is": "1.0.2",
"extsprintf": "^1.2.0"
}
},
"wcwidth": {
"version": "1.0.1",
"bundled": true,
"dev": true,
"requires": {
"defaults": "^1.0.3"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"which": {
Update packages
2018-11-25 05:00:22 +09:00
"version": "1.3.1",
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"isexe": "^2.0.0"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"which-module": {
"version": "2.0.0",
"bundled": true,
"dev": true
},
"wide-align": {
"version": "1.1.2",
"bundled": true,
"dev": true,
"requires": {
"string-width": "^1.0.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
Update packages
2018-11-25 05:00:22 +09:00
"string-width": {
"version": "1.0.2",
"bundled": true,
"dev": true,
"requires": {
"code-point-at": "^1.0.0",
"is-fullwidth-code-point": "^1.0.0",
"strip-ansi": "^3.0.0"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
},
Update packages
2018-11-25 05:00:22 +09:00
"widest-line": {
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"version": "2.0.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
"string-width": "^2.1.1"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"worker-farm": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "1.7.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"errno": "~0.1.7"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"wrap-ansi": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "5.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"ansi-styles": "^3.2.0",
"string-width": "^3.0.0",
"strip-ansi": "^5.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"ansi-regex": {
"version": "4.1.0",
"bundled": true,
"dev": true
},
"is-fullwidth-code-point": {
"version": "2.0.0",
"bundled": true,
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"string-width": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "3.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"emoji-regex": "^7.0.1",
"is-fullwidth-code-point": "^2.0.0",
"strip-ansi": "^5.1.0"
}
},
"strip-ansi": {
"version": "5.2.0",
"bundled": true,
"dev": true,
"requires": {
"ansi-regex": "^4.1.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
}
},
"wrappy": {
"version": "1.0.2",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"write-file-atomic": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "2.4.3",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"graceful-fs": "^4.1.11",
"imurmurhash": "^0.1.4",
"signal-exit": "^3.0.2"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"xdg-basedir": {
"version": "3.0.0",
"bundled": true,
"dev": true
},
"xtend": {
"version": "4.0.1",
"bundled": true,
"dev": true
},
"y18n": {
Bump y18n from 3.2.1 to 3.2.2 Bumps [y18n](https://github.com/yargs/y18n) from 3.2.1 to 3.2.2. - [Release notes](https://github.com/yargs/y18n/releases) - [Changelog](https://github.com/yargs/y18n/blob/master/CHANGELOG.md) - [Commits](https://github.com/yargs/y18n/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-30 20:50:58 +09:00
"version": "4.0.1",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2021-04-18 18:05:52 +09:00
"bundled": true,
Update packages
2018-11-25 05:00:22 +09:00
"dev": true
},
"yallist": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "3.0.3",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true
},
"yargs": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "14.2.3",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"cliui": "^5.0.0",
"decamelize": "^1.2.0",
"find-up": "^3.0.0",
"get-caller-file": "^2.0.1",
Update packages
2018-11-25 05:00:22 +09:00
"require-directory": "^2.1.1",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"require-main-filename": "^2.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"set-blocking": "^2.0.0",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"string-width": "^3.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"which-module": "^2.0.0",
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"y18n": "^4.0.0",
"yargs-parser": "^15.0.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"ansi-regex": {
"version": "4.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
},
"find-up": {
"version": "3.0.0",
"bundled": true,
"dev": true,
"requires": {
"locate-path": "^3.0.0"
}
},
"is-fullwidth-code-point": {
"version": "2.0.0",
"bundled": true,
"dev": true
},
"locate-path": {
"version": "3.0.0",
"bundled": true,
"dev": true,
"requires": {
"p-locate": "^3.0.0",
"path-exists": "^3.0.0"
}
},
"p-limit": {
"version": "2.3.0",
"bundled": true,
"dev": true,
"requires": {
"p-try": "^2.0.0"
}
},
"p-locate": {
"version": "3.0.0",
"bundled": true,
"dev": true,
"requires": {
"p-limit": "^2.0.0"
}
},
"p-try": {
"version": "2.2.0",
"bundled": true,
"dev": true
},
"string-width": {
"version": "3.1.0",
"bundled": true,
"dev": true,
"requires": {
"emoji-regex": "^7.0.1",
"is-fullwidth-code-point": "^2.0.0",
"strip-ansi": "^5.1.0"
}
},
"strip-ansi": {
"version": "5.2.0",
"bundled": true,
"dev": true,
"requires": {
"ansi-regex": "^4.1.0"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
Update packages
2018-11-25 05:00:22 +09:00
},
"yargs-parser": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"version": "15.0.1",
Update packages
2018-11-25 05:00:22 +09:00
"bundled": true,
"dev": true,
"requires": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2020-09-20 18:40:20 +09:00
"camelcase": "^5.0.0",
"decamelize": "^1.2.0"
},
"dependencies": {
"camelcase": {
"version": "5.3.1",
"bundled": true,
"dev": true
}
Update packages
2018-11-25 05:00:22 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
},
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"npmlog": {
"version": "4.1.2",
"resolved": "https://registry.npmjs.org/npmlog/-/npmlog-4.1.2.tgz",
"integrity": "sha512-2uUqazuKlTaSI/dC8AzicUck7+IrEaOnN/e0jd3Xtt1KcGpwx30v50mL7oPyr/h9bL3E4aZccVwpwP+5W9Vjkg==",
"dev": true,
"requires": {
"are-we-there-yet": "~1.1.2",
"console-control-strings": "~1.1.0",
"gauge": "~2.7.3",
"set-blocking": "~2.0.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"number-is-nan": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/number-is-nan/-/number-is-nan-1.0.1.tgz",
"integrity": "sha1-CXtgK1NCKlIsGvuHkDGDNpQaAR0=",
"dev": true
},
"object-assign": {
"version": "4.1.1",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.1.1.tgz",
"integrity": "sha1-IQmtx5ZYh8/AXLvUQsrIv7s2CGM=",
"dev": true
},
"object-copy": {
"version": "0.1.0",
"resolved": "https://registry.npmjs.org/object-copy/-/object-copy-0.1.0.tgz",
"integrity": "sha1-fn2Fi3gb18mRpBupde04EnVOmYw=",
"dev": true,
"requires": {
"copy-descriptor": "^0.1.0",
"define-property": "^0.2.5",
"kind-of": "^3.0.3"
},
"dependencies": {
"define-property": {
"version": "0.2.5",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-0.2.5.tgz",
"integrity": "sha1-w1se+RjsPJkPmlvFe+BKrOxcgRY=",
"dev": true,
"requires": {
"is-descriptor": "^0.1.0"
}
},
"kind-of": {
"version": "3.2.2",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz",
"integrity": "sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=",
"dev": true,
"requires": {
"is-buffer": "^1.1.5"
}
}
}
},
Update `npm` packages
2019-12-19 19:28:13 +09:00
"object-inspect": {
Update npm packages
2021-08-22 17:38:52 +09:00
"version": "1.11.0",
"resolved": "https://registry.npmjs.org/object-inspect/-/object-inspect-1.11.0.tgz",
"integrity": "sha512-jp7ikS6Sd3GxQfZJPyH3cjcbJF6GZPClgdV+EFygjFLQ5FmW/dRUnTd9PQ9k0JhoNDabWFbpF1yCdSWCC6gexg==",
Update npm packages
2021-05-16 17:05:58 +09:00
"dev": true
Update `npm` packages
2019-12-19 19:28:13 +09:00
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"object-keys": {
"version": "1.0.11",
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.0.11.tgz",
"integrity": "sha1-xUYBd4rVYPEULODgG8yotW0TQm0=",
"dev": true
},
"object-visit": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/object-visit/-/object-visit-1.0.1.tgz",
"integrity": "sha1-95xEk68MU3e1n+OdOV5BBC3QRbs=",
"dev": true,
"requires": {
"isobject": "^3.0.0"
}
},
"object.assign": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/object.assign/-/object.assign-4.1.0.tgz",
"integrity": "sha512-exHJeq6kBKj58mqGyTQ9DFvrZC/eR6OwxzoM9YRoGBqrXYonaFyGiFMuc9VZrXf7DarreEwMpurG3dd+CNyW5w==",
"dev": true,
"requires": {
"define-properties": "^1.1.2",
"function-bind": "^1.1.1",
"has-symbols": "^1.0.0",
"object-keys": "^1.0.11"
}
},
"object.defaults": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/object.defaults/-/object.defaults-1.1.0.tgz",
"integrity": "sha1-On+GgzS0B96gbaFtiNXNKeQ1/s8=",
"dev": true,
"requires": {
"array-each": "^1.0.1",
"array-slice": "^1.0.0",
"for-own": "^1.0.0",
"isobject": "^3.0.0"
}
},
"object.map": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/object.map/-/object.map-1.0.1.tgz",
"integrity": "sha1-z4Plncj8wK1fQlDh94s7gb2AHTc=",
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"for-own": "^1.0.0",
"make-iterator": "^1.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"object.pick": {
"version": "1.3.0",
"resolved": "https://registry.npmjs.org/object.pick/-/object.pick-1.3.0.tgz",
"integrity": "sha1-h6EKxMFpS9Lhy/U1kaZhQftd10c=",
"dev": true,
"requires": {
"isobject": "^3.0.1"
}
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"object.reduce": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/object.reduce/-/object.reduce-1.0.1.tgz",
"integrity": "sha1-b+NI8qx/oPlcpiEiZZkJaCW7A60=",
"dev": true,
"requires": {
"for-own": "^1.0.0",
"make-iterator": "^1.0.0"
}
},
Update packages
2019-08-25 03:08:09 +09:00
"object.values": {
Update npm packages
2021-10-17 18:33:19 +09:00
"version": "1.1.5",
"resolved": "https://registry.npmjs.org/object.values/-/object.values-1.1.5.tgz",
"integrity": "sha512-QUZRW0ilQ3PnPpbNtgdNV1PDbEqLIiSFB3l+EnGtBQ/8SUTLj1PZwtQHABZtLgwpJZTSZhuGLOGk57Drx2IvYg==",
Update packages
2019-08-25 03:08:09 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-16 17:05:58 +09:00
"call-bind": "^1.0.2",
Update packages
2019-08-25 03:08:09 +09:00
"define-properties": "^1.1.3",
Update npm packages
2021-10-17 18:33:19 +09:00
"es-abstract": "^1.19.1"
Update packages
2019-08-25 03:08:09 +09:00
},
"dependencies": {
"define-properties": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.1.3.tgz",
"integrity": "sha512-3MqfYKj2lLzdMSf8ZIZE/V+Zuy+BgD6f164e8K2w7dgnpKArBDerGYpM46IYYcjnkdPNMjPk9A6VFB8+3SKlXQ==",
"dev": true,
"requires": {
"object-keys": "^1.0.12"
}
},
"object-keys": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz",
"integrity": "sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==",
"dev": true
}
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"once": {
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/once/-/once-1.4.0.tgz",
"integrity": "sha1-WDsap3WWHUsROsF9nFC6753Xa9E=",
"dev": true,
"requires": {
"wrappy": "1"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"one-time": {
"version": "0.0.4",
"resolved": "https://registry.npmjs.org/one-time/-/one-time-0.0.4.tgz",
"integrity": "sha1-+M33eISCb+Tf+T46nMN7HkSAdC4=",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"optionator": {
Update `npm` packages
2020-01-31 22:04:49 +09:00
"version": "0.8.3",
"resolved": "https://registry.npmjs.org/optionator/-/optionator-0.8.3.tgz",
"integrity": "sha512-+IW9pACdk3XWmmTXG8m3upGUJst5XRGzxMRjXzAuJ1XnIFNvfhjjIuYkDvysnPQ7qzqVzLt78BCruntqRhWQbA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"deep-is": "~0.1.3",
Update `npm` packages
2020-01-31 22:04:49 +09:00
"fast-levenshtein": "~2.0.6",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"levn": "~0.3.0",
"prelude-ls": "~1.1.2",
"type-check": "~0.3.2",
Update `npm` packages
2020-01-31 22:04:49 +09:00
"word-wrap": "~1.2.3"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"ordered-read-streams": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/ordered-read-streams/-/ordered-read-streams-1.0.1.tgz",
"integrity": "sha1-d8DLN8QVJdZBZtmQ/61+xqDhNj4=",
"dev": true,
"requires": {
"readable-stream": "^2.0.1"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"p-limit": {
Update npm packages
2021-05-16 17:05:58 +09:00
"version": "1.3.0",
"resolved": "https://registry.npmjs.org/p-limit/-/p-limit-1.3.0.tgz",
"integrity": "sha512-vvcXsLAJ9Dr5rQOPk7toZQZJApBl2K4J6dANSsEuh6QI41JYcsS/qhTGa9ErIUUgK3WNQoJYvylxvjqmiqEA9Q==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"p-try": "^1.0.0"
}
},
"p-locate": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/p-locate/-/p-locate-2.0.0.tgz",
"integrity": "sha1-IKAQOyIqcMj9OcwuWAaA893l7EM=",
"dev": true,
"requires": {
"p-limit": "^1.1.0"
}
},
"p-try": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/p-try/-/p-try-1.0.0.tgz",
"integrity": "sha1-y8ec26+P1CKOE/Yh8rGiN8GyB7M=",
"dev": true
},
Update packages
2019-01-05 22:27:47 +09:00
"parent-module": {
Update packages
2019-03-31 02:59:52 +09:00
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/parent-module/-/parent-module-1.0.1.tgz",
"integrity": "sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==",
Update packages
2019-01-05 22:27:47 +09:00
"dev": true,
"requires": {
"callsites": "^3.0.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"parse-filepath": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/parse-filepath/-/parse-filepath-1.0.2.tgz",
"integrity": "sha1-pjISf1Oq89FYdvWHLz/6x2PWyJE=",
"dev": true,
"requires": {
"is-absolute": "^1.0.0",
"map-cache": "^0.2.0",
"path-root": "^0.1.1"
}
},
"parse-json": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"integrity": "sha1-9ID0BDTvgHQfhGkJn43qGPVaTck=",
"dev": true,
"requires": {
"error-ex": "^1.2.0"
}
},
Update packages
2018-12-23 00:00:53 +09:00
"parse-node-version": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/parse-node-version/-/parse-node-version-1.0.0.tgz",
"integrity": "sha512-02GTVHD1u0nWc20n2G7WX/PgdhNFG04j5fi1OkaJzPWLTcf6vh6229Lta1wTmXG/7Dg42tCssgkccVt7qvd8Kg==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"parse-passwd": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/parse-passwd/-/parse-passwd-1.0.0.tgz",
"integrity": "sha1-bVuTSkVpk7I9N/QKOC1vFmao5cY=",
"dev": true
},
"pascalcase": {
"version": "0.1.1",
"resolved": "https://registry.npmjs.org/pascalcase/-/pascalcase-0.1.1.tgz",
"integrity": "sha1-s2PlXoAGym/iF4TS2yK9FdeRfxQ=",
"dev": true
},
"path-dirname": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/path-dirname/-/path-dirname-1.0.2.tgz",
"integrity": "sha1-zDPSTVJeCZpTiMAzbG4yuRYGCeA=",
"dev": true
},
"path-exists": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-3.0.0.tgz",
"integrity": "sha1-zg6+ql94yxiSXqfYENe1mwEP1RU=",
"dev": true
},
"path-is-absolute": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.1.tgz",
"integrity": "sha1-F0uSaHNVNP+8es5r9TpanhtcX18=",
"dev": true
},
"path-parse": {
Bump path-parse from 1.0.5 to 1.0.7 Bumps [path-parse](https://github.com/jbgutierrez/path-parse) from 1.0.5 to 1.0.7. - [Release notes](https://github.com/jbgutierrez/path-parse/releases) - [Commits](https://github.com/jbgutierrez/path-parse/commits/v1.0.7) --- updated-dependencies: - dependency-name: path-parse dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-11 03:23:47 +09:00
"version": "1.0.7",
"resolved": "https://registry.npmjs.org/path-parse/-/path-parse-1.0.7.tgz",
"integrity": "sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"path-root": {
"version": "0.1.1",
"resolved": "https://registry.npmjs.org/path-root/-/path-root-0.1.1.tgz",
"integrity": "sha1-mkpoFMrBwM1zNgqV8yCDyOpHRbc=",
"dev": true,
"requires": {
"path-root-regex": "^0.1.0"
}
},
"path-root-regex": {
"version": "0.1.2",
"resolved": "https://registry.npmjs.org/path-root-regex/-/path-root-regex-0.1.2.tgz",
"integrity": "sha1-v8zcjfWxLcUsi0PsONGNcsBLqW0=",
"dev": true
},
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"path-type": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-4.0.0.tgz",
"integrity": "sha512-gDKb8aZMDeD/tZWs9P6+q0J9Mwkdl6xMV8TjnGP3qJVJ06bdMgkbBlLU8IdfOsIsFz2BW1rNVT3XuNEl8zPAvw==",
"dev": true
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"pend": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/pend/-/pend-1.2.0.tgz",
"integrity": "sha1-elfrVQpng/kRUzH89GY9XI4AelA=",
"dev": true
},
Update npm packages
2021-10-17 18:33:19 +09:00
"picocolors": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/picocolors/-/picocolors-1.0.0.tgz",
"integrity": "sha512-1fygroTLlHu66zi26VoTDv8yRgm0Fccecssto+MhsZ0D/DGW2sm8E8AjW7NU5VVTRt5GxbeZ5qBuJr+HyLYkjQ==",
"dev": true
},
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
"picomatch": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/picomatch/-/picomatch-2.3.0.tgz",
"integrity": "sha512-lY1Q/PiJGC2zOv/z391WOTD+Z02bCgsFfvxoXXf6h7kv9o+WmsmzYqrAwY63sNgOxE4xEdq0WyUnXfKeBrSvYw==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
},
Enable eslint-plugin-import to prevent unresolved paths
2018-11-23 21:50:28 +09:00
"pinkie": {
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/pinkie/-/pinkie-2.0.4.tgz",
"integrity": "sha1-clVrgM+g1IqXToDnckjoDtT3+HA=",
"dev": true
},
"pinkie-promise": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/pinkie-promise/-/pinkie-promise-2.0.1.tgz",
"integrity": "sha1-ITXW36ejWMBprJsXh3YogihFD/o=",
"dev": true,
"requires": {
"pinkie": "^2.0.0"
}
},
Update npm packages
2021-10-03 15:21:01 +09:00
"pkg-dir": {
"version": "4.2.0",
"resolved": "https://registry.npmjs.org/pkg-dir/-/pkg-dir-4.2.0.tgz",
"integrity": "sha512-HRDzbaKjC+AOWVXxAU/x54COGeIv9eb+6CkDSQoNTt4XyWoIJvuPsXizxu/Fr23EiekbtZwmh1IcIG/l/a10GQ==",
"dev": true,
"requires": {
"find-up": "^4.0.0"
},
"dependencies": {
"find-up": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-4.1.0.tgz",
"integrity": "sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw==",
"dev": true,
"requires": {
"locate-path": "^5.0.0",
"path-exists": "^4.0.0"
}
},
"locate-path": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/locate-path/-/locate-path-5.0.0.tgz",
"integrity": "sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g==",
"dev": true,
"requires": {
"p-locate": "^4.1.0"
}
},
"p-limit": {
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/p-limit/-/p-limit-2.3.0.tgz",
"integrity": "sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w==",
"dev": true,
"requires": {
"p-try": "^2.0.0"
}
},
"p-locate": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/p-locate/-/p-locate-4.1.0.tgz",
"integrity": "sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A==",
"dev": true,
"requires": {
"p-limit": "^2.2.0"
}
},
"p-try": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/p-try/-/p-try-2.2.0.tgz",
"integrity": "sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ==",
"dev": true
},
"path-exists": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-4.0.0.tgz",
"integrity": "sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==",
"dev": true
}
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"plugin-error": {
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/plugin-error/-/plugin-error-1.0.1.tgz",
"integrity": "sha512-L1zP0dk7vGweZME2i+EeakvUNqSrdiI3F91TwEoYiGrAfUXmVv6fJIq4g82PAXxNsWOp0J7ZqQy/3Szz0ajTxA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"ansi-colors": "^1.0.1",
"arr-diff": "^4.0.0",
"arr-union": "^3.1.0",
"extend-shallow": "^3.0.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update `npm` packages
2020-05-30 17:58:10 +09:00
"pluralize": {
"version": "8.0.0",
"resolved": "https://registry.npmjs.org/pluralize/-/pluralize-8.0.0.tgz",
"integrity": "sha512-Nc3IT5yHzflTfbjgqWcCPpo7DaKy4FnpB0l/zCAW0Tc7jxAiuqSxHasntB3D7887LSrA93kDJ9IXovxJYxyLCA==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"posix-character-classes": {
"version": "0.1.1",
"resolved": "https://registry.npmjs.org/posix-character-classes/-/posix-character-classes-0.1.1.tgz",
"integrity": "sha1-AerA/jta9xoqbAL+q7jB/vfgDqs=",
"dev": true
},
"postcss": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "8.4.6",
"resolved": "https://registry.npmjs.org/postcss/-/postcss-8.4.6.tgz",
"integrity": "sha512-OovjwIzs9Te46vlEx7+uXB0PLijpwjXGKXjVGGPIGubGpq7uh5Xgf6D6FiJ/SzJMBosHDp6a2hiXOS97iBXcaA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-02-06 19:24:14 +09:00
"nanoid": "^3.2.0",
Update npm packages
2021-10-31 17:38:18 +09:00
"picocolors": "^1.0.0",
Update npm packages
2022-02-06 19:24:14 +09:00
"source-map-js": "^1.0.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update the left/right CSS calculation for the `sidebarContainer` HTML element to enable IE11 compatibility As gross as this hack is, it nonetheless seem necessary to allow using CSS variables; see also https://github.com/mozilla/pdf.js/pull/11567#issuecomment-582166160
2020-02-05 08:34:44 +09:00
"postcss-calc": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "8.2.4",
"resolved": "https://registry.npmjs.org/postcss-calc/-/postcss-calc-8.2.4.tgz",
"integrity": "sha512-SmWMSJmB8MRnnULldx0lQIyhSNvuDl9HfrZkaqqE/WHAhToYsAvDq+yAsA/kIyINDszOp3Rh0GFoNuH5Ypsm3Q==",
Update the left/right CSS calculation for the `sidebarContainer` HTML element to enable IE11 compatibility As gross as this hack is, it nonetheless seem necessary to allow using CSS variables; see also https://github.com/mozilla/pdf.js/pull/11567#issuecomment-582166160
2020-02-05 08:34:44 +09:00
"dev": true,
"requires": {
Update npm packages
2022-02-20 18:08:23 +09:00
"postcss-selector-parser": "^6.0.9",
"postcss-value-parser": "^4.2.0"
Update the left/right CSS calculation for the `sidebarContainer` HTML element to enable IE11 compatibility As gross as this hack is, it nonetheless seem necessary to allow using CSS variables; see also https://github.com/mozilla/pdf.js/pull/11567#issuecomment-582166160
2020-02-05 08:34:44 +09:00
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"postcss-load-config": {
Update npm packages
2021-09-05 16:47:57 +09:00
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/postcss-load-config/-/postcss-load-config-3.1.0.tgz",
"integrity": "sha512-ipM8Ds01ZUophjDTQYSVP70slFSYg3T0/zyfII5vzhN6V57YSxMgG5syXuwi5VtS8wSf3iL30v0uBdoIVx4Q0g==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-09-05 16:47:57 +09:00
"import-cwd": "^3.0.0",
"lilconfig": "^2.0.3",
"yaml": "^1.10.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"postcss-media-query-parser": {
"version": "0.2.3",
"resolved": "https://registry.npmjs.org/postcss-media-query-parser/-/postcss-media-query-parser-0.2.3.tgz",
"integrity": "sha1-J7Ocb02U+Bsac7j3Y1HGCeXO8kQ=",
"dev": true
},
"postcss-resolve-nested-selector": {
"version": "0.1.1",
"resolved": "https://registry.npmjs.org/postcss-resolve-nested-selector/-/postcss-resolve-nested-selector-0.1.1.tgz",
"integrity": "sha1-Kcy8fDfe36wwTp//C/FZaz9qDk4=",
"dev": true
},
"postcss-safe-parser": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"version": "6.0.0",
"resolved": "https://registry.npmjs.org/postcss-safe-parser/-/postcss-safe-parser-6.0.0.tgz",
"integrity": "sha512-FARHN8pwH+WiS2OPCxJI8FuRJpTVnn6ZNFiqAM2aeW2LwTHWWmWgIyKC6cUo0L8aeKiF/14MNvnpls6R2PBeMQ==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"requires": {}
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
},
Update the left/right CSS calculation for the `sidebarContainer` HTML element to enable IE11 compatibility As gross as this hack is, it nonetheless seem necessary to allow using CSS variables; see also https://github.com/mozilla/pdf.js/pull/11567#issuecomment-582166160
2020-02-05 08:34:44 +09:00
"postcss-selector-parser": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "6.0.9",
"resolved": "https://registry.npmjs.org/postcss-selector-parser/-/postcss-selector-parser-6.0.9.tgz",
"integrity": "sha512-UO3SgnZOVTwu4kyLR22UQ1xZh086RyNZppb7lLAKBFK8a32ttG5i87Y/P3+2bRSjZNyJ1B7hfFNo273tKe9YxQ==",
Update the left/right CSS calculation for the `sidebarContainer` HTML element to enable IE11 compatibility As gross as this hack is, it nonetheless seem necessary to allow using CSS variables; see also https://github.com/mozilla/pdf.js/pull/11567#issuecomment-582166160
2020-02-05 08:34:44 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-02-22 01:38:22 +09:00
"cssesc": "^3.0.0",
Update `npm` packages
2020-10-04 20:49:28 +09:00
"util-deprecate": "^1.0.2"
Update the left/right CSS calculation for the `sidebarContainer` HTML element to enable IE11 compatibility As gross as this hack is, it nonetheless seem necessary to allow using CSS variables; see also https://github.com/mozilla/pdf.js/pull/11567#issuecomment-582166160
2020-02-05 08:34:44 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"postcss-value-parser": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "4.2.0",
"resolved": "https://registry.npmjs.org/postcss-value-parser/-/postcss-value-parser-4.2.0.tgz",
"integrity": "sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"prelude-ls": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.1.2.tgz",
"integrity": "sha1-IZMqVJ9eUv/ZqCf1cOBL5iqX2lQ=",
"dev": true
},
Update the `eslint-plugin-mozilla` to the latest version (PR 10905 follow-up) This required adding a number of additional dependencies, based on https://dxr.mozilla.org/mozilla-central/rev/4aed8e10318f38571712350856bf9e61c5f84e1f/tools/lint/eslint/eslint-plugin-mozilla/package.json#32-37 Since this, implicitly, enabled "prettier"[1] for the `extensions/firefox` directory a couple of small code changes were necessary as well. --- [1] Generally speaking I'm wondering if that name is deliberately ironic, since the style it enforces is often times extremely weird and ugly :-P
2019-09-07 19:37:13 +09:00
"prettier": {
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"version": "2.5.1",
"resolved": "https://registry.npmjs.org/prettier/-/prettier-2.5.1.tgz",
"integrity": "sha512-vBZcPRUR5MZJwoyi3ZoyQlc1rXeEck8KgeC9AwwOn+exuxLxq5toTRDTSaVrXHxelDMHy9zlicw8u66yxoSUFg==",
Update the `eslint-plugin-mozilla` to the latest version (PR 10905 follow-up) This required adding a number of additional dependencies, based on https://dxr.mozilla.org/mozilla-central/rev/4aed8e10318f38571712350856bf9e61c5f84e1f/tools/lint/eslint/eslint-plugin-mozilla/package.json#32-37 Since this, implicitly, enabled "prettier"[1] for the `extensions/firefox` directory a couple of small code changes were necessary as well. --- [1] Generally speaking I'm wondering if that name is deliberately ironic, since the style it enforces is often times extremely weird and ugly :-P
2019-09-07 19:37:13 +09:00
"dev": true
},
"prettier-linter-helpers": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/prettier-linter-helpers/-/prettier-linter-helpers-1.0.0.tgz",
"integrity": "sha512-GbK2cP9nraSSUF9N2XwUwqfzlAFlMNYYl+ShE/V+H8a9uNl/oUqB1w2EL54Jh0OlyRSd8RfWYJ3coVS4TROP2w==",
"dev": true,
"requires": {
"fast-diff": "^1.1.2"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"pretty-hrtime": {
"version": "1.0.3",
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"resolved": "https://registry.npmjs.org/pretty-hrtime/-/pretty-hrtime-1.0.3.tgz",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"integrity": "sha1-t+PqQkNaTJsnWdmeDyAesZWALuE=",
"dev": true
},
"process-nextick-args": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-2.0.0.tgz",
"integrity": "sha512-MtEC1TqN0EU5nephaJ4rAtThHtC86dNN9qCuEhtshvpVBkAW5ZO7BASN9REnF9eoXGcRub+pFuKEpOHE+HbEMw==",
"dev": true
},
"progress": {
Update packages
2018-12-23 00:00:53 +09:00
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/progress/-/progress-2.0.3.tgz",
"integrity": "sha512-7PiHtLll5LdnKIMw100I+8xJXR5gW2QwWYkT6iJva0bXitZKa/XMrSbdmg3r2Xnaidz9Qumd0VPaMrZlF9V9sA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"promise": {
"version": "7.3.1",
"resolved": "https://registry.npmjs.org/promise/-/promise-7.3.1.tgz",
"integrity": "sha512-nolQXZ/4L+bP/UGlkfaIujX9BKxGwmQ9OT4mOt5yvy8iK1h3wqTEJCijzGANTCCl9nWjY41juyAn2K3Q1hLLTg==",
"dev": true,
"requires": {
"asap": "~2.0.3"
}
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"proxy-from-env": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/proxy-from-env/-/proxy-from-env-1.1.0.tgz",
"integrity": "sha512-D+zkORCbA9f1tdWRK0RaCR3GPv50cMxcrz4X8k5LTSUD1Dkw47mKJEZQNunItRTkWwgtaUSo1RVFRIG9ZXiFYg==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"prr": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/prr/-/prr-1.0.1.tgz",
"integrity": "sha1-0/wRS6BplaRexok/SEzrHXj19HY=",
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"pug": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/pug/-/pug-2.0.4.tgz",
"integrity": "sha512-XhoaDlvi6NIzL49nu094R2NA6P37ijtgMDuWE+ofekDChvfKnzFal60bhSdiy8y2PBO6fmz3oMEIcfpBVRUdvw==",
Update packages
2018-11-25 05:00:22 +09:00
"dev": true,
"requires": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"pug-code-gen": "^2.0.2",
"pug-filters": "^3.1.1",
"pug-lexer": "^4.1.0",
"pug-linker": "^3.0.6",
"pug-load": "^2.0.12",
"pug-parser": "^5.0.1",
"pug-runtime": "^2.0.5",
"pug-strip-comments": "^1.0.4"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"pug-code-gen": {
Bump pug-code-gen from 2.0.1 to 2.0.3 Bumps [pug-code-gen](https://github.com/pugjs/pug) from 2.0.1 to 2.0.3. - [Release notes](https://github.com/pugjs/pug/releases) - [Commits](https://github.com/pugjs/pug/compare/pug-code-gen@2.0.1...pug@2.0.3) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-03 11:28:49 +09:00
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/pug-code-gen/-/pug-code-gen-2.0.3.tgz",
"integrity": "sha512-r9sezXdDuZJfW9J91TN/2LFbiqDhmltTFmGpHTsGdrNGp3p4SxAjjXEfnuK2e4ywYsRIVP0NeLbSAMHUcaX1EA==",
Update packages
2018-11-25 05:00:22 +09:00
"dev": true,
"requires": {
Bump pug-code-gen from 2.0.1 to 2.0.3 Bumps [pug-code-gen](https://github.com/pugjs/pug) from 2.0.1 to 2.0.3. - [Release notes](https://github.com/pugjs/pug/releases) - [Commits](https://github.com/pugjs/pug/compare/pug-code-gen@2.0.1...pug@2.0.3) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-03 11:28:49 +09:00
"constantinople": "^3.1.2",
Update packages
2018-11-25 05:00:22 +09:00
"doctypes": "^1.1.0",
"js-stringify": "^1.0.1",
Bump pug-code-gen from 2.0.1 to 2.0.3 Bumps [pug-code-gen](https://github.com/pugjs/pug) from 2.0.1 to 2.0.3. - [Release notes](https://github.com/pugjs/pug/releases) - [Commits](https://github.com/pugjs/pug/compare/pug-code-gen@2.0.1...pug@2.0.3) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-03 11:28:49 +09:00
"pug-attrs": "^2.0.4",
"pug-error": "^1.3.3",
"pug-runtime": "^2.0.5",
Update packages
2018-11-25 05:00:22 +09:00
"void-elements": "^2.0.1",
"with": "^5.0.0"
Bump pug-code-gen from 2.0.1 to 2.0.3 Bumps [pug-code-gen](https://github.com/pugjs/pug) from 2.0.1 to 2.0.3. - [Release notes](https://github.com/pugjs/pug/releases) - [Commits](https://github.com/pugjs/pug/compare/pug-code-gen@2.0.1...pug@2.0.3) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-03 11:28:49 +09:00
},
"dependencies": {
"pug-attrs": {
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/pug-attrs/-/pug-attrs-2.0.4.tgz",
"integrity": "sha512-TaZ4Z2TWUPDJcV3wjU3RtUXMrd3kM4Wzjbe3EWnSsZPsJ3LDI0F3yCnf2/W7PPFF+edUFQ0HgDL1IoxSz5K8EQ==",
"dev": true,
"requires": {
"constantinople": "^3.0.1",
"js-stringify": "^1.0.1",
"pug-runtime": "^2.0.5"
}
}
Update packages
2018-11-25 05:00:22 +09:00
}
},
"pug-error": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "1.3.3",
"resolved": "https://registry.npmjs.org/pug-error/-/pug-error-1.3.3.tgz",
"integrity": "sha512-qE3YhESP2mRAWMFJgKdtT5D7ckThRScXRwkfo+Erqga7dyJdY3ZquspprMCj/9sJ2ijm5hXFWQE/A3l4poMWiQ==",
Update packages
2018-11-25 05:00:22 +09:00
"dev": true
},
"pug-filters": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/pug-filters/-/pug-filters-3.1.1.tgz",
"integrity": "sha512-lFfjNyGEyVWC4BwX0WyvkoWLapI5xHSM3xZJFUhx4JM4XyyRdO8Aucc6pCygnqV2uSgJFaJWW3Ft1wCWSoQkQg==",
Update packages
2018-11-25 05:00:22 +09:00
"dev": true,
"requires": {
"clean-css": "^4.1.11",
"constantinople": "^3.0.1",
"jstransformer": "1.0.0",
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"pug-error": "^1.3.3",
"pug-walk": "^1.1.8",
Update packages
2018-11-25 05:00:22 +09:00
"resolve": "^1.1.6",
"uglify-js": "^2.6.1"
}
},
"pug-lexer": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/pug-lexer/-/pug-lexer-4.1.0.tgz",
"integrity": "sha512-i55yzEBtjm0mlplW4LoANq7k3S8gDdfC6+LThGEvsK4FuobcKfDAwt6V4jKPH9RtiE3a2Akfg5UpafZ1OksaPA==",
Update packages
2018-11-25 05:00:22 +09:00
"dev": true,
"requires": {
"character-parser": "^2.1.1",
"is-expression": "^3.0.0",
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"pug-error": "^1.3.3"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"pug-linker": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "3.0.6",
"resolved": "https://registry.npmjs.org/pug-linker/-/pug-linker-3.0.6.tgz",
"integrity": "sha512-bagfuHttfQOpANGy1Y6NJ+0mNb7dD2MswFG2ZKj22s8g0wVsojpRlqveEQHmgXXcfROB2RT6oqbPYr9EN2ZWzg==",
Update packages
2018-11-25 05:00:22 +09:00
"dev": true,
"requires": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"pug-error": "^1.3.3",
"pug-walk": "^1.1.8"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"pug-load": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "2.0.12",
"resolved": "https://registry.npmjs.org/pug-load/-/pug-load-2.0.12.tgz",
"integrity": "sha512-UqpgGpyyXRYgJs/X60sE6SIf8UBsmcHYKNaOccyVLEuT6OPBIMo6xMPhoJnqtB3Q3BbO4Z3Bjz5qDsUWh4rXsg==",
Update packages
2018-11-25 05:00:22 +09:00
"dev": true,
"requires": {
"object-assign": "^4.1.0",
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"pug-walk": "^1.1.8"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"pug-parser": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/pug-parser/-/pug-parser-5.0.1.tgz",
"integrity": "sha512-nGHqK+w07p5/PsPIyzkTQfzlYfuqoiGjaoqHv1LjOv2ZLXmGX1O+4Vcvps+P4LhxZ3drYSljjq4b+Naid126wA==",
Update packages
2018-11-25 05:00:22 +09:00
"dev": true,
"requires": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"pug-error": "^1.3.3",
Update packages
2018-11-25 05:00:22 +09:00
"token-stream": "0.0.1"
}
},
"pug-runtime": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/pug-runtime/-/pug-runtime-2.0.5.tgz",
"integrity": "sha512-P+rXKn9un4fQY77wtpcuFyvFaBww7/91f3jHa154qU26qFAnOe6SW1CbIDcxiG5lLK9HazYrMCCuDvNgDQNptw==",
Update packages
2018-11-25 05:00:22 +09:00
"dev": true
},
"pug-strip-comments": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/pug-strip-comments/-/pug-strip-comments-1.0.4.tgz",
"integrity": "sha512-i5j/9CS4yFhSxHp5iKPHwigaig/VV9g+FgReLJWWHEHbvKsbqL0oP/K5ubuLco6Wu3Kan5p7u7qk8A4oLLh6vw==",
Update packages
2018-11-25 05:00:22 +09:00
"dev": true,
"requires": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"pug-error": "^1.3.3"
Update packages
2018-11-25 05:00:22 +09:00
}
},
"pug-walk": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "1.1.8",
"resolved": "https://registry.npmjs.org/pug-walk/-/pug-walk-1.1.8.tgz",
"integrity": "sha512-GMu3M5nUL3fju4/egXwZO0XLi6fW/K3T3VTgFQ14GxNi8btlxgT5qZL//JwZFm/2Fa64J/PNS8AZeys3wiMkVA==",
Update packages
2018-11-25 05:00:22 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"pump": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/pump/-/pump-2.0.1.tgz",
"integrity": "sha512-ruPMNRkN3MHP1cWJc9OWr+T/xDP0jhXYCLfJcBuX54hhfIBnaQmAUMfDcG4DM5UMWByBbJY69QSphm3jtDKIkA==",
"dev": true,
"requires": {
"end-of-stream": "^1.1.0",
"once": "^1.3.1"
}
},
"pumpify": {
"version": "1.5.1",
"resolved": "https://registry.npmjs.org/pumpify/-/pumpify-1.5.1.tgz",
"integrity": "sha512-oClZI37HvuUJJxSKKrC17bZ9Cu0ZYhEAGPsPUy9KlMUmv9dKX2o77RUmq7f3XjIxbwyGwYzbzQ1L2Ks8sIradQ==",
"dev": true,
"requires": {
"duplexify": "^3.6.0",
"inherits": "^2.0.3",
"pump": "^2.0.0"
}
},
"punycode": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/punycode/-/punycode-2.1.1.tgz",
"integrity": "sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A==",
"dev": true
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"puppeteer": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "13.3.2",
"resolved": "https://registry.npmjs.org/puppeteer/-/puppeteer-13.3.2.tgz",
"integrity": "sha512-TIt8/R0eaUwY1c0/O0sCJpSglvGEWVoWFfGZ2dNtxX3eHuBo1ln9abaWfxTjZfsrkYATLSs8oqEdRZpMNnCsvg==",
Update Puppeteer to version 10 Hopefully the updated Chromium-version might help reduce the number of intermittent test failures. Please find additional information at https://github.com/puppeteer/puppeteer/releases/tag/v10.0.0
2021-06-01 21:55:19 +09:00
"dev": true,
"requires": {
Update npm packages
2022-02-20 18:08:23 +09:00
"cross-fetch": "3.1.5",
"debug": "4.3.3",
"devtools-protocol": "0.0.960912",
Update Puppeteer to version 10 Hopefully the updated Chromium-version might help reduce the number of intermittent test failures. Please find additional information at https://github.com/puppeteer/puppeteer/releases/tag/v10.0.0
2021-06-01 21:55:19 +09:00
"extract-zip": "2.0.1",
"https-proxy-agent": "5.0.0",
"pkg-dir": "4.2.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"progress": "2.0.3",
Update Puppeteer to version 10 Hopefully the updated Chromium-version might help reduce the number of intermittent test failures. Please find additional information at https://github.com/puppeteer/puppeteer/releases/tag/v10.0.0
2021-06-01 21:55:19 +09:00
"proxy-from-env": "1.1.0",
"rimraf": "3.0.2",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"tar-fs": "2.1.1",
"unbzip2-stream": "1.4.3",
Update npm packages
2022-02-20 18:08:23 +09:00
"ws": "8.5.0"
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
},
"dependencies": {
"debug": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "4.3.3",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.3.tgz",
"integrity": "sha512-/zxw5+vh1Tfv+4Qn7a5nsbcJKPaSvCDhojn6FEl9vupwK2VCSDtEiEtqr8DFtzYFOdz63LBkxec7DYuc2jon6Q==",
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"dev": true,
"requires": {
Upgrade Puppeteer to version 5.3.1
2020-10-04 06:06:31 +09:00
"ms": "2.1.2"
}
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
}
}
},
Update `npm` packages
2021-02-21 19:52:55 +09:00
"queue-microtask": {
Update npm packages
2021-05-02 16:30:09 +09:00
"version": "1.2.3",
"resolved": "https://registry.npmjs.org/queue-microtask/-/queue-microtask-1.2.3.tgz",
"integrity": "sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==",
Update `npm` packages
2021-02-21 19:52:55 +09:00
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"quick-lru": {
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-4.0.1.tgz",
"integrity": "sha512-ARhCpm70fzdcvNQfPoy49IaanKkTlRWF2JMzqhcJbhSFRZv7nPTvZJdcY7301IPmvW+/p0RgIWnQDLJxifsQ7g==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"randombytes": {
Update `npm` packages
2019-12-29 03:57:25 +09:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/randombytes/-/randombytes-2.1.0.tgz",
"integrity": "sha512-vYl3iOX+4CKUWuxGi9Ukhie6fsqXqS9FE2Zaic4tNFD2N2QQaXOMFbuKK4QmDHC0JO6B1Zp41J0LpT0oR68amQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"safe-buffer": "^5.1.0"
}
},
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"read-pkg": {
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-5.2.0.tgz",
"integrity": "sha512-Ug69mNOpfvKDAc2Q8DRpMjjzdtrnv9HcSMX+4VsZxD1aZ6ZzrIE7rlzXBtWTyhULSMKg076AW6WR5iZpD0JiOg==",
"dev": true,
"requires": {
"@types/normalize-package-data": "^2.4.0",
"normalize-package-data": "^2.5.0",
"parse-json": "^5.0.0",
"type-fest": "^0.6.0"
},
"dependencies": {
"normalize-package-data": {
"version": "2.5.0",
"resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.5.0.tgz",
"integrity": "sha512-/5CMN3T0R4XTj4DcGaexo+roZSdSFW/0AOOTROrjxzCG1wrWXEsGbRKevjlIL+ZDE4sZlJr5ED4YW0yqmkK+eA==",
"dev": true,
"requires": {
"hosted-git-info": "^2.1.4",
"resolve": "^1.10.0",
"semver": "2 || 3 || 4 || 5",
"validate-npm-package-license": "^3.0.1"
}
},
"parse-json": {
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-5.2.0.tgz",
"integrity": "sha512-ayCKvm/phCGxOkYRSCM82iDwct8/EonSEgCSxWxD7ve6jHggsFl4fZVQBPRNgQoKiuV/odhFrGzQXZwbifC8Rg==",
"dev": true,
"requires": {
"@babel/code-frame": "^7.0.0",
"error-ex": "^1.3.1",
"json-parse-even-better-errors": "^2.3.0",
"lines-and-columns": "^1.1.6"
}
},
"resolve": {
"version": "1.20.0",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.20.0.tgz",
"integrity": "sha512-wENBPt4ySzg4ybFQW2TT1zMQucPK95HSh/nq2CFTZVOGut2+pQvSsgtda4d26YrYcr067wjbmzOG8byDPBX63A==",
"dev": true,
"requires": {
"is-core-module": "^2.2.0",
"path-parse": "^1.0.6"
}
},
"type-fest": {
"version": "0.6.0",
"resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.6.0.tgz",
"integrity": "sha512-q+MB8nYR1KDLrgr4G5yemftpMC7/QLqVndBmEEdqzmNj5dcFOO4Oo8qlwZE3ULT3+Zim1F8Kq4cBnikNhlCMlg==",
"dev": true
}
}
},
"read-pkg-up": {
"version": "7.0.1",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-7.0.1.tgz",
"integrity": "sha512-zK0TB7Xd6JpCLmlLmufqykGE+/TlOePD6qKClNW7hHDKFh/J7/7gCWGR7joEQEW1bKq3a3yUZSObOoWLFQ4ohg==",
"dev": true,
"requires": {
"find-up": "^4.1.0",
"read-pkg": "^5.2.0",
"type-fest": "^0.8.1"
},
"dependencies": {
"find-up": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-4.1.0.tgz",
"integrity": "sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw==",
"dev": true,
"requires": {
"locate-path": "^5.0.0",
"path-exists": "^4.0.0"
}
},
"locate-path": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/locate-path/-/locate-path-5.0.0.tgz",
"integrity": "sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g==",
"dev": true,
"requires": {
"p-locate": "^4.1.0"
}
},
"p-limit": {
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/p-limit/-/p-limit-2.3.0.tgz",
"integrity": "sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w==",
"dev": true,
"requires": {
"p-try": "^2.0.0"
}
},
"p-locate": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/p-locate/-/p-locate-4.1.0.tgz",
"integrity": "sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A==",
"dev": true,
"requires": {
"p-limit": "^2.2.0"
}
},
"p-try": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/p-try/-/p-try-2.2.0.tgz",
"integrity": "sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ==",
"dev": true
},
"path-exists": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-4.0.0.tgz",
"integrity": "sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==",
"dev": true
}
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"readable-stream": {
"version": "2.3.6",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.6.tgz",
"integrity": "sha512-tQtKA9WIAhBF3+VLAseyMqZeBjW0AHJoxOtYqSUZNJxauErmLbVm2FW1y+J/YA9dUrAC39ITejlZWhVIwawkKw==",
"dev": true,
"requires": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"readdirp": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "2.2.1",
"resolved": "https://registry.npmjs.org/readdirp/-/readdirp-2.2.1.tgz",
"integrity": "sha512-1JU/8q+VgFZyxwrJ+SVIOsh+KywWGpds3NTqikiKpDMZWScmAYyKIgqkO+ARvNWJfXeXR1zxz7aHF4u4CyH6vQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"graceful-fs": "^4.1.11",
"micromatch": "^3.1.10",
"readable-stream": "^2.0.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"rechoir": {
"version": "0.6.2",
"resolved": "https://registry.npmjs.org/rechoir/-/rechoir-0.6.2.tgz",
"integrity": "sha1-hSBLVNuoLVdC4oyWdW70OvUOM4Q=",
"dev": true,
"requires": {
"resolve": "^1.1.6"
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"redent": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/redent/-/redent-3.0.0.tgz",
"integrity": "sha512-6tDA8g98We0zd0GvVeMT9arEOnTw9qM03L9cJXaCjrip1OO764RDBLBfrB4cwzNGDj5OA5ioymC9GkizgWJDUg==",
"dev": true,
"requires": {
"indent-string": "^4.0.0",
"strip-indent": "^3.0.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"regenerate": {
Update `npm` packages
2020-11-29 17:43:20 +09:00
"version": "1.4.2",
"resolved": "https://registry.npmjs.org/regenerate/-/regenerate-1.4.2.tgz",
"integrity": "sha512-zrceR/XhGYU/d/opr2EKO7aRHUeiBI8qjtfHqADTwZd6Szfy16la6kqD0MIUs5z5hx6AaKa+PixpPrR289+I0A==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update npm packages
2022-01-09 18:05:52 +09:00
"regenerate-unicode-properties": {
"version": "9.0.0",
"resolved": "https://registry.npmjs.org/regenerate-unicode-properties/-/regenerate-unicode-properties-9.0.0.tgz",
"integrity": "sha512-3E12UeNSPfjrgwjkR81m5J7Aw/T55Tu7nUyZVQYCKEOs+2dkxEY+DpPtZzO4YruuiPb7NkYLVcyJC4+zCbk5pA==",
"dev": true,
"requires": {
"regenerate": "^1.4.2"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"regenerator-runtime": {
"version": "0.11.1",
"resolved": "https://registry.npmjs.org/regenerator-runtime/-/regenerator-runtime-0.11.1.tgz",
"integrity": "sha512-MguG95oij0fC3QV3URf4V2SDYGJhJnJGqvIIgdECeODCT98wSWDAJ94SSuVpYQUoTcGUIL6L4yNB7j1DFFHSBg==",
"dev": true
},
Update packages
2018-12-23 00:00:53 +09:00
"regenerator-transform": {
Update `npm` packages
2020-07-13 18:05:50 +09:00
"version": "0.14.5",
"resolved": "https://registry.npmjs.org/regenerator-transform/-/regenerator-transform-0.14.5.tgz",
"integrity": "sha512-eOf6vka5IO151Jfsw2NO9WpGX58W6wWmefK3I1zEGr0lOD0u8rwPaNqQL1aRxUaxLeKO3ArNh3VYg1KbaD+FFw==",
Update packages
2018-12-23 00:00:53 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-07-13 18:05:50 +09:00
"@babel/runtime": "^7.8.4"
Update packages
2018-12-23 00:00:53 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"regex-not": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/regex-not/-/regex-not-1.0.2.tgz",
"integrity": "sha512-J6SDjUgDxQj5NusnOtdFxDwN/+HWykR8GELwctJ7mdqhcyy1xEc4SRFHUXvxTp661YaVKAjfRLZ9cCqS6tn32A==",
"dev": true,
"requires": {
"extend-shallow": "^3.0.2",
"safe-regex": "^1.1.0"
}
},
Update packages
2019-02-18 00:44:36 +09:00
"regexp-tree": {
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"version": "0.1.24",
"resolved": "https://registry.npmjs.org/regexp-tree/-/regexp-tree-0.1.24.tgz",
"integrity": "sha512-s2aEVuLhvnVJW6s/iPgEGK6R+/xngd2jNQ+xy4bXNDKxZKJH6jpPHY6kVeVv1IeLCHgswRj+Kl3ELaDjG6V1iw==",
Update packages
2019-03-02 22:23:47 +09:00
"dev": true
Update packages
2019-02-18 00:44:36 +09:00
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"regexpp": {
Update npm packages
2021-06-27 17:25:40 +09:00
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/regexpp/-/regexpp-3.2.0.tgz",
"integrity": "sha512-pq2bWo9mVD43nbts2wGv17XLiNLya+GklZ8kaDLV2Z08gDCsGpnKn9BFMepvWuHCbyVvY7J5o5+BVvoQbmlJLg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update packages
2018-12-23 00:00:53 +09:00
"regexpu-core": {
Update npm packages
2021-09-19 16:31:42 +09:00
"version": "4.8.0",
"resolved": "https://registry.npmjs.org/regexpu-core/-/regexpu-core-4.8.0.tgz",
"integrity": "sha512-1F6bYsoYiz6is+oz70NWur2Vlh9KWtswuRuzJOfeYUrfPX2o8n74AnUVaOGDbUqVGO9fNHu48/pjJO4sNVwsOg==",
Update packages
2018-12-23 00:00:53 +09:00
"dev": true,
"requires": {
Update npm packages
2021-09-19 16:31:42 +09:00
"regenerate": "^1.4.2",
"regenerate-unicode-properties": "^9.0.0",
"regjsgen": "^0.5.2",
"regjsparser": "^0.7.0",
"unicode-match-property-ecmascript": "^2.0.0",
"unicode-match-property-value-ecmascript": "^2.0.0"
Update npm packages
2022-01-09 18:05:52 +09:00
}
},
"regjsgen": {
"version": "0.5.2",
"resolved": "https://registry.npmjs.org/regjsgen/-/regjsgen-0.5.2.tgz",
"integrity": "sha512-OFFT3MfrH90xIW8OOSyUrk6QHD5E9JOTeGodiJeBS3J6IwlgzJMNE/1bZklWz5oTg+9dCMyEetclvCVXOPoN3A==",
"dev": true
},
"regjsparser": {
"version": "0.7.0",
"resolved": "https://registry.npmjs.org/regjsparser/-/regjsparser-0.7.0.tgz",
"integrity": "sha512-A4pcaORqmNMDVwUjWoTzuhwMGpP+NykpfqAsEgI1FSH/EzC7lrN5TMd+kN8YCovX+jMpu8eaqXgXPCa0g8FQNQ==",
"dev": true,
"requires": {
"jsesc": "~0.5.0"
Update npm packages
2021-09-19 16:31:42 +09:00
},
"dependencies": {
"jsesc": {
"version": "0.5.0",
"resolved": "https://registry.npmjs.org/jsesc/-/jsesc-0.5.0.tgz",
"integrity": "sha1-597mbjXW/Bb3EP6R1c9p9w8IkR0=",
"dev": true
}
Update packages
2018-12-23 00:00:53 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"remove-bom-buffer": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/remove-bom-buffer/-/remove-bom-buffer-3.0.0.tgz",
"integrity": "sha512-8v2rWhaakv18qcvNeli2mZ/TMTL2nEyAKRvzo1WtnZBl15SHyEhrCu2/xKlJyUFKHiHgfXIyuY6g2dObJJycXQ==",
"dev": true,
"requires": {
"is-buffer": "^1.1.5",
"is-utf8": "^0.2.1"
}
},
"remove-bom-stream": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/remove-bom-stream/-/remove-bom-stream-1.2.0.tgz",
"integrity": "sha1-BfGlk/FuQuH7kOv1nejlaVJflSM=",
"dev": true,
"requires": {
"remove-bom-buffer": "^3.0.0",
"safe-buffer": "^5.1.0",
"through2": "^2.0.3"
added transform function added depedencies removed gulp-transform dependency removed dependencies removed gulptransform dependency
2019-11-13 11:51:31 +09:00
},
"dependencies": {
"through2": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.5.tgz",
"integrity": "sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==",
"dev": true,
"requires": {
"readable-stream": "~2.3.6",
"xtend": "~4.0.1"
}
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"remove-trailing-separator": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/remove-trailing-separator/-/remove-trailing-separator-1.1.0.tgz",
"integrity": "sha1-wkvOKig62tW8P1jg1IJJuSN52O8=",
"dev": true
},
"repeat-element": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/repeat-element/-/repeat-element-1.1.2.tgz",
"integrity": "sha1-7wiaF40Ug7quTZPrmLT55OEdmQo=",
"dev": true
},
"repeat-string": {
"version": "1.6.1",
"resolved": "https://registry.npmjs.org/repeat-string/-/repeat-string-1.6.1.tgz",
"integrity": "sha1-jcrkcOHIirwtYA//Sndihtp15jc=",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"replace-ext": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/replace-ext/-/replace-ext-1.0.0.tgz",
"integrity": "sha1-3mMSg3P8v3w8z6TeWkgMRaZ5WOs=",
"dev": true
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"replace-homedir": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/replace-homedir/-/replace-homedir-1.0.0.tgz",
"integrity": "sha1-6H9tUTuSjd6AgmDBK+f+xv9ueYw=",
"dev": true,
"requires": {
"homedir-polyfill": "^1.0.1",
"is-absolute": "^1.0.0",
"remove-trailing-separator": "^1.1.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"replacestream": {
"version": "4.0.3",
"resolved": "https://registry.npmjs.org/replacestream/-/replacestream-4.0.3.tgz",
"integrity": "sha512-AC0FiLS352pBBiZhd4VXB1Ab/lh0lEgpP+GGvZqbQh8a5cmXVoTe5EX/YeTFArnp4SRGTHh1qCHu9lGs1qG8sA==",
"dev": true,
"requires": {
"escape-string-regexp": "^1.0.3",
"object-assign": "^4.0.1",
"readable-stream": "^2.0.2"
}
},
"require-directory": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/require-directory/-/require-directory-2.1.1.tgz",
"integrity": "sha1-jGStX9MNqxyXbiNE/+f3kqam30I=",
"dev": true
},
Update `npm` packages
2021-01-10 19:25:47 +09:00
"require-from-string": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/require-from-string/-/require-from-string-2.0.2.tgz",
"integrity": "sha512-Xf0nWe6RseziFMu+Ap9biiUbmplq6S9/p+7w7YXP/JBHhrUDDUhwa+vANyubuqfZWTveU//DYVGsDG7RKL/vEw==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"require-main-filename": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/require-main-filename/-/require-main-filename-1.0.1.tgz",
"integrity": "sha1-l/cXtp1IeE9fUmpsWqj/3aBVpNE=",
"dev": true
},
"requizzle": {
Update packages
2019-08-25 03:08:09 +09:00
"version": "0.2.3",
"resolved": "https://registry.npmjs.org/requizzle/-/requizzle-0.2.3.tgz",
"integrity": "sha512-YanoyJjykPxGHii0fZP0uUPEXpvqfBDxWV7s6GKAiiOsiqhX6vHNyW3Qzdmqp/iq/ExbhaGbVrjB4ruEVSM4GQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2019-08-25 03:08:09 +09:00
"lodash": "^4.17.14"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"resolve": {
"version": "1.7.1",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.7.1.tgz",
"integrity": "sha512-c7rwLofp8g1U+h1KNyHL/jicrKg1Ek4q+Lr33AL65uZTinUZHe30D5HlyN5V9NW0JX1D5dXQ4jqW5l7Sy/kGfw==",
"dev": true,
"requires": {
"path-parse": "^1.0.5"
}
},
"resolve-dir": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/resolve-dir/-/resolve-dir-1.0.1.tgz",
"integrity": "sha1-eaQGRMNivoLybv/nOcm7U4IEb0M=",
"dev": true,
"requires": {
"expand-tilde": "^2.0.0",
"global-modules": "^1.0.0"
}
},
"resolve-from": {
Update packages
2019-01-05 22:27:47 +09:00
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-4.0.0.tgz",
"integrity": "sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"resolve-options": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/resolve-options/-/resolve-options-1.1.0.tgz",
"integrity": "sha1-MrueOcBtZzONyTeMDW1gdFZq0TE=",
"dev": true,
"requires": {
"value-or-function": "^3.0.0"
}
},
"resolve-url": {
"version": "0.2.1",
"resolved": "https://registry.npmjs.org/resolve-url/-/resolve-url-0.2.1.tgz",
"integrity": "sha1-LGN/53yJOv0qZj/iGqkIAGjiBSo=",
"dev": true
},
"ret": {
"version": "0.1.15",
"resolved": "https://registry.npmjs.org/ret/-/ret-0.1.15.tgz",
"integrity": "sha512-TTlYpa+OL+vMMNG24xSlQGEJ3B/RzEfUlLct7b5G/ytav+wPrplCpVMFuwzXbkecJrb6IYo1iFb0S9v37754mg==",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"reusify": {
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/reusify/-/reusify-1.0.4.tgz",
"integrity": "sha512-U9nH88a3fc/ekCF1l0/UP1IosiuIjyTh7hBvXVMHYgVcfGvt897Xguj2UOLDeI5BG2m7/uwyaLVT6fbtCwTyzw==",
"dev": true
},
"right-align": {
"version": "0.1.3",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"resolved": "https://registry.npmjs.org/right-align/-/right-align-0.1.3.tgz",
"integrity": "sha1-YTObci/mo1FWiSENJOFMlhSGE+8=",
"dev": true,
"requires": {
"align-text": "^0.1.1"
}
},
"rimraf": {
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-3.0.2.tgz",
"integrity": "sha512-JZkJMZkAGFFPP2YqXZXPbMlMBgsxzE8ILs4lMIX/2o0L9UBw9O/Y3o6wFw/i9YLapcUJWwqbi3kdxIPdC62TIA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2019-01-05 22:27:47 +09:00
"glob": "^7.1.3"
},
"dependencies": {
"glob": {
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"version": "7.1.6",
"resolved": "https://registry.npmjs.org/glob/-/glob-7.1.6.tgz",
"integrity": "sha512-LwaxwyZ72Lk7vZINtNNrywX0ZuLyStrdDtabefZKAY5ZGJhVtgdznluResxNmPitE0SAO+O26sWTHeKSI2wMBA==",
Update packages
2019-01-05 22:27:47 +09:00
"dev": true,
"requires": {
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
"minimatch": "^3.0.4",
"once": "^1.3.0",
"path-is-absolute": "^1.0.0"
}
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"run-parallel": {
Update `npm` packages
2021-02-21 19:52:55 +09:00
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/run-parallel/-/run-parallel-1.2.0.tgz",
"integrity": "sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==",
"dev": true,
"requires": {
"queue-microtask": "^1.2.2"
}
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"safe-buffer": {
"version": "5.1.2",
"resolved": "https://registry.npmjs.org/safe-buffer/-/safe-buffer-5.1.2.tgz",
"integrity": "sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==",
"dev": true
},
"safe-regex": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/safe-regex/-/safe-regex-1.1.0.tgz",
"integrity": "sha1-QKNmnzsHfR6UPURinhV91IAjvy4=",
"dev": true,
"requires": {
"ret": "~0.1.10"
}
},
"safer-buffer": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/safer-buffer/-/safer-buffer-2.1.2.tgz",
"integrity": "sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==",
"dev": true
},
"sax": {
"version": "1.2.4",
"resolved": "https://registry.npmjs.org/sax/-/sax-1.2.4.tgz",
"integrity": "sha512-NqVDv9TpANUjFm0N8uM5GxL36UgKi9/atZw+x7YFnQ8ckwFGKrl4xX4yWtrey3UJm5nP1kUbnYgLopqWNSRhWw==",
"dev": true
},
"schema-utils": {
Update `npm` packages
2020-11-15 21:51:52 +09:00
"version": "2.7.1",
"resolved": "https://registry.npmjs.org/schema-utils/-/schema-utils-2.7.1.tgz",
"integrity": "sha512-SHiNtMOUGWBQJwzISiVYKu82GiV4QYGePp3odlY1tuKO7gPtphAT5R/py0fA6xtbgLL/RvtJZnU9b8s0F1q0Xg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-11-15 21:51:52 +09:00
"@types/json-schema": "^7.0.5",
"ajv": "^6.12.4",
"ajv-keywords": "^3.5.2"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"semver": {
"version": "5.5.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-5.5.0.tgz",
"integrity": "sha512-4SJ3dm0WAwWy/NVeioZh5AntkdJoWKxHxcmyP622fOkgHa4z3R0TdBJICINyaSDE6uNwVc8gZr+ZinwZAH4xIA==",
"dev": true
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"semver-greatest-satisfied-range": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/semver-greatest-satisfied-range/-/semver-greatest-satisfied-range-1.1.0.tgz",
"integrity": "sha1-E+jCZYq5aRywzXEJMkAoDTb3els=",
"dev": true,
"requires": {
"sver-compat": "^1.5.0"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"serialize-javascript": {
Update npm packages
2021-06-27 17:25:40 +09:00
"version": "6.0.0",
"resolved": "https://registry.npmjs.org/serialize-javascript/-/serialize-javascript-6.0.0.tgz",
"integrity": "sha512-Qr3TosvguFt8ePWqsvRfrKyQXIiW+nGbYpy8XK24NQHE83caxWt+mIymTT19DGFbNWNLfEwsrkSmN64lVWB9ag==",
Update `npm` packages
2020-07-26 18:15:21 +09:00
"dev": true,
"requires": {
"randombytes": "^2.1.0"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"server-destroy": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/server-destroy/-/server-destroy-1.0.1.tgz",
"integrity": "sha1-8Tv5KOQrnD55OD5hzDmYtdFObN0=",
"dev": true
},
"set-blocking": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/set-blocking/-/set-blocking-2.0.0.tgz",
"integrity": "sha1-BF+XgtARrppoA93TgrJDkrPYkPc=",
"dev": true
},
"set-value": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/set-value/-/set-value-2.0.1.tgz",
"integrity": "sha512-JxHc1weCN68wRY0fhCoXpyK55m/XPHafOmK4UWD7m2CI14GMcFypt4w/0+NV5f/ZMby2F6S2wwA7fgynh9gWSw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"extend-shallow": "^2.0.1",
"is-extendable": "^0.1.1",
"is-plain-object": "^2.0.3",
"split-string": "^3.0.1"
},
"dependencies": {
"extend-shallow": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/extend-shallow/-/extend-shallow-2.0.1.tgz",
"integrity": "sha1-Ua99YUrZqfYQ6huvu5idaxxWiQ8=",
"dev": true,
"requires": {
"is-extendable": "^0.1.0"
}
}
}
},
Update npm packages
2021-08-22 17:38:52 +09:00
"side-channel": {
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/side-channel/-/side-channel-1.0.4.tgz",
"integrity": "sha512-q5XPytqFEIKHkGdiMIrY10mvLRvnQh42/+GoBlFW3b2LXLE2xxJpZFdm94we0BaoV3RwJyGqg5wS7epxTv0Zvw==",
"dev": true,
"requires": {
"call-bind": "^1.0.0",
"get-intrinsic": "^1.0.2",
"object-inspect": "^1.9.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"signal-exit": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "3.0.7",
"resolved": "https://registry.npmjs.org/signal-exit/-/signal-exit-3.0.7.tgz",
"integrity": "sha512-wnD2ZE+l+SPC/uoS0vXeE9L1+0wuaMqKlfz9AMUo38JsyLSBWSFcHR1Rri62LZc12vLr1gb3jl7iwQhgwpAbGQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update the `canvas` npm package to fix Travis CI builds (issue 10790)
2019-05-08 16:55:26 +09:00
"simple-concat": {
Update `npm` packages
2021-03-07 20:00:57 +09:00
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/simple-concat/-/simple-concat-1.0.1.tgz",
"integrity": "sha512-cSFtAPtRhljv69IK0hTVZQ+OfE9nePi/rtJmw5UjHeVyVroEqJXP1sFztKUy1qU+xvz3u/sfYJLa947b7nAN2Q==",
Update the `canvas` npm package to fix Travis CI builds (issue 10790)
2019-05-08 16:55:26 +09:00
"dev": true
},
"simple-get": {
Bump simple-get from 3.1.0 to 3.1.1 Bumps [simple-get](https://github.com/feross/simple-get) from 3.1.0 to 3.1.1. - [Release notes](https://github.com/feross/simple-get/releases) - [Commits](https://github.com/feross/simple-get/compare/v3.1.0...v3.1.1) --- updated-dependencies: - dependency-name: simple-get dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-06 21:14:16 +09:00
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/simple-get/-/simple-get-3.1.1.tgz",
"integrity": "sha512-CQ5LTKGfCpvE1K0n2us+kuMPbk/q0EKl82s4aheV9oXjFEz6W/Y7oQFVJuU6QG77hRT4Ghb5RURteF5vnWjupA==",
Update the `canvas` npm package to fix Travis CI builds (issue 10790)
2019-05-08 16:55:26 +09:00
"dev": true,
"requires": {
Update `npm` packages
2019-12-29 03:57:25 +09:00
"decompress-response": "^4.2.0",
Update the `canvas` npm package to fix Travis CI builds (issue 10790)
2019-05-08 16:55:26 +09:00
"once": "^1.3.1",
"simple-concat": "^1.0.0"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"simple-swizzle": {
"version": "0.2.2",
"resolved": "https://registry.npmjs.org/simple-swizzle/-/simple-swizzle-0.2.2.tgz",
"integrity": "sha1-pNprY1/8zMoz9w0Xy5JZLeleVXo=",
"dev": true,
"requires": {
"is-arrayish": "^0.3.1"
},
"dependencies": {
"is-arrayish": {
"version": "0.3.2",
"resolved": "https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.3.2.tgz",
"integrity": "sha512-eVRqCvVlZbuw3GrM63ovNSNAeA1K16kaR/LRY/92w0zxQ5/1YzwblUX652i4Xs9RwAGjW9d9y6X88t8OaAJfWQ==",
"dev": true
}
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"slash": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/slash/-/slash-3.0.0.tgz",
"integrity": "sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"slice-ansi": {
Update `npm` packages
2020-12-27 19:11:18 +09:00
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/slice-ansi/-/slice-ansi-4.0.0.tgz",
"integrity": "sha512-qMCMfhY040cVHT43K9BFygqYbUPFZKHOg7K73mtTWJRb8pyP3fzf4Ixd5SzdEJQ6MRUg/WBnOLxghZtKKurENQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-12-27 19:11:18 +09:00
"ansi-styles": "^4.0.0",
"astral-regex": "^2.0.0",
"is-fullwidth-code-point": "^3.0.0"
},
"dependencies": {
"ansi-styles": {
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz",
"integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==",
"dev": true,
"requires": {
"color-convert": "^2.0.1"
}
},
"color-convert": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz",
"integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==",
"dev": true,
"requires": {
"color-name": "~1.1.4"
}
},
"is-fullwidth-code-point": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz",
"integrity": "sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==",
"dev": true
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"slugg": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/slugg/-/slugg-1.2.1.tgz",
"integrity": "sha1-51KvIkGvPycURjxd4iXOpHYIdAo=",
"dev": true
},
"snapdragon": {
"version": "0.8.2",
"resolved": "https://registry.npmjs.org/snapdragon/-/snapdragon-0.8.2.tgz",
"integrity": "sha512-FtyOnWN/wCHTVXOMwvSv26d+ko5vWlIDD6zoUJ7LW8vh+ZBC8QdljveRP+crNrtBwioEUWy/4dMtbBjA4ioNlg==",
"dev": true,
"requires": {
"base": "^0.11.1",
"debug": "^2.2.0",
"define-property": "^0.2.5",
"extend-shallow": "^2.0.1",
"map-cache": "^0.2.2",
"source-map": "^0.5.6",
"source-map-resolve": "^0.5.0",
"use": "^3.1.0"
},
"dependencies": {
"define-property": {
"version": "0.2.5",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-0.2.5.tgz",
"integrity": "sha1-w1se+RjsPJkPmlvFe+BKrOxcgRY=",
"dev": true,
"requires": {
"is-descriptor": "^0.1.0"
}
},
"extend-shallow": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/extend-shallow/-/extend-shallow-2.0.1.tgz",
"integrity": "sha1-Ua99YUrZqfYQ6huvu5idaxxWiQ8=",
"dev": true,
"requires": {
"is-extendable": "^0.1.0"
}
},
"source-map": {
"version": "0.5.7",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.7.tgz",
"integrity": "sha1-igOdLRAh0i0eoUyA2OpGi6LvP8w=",
"dev": true
}
}
},
"snapdragon-node": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/snapdragon-node/-/snapdragon-node-2.1.1.tgz",
"integrity": "sha512-O27l4xaMYt/RSQ5TR3vpWCAB5Kb/czIcqUFOM/C4fYcLnbZUc1PkjTAMjof2pBWaSTwOUd6qUHcFGVGj7aIwnw==",
"dev": true,
"requires": {
"define-property": "^1.0.0",
"isobject": "^3.0.0",
"snapdragon-util": "^3.0.1"
},
"dependencies": {
"define-property": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-1.0.0.tgz",
"integrity": "sha1-dp66rz9KY6rTr56NMEybvnm/sOY=",
"dev": true,
"requires": {
"is-descriptor": "^1.0.0"
}
},
"is-accessor-descriptor": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-accessor-descriptor/-/is-accessor-descriptor-1.0.0.tgz",
"integrity": "sha512-m5hnHTkcVsPfqx3AKlyttIPb7J+XykHvJP2B9bZDjlhLIoEq4XoK64Vg7boZlVWYK6LUY94dYPEE7Lh0ZkZKcQ==",
"dev": true,
"requires": {
"kind-of": "^6.0.0"
}
},
"is-data-descriptor": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-data-descriptor/-/is-data-descriptor-1.0.0.tgz",
"integrity": "sha512-jbRXy1FmtAoCjQkVmIVYwuuqDFUbaOeDjmed1tOGPrsMhtJA4rD9tkgA0F1qJ3gRFRXcHYVkdeaP50Q5rE/jLQ==",
"dev": true,
"requires": {
"kind-of": "^6.0.0"
}
},
"is-descriptor": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/is-descriptor/-/is-descriptor-1.0.2.tgz",
"integrity": "sha512-2eis5WqQGV7peooDyLmNEPUrps9+SXX5c9pL3xEB+4e9HnGuDa7mB7kHxHw4CbqS9k1T2hOH3miL8n8WtiYVtg==",
"dev": true,
"requires": {
"is-accessor-descriptor": "^1.0.0",
"is-data-descriptor": "^1.0.0",
"kind-of": "^6.0.2"
}
}
}
},
"snapdragon-util": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/snapdragon-util/-/snapdragon-util-3.0.1.tgz",
"integrity": "sha512-mbKkMdQKsjX4BAL4bRYTj21edOf8cN7XHdYUJEe+Zn99hVEYcMvKPct1IqNe7+AZPirn8BCDOQBHQZknqmKlZQ==",
"dev": true,
"requires": {
"kind-of": "^3.2.0"
},
"dependencies": {
"kind-of": {
"version": "3.2.2",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz",
"integrity": "sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=",
"dev": true,
"requires": {
"is-buffer": "^1.1.5"
}
}
}
},
"source-map": {
"version": "0.6.1",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.6.1.tgz",
"integrity": "sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==",
"dev": true
},
Update npm packages
2021-05-30 14:43:13 +09:00
"source-map-js": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/source-map-js/-/source-map-js-1.0.2.tgz",
"integrity": "sha512-R0XvVJ9WusLiqTCEiGCmICCMplcCkIwwR11mOSD9CR5u+IXYdiseeEuXCVAjS54zqwkLcPNnmU4OeJ6tUrWhDw==",
Update npm packages
2021-05-30 14:43:13 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"source-map-resolve": {
"version": "0.5.2",
"resolved": "https://registry.npmjs.org/source-map-resolve/-/source-map-resolve-0.5.2.tgz",
"integrity": "sha512-MjqsvNwyz1s0k81Goz/9vRBe9SZdB09Bdw+/zYyO+3CuPk6fouTaxscHkgtE8jKvf01kVfl8riHzERQ/kefaSA==",
"dev": true,
"requires": {
"atob": "^2.1.1",
"decode-uri-component": "^0.2.0",
"resolve-url": "^0.2.1",
"source-map-url": "^0.4.0",
"urix": "^0.1.0"
}
},
Update packages
2018-12-23 00:00:53 +09:00
"source-map-support": {
Update the `dommatrix` package to the latest version
2021-11-14 18:20:54 +09:00
"version": "0.5.20",
"resolved": "https://registry.npmjs.org/source-map-support/-/source-map-support-0.5.20.tgz",
"integrity": "sha512-n1lZZ8Ve4ksRqizaBQgxXDgKwttHDhyfQjA6YZZn8+AroHbsIz+JjwxQDxbp+7y5OYCI8t1Yk7etjD9CRd2hIw==",
Update packages
2018-12-23 00:00:53 +09:00
"dev": true,
"requires": {
"buffer-from": "^1.0.0",
"source-map": "^0.6.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"source-map-url": {
"version": "0.4.0",
"resolved": "https://registry.npmjs.org/source-map-url/-/source-map-url-0.4.0.tgz",
"integrity": "sha1-PpNdfd1zYxuXZZlW1VEo6HtQhKM=",
"dev": true
},
"sparkles": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/sparkles/-/sparkles-1.0.1.tgz",
"integrity": "sha512-dSO0DDYUahUt/0/pD/Is3VIm5TGJjludZ0HVymmhYF6eNA53PVLhnUk0znSYbH8IYBuJdCE+1luR22jNLMaQdw==",
"dev": true
},
"spdx-correct": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-3.0.0.tgz",
"integrity": "sha512-N19o9z5cEyc8yQQPukRCZ9EUmb4HUpnrmaL/fxS2pBo2jbfcFRVuFZ/oFC+vZz0MNNk0h80iMn5/S6qGZOL5+g==",
"dev": true,
"requires": {
"spdx-expression-parse": "^3.0.0",
"spdx-license-ids": "^3.0.0"
}
},
"spdx-exceptions": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-2.1.0.tgz",
"integrity": "sha512-4K1NsmrlCU1JJgUrtgEeTVyfx8VaYea9J9LvARxhbHtVtohPs/gFGG5yy49beySjlIMhhXZ4QqujIZEfS4l6Cg==",
"dev": true
},
"spdx-expression-parse": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-3.0.0.tgz",
"integrity": "sha512-Yg6D3XpRD4kkOmTpdgbUiEJFKghJH03fiC1OPll5h/0sO6neh2jqRDVHOQ4o/LMea0tgCkbMgea5ip/e+MkWyg==",
"dev": true,
"requires": {
"spdx-exceptions": "^2.1.0",
"spdx-license-ids": "^3.0.0"
}
},
"spdx-license-ids": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-3.0.0.tgz",
"integrity": "sha512-2+EPwgbnmOIl8HjGBXXMd9NAu02vLjOO1nWw4kmeRDFyHn+M/ETfHxQUK0oXg8ctgVnl9t3rosNVsZ1jG61nDA==",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"specificity": {
"version": "0.4.1",
"resolved": "https://registry.npmjs.org/specificity/-/specificity-0.4.1.tgz",
"integrity": "sha512-1klA3Gi5PD1Wv9Q0wUoOQN1IWAuPu0D1U03ThXTr0cJ20+/iq2tHSDnK7Kk/0LXJ1ztUB2/1Os0wKmfyNgUQfg==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"split-string": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/split-string/-/split-string-3.1.0.tgz",
"integrity": "sha512-NzNVhJDYpwceVVii8/Hu6DKfD2G+NrQHlS/V/qgv763EYudVwEcMQNxd2lh+0VrUByXN/oJkl5grOhYWvQUYiw==",
"dev": true,
"requires": {
"extend-shallow": "^3.0.0"
}
},
"sprintf-js": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.0.3.tgz",
Update eslint-plugin-mozilla to ^1.0.1
2018-11-23 22:40:05 +09:00
"integrity": "sha1-BOaSb2YolTVPPdAVIDYzuFcpfiw=",
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"stack-trace": {
"version": "0.0.10",
"resolved": "https://registry.npmjs.org/stack-trace/-/stack-trace-0.0.10.tgz",
"integrity": "sha1-VHxws0fo0ytOEI6hoqFZ5f3eGcA=",
"dev": true
},
"static-extend": {
"version": "0.1.2",
"resolved": "https://registry.npmjs.org/static-extend/-/static-extend-0.1.2.tgz",
"integrity": "sha1-YICcOcv/VTNyJv1eC1IPNB8ftcY=",
"dev": true,
"requires": {
"define-property": "^0.2.5",
"object-copy": "^0.1.0"
},
"dependencies": {
"define-property": {
"version": "0.2.5",
"resolved": "https://registry.npmjs.org/define-property/-/define-property-0.2.5.tgz",
"integrity": "sha1-w1se+RjsPJkPmlvFe+BKrOxcgRY=",
"dev": true,
"requires": {
"is-descriptor": "^0.1.0"
}
}
}
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"stream-exhaust": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/stream-exhaust/-/stream-exhaust-1.0.2.tgz",
"integrity": "sha512-b/qaq/GlBK5xaq1yrK9/zFcyRSTNxmcZwFLGSTG0mXgZl/4Z6GgiyYOXOvY7N3eEvFRAG1bkDRz5EPGSvPYQlw==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"stream-shift": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/stream-shift/-/stream-shift-1.0.0.tgz",
"integrity": "sha1-1cdSgl5TZ+eG944Y5EXqIjoVWVI=",
"dev": true
},
"streamqueue": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/streamqueue/-/streamqueue-1.1.2.tgz",
"integrity": "sha512-CHUpqa+1BM99z7clQz9W6L9ZW4eXRRQCR0H+utVAGGvNo2ePlJAFjhdK0IjunaBbY/gWKJawk5kpJeyz0EXxRA==",
"dev": true,
"requires": {
"isstream": "^0.1.2",
"readable-stream": "^2.3.3"
}
},
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"string_decoder": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-1.1.1.tgz",
"integrity": "sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==",
"dev": true,
"requires": {
"safe-buffer": "~5.1.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"string-width": {
Update npm packages
2021-05-30 14:43:13 +09:00
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/string-width/-/string-width-1.0.2.tgz",
"integrity": "sha1-EYvfW4zcUaKn5w0hHgfisLmxB9M=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-30 14:43:13 +09:00
"code-point-at": "^1.0.0",
"is-fullwidth-code-point": "^1.0.0",
"strip-ansi": "^3.0.0"
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
}
},
"string.prototype.trimend": {
Update npm packages
2021-05-16 17:05:58 +09:00
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/string.prototype.trimend/-/string.prototype.trimend-1.0.4.tgz",
"integrity": "sha512-y9xCjw1P23Awk8EvTpcyL2NIr1j7wJ39f+k6lvRnSMz+mz9CGz9NYPelDk42kOz6+ql8xjfK8oYzy3jAP5QU5A==",
"dev": true,
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"requires": {
Update npm packages
2021-05-16 17:05:58 +09:00
"call-bind": "^1.0.2",
"define-properties": "^1.1.3"
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
},
"dependencies": {
"define-properties": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.1.3.tgz",
"integrity": "sha512-3MqfYKj2lLzdMSf8ZIZE/V+Zuy+BgD6f164e8K2w7dgnpKArBDerGYpM46IYYcjnkdPNMjPk9A6VFB8+3SKlXQ==",
Update npm packages
2021-05-16 17:05:58 +09:00
"dev": true,
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"requires": {
"object-keys": "^1.0.12"
}
},
"object-keys": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz",
Update npm packages
2021-05-16 17:05:58 +09:00
"integrity": "sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==",
"dev": true
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
}
}
},
"string.prototype.trimstart": {
Update npm packages
2021-05-16 17:05:58 +09:00
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/string.prototype.trimstart/-/string.prototype.trimstart-1.0.4.tgz",
"integrity": "sha512-jh6e984OBfvxS50tdY2nRZnoC5/mLFKOREQfw8t5yytkoUsJRNxvI/E39qu1sD0OtWI3OC0XgKSmcWwziwYuZw==",
"dev": true,
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"requires": {
Update npm packages
2021-05-16 17:05:58 +09:00
"call-bind": "^1.0.2",
"define-properties": "^1.1.3"
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
},
"dependencies": {
"define-properties": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.1.3.tgz",
"integrity": "sha512-3MqfYKj2lLzdMSf8ZIZE/V+Zuy+BgD6f164e8K2w7dgnpKArBDerGYpM46IYYcjnkdPNMjPk9A6VFB8+3SKlXQ==",
Update npm packages
2021-05-16 17:05:58 +09:00
"dev": true,
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"requires": {
"object-keys": "^1.0.12"
}
},
"object-keys": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz",
Update npm packages
2021-05-16 17:05:58 +09:00
"integrity": "sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==",
"dev": true
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
}
}
},
"strip-ansi": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-3.0.1.tgz",
"integrity": "sha1-ajhfuIU9lS1f8F0Oiq+UJ43GPc8=",
"dev": true,
"requires": {
"ansi-regex": "^2.0.0"
}
},
"strip-bom": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-2.0.0.tgz",
"integrity": "sha1-YhmoVhZSBJHzV4i9vxRHqZx+aw4=",
"dev": true,
"requires": {
"is-utf8": "^0.2.0"
}
},
"strip-indent": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-3.0.0.tgz",
"integrity": "sha512-laJTa3Jb+VQpaC6DseHhF7dXVqHTfJPCRDaEbid/drOhgitgYku/letMUqOXFoWV0zIIUbjpdH2t+tYj4bQMRQ==",
"dev": true,
"requires": {
"min-indent": "^1.0.0"
}
},
"strip-json-comments": {
Update npm packages
2021-05-30 14:43:13 +09:00
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/strip-json-comments/-/strip-json-comments-3.1.1.tgz",
"integrity": "sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true
},
"style-search": {
"version": "0.1.0",
"resolved": "https://registry.npmjs.org/style-search/-/style-search-0.1.0.tgz",
"integrity": "sha1-eVjHk+R+MuB9K1yv5cC/jhLneQI=",
"dev": true
},
"stylelint": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "14.5.1",
"resolved": "https://registry.npmjs.org/stylelint/-/stylelint-14.5.1.tgz",
"integrity": "sha512-8Hf4HtnhxlWlf7iXF9zFfhSc3X0teRnVzl6PqPs2JEFx+dy/mhMhghZfiTDW4QG0ihDw9+WP7GZw5Nzx7cQF5A==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-02 16:30:09 +09:00
"balanced-match": "^2.0.0",
Update npm packages
2021-12-26 19:09:29 +09:00
"colord": "^2.9.2",
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"cosmiconfig": "^7.0.1",
Update npm packages
2022-02-20 18:08:23 +09:00
"css-functions-list": "^3.0.1",
Update npm packages
2021-12-26 19:09:29 +09:00
"debug": "^4.3.3",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"execall": "^2.0.0",
Update npm packages
2022-02-06 19:24:14 +09:00
"fast-glob": "^3.2.11",
Update `npm` packages
2020-09-06 18:49:49 +09:00
"fastest-levenshtein": "^1.0.12",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"file-entry-cache": "^6.0.1",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"get-stdin": "^8.0.0",
"global-modules": "^2.0.0",
Update npm packages
2022-02-06 19:24:14 +09:00
"globby": "^11.1.0",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"globjoin": "^0.1.4",
"html-tags": "^3.1.0",
Update npm packages
2021-12-26 19:09:29 +09:00
"ignore": "^5.2.0",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"import-lazy": "^4.0.0",
"imurmurhash": "^0.1.4",
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"is-plain-object": "^5.0.0",
Update npm packages
2021-12-26 19:09:29 +09:00
"known-css-properties": "^0.24.0",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"mathml-tag-names": "^2.1.3",
Update `npm` packages
2021-01-24 16:34:00 +09:00
"meow": "^9.0.0",
Update npm packages
2021-05-02 16:30:09 +09:00
"micromatch": "^4.0.4",
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"normalize-path": "^3.0.0",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"normalize-selector": "^0.2.0",
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"picocolors": "^1.0.0",
Update npm packages
2022-02-20 18:08:23 +09:00
"postcss": "^8.4.6",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"postcss-media-query-parser": "^0.2.3",
"postcss-resolve-nested-selector": "^0.1.1",
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"postcss-safe-parser": "^6.0.0",
Update npm packages
2022-02-06 19:24:14 +09:00
"postcss-selector-parser": "^6.0.9",
"postcss-value-parser": "^4.2.0",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"resolve-from": "^5.0.0",
"specificity": "^0.4.1",
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"string-width": "^4.2.3",
"strip-ansi": "^6.0.1",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"style-search": "^0.1.0",
Update npm packages
2022-02-06 19:24:14 +09:00
"supports-hyperlinks": "^2.2.0",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"svg-tags": "^1.0.0",
Update npm packages
2022-02-06 19:24:14 +09:00
"table": "^6.8.0",
Update npm packages
2021-05-02 16:30:09 +09:00
"v8-compile-cache": "^2.3.0",
Update npm packages
2022-02-20 18:08:23 +09:00
"write-file-atomic": "^4.0.1"
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
},
"dependencies": {
"ansi-regex": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2021-10-17 18:47:09 +09:00
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
"integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true
},
Update npm packages
2021-05-02 16:30:09 +09:00
"balanced-match": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-2.0.0.tgz",
"integrity": "sha512-1ugUSr8BHXRnK23KfuYS+gVMC3LB8QGH9W1iGtDPsNWoQbgtXSExkBu2aDR4epiGWZOjZsj6lDl/N/AqqTC3UA==",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"braces": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/braces/-/braces-3.0.2.tgz",
"integrity": "sha512-b8um+L1RzM3WDSzvhm6gIz1yfTbBt6YTlcEKAvsmqCZZFw46z626lVj9j1yEPW33H5H+lBQpZMP1k8l+78Ha0A==",
"dev": true,
"requires": {
"fill-range": "^7.0.1"
}
},
"debug": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"version": "4.3.3",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.3.tgz",
"integrity": "sha512-/zxw5+vh1Tfv+4Qn7a5nsbcJKPaSvCDhojn6FEl9vupwK2VCSDtEiEtqr8DFtzYFOdz63LBkxec7DYuc2jon6Q==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-09-20 18:34:24 +09:00
"ms": "2.1.2"
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
}
},
"fill-range": {
"version": "7.0.1",
"resolved": "https://registry.npmjs.org/fill-range/-/fill-range-7.0.1.tgz",
"integrity": "sha512-qOo9F+dMUmC2Lcb4BbVvnKJxTPjCm+RRpe4gDuGrzkL7mEVl/djYSu2OdQ2Pa302N4oqkSg9ir6jaLWJ2USVpQ==",
"dev": true,
"requires": {
"to-regex-range": "^5.0.1"
}
},
"global-modules": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/global-modules/-/global-modules-2.0.0.tgz",
"integrity": "sha512-NGbfmJBp9x8IxyJSd1P+otYK8vonoJactOogrVfFRIAEY1ukil8RSKDz2Yo7wh1oihl51l/r6W4epkeKJHqL8A==",
"dev": true,
"requires": {
"global-prefix": "^3.0.0"
}
},
"global-prefix": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/global-prefix/-/global-prefix-3.0.0.tgz",
"integrity": "sha512-awConJSVCHVGND6x3tmMaKcQvwXLhjdkmomy2W+Goaui8YPgYgXJZewhg3fWC+DlfqqQuWg8AwqjGTD2nAPVWg==",
"dev": true,
"requires": {
"ini": "^1.3.5",
"kind-of": "^6.0.2",
"which": "^1.3.1"
}
},
"ignore": {
Update npm packages
2021-12-26 19:09:29 +09:00
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/ignore/-/ignore-5.2.0.tgz",
"integrity": "sha512-CmxgYGiEPCLhfLnpPp1MoRmifwEIOgjcHXxOBjv7mY96c+eWScsOP9c112ZyLdWHi0FxHjI+4uVhKYp/gcdRmQ==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true
},
"is-fullwidth-code-point": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz",
"integrity": "sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==",
"dev": true
},
"is-number": {
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/is-number/-/is-number-7.0.0.tgz",
"integrity": "sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==",
"dev": true
},
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"is-plain-object": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/is-plain-object/-/is-plain-object-5.0.0.tgz",
"integrity": "sha512-VRSzKkbMm5jMDoKLbltAkFQ5Qr7VDiTFGXxYFXXowVj387GeGNOCsOH6Msy00SGZ3Fp84b1Naa1psqgcCIEP5Q==",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"micromatch": {
Update npm packages
2021-05-02 16:30:09 +09:00
"version": "4.0.4",
"resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.4.tgz",
"integrity": "sha512-pRmzw/XUcwXGpD9aI9q/0XOwLNygjETJ8y0ao0wdqprrzDa4YnxLcz7fQRZr8voh8V10kGhABbNcHVk5wHgWwg==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true,
"requires": {
"braces": "^3.0.1",
Update npm packages
2021-05-02 16:30:09 +09:00
"picomatch": "^2.2.3"
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
}
},
"ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
},
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"normalize-path": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/normalize-path/-/normalize-path-3.0.0.tgz",
"integrity": "sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==",
Update npm packages
2021-05-02 16:30:09 +09:00
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"resolve-from": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-5.0.0.tgz",
"integrity": "sha512-qYg9KP24dD5qka9J47d0aVky0N+b4fTU89LN9iDnjB5waksiC49rvMB0PrUJQGoTmH50XPiqOvAjDfaijGxYZw==",
"dev": true
},
"string-width": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"version": "4.2.3",
"resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz",
"integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==",
Update `npm` packages
2020-04-02 19:13:14 +09:00
"dev": true,
"requires": {
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"emoji-regex": "^8.0.0",
"is-fullwidth-code-point": "^3.0.0",
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"strip-ansi": "^6.0.1"
Update `npm` packages
2020-04-02 19:13:14 +09:00
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"strip-ansi": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"version": "6.0.1",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
"integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true,
"requires": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"ansi-regex": "^5.0.1"
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
}
},
"to-regex-range": {
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/to-regex-range/-/to-regex-range-5.0.1.tgz",
"integrity": "sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==",
"dev": true,
"requires": {
"is-number": "^7.0.0"
}
Update `npm` packages
2019-12-19 19:28:13 +09:00
}
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"stylelint-config-prettier": {
Update the `stylelint-config-prettier` package to the latest version Please refer to https://github.com/prettier/stylelint-config-prettier/releases
2021-10-17 18:37:40 +09:00
"version": "9.0.3",
"resolved": "https://registry.npmjs.org/stylelint-config-prettier/-/stylelint-config-prettier-9.0.3.tgz",
"integrity": "sha512-5n9gUDp/n5tTMCq1GLqSpA30w2sqWITSSEiAWQlpxkKGAUbjcemQ0nbkRvRUa0B1LgD3+hCvdL7B1eTxy1QHJg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"requires": {}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"stylelint-prettier": {
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"version": "2.0.0",
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"resolved": "https://registry.npmjs.org/stylelint-prettier/-/stylelint-prettier-2.0.0.tgz",
"integrity": "sha512-jvT3G+9lopkeB0ARmDPszyfaOnvnIF+30QCjZxyt7E6fynI1T9mOKgYDNb9bXX17M7PXMZaX3j/26wqakjp1tw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"prettier-linter-helpers": "^1.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"summary": {
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/summary/-/summary-2.1.0.tgz",
"integrity": "sha512-nMIjMrd5Z2nuB2RZCKJfFMjgS3fygbeyGk9PxPPaJR1RIcyN9yn4A63Isovzm3ZtQuEkLBVgMdPup8UeLH7aQw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"supports-color": {
"version": "5.4.0",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-5.4.0.tgz",
"integrity": "sha512-zjaXglF5nnWpsq470jSv6P9DwPvgLkuapYmfDm3JWOm0vkNTVF2tI4UrN2r6jH1qM/uc/WtxYY1hYoA2dOKj5w==",
"dev": true,
"requires": {
"has-flag": "^3.0.0"
}
},
Update npm packages
2022-02-06 19:24:14 +09:00
"supports-hyperlinks": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/supports-hyperlinks/-/supports-hyperlinks-2.2.0.tgz",
"integrity": "sha512-6sXEzV5+I5j8Bmq9/vUphGRM/RJNT9SCURJLjwfOg51heRtguGWDzcaBlgAzKhQa0EVNpPEKzQuBwZ8S8WaCeQ==",
"dev": true,
"requires": {
"has-flag": "^4.0.0",
"supports-color": "^7.0.0"
},
"dependencies": {
"has-flag": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz",
"integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==",
"dev": true
},
"supports-color": {
"version": "7.2.0",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-7.2.0.tgz",
"integrity": "sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==",
"dev": true,
"requires": {
"has-flag": "^4.0.0"
}
}
}
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"sver-compat": {
"version": "1.5.0",
"resolved": "https://registry.npmjs.org/sver-compat/-/sver-compat-1.5.0.tgz",
"integrity": "sha1-PPh9/rTQe0o/FIJ7wYaz/QxkXNg=",
"dev": true,
"requires": {
"es6-iterator": "^2.0.1",
"es6-symbol": "^3.1.1"
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"svg-tags": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/svg-tags/-/svg-tags-1.0.0.tgz",
"integrity": "sha1-WPcc7jvVGbWdSyqEO2x95krAR2Q=",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"systemjs": {
Update packages
2019-01-21 00:34:24 +09:00
"version": "0.21.6",
"resolved": "https://registry.npmjs.org/systemjs/-/systemjs-0.21.6.tgz",
"integrity": "sha512-R+5S9eV9vcQgWOoS4D87joZ4xkFJHb19ZsyKY07D1+VBDE9bwYcU+KXE0r5XlDA8mFoJGyuWDbfrNoh90JsA8g==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"systemjs-plugin-babel": {
"version": "0.0.25",
"resolved": "https://registry.npmjs.org/systemjs-plugin-babel/-/systemjs-plugin-babel-0.0.25.tgz",
"integrity": "sha512-RMKSizWWlw4+IpDB385ugxn7Owd9W+HEtjYDQ6yO1FpsnER/vk6FbXRweUF+mvRi6EHgk8vDdUdtui7ReDwX3w==",
"dev": true
},
"table": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "6.8.0",
"resolved": "https://registry.npmjs.org/table/-/table-6.8.0.tgz",
"integrity": "sha512-s/fitrbVeEyHKFa7mFdkuQMWlH1Wgw/yEXMt5xACT4ZpzWFluehAxRtUUQKPuWhaLAWhFcVx6w3oC8VKaUfPGA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-02 16:30:09 +09:00
"ajv": "^8.0.1",
"lodash.truncate": "^4.4.2",
Update `npm` packages
2020-12-27 19:11:18 +09:00
"slice-ansi": "^4.0.0",
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"string-width": "^4.2.3",
"strip-ansi": "^6.0.1"
Update packages
2018-12-23 00:00:53 +09:00
},
"dependencies": {
Update `npm` packages
2021-01-10 19:25:47 +09:00
"ajv": {
Update npm packages
2022-02-06 19:24:14 +09:00
"version": "8.10.0",
"resolved": "https://registry.npmjs.org/ajv/-/ajv-8.10.0.tgz",
"integrity": "sha512-bzqAEZOjkrUMl2afH8dknrq5KEk2SrwdBROR+vH1EKVQTqaUbJVPdc/gEdggTMM0Se+s+Ja4ju4TlNcStKl2Hw==",
Update `npm` packages
2021-01-10 19:25:47 +09:00
"dev": true,
"requires": {
"fast-deep-equal": "^3.1.1",
"json-schema-traverse": "^1.0.0",
"require-from-string": "^2.0.2",
"uri-js": "^4.2.2"
}
},
Update packages
2019-02-18 00:44:36 +09:00
"ansi-regex": {
Fix (some) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command.
2021-10-17 18:47:09 +09:00
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
"integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
Update `npm` packages
2020-12-27 19:11:18 +09:00
"dev": true
},
"is-fullwidth-code-point": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz",
"integrity": "sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==",
"dev": true
},
Update `npm` packages
2021-01-10 19:25:47 +09:00
"json-schema-traverse": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-1.0.0.tgz",
"integrity": "sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug==",
"dev": true
},
Update packages
2019-02-18 00:44:36 +09:00
"string-width": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"version": "4.2.3",
"resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz",
"integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==",
Update packages
2019-02-18 00:44:36 +09:00
"dev": true,
"requires": {
Update `npm` packages
2020-12-27 19:11:18 +09:00
"emoji-regex": "^8.0.0",
"is-fullwidth-code-point": "^3.0.0",
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"strip-ansi": "^6.0.1"
Update packages
2019-02-18 00:44:36 +09:00
}
},
"strip-ansi": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"version": "6.0.1",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
"integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
Update packages
2019-02-18 00:44:36 +09:00
"dev": true,
"requires": {
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"ansi-regex": "^5.0.1"
Update packages
2019-02-18 00:44:36 +09:00
}
Update packages
2018-12-23 00:00:53 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"taffydb": {
"version": "2.6.2",
"resolved": "https://registry.npmjs.org/taffydb/-/taffydb-2.6.2.tgz",
"integrity": "sha1-fLy2S1oUG2ou/CxdLGe04VCyomg=",
"dev": true
},
"tapable": {
Update npm packages
2021-09-19 16:31:42 +09:00
"version": "2.2.1",
"resolved": "https://registry.npmjs.org/tapable/-/tapable-2.2.1.tgz",
"integrity": "sha512-GNzQvQTOIP6RyTfE2Qxb8ZVlNmw0n88vp1szwWRimP02mnTsx3Wtn5qRdqY9w2XduFNUgvOwhNnQsjwCp+kqaQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"tar": {
Bump tar from 4.4.15 to 4.4.19 Bumps [tar](https://github.com/npm/node-tar) from 4.4.15 to 4.4.19. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](https://github.com/npm/node-tar/compare/v4.4.15...v4.4.19) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-01 01:39:41 +09:00
"version": "6.1.11",
"resolved": "https://registry.npmjs.org/tar/-/tar-6.1.11.tgz",
"integrity": "sha512-an/KZQzQUkZCkuoAA64hM92X0Urb6VpRhAFllDzz44U2mcD5scmT3zBc4VgVpkugF580+DQn8eAFSyoQt0tznA==",
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"dev": true,
"requires": {
Update npm packages
2021-05-30 14:43:13 +09:00
"chownr": "^2.0.0",
"fs-minipass": "^2.0.0",
"minipass": "^3.0.0",
"minizlib": "^2.1.1",
"mkdirp": "^1.0.3",
"yallist": "^4.0.0"
Update the `mkdirp` package, since its major version was increased
2020-04-02 19:18:23 +09:00
},
"dependencies": {
Update npm packages
2021-05-30 14:43:13 +09:00
"chownr": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/chownr/-/chownr-2.0.0.tgz",
"integrity": "sha512-bIomtDF5KGpdogkLd9VspvFzk9KfpyyGlS8YFVZl7TGPBHL5snIOnxeshwVgPteQ9b4Eydl+pVbIyE1DcvCWgQ==",
"dev": true
},
"yallist": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/yallist/-/yallist-4.0.0.tgz",
"integrity": "sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A==",
"dev": true
Update the `mkdirp` package, since its major version was increased
2020-04-02 19:18:23 +09:00
}
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
}
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"tar-fs": {
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/tar-fs/-/tar-fs-2.1.1.tgz",
"integrity": "sha512-V0r2Y9scmbDRLCNex/+hYzvp/zyYjvFbHPNgVTKfQvVrb6guiE/fxP+XblDNR011utopbkex2nM4dHNV6GDsng==",
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"dev": true,
"requires": {
"chownr": "^1.1.1",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"mkdirp-classic": "^0.5.2",
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"pump": "^3.0.0",
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"tar-stream": "^2.1.4"
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
},
"dependencies": {
"pump": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/pump/-/pump-3.0.0.tgz",
"integrity": "sha512-LwZy+p3SFs1Pytd/jYct4wpv49HiYCqd9Rlc5ZVdk0V+8Yzv6jR5Blk3TRmPL1ft69TxP0IMZGJ+WPFU2BFhww==",
"dev": true,
"requires": {
"end-of-stream": "^1.1.0",
"once": "^1.3.1"
}
}
}
},
"tar-stream": {
Update Puppeteer to version 6 (issue 12945) Please see https://github.com/puppeteer/puppeteer/releases/tag/v6.0.0
2021-02-02 21:18:22 +09:00
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/tar-stream/-/tar-stream-2.2.0.tgz",
"integrity": "sha512-ujeqbceABgwMZxEJnk2HDY2DlnUZ+9oEcb1KzTVfYHio0UE6dG71n60d8D2I4qNvleWrrXpmjpt7vZeF1LnMZQ==",
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"dev": true,
"requires": {
Upgrade Puppeteer to version 5.3.1
2020-10-04 06:06:31 +09:00
"bl": "^4.0.3",
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"end-of-stream": "^1.4.1",
"fs-constants": "^1.0.0",
"inherits": "^2.0.3",
"readable-stream": "^3.1.1"
},
"dependencies": {
"readable-stream": {
"version": "3.6.0",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-3.6.0.tgz",
"integrity": "sha512-BViHy7LKeTz4oNnkcLJ+lVSL6vpiFeX6/d3oSH8zCW7UxP2onchk+vTGB143xuFjHS3deTgkKoXXymXqymiIdA==",
"dev": true,
"requires": {
"inherits": "^2.0.3",
"string_decoder": "^1.1.1",
"util-deprecate": "^1.0.1"
}
}
}
},
Replace UglifyJS with Terser
2018-11-23 20:06:07 +09:00
"terser": {
Update npm packages
2021-11-28 18:40:29 +09:00
"version": "5.10.0",
"resolved": "https://registry.npmjs.org/terser/-/terser-5.10.0.tgz",
"integrity": "sha512-AMmF99DMfEDiRJfxfY5jj5wNH/bYO09cniSqhfoyxc8sFoYIgkJy86G04UoZU5VjlpnplVu0K6Tx6E9b5+DlHA==",
Replace UglifyJS with Terser
2018-11-23 20:06:07 +09:00
"dev": true,
"requires": {
Update packages
2019-08-25 03:08:09 +09:00
"commander": "^2.20.0",
Upgrade `terser` to version 5 The only significant change is that the `minify` command is now asynchronous, which we can handle easily by simply making the containing functions `async`. Based on https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/async_function#Browser_compatibility, using `async`/`await` in the gulpfile should no longer be an issue as far as I can tell.
2020-10-07 21:28:17 +09:00
"source-map": "~0.7.2",
Update npm packages
2021-09-19 16:31:42 +09:00
"source-map-support": "~0.5.20"
Replace UglifyJS with Terser
2018-11-23 20:06:07 +09:00
},
"dependencies": {
"commander": {
Update packages
2019-10-18 23:42:02 +09:00
"version": "2.20.3",
"resolved": "https://registry.npmjs.org/commander/-/commander-2.20.3.tgz",
"integrity": "sha512-GpVkmM8vF2vQUkj2LvZmD35JxeJOLCwJ9cUkugyk2nuhbv3+mJvpLYYt+0+USMxE+oj+ey/lJEnhZw75x/OMcQ==",
Replace UglifyJS with Terser
2018-11-23 20:06:07 +09:00
"dev": true
Upgrade `terser` to version 5 The only significant change is that the `minify` command is now asynchronous, which we can handle easily by simply making the containing functions `async`. Based on https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/async_function#Browser_compatibility, using `async`/`await` in the gulpfile should no longer be an issue as far as I can tell.
2020-10-07 21:28:17 +09:00
},
"source-map": {
"version": "0.7.3",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.7.3.tgz",
"integrity": "sha512-CkCj6giN3S+n9qrYiBTX5gystlENnRW5jZeNLHpe6aue+SrHcG5VYwujhW9s4dY31mEGsxBDrHR6oI69fTXsaQ==",
"dev": true
Replace UglifyJS with Terser
2018-11-23 20:06:07 +09:00
}
}
},
Update Webpack to the latest stable version (4.29.5)
2019-02-24 05:11:46 +09:00
"terser-webpack-plugin": {
Update npm packages
2021-11-14 18:17:30 +09:00
"version": "5.2.5",
"resolved": "https://registry.npmjs.org/terser-webpack-plugin/-/terser-webpack-plugin-5.2.5.tgz",
"integrity": "sha512-3luOVHku5l0QBeYS8r4CdHYWEGMmIj3H1U64jgkdZzECcSOJAyJ9TjuqcQZvw1Y+4AOBN9SeYJPJmFn2cM4/2g==",
Update Webpack to the latest stable version (4.29.5)
2019-02-24 05:11:46 +09:00
"dev": true,
"requires": {
Update npm packages
2021-09-05 16:47:57 +09:00
"jest-worker": "^27.0.6",
"schema-utils": "^3.1.1",
Update npm packages
2021-06-27 17:25:40 +09:00
"serialize-javascript": "^6.0.0",
Update Webpack to the latest stable version (4.29.5)
2019-02-24 05:11:46 +09:00
"source-map": "^0.6.1",
Update npm packages
2021-09-05 16:47:57 +09:00
"terser": "^5.7.2"
Update `npm` packages
2020-04-02 19:13:14 +09:00
},
"dependencies": {
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"schema-utils": {
Update npm packages
2021-07-25 17:24:10 +09:00
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/schema-utils/-/schema-utils-3.1.1.tgz",
"integrity": "sha512-Y5PQxS4ITlC+EahLuXaY86TXfR7Dc5lw294alXOq86JAHCihAIZfqv8nNCWvaEJvaC51uN9hbLGeV0cFBdH+Fw==",
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"dev": true,
"requires": {
Update npm packages
2021-07-25 17:24:10 +09:00
"@types/json-schema": "^7.0.8",
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"ajv": "^6.12.5",
"ajv-keywords": "^3.5.2"
}
}
}
},
"text-hex": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/text-hex/-/text-hex-1.0.0.tgz",
"integrity": "sha512-uuVGNWzgJ4yhRaNSiubPY7OjISw4sw4E5Uv0wbjp+OzcbmVU/rsT8ujgcXJhn9ypzsgr5vlzpPqP+MBBKcGvbg==",
"dev": true
},
"text-table": {
"version": "0.2.0",
"resolved": "https://registry.npmjs.org/text-table/-/text-table-0.2.0.tgz",
"integrity": "sha1-f17oI66AUgfACvLfSoTsP8+lcLQ=",
"dev": true
},
"textextensions": {
Update npm packages
2021-05-02 16:30:09 +09:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/textextensions/-/textextensions-3.3.0.tgz",
"integrity": "sha512-mk82dS8eRABNbeVJrEiN5/UMSCliINAuz8mkUwH4SwslkNP//gbEzlWNS5au0z5Dpx40SQxzqZevZkn+WYJ9Dw==",
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"dev": true
},
"through": {
"version": "2.3.8",
"resolved": "https://registry.npmjs.org/through/-/through-2.3.8.tgz",
"integrity": "sha1-DdTJ/6q8NXlgsbckEV1+Doai4fU=",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"through2": {
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"version": "4.0.2",
"resolved": "https://registry.npmjs.org/through2/-/through2-4.0.2.tgz",
"integrity": "sha512-iOqSav00cVxEEICeD7TjLB1sueEL+81Wpzp2bY17uZjZN0pWZPuo4suZ/61VujxmqSGFfgOcNuTZ85QJwNZQpw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"readable-stream": "3"
Update `npm` packages
2020-06-27 18:30:30 +09:00
},
"dependencies": {
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"readable-stream": {
"version": "3.6.0",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-3.6.0.tgz",
"integrity": "sha512-BViHy7LKeTz4oNnkcLJ+lVSL6vpiFeX6/d3oSH8zCW7UxP2onchk+vTGB143xuFjHS3deTgkKoXXymXqymiIdA==",
"dev": true,
"requires": {
"inherits": "^2.0.3",
"string_decoder": "^1.1.1",
"util-deprecate": "^1.0.1"
}
Update `npm` packages
2020-06-27 18:30:30 +09:00
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"through2-filter": {
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/through2-filter/-/through2-filter-3.0.0.tgz",
"integrity": "sha512-jaRjI2WxN3W1V8/FMZ9HKIBXixtiqs3SQSX4/YGIiP3gL6djW48VoZq9tDqeCWs3MT8YY5wb/zli8VW8snY1CA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"through2": "~2.0.0",
"xtend": "~4.0.0"
added transform function added depedencies removed gulp-transform dependency removed dependencies removed gulptransform dependency
2019-11-13 11:51:31 +09:00
},
"dependencies": {
"through2": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.5.tgz",
"integrity": "sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==",
"dev": true,
"requires": {
"readable-stream": "~2.3.6",
"xtend": "~4.0.1"
}
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"time-stamp": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/time-stamp/-/time-stamp-1.1.0.tgz",
"integrity": "sha1-dkpaEa9QVhkhsTPztE5hhofg9cM=",
"dev": true
},
"to-absolute-glob": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/to-absolute-glob/-/to-absolute-glob-2.0.2.tgz",
"integrity": "sha1-GGX0PZ50sIItufFFt4z/fQ98hJs=",
"dev": true,
"requires": {
"is-absolute": "^1.0.0",
"is-negated-glob": "^1.0.0"
}
},
"to-fast-properties": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/to-fast-properties/-/to-fast-properties-1.0.3.tgz",
"integrity": "sha1-uDVx+k2MJbguIxsG46MFXeTKGkc=",
"dev": true
},
"to-object-path": {
"version": "0.3.0",
"resolved": "https://registry.npmjs.org/to-object-path/-/to-object-path-0.3.0.tgz",
"integrity": "sha1-KXWIt7Dn4KwI4E5nL4XB9JmeF68=",
"dev": true,
"requires": {
"kind-of": "^3.0.2"
},
"dependencies": {
"kind-of": {
"version": "3.2.2",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz",
"integrity": "sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=",
"dev": true,
"requires": {
"is-buffer": "^1.1.5"
}
}
}
},
"to-regex": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/to-regex/-/to-regex-3.0.2.tgz",
"integrity": "sha512-FWtleNAtZ/Ki2qtqej2CXTOayOH9bHDQF+Q48VpWyDXjbYxA4Yz8iDB31zXOBUlOHHKidDbqGVrTUvQMPmBGBw==",
"dev": true,
"requires": {
"define-property": "^2.0.2",
"extend-shallow": "^3.0.2",
"regex-not": "^1.0.2",
"safe-regex": "^1.1.0"
}
},
"to-regex-range": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/to-regex-range/-/to-regex-range-2.1.1.tgz",
"integrity": "sha1-fIDBe53+vlmeJzZ+DU3VWQFB2zg=",
"dev": true,
"requires": {
"is-number": "^3.0.0",
"repeat-string": "^1.6.1"
}
},
"to-through": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/to-through/-/to-through-2.0.0.tgz",
"integrity": "sha1-/JKtq6ByZHvAtn1rA2ZKoZUJOvY=",
"dev": true,
"requires": {
"through2": "^2.0.3"
added transform function added depedencies removed gulp-transform dependency removed dependencies removed gulptransform dependency
2019-11-13 11:51:31 +09:00
},
"dependencies": {
"through2": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.5.tgz",
"integrity": "sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==",
"dev": true,
"requires": {
"readable-stream": "~2.3.6",
"xtend": "~4.0.1"
}
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update packages
2018-11-25 05:00:22 +09:00
"token-stream": {
"version": "0.0.1",
"resolved": "https://registry.npmjs.org/token-stream/-/token-stream-0.0.1.tgz",
"integrity": "sha1-zu78cXp2xDFvEm0LnbqlXX598Bo=",
"dev": true
},
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"tr46": {
"version": "0.0.3",
"resolved": "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz",
"integrity": "sha1-gYT9NH2snNwYWZLzpmIuFLnZq2o=",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"trim-newlines": {
Bump trim-newlines from 3.0.0 to 3.0.1 Bumps [trim-newlines](https://github.com/sindresorhus/trim-newlines) from 3.0.0 to 3.0.1. - [Release notes](https://github.com/sindresorhus/trim-newlines/releases) - [Commits](https://github.com/sindresorhus/trim-newlines/commits) --- updated-dependencies: - dependency-name: trim-newlines dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2021-06-08 17:11:20 +09:00
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-3.0.1.tgz",
"integrity": "sha512-c1PTsA3tYrIsLGkJkzHF+w9F2EyxfXGo4UyJc4pFL++FMjnq0HJS69T3M7d//gKrFKwy429bouPescbjecU+Zw==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true
},
Update packages
2018-11-25 05:00:22 +09:00
"triple-beam": {
"version": "1.3.0",
"resolved": "https://registry.npmjs.org/triple-beam/-/triple-beam-1.3.0.tgz",
"integrity": "sha512-XrHUvV5HpdLmIj4uVMxHggLbFSZYIn7HEWsqePZcI50pco+MPqJ50wMGY794X7AOOhxOBAjbkqfAbEe/QMp2Lw==",
"dev": true
},
Update `npm` packages
2020-06-13 17:36:11 +09:00
"tsconfig-paths": {
Update npm packages
2022-01-09 18:05:52 +09:00
"version": "3.12.0",
"resolved": "https://registry.npmjs.org/tsconfig-paths/-/tsconfig-paths-3.12.0.tgz",
"integrity": "sha512-e5adrnOYT6zqVnWqZu7i/BQ3BnhzvGbjEjejFXO20lKIKpwTaupkCPgEfv4GZK1IBciJUEhYs3J3p75FdaTFVg==",
Update `npm` packages
2020-06-13 17:36:11 +09:00
"dev": true,
"requires": {
Update npm packages
2021-09-05 16:47:57 +09:00
"@types/json5": "^0.0.29",
"json5": "^1.0.1",
Update `npm` packages
2020-06-13 17:36:11 +09:00
"minimist": "^1.2.0",
"strip-bom": "^3.0.0"
},
"dependencies": {
Update npm packages
2021-09-05 16:47:57 +09:00
"json5": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/json5/-/json5-1.0.1.tgz",
"integrity": "sha512-aKS4WQjPenRxiQsC93MNfjx+nbF4PAdYzmd/1JIj8HYzqfbu86beTuNgXDzPknWk0n0uARlyewZo4s++ES36Ow==",
"dev": true,
"requires": {
"minimist": "^1.2.0"
}
},
Update `npm` packages
2020-06-13 17:36:11 +09:00
"strip-bom": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-3.0.0.tgz",
"integrity": "sha1-IzTBjpx1n3vdVv3vfprj1YjmjtM=",
"dev": true
}
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"ttest": {
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/ttest/-/ttest-3.0.0.tgz",
"integrity": "sha512-bLo+LdYokiDZHVFIWJmC5afoh7wZ+o1h++0XXKh01+yprzz8CnaiGNcbcbqP0e3+iyDqclLI+rM0j/9AwmRljw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2019-09-15 22:35:32 +09:00
"distributions": "^2.1.0",
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"summary": "^2.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"type-check": {
"version": "0.3.2",
"resolved": "https://registry.npmjs.org/type-check/-/type-check-0.3.2.tgz",
"integrity": "sha1-WITKtRLPHTVeP7eE8wgEsrUg23I=",
"dev": true,
"requires": {
"prelude-ls": "~1.1.2"
}
},
Update npm packages
2019-11-11 19:22:03 +09:00
"type-fest": {
Update `npm` packages
2019-11-23 19:25:24 +09:00
"version": "0.8.1",
"resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.8.1.tgz",
"integrity": "sha512-4dbzIzqvjtgiM5rw1k5rEHtBANKmdudhGyBEajN01fEyhaAIhsoKNy6y7+IN93IfpFtwY9iqi7kD+xwKhQsNJA==",
Update npm packages
2019-11-11 19:22:03 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"typedarray": {
"version": "0.0.6",
"resolved": "https://registry.npmjs.org/typedarray/-/typedarray-0.0.6.tgz",
"integrity": "sha1-hnrHTjhkGHsdPUfZlqeOxciDB3c=",
"dev": true
},
Add typescript definitions This PR adds typescript definitions from the JSDoc already present. It adds a new gulp-target 'types' that calls 'tsc', the typescript compiler, to create the definitions. To use the definitions, users can simply do the following: ``` import {getDocument, GlobalWorkerOptions} from "pdfjs-dist"; import pdfjsWorker from "pdfjs-dist/build/pdf.worker.entry"; GlobalWorkerOptions.workerSrc = pdfjsWorker; const pdf = await getDocument("file:///some.pdf").promise; ``` Co-authored-by: @oBusk Co-authored-by: @tamuratak
2020-07-23 05:38:04 +09:00
"typescript": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "4.5.5",
"resolved": "https://registry.npmjs.org/typescript/-/typescript-4.5.5.tgz",
"integrity": "sha512-TCTIul70LyWe6IJWT8QSYeA54WQe8EjQFU4wY52Fasj5UKx88LNYKCgBEHcOMOrFF1rKGbD8v/xcNWVUq9SymA==",
Add typescript definitions This PR adds typescript definitions from the JSDoc already present. It adds a new gulp-target 'types' that calls 'tsc', the typescript compiler, to create the definitions. To use the definitions, users can simply do the following: ``` import {getDocument, GlobalWorkerOptions} from "pdfjs-dist"; import pdfjsWorker from "pdfjs-dist/build/pdf.worker.entry"; GlobalWorkerOptions.workerSrc = pdfjsWorker; const pdf = await getDocument("file:///some.pdf").promise; ``` Co-authored-by: @oBusk Co-authored-by: @tamuratak
2020-07-23 05:38:04 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"typogr": {
Update packages
2018-07-01 03:39:31 +09:00
"version": "0.6.8",
"resolved": "https://registry.npmjs.org/typogr/-/typogr-0.6.8.tgz",
"integrity": "sha512-zjUkJd8Nt9NvXTzjBYpk5Pw0OgXTStgATbUAAhVvCrFtjvRVcDvtKjtxCRMRZsK0fx2MVa8hoqMiTPSgWOA9pg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"async": "0.2",
"commander": "1.0",
Update packages
2018-07-01 03:39:31 +09:00
"glob": "^7.1.2",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"mkdirp": "0.3"
},
"dependencies": {
"mkdirp": {
"version": "0.3.5",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz",
"integrity": "sha1-3j5fiWHIjHh+4TaN+EmsRBPsqNc=",
"dev": true
}
}
},
Include forgotten changes after Wintersmith update This should have been part of the previous commit that updated the Wintersmith dependency. Markdown support is no longer included in Pug itself and should be done by a transformer instead.
2018-11-25 05:39:54 +09:00
"uc.micro": {
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/uc.micro/-/uc.micro-1.0.5.tgz",
Update eslint-plugin-mozilla to ^1.0.1
2018-11-23 22:40:05 +09:00
"integrity": "sha512-JoLI4g5zv5qNyT09f4YAvEZIIV1oOjqnewYg5D38dkQljIzpPT296dbIGvKro3digYI1bkb7W6EP1y4uDlmzLg==",
"dev": true
Include forgotten changes after Wintersmith update This should have been part of the previous commit that updated the Wintersmith dependency. Markdown support is no longer included in Pug itself and should be done by a transformer instead.
2018-11-25 05:39:54 +09:00
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"uglify-js": {
"version": "2.8.29",
"resolved": "https://registry.npmjs.org/uglify-js/-/uglify-js-2.8.29.tgz",
"integrity": "sha1-KcVzMUgFe7Th913zW3qcty5qWd0=",
"dev": true,
"requires": {
"source-map": "~0.5.1",
"uglify-to-browserify": "~1.0.0",
"yargs": "~3.10.0"
},
"dependencies": {
"source-map": {
"version": "0.5.7",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.7.tgz",
"integrity": "sha1-igOdLRAh0i0eoUyA2OpGi6LvP8w=",
"dev": true
},
"yargs": {
"version": "3.10.0",
"resolved": "https://registry.npmjs.org/yargs/-/yargs-3.10.0.tgz",
"integrity": "sha1-9+572FfdfB0tOMDnTvvWgdFDH9E=",
"dev": true,
"requires": {
"camelcase": "^1.0.2",
"cliui": "^2.1.0",
"decamelize": "^1.0.0",
"window-size": "0.1.0"
}
}
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"uglify-to-browserify": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/uglify-to-browserify/-/uglify-to-browserify-1.0.2.tgz",
"integrity": "sha1-bgkk1r2mta/jSeOabWMoUKD4grc=",
"dev": true,
"optional": true
},
Update npm packages
2021-05-16 17:05:58 +09:00
"unbox-primitive": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/unbox-primitive/-/unbox-primitive-1.0.1.tgz",
"integrity": "sha512-tZU/3NqK3dA5gpE1KtyiJUrEB0lxnGkMFHptJ7q6ewdZ8s12QrODwNbhIJStmJkd1QDXa1NRA8aF2A1zk/Ypyw==",
"dev": true,
"requires": {
"function-bind": "^1.1.1",
"has-bigints": "^1.0.1",
"has-symbols": "^1.0.2",
"which-boxed-primitive": "^1.0.2"
},
"dependencies": {
"has-symbols": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.2.tgz",
"integrity": "sha512-chXa79rL/UC2KlX17jo3vRGz0azaWEx5tGqZg5pO3NUyEJVB17dMruQlzCCOfUvElghKcm5194+BCRvi2Rv/Gw==",
"dev": true
}
}
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"unbzip2-stream": {
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"version": "1.4.3",
"resolved": "https://registry.npmjs.org/unbzip2-stream/-/unbzip2-stream-1.4.3.tgz",
"integrity": "sha512-mlExGW4w71ebDJviH16lQLtZS32VKqsSfk80GCfUlwT/4/hNRFsoscrF/c++9xinkMzECL1uL9DDwXqFWkruPg==",
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"dev": true,
"requires": {
"buffer": "^5.2.1",
"through": "^2.3.8"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"unc-path-regex": {
"version": "0.1.2",
"resolved": "https://registry.npmjs.org/unc-path-regex/-/unc-path-regex-0.1.2.tgz",
"integrity": "sha1-5z3T17DXxe2G+6xrCufYxqadUPo=",
"dev": true
},
"underscore": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "1.13.2",
"resolved": "https://registry.npmjs.org/underscore/-/underscore-1.13.2.tgz",
"integrity": "sha512-ekY1NhRzq0B08g4bGuX4wd2jZx5GnKz6mKSqFL4nqBlfyMGiG10gDFhDTMEfYmDL6Jy0FUIZp7wiRB+0BP7J2g==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"undertaker": {
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/undertaker/-/undertaker-1.2.1.tgz",
"integrity": "sha512-71WxIzDkgYk9ZS+spIB8iZXchFhAdEo2YU8xYqBYJ39DIUIqziK78ftm26eecoIY49X0J2MLhG4hr18Yp6/CMA==",
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"dev": true,
"requires": {
"arr-flatten": "^1.0.1",
"arr-map": "^2.0.0",
"bach": "^1.0.0",
"collection-map": "^1.0.0",
"es6-weak-map": "^2.0.1",
"last-run": "^1.1.0",
"object.defaults": "^1.0.0",
"object.reduce": "^1.0.0",
"undertaker-registry": "^1.0.0"
}
},
"undertaker-registry": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/undertaker-registry/-/undertaker-registry-1.0.1.tgz",
"integrity": "sha1-XkvaMI5KiirlhPm5pDWaSZglzFA=",
"dev": true
},
Update npm packages
2022-01-09 18:05:52 +09:00
"unicode-canonical-property-names-ecmascript": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/unicode-canonical-property-names-ecmascript/-/unicode-canonical-property-names-ecmascript-2.0.0.tgz",
"integrity": "sha512-yY5PpDlfVIU5+y/BSCxAJRBIS1Zc2dDG3Ujq+sR0U+JjUevW2JhocOF+soROYDSaAezOzOKuyyixhD6mBknSmQ==",
"dev": true
},
"unicode-match-property-ecmascript": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/unicode-match-property-ecmascript/-/unicode-match-property-ecmascript-2.0.0.tgz",
"integrity": "sha512-5kaZCrbp5mmbz5ulBkDkbY0SsPOjKqVS35VpL9ulMPfSl0J0Xsm+9Evphv9CoIZFwre7aJoa94AY6seMKGVN5Q==",
"dev": true,
"requires": {
"unicode-canonical-property-names-ecmascript": "^2.0.0",
"unicode-property-aliases-ecmascript": "^2.0.0"
}
},
"unicode-match-property-value-ecmascript": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/unicode-match-property-value-ecmascript/-/unicode-match-property-value-ecmascript-2.0.0.tgz",
"integrity": "sha512-7Yhkc0Ye+t4PNYzOGKedDhXbYIBe1XEQYQxOPyhcXNMJ0WCABqqj6ckydd6pWRZTHV4GuCPKdBAUiMc60tsKVw==",
"dev": true
},
"unicode-property-aliases-ecmascript": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/unicode-property-aliases-ecmascript/-/unicode-property-aliases-ecmascript-2.0.0.tgz",
"integrity": "sha512-5Zfuy9q/DFr4tfO7ZPeVXb1aPoeQSdeFMLpYuFebehDAhbuevLs5yxSZmIFN1tP5F9Wl4IpJrYojg85/zgyZHQ==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"union-value": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/union-value/-/union-value-1.0.1.tgz",
"integrity": "sha512-tJfXmxMeWYnczCVs7XAEvIV7ieppALdyepWMkHkwciRpZraG/xwT+s2JN8+pr1+8jCRf80FFzvr+MpQeeoF4Xg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"arr-union": "^3.1.0",
"get-value": "^2.0.6",
"is-extendable": "^0.1.1",
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"set-value": "^2.0.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"unique-stream": {
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/unique-stream/-/unique-stream-2.3.1.tgz",
"integrity": "sha512-2nY4TnBE70yoxHkDli7DMazpWiP7xMdCYqU2nBRO0UB+ZpEkGsSija7MvmvnZFUeC+mrgiUfcHSr3LmRFIg4+A==",
"dev": true,
"requires": {
"json-stable-stringify-without-jsonify": "^1.0.1",
"through2-filter": "^3.0.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"unset-value": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/unset-value/-/unset-value-1.0.0.tgz",
"integrity": "sha1-g3aHP30jNRef+x5vw6jtDfyKtVk=",
"dev": true,
"requires": {
"has-value": "^0.3.1",
"isobject": "^3.0.0"
},
"dependencies": {
"has-value": {
"version": "0.3.1",
"resolved": "https://registry.npmjs.org/has-value/-/has-value-0.3.1.tgz",
"integrity": "sha1-ex9YutpiyoJ+wKIHgCVlSEWZXh8=",
"dev": true,
"requires": {
"get-value": "^2.0.3",
"has-values": "^0.1.4",
"isobject": "^2.0.0"
},
"dependencies": {
"isobject": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/isobject/-/isobject-2.1.0.tgz",
"integrity": "sha1-8GVWEJaj8dou9GJy+BXIQNh+DIk=",
"dev": true,
"requires": {
"isarray": "1.0.0"
}
}
}
},
"has-values": {
"version": "0.1.4",
"resolved": "https://registry.npmjs.org/has-values/-/has-values-0.1.4.tgz",
"integrity": "sha1-bWHeldkd/Km5oCCJrThL/49it3E=",
"dev": true
}
}
},
"upath": {
Fix (most) vulnerabilities reported by `npm audit` This was done automatically, using the `npm audit fix` command. *Please note:* There's two vulnerabilities left, however they couldn't be fixed automatically and may thus benefit from being handled separately.
2019-10-18 23:43:55 +09:00
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/upath/-/upath-1.2.0.tgz",
"integrity": "sha512-aZwGpamFO61g3OlfT7OQCHqhGnW43ieH9WZeP7QxN/G/jS4jfqUkZxoryvJgVPEcrl5NL/ggHsSmLMHuH64Lhg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"uri-js": {
"version": "4.2.2",
"resolved": "https://registry.npmjs.org/uri-js/-/uri-js-4.2.2.tgz",
"integrity": "sha512-KY9Frmirql91X2Qgjry0Wd4Y+YTdrdZheS8TFwvkbLWf/G5KNJDCh6pKL5OZctEW4+0Baa5idK2ZQuELRwPznQ==",
"dev": true,
"requires": {
"punycode": "^2.1.0"
}
},
"urix": {
"version": "0.1.0",
"resolved": "https://registry.npmjs.org/urix/-/urix-0.1.0.tgz",
"integrity": "sha1-2pN/emLiH+wf0Y1Js1wpNQZ6bHI=",
"dev": true
},
"use": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/use/-/use-3.1.0.tgz",
"integrity": "sha512-6UJEQM/L+mzC3ZJNM56Q4DFGLX/evKGRg15UJHGB9X5j5Z3AFbgZvjUh2yq/UJUY4U5dh7Fal++XbNg1uzpRAw==",
"dev": true,
"requires": {
"kind-of": "^6.0.2"
}
},
"util-deprecate": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
"integrity": "sha1-RQ1Nyfpw3nMnYvvS1KKJgUGaDM8=",
"dev": true
},
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
"v8-compile-cache": {
Update `npm` packages
2021-03-07 20:00:57 +09:00
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/v8-compile-cache/-/v8-compile-cache-2.3.0.tgz",
"integrity": "sha512-l8lCEmLcLYZh4nbunNZvQCJc5pv7+RCwa8q/LdUx8u7lsWvPDKmpodJAJNwkAhJC//dFY48KuIEmjtd4RViDrA==",
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"v8flags": {
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"version": "3.1.3",
"resolved": "https://registry.npmjs.org/v8flags/-/v8flags-3.1.3.tgz",
"integrity": "sha512-amh9CCg3ZxkzQ48Mhcb8iX7xpAfYJgePHxWMQCBWECpOSqJUXgY26ncA61UTV0BkPqfhcy6mzwCIoP4ygxpW8w==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Upgrade to Gulp 4 This required the following changes in the Gulpfile: - Defining a series of tasks is no longer done with arrays, but with the `gulp.series` function. The `web` target is refactored to use a smaller number of tasks to prevent tasks from running multiple times. - Getting all tasks must now be done through the task registry. - Tasks that don't return anything must call `done` upon completion. Moreover, this upgrade allows us to use the latest Node.js on Travis CI again.
2018-11-19 02:33:23 +09:00
"homedir-polyfill": "^1.0.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
"validate-npm-package-license": {
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.3.tgz",
"integrity": "sha512-63ZOUnL4SIXj4L0NixR3L1lcjO38crAbgrTpl28t8jjrfuiOBL5Iygm+60qPs/KsZGzPNg6Smnc/oY16QTjF0g==",
"dev": true,
"requires": {
"spdx-correct": "^3.0.0",
"spdx-expression-parse": "^3.0.0"
}
},
"value-or-function": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/value-or-function/-/value-or-function-3.0.0.tgz",
"integrity": "sha1-HCQ6ULWVwb5Up1S/7OhWO5/42BM=",
"dev": true
},
"vinyl": {
Update `npm` packages
2020-10-04 20:49:28 +09:00
"version": "2.2.1",
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-2.2.1.tgz",
"integrity": "sha512-LII3bXRFBZLlezoG5FfZVcXflZgWP/4dCwKtxd5ky9+LOtM4CS3bIRQsmR1KMnMW07jpE8fqR2lcxPZ+8sJIcw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"clone": "^2.1.1",
"clone-buffer": "^1.0.0",
"clone-stats": "^1.0.0",
"cloneable-readable": "^1.0.0",
"remove-trailing-separator": "^1.0.1",
"replace-ext": "^1.0.0"
}
},
"vinyl-fs": {
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/vinyl-fs/-/vinyl-fs-3.0.3.tgz",
"integrity": "sha512-vIu34EkyNyJxmP0jscNzWBSygh7VWhqun6RmqVfXePrOwi9lhvRs//dOaGOTRUQr4tx7/zd26Tk5WeSVZitgng==",
"dev": true,
"requires": {
"fs-mkdirp-stream": "^1.0.0",
"glob-stream": "^6.1.0",
"graceful-fs": "^4.0.0",
"is-valid-glob": "^1.0.0",
"lazystream": "^1.0.0",
"lead": "^1.0.0",
"object.assign": "^4.0.4",
"pumpify": "^1.3.5",
"readable-stream": "^2.3.3",
"remove-bom-buffer": "^3.0.0",
"remove-bom-stream": "^1.2.0",
"resolve-options": "^1.1.0",
"through2": "^2.0.0",
"to-through": "^2.0.0",
"value-or-function": "^3.0.0",
"vinyl": "^2.0.0",
"vinyl-sourcemap": "^1.1.0"
},
"dependencies": {
added transform function added depedencies removed gulp-transform dependency removed dependencies removed gulptransform dependency
2019-11-13 11:51:31 +09:00
"through2": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.5.tgz",
"integrity": "sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==",
"dev": true,
"requires": {
"readable-stream": "~2.3.6",
"xtend": "~4.0.1"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
},
"vinyl-sourcemap": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/vinyl-sourcemap/-/vinyl-sourcemap-1.1.0.tgz",
"integrity": "sha1-kqgAWTo4cDqM2xHYswCtS+Y7PhY=",
"dev": true,
"requires": {
"append-buffer": "^1.0.2",
"convert-source-map": "^1.5.0",
"graceful-fs": "^4.1.6",
"normalize-path": "^2.1.1",
"now-and-later": "^2.0.0",
"remove-bom-buffer": "^3.0.0",
"vinyl": "^2.0.0"
}
},
"vinyl-sourcemaps-apply": {
"version": "0.2.1",
"resolved": "https://registry.npmjs.org/vinyl-sourcemaps-apply/-/vinyl-sourcemaps-apply-0.2.1.tgz",
"integrity": "sha1-q2VJ1h0XLCsbh75cUI0jnI74dwU=",
"dev": true,
"requires": {
"source-map": "^0.5.1"
},
"dependencies": {
"source-map": {
"version": "0.5.7",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.5.7.tgz",
"integrity": "sha1-igOdLRAh0i0eoUyA2OpGi6LvP8w=",
"dev": true
}
}
},
"void-elements": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/void-elements/-/void-elements-2.0.1.tgz",
"integrity": "sha1-wGavtYK7HLQSjWDqkjkulNXp2+w=",
"dev": true
},
Add basic linting of JSON files using `eslint-plugin-json` By adding basic linting of JSON files, we can ensure that they're actually valid and prevent e.g. test-failures caused by *accidental* errors when editing the `test/test_manifest.json` file (something that I've done *many* times myself). For now this simply uses the `recommended` configuration, but we can obviously tweak this later if/when needed. Please find additional information at https://github.com/azeemba/eslint-plugin-json
2021-06-15 18:59:47 +09:00
"vscode-json-languageservice": {
Update npm packages
2021-08-08 17:45:36 +09:00
"version": "4.1.6",
"resolved": "https://registry.npmjs.org/vscode-json-languageservice/-/vscode-json-languageservice-4.1.6.tgz",
"integrity": "sha512-DIKb3tcfRtb3tIE6g9SLOl5E9tNSt6kljH08Wa5RwFlVshtXGrDDzttchze4CYy9pJpE9mBtCbRHmLvY1Z1ZXA==",
Add basic linting of JSON files using `eslint-plugin-json` By adding basic linting of JSON files, we can ensure that they're actually valid and prevent e.g. test-failures caused by *accidental* errors when editing the `test/test_manifest.json` file (something that I've done *many* times myself). For now this simply uses the `recommended` configuration, but we can obviously tweak this later if/when needed. Please find additional information at https://github.com/azeemba/eslint-plugin-json
2021-06-15 18:59:47 +09:00
"dev": true,
"requires": {
"jsonc-parser": "^3.0.0",
"vscode-languageserver-textdocument": "^1.0.1",
"vscode-languageserver-types": "^3.16.0",
"vscode-nls": "^5.0.0",
"vscode-uri": "^3.0.2"
}
},
"vscode-languageserver-textdocument": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/vscode-languageserver-textdocument/-/vscode-languageserver-textdocument-1.0.1.tgz",
"integrity": "sha512-UIcJDjX7IFkck7cSkNNyzIz5FyvpQfY7sdzVy+wkKN/BLaD4DQ0ppXQrKePomCxTS7RrolK1I0pey0bG9eh8dA==",
"dev": true
},
"vscode-languageserver-types": {
"version": "3.16.0",
"resolved": "https://registry.npmjs.org/vscode-languageserver-types/-/vscode-languageserver-types-3.16.0.tgz",
"integrity": "sha512-k8luDIWJWyenLc5ToFQQMaSrqCHiLwyKPHKPQZ5zz21vM+vIVUSvsRpcbiECH4WR88K2XZqc4ScRcZ7nk/jbeA==",
"dev": true
},
"vscode-nls": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/vscode-nls/-/vscode-nls-5.0.0.tgz",
"integrity": "sha512-u0Lw+IYlgbEJFF6/qAqG2d1jQmJl0eyAGJHoAJqr2HT4M2BNuQYSEiSE75f52pXHSJm8AlTjnLLbBFPrdz2hpA==",
"dev": true
},
"vscode-uri": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/vscode-uri/-/vscode-uri-3.0.2.tgz",
"integrity": "sha512-jkjy6pjU1fxUvI51P+gCsxg1u2n8LSt0W6KrCNQceaziKzff74GoWmjVG46KieVzybO1sttPQmYfrwSHey7GUA==",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"watchpack": {
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/watchpack/-/watchpack-2.3.1.tgz",
"integrity": "sha512-x0t0JuydIo8qCNctdDrn1OzH/qDzk2+rdCOC3YzumZ42fiMqmQ7T3xQurykYMhYfHaPHTp4ZxAx2NfUo1K6QaA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"glob-to-regexp": "^0.4.1",
"graceful-fs": "^4.1.2"
Fix *most* vulnerabilities reported by `npm audit` This was automatically, by using the `npm audit fix` command.
2020-06-27 18:32:51 +09:00
}
},
Replace the bundled `ReadableStream` polyfill with the `web-streams-polyfill` npm package (issue 11157) Compared to the recently replaced `URL` polyfill, the new `ReadableStream` polyfill isn't being exported globally for two reasons: - We're currently checking for the existence of a global `ReadableStream` implementation when determining if the Fetch API will be used; please see `isFetchSupported` in the src/display/display_utils.js file. - Given that it's much newer functionality (compared to `URL`) and that not all browsers may implement all parts of the specification yet, not exposing the `ReadableStream` globally seems safer for now.
2019-09-24 04:55:55 +09:00
"web-streams-polyfill": {
Update npm packages
2021-11-14 18:17:30 +09:00
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/web-streams-polyfill/-/web-streams-polyfill-3.2.0.tgz",
"integrity": "sha512-EqPmREeOzttaLRm5HS7io98goBgZ7IVz79aDvqjD0kYXLtFZTc0T/U6wHTPKyIjb+MdN7DFIIX6hgdBEpWmfPA==",
Replace the bundled `ReadableStream` polyfill with the `web-streams-polyfill` npm package (issue 11157) Compared to the recently replaced `URL` polyfill, the new `ReadableStream` polyfill isn't being exported globally for two reasons: - We're currently checking for the existence of a global `ReadableStream` implementation when determining if the Fetch API will be used; please see `isFetchSupported` in the src/display/display_utils.js file. - Given that it's much newer functionality (compared to `URL`) and that not all browsers may implement all parts of the specification yet, not exposing the `ReadableStream` globally seems safer for now.
2019-09-24 04:55:55 +09:00
"dev": true
},
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"webidl-conversions": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz",
"integrity": "sha1-JFNCdeKnvGvnvIZhHMFq4KVlSHE=",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"webpack": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "5.69.1",
"resolved": "https://registry.npmjs.org/webpack/-/webpack-5.69.1.tgz",
"integrity": "sha512-+VyvOSJXZMT2V5vLzOnDuMz5GxEqLk7hKWQ56YxPW/PQRUuKimPqmEIJOx8jHYeyo65pKbapbW464mvsKbaj4A==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2022-02-20 18:08:23 +09:00
"@types/eslint-scope": "^3.7.3",
"@types/estree": "^0.0.51",
Update npm packages
2021-07-11 19:14:47 +09:00
"@webassemblyjs/ast": "1.11.1",
"@webassemblyjs/wasm-edit": "1.11.1",
"@webassemblyjs/wasm-parser": "1.11.1",
"acorn": "^8.4.1",
Update npm packages
2021-08-08 17:45:36 +09:00
"acorn-import-assertions": "^1.7.6",
Update `npm` packages
2020-11-01 18:04:57 +09:00
"browserslist": "^4.14.5",
Update packages
2019-08-25 03:08:09 +09:00
"chrome-trace-event": "^1.0.2",
Update npm packages
2021-10-03 15:21:01 +09:00
"enhanced-resolve": "^5.8.3",
"es-module-lexer": "^0.9.0",
Update npm packages
2021-05-30 14:43:13 +09:00
"eslint-scope": "5.1.1",
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"events": "^3.2.0",
"glob-to-regexp": "^0.4.1",
Update npm packages
2022-01-23 18:58:15 +09:00
"graceful-fs": "^4.2.9",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"json-parse-better-errors": "^1.0.2",
Update `npm` packages
2021-01-10 19:25:47 +09:00
"loader-runner": "^4.2.0",
Upgrade `webpack` to version 5 The only noticeable changes are that the built files are now *slightly* smaller, and that Webpack now supports optional chaining and nullish coalescing without the need for Babel plugins.
2020-10-11 17:08:22 +09:00
"mime-types": "^2.1.27",
"neo-async": "^2.6.2",
Update npm packages
2021-07-25 17:24:10 +09:00
"schema-utils": "^3.1.0",
Update `npm` packages
2020-11-29 17:43:20 +09:00
"tapable": "^2.1.1",
Update npm packages
2021-06-27 17:25:40 +09:00
"terser-webpack-plugin": "^5.1.3",
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"watchpack": "^2.3.1",
Update npm packages
2022-01-23 18:58:15 +09:00
"webpack-sources": "^3.2.3"
Update packages
2018-09-10 00:54:24 +09:00
},
Update `npm` packages
2021-02-07 19:55:03 +09:00
"dependencies": {
"schema-utils": {
Update npm packages
2021-07-25 17:24:10 +09:00
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/schema-utils/-/schema-utils-3.1.1.tgz",
"integrity": "sha512-Y5PQxS4ITlC+EahLuXaY86TXfR7Dc5lw294alXOq86JAHCihAIZfqv8nNCWvaEJvaC51uN9hbLGeV0cFBdH+Fw==",
Update `npm` packages
2021-02-07 19:55:03 +09:00
"dev": true,
"requires": {
Update npm packages
2021-07-25 17:24:10 +09:00
"@types/json-schema": "^7.0.8",
Update `npm` packages
2021-02-07 19:55:03 +09:00
"ajv": "^6.12.5",
"ajv-keywords": "^3.5.2"
}
}
}
},
"webpack-sources": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "3.2.3",
"resolved": "https://registry.npmjs.org/webpack-sources/-/webpack-sources-3.2.3.tgz",
"integrity": "sha512-/DyMEOrDgLKKIG0fmvtz+4dUX/3Ghozwgm6iPp8KRhvn+eQf9+Q7GWxVNMk3+uCPWfdXYC4ExGBckIXdFEfH1w==",
Update npm packages
2021-08-08 17:45:36 +09:00
"dev": true
Update `npm` packages
2021-02-07 19:55:03 +09:00
},
"webpack-stream": {
Update the `webpack-stream` package to the latest version
2021-09-05 16:58:59 +09:00
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/webpack-stream/-/webpack-stream-7.0.0.tgz",
"integrity": "sha512-XoAQTHyCaYMo6TS7Atv1HYhtmBgKiVLONJbzLBl2V3eibXQ2IT/MCRM841RW/r3vToKD5ivrTJFWgd/ghoxoRg==",
Update `npm` packages
2021-02-07 19:55:03 +09:00
"dev": true,
"requires": {
"fancy-log": "^1.3.3",
"lodash.clone": "^4.3.2",
"lodash.some": "^4.2.2",
"memory-fs": "^0.5.0",
"plugin-error": "^1.0.1",
Update the `webpack-stream` package to the latest version
2021-09-05 16:58:59 +09:00
"supports-color": "^8.1.1",
Update `npm` packages
2021-02-07 19:55:03 +09:00
"through": "^2.3.8",
Update the `webpack-stream` package to the latest version
2021-09-05 16:58:59 +09:00
"vinyl": "^2.2.1"
Update `npm` packages
2021-02-07 19:55:03 +09:00
},
Update packages
2018-09-10 00:54:24 +09:00
"dependencies": {
Update the `webpack-stream` dependency (issue 11996) Given that the long-standing `webpack-stream` issue 201 was recently fixed in PR 207, and a new version released, we should now finally be able to update the dependency. However, depending on if/when `webpack-stream` gets support for Webpack 5 (which is currently in beta) we may still want remove our `webpack-stream` dependency.
2020-09-20 20:42:16 +09:00
"has-flag": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz",
"integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==",
"dev": true
},
"supports-color": {
Update the `webpack-stream` package to the latest version
2021-09-05 16:58:59 +09:00
"version": "8.1.1",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-8.1.1.tgz",
"integrity": "sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q==",
Update the `webpack-stream` dependency (issue 11996) Given that the long-standing `webpack-stream` issue 201 was recently fixed in PR 207, and a new version released, we should now finally be able to update the dependency. However, depending on if/when `webpack-stream` gets support for Webpack 5 (which is currently in beta) we may still want remove our `webpack-stream` dependency.
2020-09-20 20:42:16 +09:00
"dev": true,
"requires": {
"has-flag": "^4.0.0"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
},
Upgrade to Puppeteer 12
2021-11-29 03:22:52 +09:00
"whatwg-url": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/whatwg-url/-/whatwg-url-5.0.0.tgz",
"integrity": "sha1-lmRU6HZUYuN2RNNib2dCzotwll0=",
"dev": true,
"requires": {
"tr46": "~0.0.3",
"webidl-conversions": "^3.0.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"which": {
"version": "1.3.1",
"resolved": "https://registry.npmjs.org/which/-/which-1.3.1.tgz",
"integrity": "sha512-HxJdYWq1MTIQbJ3nw0cqssHoTNU267KlrDuGZ1WYlxDStUtKUhOaJmh112/TZmHxxUfuJqPXSOm7tDyas0OSIQ==",
"dev": true,
"requires": {
"isexe": "^2.0.0"
}
},
Update npm packages
2021-05-16 17:05:58 +09:00
"which-boxed-primitive": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/which-boxed-primitive/-/which-boxed-primitive-1.0.2.tgz",
"integrity": "sha512-bwZdv0AKLpplFY2KZRX6TvyuN7ojjr7lwkg6ml0roIy9YeuSr7JS372qlNW18UQYzgYK9ziGcerWqZOmEn9VNg==",
"dev": true,
"requires": {
"is-bigint": "^1.0.1",
"is-boolean-object": "^1.1.0",
"is-number-object": "^1.0.4",
"is-string": "^1.0.5",
"is-symbol": "^1.0.3"
}
},
Implement the `NodeCanvasFactory` class to execute more unit tests in Node.js
2019-02-11 03:29:38 +09:00
"wide-align": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/wide-align/-/wide-align-1.1.3.tgz",
"integrity": "sha512-QGkOQc8XL6Bt5PwnsExKBPuMKBxnGxWWW3fU55Xt4feHozMUhdUMaBCk290qpm/wG5u/RSKzwdAC4i51YigihA==",
"dev": true,
"requires": {
"string-width": "^1.0.2 || 2"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"window-size": {
"version": "0.1.0",
"resolved": "https://registry.npmjs.org/window-size/-/window-size-0.1.0.tgz",
"integrity": "sha1-VDjNLqk7IC76Ohn+iIeu58lPnJ0=",
"dev": true
},
"winston": {
Update packages
2018-11-25 05:00:22 +09:00
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/winston/-/winston-3.1.0.tgz",
"integrity": "sha512-FsQfEE+8YIEeuZEYhHDk5cILo1HOcWkGwvoidLrDgPog0r4bser1lEIOco2dN9zpDJ1M88hfDgZvxe5z4xNcwg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update packages
2018-11-25 05:00:22 +09:00
"async": "^2.6.0",
"diagnostics": "^1.1.1",
"is-stream": "^1.1.0",
"logform": "^1.9.1",
"one-time": "0.0.4",
"readable-stream": "^2.3.6",
"stack-trace": "0.0.x",
"triple-beam": "^1.3.0",
"winston-transport": "^4.2.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
"async": {
Update packages
2018-11-25 05:00:22 +09:00
"version": "2.6.1",
"resolved": "https://registry.npmjs.org/async/-/async-2.6.1.tgz",
"integrity": "sha512-fNEiL2+AZt6AlAw/29Cr0UDe4sRAHCpEHh54WMz+Bb7QfNcFw4h3loofyJpLeQs4Yx7yuqu/2dLgM5hKOs6HlQ==",
"dev": true,
"requires": {
"lodash": "^4.17.10"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
},
Update packages
2018-11-25 05:00:22 +09:00
"winston-transport": {
"version": "4.2.0",
"resolved": "https://registry.npmjs.org/winston-transport/-/winston-transport-4.2.0.tgz",
"integrity": "sha512-0R1bvFqxSlK/ZKTH86nymOuKv/cT1PQBMuDdA7k7f0S9fM44dNH6bXnuxwXPrN8lefJgtZq08BKdyZ0DZIy/rg==",
"dev": true,
"requires": {
"readable-stream": "^2.3.6",
"triple-beam": "^1.2.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"wintersmith": {
Update packages
2018-11-25 05:00:22 +09:00
"version": "2.5.0",
"resolved": "https://registry.npmjs.org/wintersmith/-/wintersmith-2.5.0.tgz",
"integrity": "sha512-2NWoVZOYkzyH2CutEaHyZWBzW9mIxaGuolzcH8lEWOxNROTV3XJ7Fd5VTp46WtvBm77czCXe+SLtEsIt/OSJvA==",
"dev": true,
"requires": {
"async": "^2.6.1",
"chalk": "^2.4.1",
"chokidar": "^2.0.4",
"coffee-script": "^1.12.7",
"highlight.js": "^9.13.1",
"js-yaml": "^3.12.0",
"marked": "^0.5.1",
"mime": "^2.3.1",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"minimatch": "^3.0.3",
"minimist": "^1.2.0",
"mkdirp": "^0.5.1",
"ncp": "^2.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"npm": "^6.4.1",
"pug": "^2.0.3",
"rimraf": "^2.6.2",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"server-destroy": "^1.0.1",
"slugg": "^1.2.1",
Update packages
2018-11-25 05:00:22 +09:00
"winston": "^3.1.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
"async": {
"version": "2.6.1",
"resolved": "https://registry.npmjs.org/async/-/async-2.6.1.tgz",
"integrity": "sha512-fNEiL2+AZt6AlAw/29Cr0UDe4sRAHCpEHh54WMz+Bb7QfNcFw4h3loofyJpLeQs4Yx7yuqu/2dLgM5hKOs6HlQ==",
"dev": true,
"requires": {
"lodash": "^4.17.10"
}
},
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"glob": {
"version": "7.1.6",
"resolved": "https://registry.npmjs.org/glob/-/glob-7.1.6.tgz",
"integrity": "sha512-LwaxwyZ72Lk7vZINtNNrywX0ZuLyStrdDtabefZKAY5ZGJhVtgdznluResxNmPitE0SAO+O26sWTHeKSI2wMBA==",
"dev": true,
"requires": {
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
"minimatch": "^3.0.4",
"once": "^1.3.0",
"path-is-absolute": "^1.0.0"
}
},
Update packages
2018-11-25 05:00:22 +09:00
"marked": {
"version": "0.5.2",
"resolved": "https://registry.npmjs.org/marked/-/marked-0.5.2.tgz",
"integrity": "sha512-fdZvBa7/vSQIZCi4uuwo2N3q+7jJURpMVCcbaX0S1Mg65WZ5ilXvC67MviJAsdjqqgD+CEq4RKo5AYGgINkVAA==",
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
Update the `mkdirp` package, since its major version was increased
2020-04-02 19:18:23 +09:00
"mkdirp": {
"version": "0.5.4",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.4.tgz",
"integrity": "sha512-iG9AK/dJLtJ0XNgTuDbSyNS3zECqDlAhnQW4CsNxBG3LQJBbHmRX1egw39DmtOdCAqY+dKXV+sgPgilNWUKMVw==",
"dev": true,
"requires": {
"minimist": "^1.2.5"
}
},
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"rimraf": {
"version": "2.7.1",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.7.1.tgz",
"integrity": "sha512-uWjbaKIK3T1OSVptzX7Nl6PvQ3qAGtKEtVRjRuazjfL3Bx5eI409VZSqgND+4UNnmzLVdPj9FqFJNPqBZFve4w==",
"dev": true,
"requires": {
"glob": "^7.1.3"
}
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
},
"with": {
"version": "5.1.1",
"resolved": "https://registry.npmjs.org/with/-/with-5.1.1.tgz",
"integrity": "sha1-+k2qktrzLE6pTtRTyB8EaGtXXf4=",
"dev": true,
"requires": {
"acorn": "^3.1.0",
"acorn-globals": "^3.0.0"
},
"dependencies": {
"acorn": {
"version": "3.3.0",
Update eslint-plugin-mozilla to ^1.0.1
2018-11-23 22:40:05 +09:00
"resolved": "https://registry.npmjs.org/acorn/-/acorn-3.3.0.tgz",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"integrity": "sha1-ReN/s56No/JbruP/U2niu18iAXo=",
"dev": true
}
}
},
Update `npm` packages
2019-11-23 19:25:24 +09:00
"word-wrap": {
"version": "1.2.3",
"resolved": "https://registry.npmjs.org/word-wrap/-/word-wrap-1.2.3.tgz",
"integrity": "sha512-Hz/mrNwitNRh/HUAtM/VT/5VH+ygD6DV7mYKZAtHOrbs8U7lvPS6xf7EJKMF0uW1KJCl0H701g3ZGus+muE5vQ==",
"dev": true
},
Fix some dependency vulnerabilities reported by `npm audit` This is done automatically using the `npm audit fix` command.
2021-12-11 23:28:29 +09:00
"wordwrap": {
"version": "0.0.2",
"resolved": "https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.2.tgz",
"integrity": "sha1-t5Zpu0LstAn4PVg8rVLKF+qhZD8=",
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"wrap-ansi": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-2.1.0.tgz",
"integrity": "sha1-2Pw9KE3QV5T+hJc8rs3Rz4JP3YU=",
"dev": true,
"requires": {
"string-width": "^1.0.1",
"strip-ansi": "^3.0.1"
}
},
"wrappy": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.2.tgz",
"integrity": "sha1-tSQ9jz7BqjXxNkYFvA0QNuMKtp8=",
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"write-file-atomic": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/write-file-atomic/-/write-file-atomic-4.0.1.tgz",
"integrity": "sha512-nSKUxgAbyioruk6hU87QzVbY279oYT6uiwgDoujth2ju4mJ+TZau7SQBhtbTmUyuNYTuXnSyRn66FV0+eCgcrQ==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true,
"requires": {
"imurmurhash": "^0.1.4",
Update npm packages
2022-02-20 18:08:23 +09:00
"signal-exit": "^3.0.7"
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
}
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"ws": {
Update npm packages
2022-02-20 18:08:23 +09:00
"version": "8.5.0",
"resolved": "https://registry.npmjs.org/ws/-/ws-8.5.0.tgz",
"integrity": "sha512-BWX0SWVgLPzYwF8lTzEy1egjhS4S4OEAHfsO8o65WOVsrnSRGaSiUaa9e0ggGlkMTtBlmOpEXiie9RUcBO86qg==",
Convert `package-lock.json` to lock file version 2 Since NPM 7, which is over a year old now since it released in October 2020, NPM automatically transforms lock files from version 1 to version 2. In the NPM 7 release notes they reported: "One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users. The lockfile v2 unlocks the ability to do deterministic and reproducible builds to produce a package tree." Not only is this change backwards compatible (so older versions of NPM will still be able to install everything as expected), reproducability is also a nice property to have and modern NPM versions will otherwise constantly do the conversion anyway, causing contributors to explicitly have to revert the change. Therefore, I believe we should do this now since it doesn't break backwards compatibility for consumers of this file. It only means that producers of this file (i.e., us contributors) need to use at least NPM 7 or higher (as of writing NPM 8 is even available). According to https://nodejs.org/en/download/releases/ this means contributors should at least run Node.js 15.0.0, while 17.1.0 is the most recent as of writing, so to me that sounds reasonable to ask.
2021-11-29 03:11:09 +09:00
"dev": true,
"requires": {}
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"xmlcreate": {
Update npm packages
2022-01-23 18:58:15 +09:00
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/xmlcreate/-/xmlcreate-2.0.4.tgz",
"integrity": "sha512-nquOebG4sngPmGPICTS5EnxqhKbCmz5Ox5hsszI2T6U5qdrJizBc+0ilYSEjTSzU0yZcmvppztXe/5Al5fUwdg==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
"xtend": {
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"integrity": "sha1-pcbVMr5lbiPbgg77lDofBJmNY68=",
"dev": true
},
"y18n": {
Bump y18n from 3.2.1 to 3.2.2 Bumps [y18n](https://github.com/yargs/y18n) from 3.2.1 to 3.2.2. - [Release notes](https://github.com/yargs/y18n/releases) - [Changelog](https://github.com/yargs/y18n/blob/master/CHANGELOG.md) - [Commits](https://github.com/yargs/y18n/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-30 20:50:58 +09:00
"version": "3.2.2",
"resolved": "https://registry.npmjs.org/y18n/-/y18n-3.2.2.tgz",
"integrity": "sha512-uGZHXkHnhF0XeeAPgnKfPv1bgKAYyVvmNL1xlKsPYZPaIHxGti2hHqvOCQv71XMsLxu1QjergkqogUnms5D3YQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"yaml": {
Update npm packages
2021-05-02 16:30:09 +09:00
"version": "1.10.2",
"resolved": "https://registry.npmjs.org/yaml/-/yaml-1.10.2.tgz",
"integrity": "sha512-r3vXyErRCYJ7wg28yvBY5VSoAF8ZvlcW9/BwUzEtUsjvX/DKs24dIkuwjtuprwJJHsbyUbLApepYTR1BN4uHrg==",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"dev": true
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"yargs": {
Update npm packages
2021-12-26 19:09:29 +09:00
"version": "17.3.1",
"resolved": "https://registry.npmjs.org/yargs/-/yargs-17.3.1.tgz",
"integrity": "sha512-WUANQeVgjLbNsEmGk20f+nlHgOqzRFpiGWVaBrYGYIGANIIu3lWjoyi0fNlFmJkvfhCZ6BXINe7/W2O2bV4iaA==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update the `yargs` package to the latest version While I wasn't able to figure out *exactly* why the old format didn't work, re-factoring the `parseOptions` function to use `yargs` differently "just worked" so that's hopefully good enough here. With these changes everything related to a *particular* option now appears in one place, rather than being spread out, which aids readability in my opinion. Also, the options are now sorted alphabetically, to make it easier to find a particular one. https://www.npmjs.com/package/yargs
2021-04-15 22:18:57 +09:00
"cliui": "^7.0.2",
"escalade": "^3.1.1",
"get-caller-file": "^2.0.5",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"require-directory": "^2.1.1",
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"string-width": "^4.2.3",
Update the `yargs` package to the latest version While I wasn't able to figure out *exactly* why the old format didn't work, re-factoring the `parseOptions` function to use `yargs` differently "just worked" so that's hopefully good enough here. With these changes everything related to a *particular* option now appears in one place, rather than being spread out, which aids readability in my opinion. Also, the options are now sorted alphabetically, to make it easier to find a particular one. https://www.npmjs.com/package/yargs
2021-04-15 22:18:57 +09:00
"y18n": "^5.0.5",
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"yargs-parser": "^21.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
},
"dependencies": {
"ansi-regex": {
Update npm packages
2021-10-03 15:21:01 +09:00
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
"integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true
},
Update the `yargs` package to the latest version While I wasn't able to figure out *exactly* why the old format didn't work, re-factoring the `parseOptions` function to use `yargs` differently "just worked" so that's hopefully good enough here. With these changes everything related to a *particular* option now appears in one place, rather than being spread out, which aids readability in my opinion. Also, the options are now sorted alphabetically, to make it easier to find a particular one. https://www.npmjs.com/package/yargs
2021-04-15 22:18:57 +09:00
"ansi-styles": {
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz",
"integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==",
Update packages
2019-10-18 23:42:02 +09:00
"dev": true,
"requires": {
Update the `yargs` package to the latest version While I wasn't able to figure out *exactly* why the old format didn't work, re-factoring the `parseOptions` function to use `yargs` differently "just worked" so that's hopefully good enough here. With these changes everything related to a *particular* option now appears in one place, rather than being spread out, which aids readability in my opinion. Also, the options are now sorted alphabetically, to make it easier to find a particular one. https://www.npmjs.com/package/yargs
2021-04-15 22:18:57 +09:00
"color-convert": "^2.0.1"
Update packages
2019-10-18 23:42:02 +09:00
}
},
Update the `yargs` package to the latest version While I wasn't able to figure out *exactly* why the old format didn't work, re-factoring the `parseOptions` function to use `yargs` differently "just worked" so that's hopefully good enough here. With these changes everything related to a *particular* option now appears in one place, rather than being spread out, which aids readability in my opinion. Also, the options are now sorted alphabetically, to make it easier to find a particular one. https://www.npmjs.com/package/yargs
2021-04-15 22:18:57 +09:00
"cliui": {
"version": "7.0.4",
"resolved": "https://registry.npmjs.org/cliui/-/cliui-7.0.4.tgz",
"integrity": "sha512-OcRE68cOsVMXp1Yvonl/fzkQOyjLSu/8bhPDfQt0e0/Eb283TKP20Fs2MqoPsr9SwA595rRCA+QMzYc9nBP+JQ==",
Update packages
2019-10-18 23:42:02 +09:00
"dev": true,
"requires": {
Update the `yargs` package to the latest version While I wasn't able to figure out *exactly* why the old format didn't work, re-factoring the `parseOptions` function to use `yargs` differently "just worked" so that's hopefully good enough here. With these changes everything related to a *particular* option now appears in one place, rather than being spread out, which aids readability in my opinion. Also, the options are now sorted alphabetically, to make it easier to find a particular one. https://www.npmjs.com/package/yargs
2021-04-15 22:18:57 +09:00
"string-width": "^4.2.0",
"strip-ansi": "^6.0.0",
"wrap-ansi": "^7.0.0"
Update packages
2019-10-18 23:42:02 +09:00
}
},
Update the `yargs` package to the latest version While I wasn't able to figure out *exactly* why the old format didn't work, re-factoring the `parseOptions` function to use `yargs` differently "just worked" so that's hopefully good enough here. With these changes everything related to a *particular* option now appears in one place, rather than being spread out, which aids readability in my opinion. Also, the options are now sorted alphabetically, to make it easier to find a particular one. https://www.npmjs.com/package/yargs
2021-04-15 22:18:57 +09:00
"color-convert": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz",
"integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==",
Update packages
2019-10-18 23:42:02 +09:00
"dev": true,
"requires": {
Update the `yargs` package to the latest version While I wasn't able to figure out *exactly* why the old format didn't work, re-factoring the `parseOptions` function to use `yargs` differently "just worked" so that's hopefully good enough here. With these changes everything related to a *particular* option now appears in one place, rather than being spread out, which aids readability in my opinion. Also, the options are now sorted alphabetically, to make it easier to find a particular one. https://www.npmjs.com/package/yargs
2021-04-15 22:18:57 +09:00
"color-name": "~1.1.4"
Update packages
2019-10-18 23:42:02 +09:00
}
},
Update the `yargs` package to the latest version While I wasn't able to figure out *exactly* why the old format didn't work, re-factoring the `parseOptions` function to use `yargs` differently "just worked" so that's hopefully good enough here. With these changes everything related to a *particular* option now appears in one place, rather than being spread out, which aids readability in my opinion. Also, the options are now sorted alphabetically, to make it easier to find a particular one. https://www.npmjs.com/package/yargs
2021-04-15 22:18:57 +09:00
"get-caller-file": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/get-caller-file/-/get-caller-file-2.0.5.tgz",
"integrity": "sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==",
Update packages
2019-10-18 23:42:02 +09:00
"dev": true
},
Update the `yargs` package to the latest version While I wasn't able to figure out *exactly* why the old format didn't work, re-factoring the `parseOptions` function to use `yargs` differently "just worked" so that's hopefully good enough here. With these changes everything related to a *particular* option now appears in one place, rather than being spread out, which aids readability in my opinion. Also, the options are now sorted alphabetically, to make it easier to find a particular one. https://www.npmjs.com/package/yargs
2021-04-15 22:18:57 +09:00
"is-fullwidth-code-point": {
Update packages
2019-10-18 23:42:02 +09:00
"version": "3.0.0",
Update the `yargs` package to the latest version While I wasn't able to figure out *exactly* why the old format didn't work, re-factoring the `parseOptions` function to use `yargs` differently "just worked" so that's hopefully good enough here. With these changes everything related to a *particular* option now appears in one place, rather than being spread out, which aids readability in my opinion. Also, the options are now sorted alphabetically, to make it easier to find a particular one. https://www.npmjs.com/package/yargs
2021-04-15 22:18:57 +09:00
"resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz",
"integrity": "sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==",
"dev": true
},
"string-width": {
Update npm packages
2021-10-03 15:21:01 +09:00
"version": "4.2.3",
"resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz",
"integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==",
Update packages
2019-10-18 23:42:02 +09:00
"dev": true,
"requires": {
Update the `yargs` package to the latest version While I wasn't able to figure out *exactly* why the old format didn't work, re-factoring the `parseOptions` function to use `yargs` differently "just worked" so that's hopefully good enough here. With these changes everything related to a *particular* option now appears in one place, rather than being spread out, which aids readability in my opinion. Also, the options are now sorted alphabetically, to make it easier to find a particular one. https://www.npmjs.com/package/yargs
2021-04-15 22:18:57 +09:00
"emoji-regex": "^8.0.0",
"is-fullwidth-code-point": "^3.0.0",
Update npm packages
2021-10-03 15:21:01 +09:00
"strip-ansi": "^6.0.1"
Update packages
2019-10-18 23:42:02 +09:00
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"strip-ansi": {
Update npm packages
2021-10-03 15:21:01 +09:00
"version": "6.0.1",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
"integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update npm packages
2021-10-03 15:21:01 +09:00
"ansi-regex": "^5.0.1"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
},
Update the `yargs` package to the latest version While I wasn't able to figure out *exactly* why the old format didn't work, re-factoring the `parseOptions` function to use `yargs` differently "just worked" so that's hopefully good enough here. With these changes everything related to a *particular* option now appears in one place, rather than being spread out, which aids readability in my opinion. Also, the options are now sorted alphabetically, to make it easier to find a particular one. https://www.npmjs.com/package/yargs
2021-04-15 22:18:57 +09:00
"wrap-ansi": {
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-7.0.0.tgz",
"integrity": "sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
Update the `yargs` package to the latest version While I wasn't able to figure out *exactly* why the old format didn't work, re-factoring the `parseOptions` function to use `yargs` differently "just worked" so that's hopefully good enough here. With these changes everything related to a *particular* option now appears in one place, rather than being spread out, which aids readability in my opinion. Also, the options are now sorted alphabetically, to make it easier to find a particular one. https://www.npmjs.com/package/yargs
2021-04-15 22:18:57 +09:00
"ansi-styles": "^4.0.0",
"string-width": "^4.1.0",
"strip-ansi": "^6.0.0"
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
Update the `yargs` package to the latest version While I wasn't able to figure out *exactly* why the old format didn't work, re-factoring the `parseOptions` function to use `yargs` differently "just worked" so that's hopefully good enough here. With these changes everything related to a *particular* option now appears in one place, rather than being spread out, which aids readability in my opinion. Also, the options are now sorted alphabetically, to make it easier to find a particular one. https://www.npmjs.com/package/yargs
2021-04-15 22:18:57 +09:00
},
"y18n": {
"version": "5.0.8",
"resolved": "https://registry.npmjs.org/y18n/-/y18n-5.0.8.tgz",
"integrity": "sha512-0pfFzegeDWJHJIAmTLRP2DwHjdF5s7jo9tuztdQxAhINCdvS+3nGINqPd00AphqJR/0LhANUS6/+7SCb98YOfA==",
"dev": true
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
},
"yargs-parser": {
"version": "21.0.0",
"resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-21.0.0.tgz",
"integrity": "sha512-z9kApYUOCwoeZ78rfRYYWdiU/iNL6mwwYlkkZfJoyMR1xps+NEBX5X7XmRpxkZHhXJ6+Ey00IwKxBBSW9FIjyA==",
"dev": true
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
}
}
},
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"yargs-parser": {
Update `npm` packages
2021-03-07 20:00:57 +09:00
"version": "20.2.6",
"resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-20.2.6.tgz",
"integrity": "sha512-AP1+fQIWSM/sMiET8fyayjx/J+JmTPt2Mr0FkrgqB4todtfa53sOsrSAcIrJRD5XS20bKUwaDIuMkWKCEiQLKA==",
Update `npm` packages
2020-11-29 17:43:20 +09:00
"dev": true
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
},
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"yauzl": {
"version": "2.10.0",
"resolved": "https://registry.npmjs.org/yauzl/-/yauzl-2.10.0.tgz",
"integrity": "sha1-x+sXyT4RLLEIb6bY5R+wZnt5pfk=",
"dev": true,
"requires": {
"buffer-crc32": "~0.2.3",
"fd-slicer": "~1.1.0"
}
},
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"yazl": {
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"version": "2.5.1",
"resolved": "https://registry.npmjs.org/yazl/-/yazl-2.5.1.tgz",
"integrity": "sha512-phENi2PLiHnHb6QBVot+dJnaAZ0xosj7p3fWl+znIjBDlnMI2PsZCJZ306BPTFOaHf5qdDEI8x5qFrSOBN5vrw==",
Include `package-lock.json` for reproducible builds
2018-05-20 22:19:49 +09:00
"dev": true,
"requires": {
"buffer-crc32": "~0.2.3"
}
}
}
}
Reference in New Issue Copy Permalink