octoleo/nativefier
2
2
Fork 0
mirror of https://github.com/Llewellynvdm/nativefier.git synced 2024-11-16 01:37:07 +00:00
Code Issues Releases Activity
fae8edd183
nativefier/npm-shrinkwrap.json

5771 lines
232 KiB
JSON
Raw Normal View History

Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
{
"name": "nativefier",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"version": "50.1.0",
"lockfileVersion": 1,
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"requires": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"@ampproject/remapping": {
Relock dependencies
2022-05-02 03:22:57 +00:00
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/@ampproject/remapping/-/remapping-2.2.0.tgz",
"integrity": "sha512-qRmjj8nj9qmLTQXXmaR1cck3UXSRMPrbsLJAasZpF+t3riI71BXed5ebIOYwQntykeZuhjsdweEc9BxH5Jc26w==",
Relock dependencies
2022-02-06 22:47:06 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock dependencies
2022-05-02 03:22:57 +00:00
"@jridgewell/gen-mapping": "^0.1.0",
"@jridgewell/trace-mapping": "^0.3.9"
Relock dependencies
2022-02-06 22:47:06 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/code-frame": {
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"version": "7.18.6",
"resolved": "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.18.6.tgz",
"integrity": "sha512-TDCmlK5eOvH+eH7cdAFlNXeVJqWIQ7gW9tY1GJIpUtFb6CmjVyq2VM3u71bOyR8CRihcCgMUYoDNyLXao3+70Q==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"@babel/highlight": "^7.18.6"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/compat-data": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "7.21.0",
"resolved": "https://registry.npmjs.org/@babel/compat-data/-/compat-data-7.21.0.tgz",
"integrity": "sha512-gMuZsmsgxk/ENC3O/fRw5QY8A9/uxQbbCEypnLIiYYc/qVJtEV7ouxC3EllIIwNzMqAQee5tanFabWsUOutS7g==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/core": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "7.21.3",
"resolved": "https://registry.npmjs.org/@babel/core/-/core-7.21.3.tgz",
"integrity": "sha512-qIJONzoa/qiHghnm0l1n4i/6IIziDpzqc36FBs4pzMhDUraHqponwJLiAKm1hGLP3OSB/TVNz6rMwVGpwxxySw==",
Upgrade Electron from 13 to 16 (PR #1288) https://www.electronjs.org/docs/latest/breaking-changes Co-authored-by: Ronan Jouchet <ronan@jouchet.fr>
2022-01-02 11:17:06 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@ampproject/remapping": "^2.2.0",
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"@babel/code-frame": "^7.18.6",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@babel/generator": "^7.21.3",
"@babel/helper-compilation-targets": "^7.20.7",
"@babel/helper-module-transforms": "^7.21.2",
"@babel/helpers": "^7.21.0",
"@babel/parser": "^7.21.3",
"@babel/template": "^7.20.7",
"@babel/traverse": "^7.21.3",
"@babel/types": "^7.21.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"convert-source-map": "^1.7.0",
"debug": "^4.1.0",
"gensync": "^1.0.0-beta.2",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"json5": "^2.2.2",
Relock dependencies
2022-02-06 22:47:06 +00:00
"semver": "^6.3.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"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
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/generator": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "7.21.3",
"resolved": "https://registry.npmjs.org/@babel/generator/-/generator-7.21.3.tgz",
"integrity": "sha512-QS3iR1GYC/YGUnW7IdggFeN5c1poPUurnGttOV/bZgPGV+izC/D8HnD6DLwod0fsatNyVn1G3EVWMYIF0nHbeA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@babel/types": "^7.21.3",
relock cli
2022-07-23 22:39:04 +00:00
"@jridgewell/gen-mapping": "^0.3.2",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@jridgewell/trace-mapping": "^0.3.17",
Relock dependencies
2022-05-02 03:22:57 +00:00
"jsesc": "^2.5.1"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Relock dependencies
2022-05-30 13:42:40 +00:00
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jridgewell/gen-mapping": {
"version": "0.3.2",
"resolved": "https://registry.npmjs.org/@jridgewell/gen-mapping/-/gen-mapping-0.3.2.tgz",
"integrity": "sha512-mh65xKQAzI6iBcFzwv28KVWSmCkdRBWoOh+bYQGW3+6OZvbbN3TqMGo5hqYxQniRcH9F2VZIoJCm4pa3BPDK/A==",
"dev": true,
"requires": {
"@jridgewell/set-array": "^1.0.1",
"@jridgewell/sourcemap-codec": "^1.4.10",
"@jridgewell/trace-mapping": "^0.3.9"
}
}
Relock dependencies
2022-05-30 13:42:40 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/helper-compilation-targets": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "7.20.7",
"resolved": "https://registry.npmjs.org/@babel/helper-compilation-targets/-/helper-compilation-targets-7.20.7.tgz",
"integrity": "sha512-4tGORmfQcrc+bvrjb5y3dG9Mx1IOZjsHqQVUz7XCNHO+iTmqxWnVg3KRygjGmpRLJGdQSKuvFinbIb0CnZwHAQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@babel/compat-data": "^7.20.5",
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"@babel/helper-validator-option": "^7.18.6",
relock cli
2022-09-18 02:30:33 +00:00
"browserslist": "^4.21.3",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"lru-cache": "^5.1.1",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"semver": "^6.3.0"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"lru-cache": {
"version": "5.1.1",
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-5.1.1.tgz",
"integrity": "sha512-KpNARQA3Iwv+jTA0utUVVbrh+Jlrr1Fv0e56GGzAFOXN7dk/FviaDW8LHmK52DlcH4WP2n6gI8vN1aesBFgo9w==",
"dev": true,
"requires": {
"yallist": "^3.0.2"
}
},
"semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==",
"dev": true
},
"yallist": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/yallist/-/yallist-3.1.1.tgz",
"integrity": "sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g==",
"dev": true
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/helper-environment-visitor": {
relock cli
2022-07-23 22:39:04 +00:00
"version": "7.18.9",
"resolved": "https://registry.npmjs.org/@babel/helper-environment-visitor/-/helper-environment-visitor-7.18.9.tgz",
"integrity": "sha512-3r/aACDJ3fhQ/EVgFy0hpj8oHyHpQc+LPtJoY9SzTThAsStm4Ptegq92vqKoE3vD706ZVFWITnMnxucw+S9Ipg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/helper-function-name": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "7.21.0",
"resolved": "https://registry.npmjs.org/@babel/helper-function-name/-/helper-function-name-7.21.0.tgz",
"integrity": "sha512-HfK1aMRanKHpxemaY2gqBmL04iAPOPRj7DxtNbiDOrJK+gdwkiNRVpCpUJYbUT+aZyemKN8brqTOxzCaG6ExRg==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@babel/template": "^7.20.7",
"@babel/types": "^7.21.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/helper-hoist-variables": {
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"version": "7.18.6",
"resolved": "https://registry.npmjs.org/@babel/helper-hoist-variables/-/helper-hoist-variables-7.18.6.tgz",
"integrity": "sha512-UlJQPkFqFULIcyW5sbzgbkxn2FKRgwWiRexcuaR8RNJRy8+LLveqPjwZV/bwrLZCN0eUHD/x8D0heK1ozuoo6Q==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"@babel/types": "^7.18.6"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/helper-module-imports": {
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"version": "7.18.6",
"resolved": "https://registry.npmjs.org/@babel/helper-module-imports/-/helper-module-imports-7.18.6.tgz",
"integrity": "sha512-0NFvs3VkuSYbFi1x2Vd6tKrywq+z/cLeYC/RJNFrIX/30Bf5aiGYbtvGXolEktzJH8o5E5KJ3tT+nkxuuZFVlA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"@babel/types": "^7.18.6"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/helper-module-transforms": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "7.21.2",
"resolved": "https://registry.npmjs.org/@babel/helper-module-transforms/-/helper-module-transforms-7.21.2.tgz",
"integrity": "sha512-79yj2AR4U/Oqq/WOV7Lx6hUjau1Zfo4cI+JLAVYeMV5XIlbOhmjEk5ulbTc9fMpmlojzZHkUUxAiK+UKn+hNQQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
relock cli
2022-07-23 22:39:04 +00:00
"@babel/helper-environment-visitor": "^7.18.9",
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"@babel/helper-module-imports": "^7.18.6",
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"@babel/helper-simple-access": "^7.20.2",
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"@babel/helper-split-export-declaration": "^7.18.6",
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"@babel/helper-validator-identifier": "^7.19.1",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@babel/template": "^7.20.7",
"@babel/traverse": "^7.21.2",
"@babel/types": "^7.21.2"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/helper-plugin-utils": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "7.20.2",
"resolved": "https://registry.npmjs.org/@babel/helper-plugin-utils/-/helper-plugin-utils-7.20.2.tgz",
"integrity": "sha512-8RvlJG2mj4huQ4pZ+rU9lqKi9ZKiRmuvGuM2HlWmkmgOhbs6zEAw6IEiJ5cQqGbDzGZOhwuOQNtZMi/ENLjZoQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/helper-simple-access": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "7.20.2",
"resolved": "https://registry.npmjs.org/@babel/helper-simple-access/-/helper-simple-access-7.20.2.tgz",
"integrity": "sha512-+0woI/WPq59IrqDYbVGfshjT5Dmk/nnbdpcF8SnMhhXObpTq2KNBdLFRFrkVdbDOyUmHBCxzm5FHV1rACIkIbA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"@babel/types": "^7.20.2"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/helper-split-export-declaration": {
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"version": "7.18.6",
"resolved": "https://registry.npmjs.org/@babel/helper-split-export-declaration/-/helper-split-export-declaration-7.18.6.tgz",
"integrity": "sha512-bde1etTx6ZyTmobl9LLMMQsaizFVZrquTEHOqKeQESMKo4PlObf+8+JA25ZsIpZhT/WEd39+vOdLXAFG/nELpA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"@babel/types": "^7.18.6"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/helper-string-parser": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "7.19.4",
"resolved": "https://registry.npmjs.org/@babel/helper-string-parser/-/helper-string-parser-7.19.4.tgz",
"integrity": "sha512-nHtDoQcuqFmwYNYPz3Rah5ph2p8PFeFCsZk9A/48dPc/rGocJ5J3hAAZ7pb76VWX3fZKu+uEr/FhH5jLx7umrw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
macOS: Move handling of "universal" apps to electron-packager instead of our own thing (#1443) Supported since [electron-packager 15.5.0](https://github.com/electron/electron-packager/releases/tag/v15.5.0). This should fix #1405 as well
2022-08-02 02:44:23 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/helper-validator-identifier": {
relock cli
2022-09-18 02:30:33 +00:00
"version": "7.19.1",
"resolved": "https://registry.npmjs.org/@babel/helper-validator-identifier/-/helper-validator-identifier-7.19.1.tgz",
"integrity": "sha512-awrNfaMtnHUr653GgGEs++LlAvW6w+DcPrOliSMXWCKo597CwL5Acf/wWdNkf/tfEQE3mjkeD1YOVZOUV/od1w==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/helper-validator-option": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "7.21.0",
"resolved": "https://registry.npmjs.org/@babel/helper-validator-option/-/helper-validator-option-7.21.0.tgz",
"integrity": "sha512-rmL/B8/f0mKS2baE9ZpyTcTavvEuWhTTW8amjzXNvYG4AwBsqTLikfXsEofsJEfKHf+HQVQbFOHy6o+4cnC/fQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/helpers": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "7.21.0",
"resolved": "https://registry.npmjs.org/@babel/helpers/-/helpers-7.21.0.tgz",
"integrity": "sha512-XXve0CBtOW0pd7MRzzmoyuSj0e3SEzj8pgyFxnTT1NJZL38BD1MK7yYrm8yefRPIDvNNe14xR4FdbHwpInD4rA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@babel/template": "^7.20.7",
"@babel/traverse": "^7.21.0",
"@babel/types": "^7.21.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/highlight": {
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"version": "7.18.6",
"resolved": "https://registry.npmjs.org/@babel/highlight/-/highlight-7.18.6.tgz",
"integrity": "sha512-u7stbOuYjaPezCuLj29hNW1v64M2Md2qupEKP1fHc7WdOA3DgLh37suiSrZYY7haUB7iBeQZ9P1uiRF359do3g==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"@babel/helper-validator-identifier": "^7.18.6",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"chalk": "^2.0.0",
"js-tokens": "^4.0.0"
},
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00: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==",
"dev": true,
"requires": {
"color-convert": "^1.9.0"
}
},
"chalk": {
"version": "2.4.2",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-2.4.2.tgz",
"integrity": "sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==",
"dev": true,
"requires": {
"ansi-styles": "^3.2.1",
"escape-string-regexp": "^1.0.5",
"supports-color": "^5.3.0"
}
},
"color-convert": {
"version": "1.9.3",
"resolved": "https://registry.npmjs.org/color-convert/-/color-convert-1.9.3.tgz",
"integrity": "sha512-QfAUtd+vFdAtFQcC8CCyYt1fYWxSqAiK2cSD6zDB8N3cpsEBAvRxp9zOGg6G/SHHJYAT88/az/IuDGALsNVbGg==",
"dev": true,
"requires": {
"color-name": "1.1.3"
}
},
"color-name": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.3.tgz",
"integrity": "sha512-72fSenhMw2HZMTVHeCA9KCmpEIbzWiQsjN+BHcBbS9vr1mtt+vJjPdksIBNUmKAW8TFUDPJK5SUU3QhE9NEXDw==",
"dev": true
},
"escape-string-regexp": {
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz",
"integrity": "sha512-vbRorB5FUQWvla16U8R/qgaFIya2qGzwDrNmCZuYKrbdSUMG6I1ZCGQRefkRVhuOkIGVne7BQ35DSfo1qvJqFg==",
"dev": true
},
"has-flag": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/has-flag/-/has-flag-3.0.0.tgz",
"integrity": "sha512-sKJf1+ceQBr4SMkvQnBDNDtf4TXpVhVGateu0t918bl30FnbE2m4vNLX+VWe/dpjlb+HugGYzW7uQXH98HPEYw==",
"dev": true
},
"supports-color": {
"version": "5.5.0",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-5.5.0.tgz",
"integrity": "sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow==",
"dev": true,
"requires": {
"has-flag": "^3.0.0"
}
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/parser": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "7.21.3",
"resolved": "https://registry.npmjs.org/@babel/parser/-/parser-7.21.3.tgz",
"integrity": "sha512-lobG0d7aOfQRXh8AyklEAgZGvA4FShxo6xQbUrrT/cNBPUdIDojlokwJsQyCC/eKia7ifqM0yP+2DRZ4WKw2RQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/plugin-syntax-async-generators": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/helper-plugin-utils": "^7.8.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/plugin-syntax-bigint": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "7.8.3",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-bigint/-/plugin-syntax-bigint-7.8.3.tgz",
"integrity": "sha512-wnTnFlG+YxQm3vDxpGE57Pj0srRU4sHE/mDkt1qv2YJJSeUAec2ma4WLUnUPeKjyrfntVwe/N6dCXpU+zL3Npg==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/helper-plugin-utils": "^7.8.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/plugin-syntax-class-properties": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/helper-plugin-utils": "^7.12.13"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/plugin-syntax-import-meta": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "7.10.4",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-import-meta/-/plugin-syntax-import-meta-7.10.4.tgz",
"integrity": "sha512-Yqfm+XDx0+Prh3VSeEQCPU81yC+JWZ2pDPFSS4ZdpfZhp4MkFMaDC1UqseovEKwSUpnIL7+vK+Clp7bfh0iD7g==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/helper-plugin-utils": "^7.10.4"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/plugin-syntax-json-strings": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/helper-plugin-utils": "^7.8.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/plugin-syntax-logical-assignment-operators": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/helper-plugin-utils": "^7.10.4"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/plugin-syntax-nullish-coalescing-operator": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/helper-plugin-utils": "^7.8.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/plugin-syntax-numeric-separator": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/helper-plugin-utils": "^7.10.4"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/plugin-syntax-object-rest-spread": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/helper-plugin-utils": "^7.8.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/plugin-syntax-optional-catch-binding": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/helper-plugin-utils": "^7.8.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/plugin-syntax-optional-chaining": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/helper-plugin-utils": "^7.8.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/plugin-syntax-top-level-await": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/helper-plugin-utils": "^7.14.5"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/plugin-syntax-typescript": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "7.20.0",
"resolved": "https://registry.npmjs.org/@babel/plugin-syntax-typescript/-/plugin-syntax-typescript-7.20.0.tgz",
"integrity": "sha512-rd9TkG+u1CExzS4SM1BlMEhMXwFLKVjOAFFCDx9PbX5ycJWDoWMcwdJH9RhkPu1dOgn5TrxLot/Gx6lWFuAUNQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"@babel/helper-plugin-utils": "^7.19.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/template": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "7.20.7",
"resolved": "https://registry.npmjs.org/@babel/template/-/template-7.20.7.tgz",
"integrity": "sha512-8SegXApWe6VoNw0r9JHpSteLKTpTiLZ4rMlGIm9JQ18KiCtyQiAMEazujAHrUS5flrcqYZa75ukev3P6QmUwUw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"@babel/code-frame": "^7.18.6",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@babel/parser": "^7.20.7",
"@babel/types": "^7.20.7"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/traverse": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "7.21.3",
"resolved": "https://registry.npmjs.org/@babel/traverse/-/traverse-7.21.3.tgz",
"integrity": "sha512-XLyopNeaTancVitYZe2MlUEvgKb6YVVPXzofHgqHijCImG33b/uTurMS488ht/Hbsb2XK3U2BnSTxKVNGV3nGQ==",
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"@babel/code-frame": "^7.18.6",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@babel/generator": "^7.21.3",
relock cli
2022-07-23 22:39:04 +00:00
"@babel/helper-environment-visitor": "^7.18.9",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@babel/helper-function-name": "^7.21.0",
Bump default Electron to 18.3.5 https://github.com/electron/electron/releases/tag/v18.3.2 https://github.com/electron/electron/releases/tag/v18.3.3 https://github.com/electron/electron/releases/tag/v18.3.4 https://github.com/electron/electron/releases/tag/v18.3.5
2022-06-27 19:56:57 +00:00
"@babel/helper-hoist-variables": "^7.18.6",
"@babel/helper-split-export-declaration": "^7.18.6",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@babel/parser": "^7.21.3",
"@babel/types": "^7.21.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"debug": "^4.1.0",
"globals": "^11.1.0"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"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
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@babel/types": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "7.21.3",
"resolved": "https://registry.npmjs.org/@babel/types/-/types-7.21.3.tgz",
"integrity": "sha512-sBGdETxC+/M4o/zKC0sl6sjWv62WFR/uzxrJ6uYyMLZOUlPnwzw0tKgVHOXxaAd5l2g8pEDM5RZ495GPQI77kg==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"@babel/helper-string-parser": "^7.19.4",
"@babel/helper-validator-identifier": "^7.19.1",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"to-fast-properties": "^2.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@bcoe/v8-coverage": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.2.3",
"resolved": "https://registry.npmjs.org/@bcoe/v8-coverage/-/v8-coverage-0.2.3.tgz",
"integrity": "sha512-0hYQ8SB4Db5zvZB4axdMHGwEaQjkZzFjQiN9LVYvIFB2nSUHW9tYpxWriPrWDASIxiaXax83REcLxuSdnGPZtw==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@discoveryjs/json-ext": {
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-03-21 03:32:19 +00:00
"version": "0.5.7",
"resolved": "https://registry.npmjs.org/@discoveryjs/json-ext/-/json-ext-0.5.7.tgz",
"integrity": "sha512-dBVuXR082gk3jsFp7Rd/JI4kytwGHecnCoTtXFb7DB6CNHp4rg5k1bhg0nWdLGLnOV71lmDzGQaLMy8iPLY0pw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@electron/get": {
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-03-21 03:32:19 +00:00
"version": "1.14.1",
"resolved": "https://registry.npmjs.org/@electron/get/-/get-1.14.1.tgz",
"integrity": "sha512-BrZYyL/6m0ZXz/lDxy/nlVhQz+WF+iPS6qXolEU8atw7h6v1aYkjwJZ63m+bJMBTxDE66X+r2tPS4a/8C82sZw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"debug": "^4.1.1",
"env-paths": "^2.2.0",
"fs-extra": "^8.1.0",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"global-agent": "^3.0.0",
"global-tunnel-ng": "^2.7.1",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"got": "^9.6.0",
"progress": "^2.0.3",
"semver": "^6.2.0",
"sumchecker": "^3.0.1"
},
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fs-extra": {
"version": "8.1.0",
"resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-8.1.0.tgz",
"integrity": "sha512-yhlQgA6mnOJUKOsRUFsgJdQCvkKhcz8tlZG5HBQfReYZy46OwLcY+Zia0mtdHsOo9y/hP+CxMN0TU9QxoOtG4g==",
"requires": {
"graceful-fs": "^4.2.0",
"jsonfile": "^4.0.0",
"universalify": "^0.1.0"
}
},
"semver": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz",
"integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw=="
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@electron/universal": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "1.3.4",
"resolved": "https://registry.npmjs.org/@electron/universal/-/universal-1.3.4.tgz",
"integrity": "sha512-BdhBgm2ZBnYyYRLRgOjM5VHkyFItsbggJ0MHycOjKWdFGYwK97ZFXH54dTvUWEfha81vfvwr5On6XBjt99uDcg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"@electron/asar": "^3.2.1",
macOS: universal architecture app support (fix #1384, PR #1386) As noted in `API.md`: - When specifying `universal` you must be building for the `darwin`, `mas`, `mac`, or `osx` platforms. This will generate a universal (M1 and x86) app.
2022-04-18 23:11:31 +00:00
"@malept/cross-spawn-promise": "^1.1.0",
"debug": "^4.3.1",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"dir-compare": "^3.0.0",
macOS: universal architecture app support (fix #1384, PR #1386) As noted in `API.md`: - When specifying `universal` you must be building for the `darwin`, `mas`, `mac`, or `osx` platforms. This will generate a universal (M1 and x86) app.
2022-04-18 23:11:31 +00:00
"fs-extra": "^9.0.1",
"minimatch": "^3.0.4",
"plist": "^3.0.4"
},
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@electron/asar": {
"version": "3.2.3",
"resolved": "https://registry.npmjs.org/@electron/asar/-/asar-3.2.3.tgz",
"integrity": "sha512-wmOfE6szYyqZhRIiLH+eyZEp+bGcJI0OD/SCvSUrfBE0jvauyGYO2ZhpWxmNCcDojKu5DYrsVqT5BOCZZ01XIg==",
"requires": {
"@types/glob": "^7.1.1",
"chromium-pickle-js": "^0.2.0",
"commander": "^5.0.0",
"glob": "^7.1.6",
"minimatch": "^3.0.4"
}
},
"fs-extra": {
"version": "9.1.0",
"resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-9.1.0.tgz",
"integrity": "sha512-hcg3ZmepS30/7BSFqRvoo3DOMQu7IjqxO5nCDt+zM9XWjb33Wg7ziNT+Qvqbuc3+gWpzO02JubVyk2G4Zvo1OQ==",
"requires": {
"at-least-node": "^1.0.0",
"graceful-fs": "^4.2.0",
"jsonfile": "^6.0.1",
"universalify": "^2.0.0"
}
},
"jsonfile": {
"version": "6.1.0",
"resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-6.1.0.tgz",
"integrity": "sha512-5dgndWOriYSm5cnYaJNhalLNDKOqFwyDB/rr1E9ZsGciGvKPs8R2xYGCacuf3z6K1YKDz182fd+fY3cn3pMqXQ==",
"requires": {
"graceful-fs": "^4.1.6",
"universalify": "^2.0.0"
}
},
"universalify": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/universalify/-/universalify-2.0.0.tgz",
"integrity": "sha512-hAZsKq7Yy11Zu1DE0OzWjw7nnLZmJZYTDZZyEFHZdUhV8FkH5MCfoU1XMaxXovpyW5nq5scPqq0ZDP9Zyl04oQ=="
}
macOS: universal architecture app support (fix #1384, PR #1386) As noted in `API.md`: - When specifying `universal` you must be building for the `darwin`, `mas`, `mac`, or `osx` platforms. This will generate a universal (M1 and x86) app.
2022-04-18 23:11:31 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@eslint-community/eslint-utils": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "4.4.0",
"resolved": "https://registry.npmjs.org/@eslint-community/eslint-utils/-/eslint-utils-4.4.0.tgz",
"integrity": "sha512-1/sA4dwrzBAyeUoQ6oxahHKmrZvsnLCg4RfxW3ZFGGmQkSNQPFNLV9CUEFQP1x9EYXHTo5p6xdhZM1Ne9p/AfA==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"eslint-visitor-keys": "^3.3.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@eslint-community/regexpp": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "4.4.1",
"resolved": "https://registry.npmjs.org/@eslint-community/regexpp/-/regexpp-4.4.1.tgz",
"integrity": "sha512-BISJ6ZE4xQsuL/FmsyRaiffpq977bMlsKfGHTQrOGFErfByxIe6iZTxPf/00Zon9b9a7iUykfQwejN3s2ZW/Bw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@eslint/eslintrc": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/@eslint/eslintrc/-/eslintrc-2.0.1.tgz",
"integrity": "sha512-eFRmABvW2E5Ho6f5fHLqgena46rOj7r7OKHYfLElqcBfGFHHpjBhivyi5+jOEQuSpdc/1phIZJlbC2te+tZNIw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"ajv": "^6.12.4",
Bump to eslint 8 https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0
2021-11-01 19:47:46 +00:00
"debug": "^4.3.2",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"espree": "^9.5.0",
"globals": "^13.19.0",
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-03-21 03:32:19 +00:00
"ignore": "^5.2.0",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"import-fresh": "^3.2.1",
Relock dependencies
2021-11-22 21:03:07 +00:00
"js-yaml": "^4.1.0",
Relock dependencies
2022-05-30 13:42:40 +00:00
"minimatch": "^3.1.2",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"strip-json-comments": "^3.1.1"
Bump to eslint 8 https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0
2021-11-01 19:47:46 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@eslint/js": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "8.36.0",
"resolved": "https://registry.npmjs.org/@eslint/js/-/js-8.36.0.tgz",
"integrity": "sha512-lxJ9R5ygVm8ZWgYdUweoq5ownDlJ4upvoWmO4eLxBYHdMo+vZ/Rx0EN6MbKWDJOSUGrqJy2Gt+Dyv/VKml0fjg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@humanwhocodes/config-array": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "0.11.8",
"resolved": "https://registry.npmjs.org/@humanwhocodes/config-array/-/config-array-0.11.8.tgz",
"integrity": "sha512-UybHIJzJnR5Qc/MsD9Kr+RpO2h+/P1GhOwdiLPXK5TWk5sgTdu88bTD9UP+CKbPPh5Rni1u0GjAdYQLemG8g+g==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
relock dependencies
2021-12-06 20:56:02 +00:00
"@humanwhocodes/object-schema": "^1.2.1",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"debug": "^4.1.1",
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"minimatch": "^3.0.5"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@humanwhocodes/module-importer": {
relock cli
2022-08-29 00:41:15 +00:00
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/@humanwhocodes/module-importer/-/module-importer-1.0.1.tgz",
"integrity": "sha512-bxveV4V8v5Yb4ncFTT3rPSgZBOpCkjfK0y4oVVVJwIuDVBRMDXrPyXRL988i5ap9m9bnyEEjWfm5WkBmtffLfA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
relock cli
2022-08-29 00:41:15 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@humanwhocodes/object-schema": {
Relock dependencies
2021-11-22 21:03:07 +00: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==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@istanbuljs/load-nyc-config": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/@istanbuljs/load-nyc-config/-/load-nyc-config-1.1.0.tgz",
"integrity": "sha512-VjeHSlIzpv/NyD3N0YuHfXOPDIixcA1q2ZV98wsMqcYlPmv2n3Yb2lYP9XMElnaFVXg5A7YLTeLu6V84uQDjmQ==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"camelcase": "^5.3.1",
"find-up": "^4.1.0",
"get-package-type": "^0.1.0",
"js-yaml": "^3.13.1",
"resolve-from": "^5.0.0"
},
Bump to eslint 8 https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0
2021-11-01 19:47:46 +00:00
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"argparse": {
"version": "1.0.10",
"resolved": "https://registry.npmjs.org/argparse/-/argparse-1.0.10.tgz",
"integrity": "sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==",
"dev": true,
"requires": {
"sprintf-js": "~1.0.2"
}
},
"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"
}
},
"js-yaml": {
"version": "3.14.1",
"resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.14.1.tgz",
"integrity": "sha512-okMH7OXXJ7YrN9Ok3/SXrnu4iX9yOk+25nqX4imS2npuvTYDmo/QEZoqwZkYaIDk3jVvBOTOIEgEhaLOynBS9g==",
"dev": true,
"requires": {
"argparse": "^1.0.7",
"esprima": "^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
},
"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
},
"sprintf-js": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.0.3.tgz",
"integrity": "sha512-D9cPgkvLlV3t3IzL0D0YLvGA9Ahk4PcvVwUbN0dSGr1aP0Nrt4AEnTUbuGvquEC0mA64Gqt1fzirlRs5ibXx8g==",
"dev": true
}
Bump to eslint 8 https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0
2021-11-01 19:47:46 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@istanbuljs/schema": {
"version": "0.1.3",
"resolved": "https://registry.npmjs.org/@istanbuljs/schema/-/schema-0.1.3.tgz",
"integrity": "sha512-ZXRY4jNvVgSVQ8DL3LTcakaAtXwTVUxE81hslsyD2AtoXW/wVob10HkOJ1X/pAlcI7D+2YoZKg5do8G/w6RYgA==",
"dev": true
macOS: Move handling of "universal" apps to electron-packager instead of our own thing (#1443) Supported since [electron-packager 15.5.0](https://github.com/electron/electron-packager/releases/tag/v15.5.0). This should fix #1405 as well
2022-08-02 02:44:23 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jest/console": {
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/@jest/console/-/console-28.1.3.tgz",
"integrity": "sha512-QPAkP5EwKdK/bxIr6C1I4Vs0rm2nHiANzj/Z5X2JQkrZo6IqvC4ldZ9K95tF0HdidhA8Bo6egxSzUFPYKcEXLw==",
Bump to eslint 8 https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0
2021-11-01 19:47:46 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
"@jest/types": "^28.1.3",
"@types/node": "*",
"chalk": "^4.0.0",
"jest-message-util": "^28.1.3",
"jest-util": "^28.1.3",
"slash": "^3.0.0"
Bump to eslint 8 https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0
2021-11-01 19:47:46 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jest/core": {
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/@jest/core/-/core-28.1.3.tgz",
"integrity": "sha512-CIKBrlaKOzA7YG19BEqCw3SLIsEwjZkeJzf5bdooVnW4bH5cktqe3JX+G2YV1aK5vP8N9na1IGWFzYaTp6k6NA==",
macOS: Move handling of "universal" apps to electron-packager instead of our own thing (#1443) Supported since [electron-packager 15.5.0](https://github.com/electron/electron-packager/releases/tag/v15.5.0). This should fix #1405 as well
2022-08-02 02:44:23 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/console": "^28.1.3",
"@jest/reporters": "^28.1.3",
"@jest/test-result": "^28.1.3",
"@jest/transform": "^28.1.3",
"@jest/types": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/node": "*",
"ansi-escapes": "^4.2.1",
"chalk": "^4.0.0",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"ci-info": "^3.2.0",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"exit": "^0.1.2",
Relock dependencies
2022-02-06 22:47:06 +00:00
"graceful-fs": "^4.2.9",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-changed-files": "^28.1.3",
"jest-config": "^28.1.3",
"jest-haste-map": "^28.1.3",
"jest-message-util": "^28.1.3",
"jest-regex-util": "^28.0.2",
"jest-resolve": "^28.1.3",
"jest-resolve-dependencies": "^28.1.3",
"jest-runner": "^28.1.3",
"jest-runtime": "^28.1.3",
"jest-snapshot": "^28.1.3",
"jest-util": "^28.1.3",
"jest-validate": "^28.1.3",
"jest-watcher": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"micromatch": "^4.0.4",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"pretty-format": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"rimraf": "^3.0.0",
"slash": "^3.0.0",
"strip-ansi": "^6.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jest/environment": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/@jest/environment/-/environment-28.1.3.tgz",
"integrity": "sha512-1bf40cMFTEkKyEf585R9Iz1WayDjHoHqvts0XFYEqyKM3cFWDpeMoqKKTAF9LSYQModPUlh8FKptoM2YcMWAXA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/fake-timers": "^28.1.3",
"@jest/types": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/node": "*",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-mock": "^28.1.3"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jest/expect": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/@jest/expect/-/expect-28.1.3.tgz",
"integrity": "sha512-lzc8CpUbSoE4dqT0U+g1qODQjBRHPpCPXissXD4mS9+sWQdmmpeJ9zSH1rS1HEkrsMN0fb7nKrJ9giAR1d3wBw==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"expect": "^28.1.3",
"jest-snapshot": "^28.1.3"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jest/expect-utils": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/@jest/expect-utils/-/expect-utils-28.1.3.tgz",
"integrity": "sha512-wvbi9LUrHJLn3NlDW6wF2hvIMtd4JUl2QNVrjq+IBSHirgfrR3o9RnVtxzdEGO2n9JyIWwHnLfby5KzqBGg2YA==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-get-type": "^28.0.2"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jest/fake-timers": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/@jest/fake-timers/-/fake-timers-28.1.3.tgz",
"integrity": "sha512-D/wOkL2POHv52h+ok5Oj/1gOG9HSywdoPtFsRCUmlCILXNn5eIWmcnd3DIiWlJnpGvQtmajqBP95Ei0EimxfLw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/types": "^28.1.3",
"@sinonjs/fake-timers": "^9.1.2",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/node": "*",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-message-util": "^28.1.3",
"jest-mock": "^28.1.3",
"jest-util": "^28.1.3"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jest/globals": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/@jest/globals/-/globals-28.1.3.tgz",
"integrity": "sha512-XFU4P4phyryCXu1pbcqMO0GSQcYe1IsalYCDzRNyhetyeyxMcIxa11qPNDpVNLeretItNqEmYYQn1UYz/5x1NA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/environment": "^28.1.3",
"@jest/expect": "^28.1.3",
"@jest/types": "^28.1.3"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jest/reporters": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/@jest/reporters/-/reporters-28.1.3.tgz",
"integrity": "sha512-JuAy7wkxQZVNU/V6g9xKzCGC5LVXx9FDcABKsSXp5MiKPEE2144a/vXTEDoyzjUpZKfVwp08Wqg5A4WfTMAzjg==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@bcoe/v8-coverage": "^0.2.3",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/console": "^28.1.3",
"@jest/test-result": "^28.1.3",
"@jest/transform": "^28.1.3",
"@jest/types": "^28.1.3",
"@jridgewell/trace-mapping": "^0.3.13",
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"@types/node": "*",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"chalk": "^4.0.0",
"collect-v8-coverage": "^1.0.0",
"exit": "^0.1.2",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"glob": "^7.1.3",
Relock dependencies
2022-02-06 22:47:06 +00:00
"graceful-fs": "^4.2.9",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"istanbul-lib-coverage": "^3.0.0",
Bump default Electron from 16.0.5 to 16.0.6 https://github.com/electron/electron/releases/tag/v16.0.6
2022-01-06 14:43:10 +00:00
"istanbul-lib-instrument": "^5.1.0",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"istanbul-lib-report": "^3.0.0",
"istanbul-lib-source-maps": "^4.0.0",
Bump default Electron from 16.0.5 to 16.0.6 https://github.com/electron/electron/releases/tag/v16.0.6
2022-01-06 14:43:10 +00:00
"istanbul-reports": "^3.1.3",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-message-util": "^28.1.3",
"jest-util": "^28.1.3",
"jest-worker": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"slash": "^3.0.0",
"string-length": "^4.0.1",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"strip-ansi": "^6.0.0",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"terminal-link": "^2.0.0",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"v8-to-istanbul": "^9.0.1"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jest/schemas": {
bump jest **types**, so far it still builds
2022-07-23 22:43:04 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/@jest/schemas/-/schemas-28.1.3.tgz",
"integrity": "sha512-/l/VWsdt/aBXgjshLWOFyFt3IVdYypu5y2Wn2rOO1un6nkqIn8SLXzgIMYXFyYsRWDyF5EthmKJMIdJvk08grg==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
bump jest **types**, so far it still builds
2022-07-23 22:43:04 +00:00
"@sinclair/typebox": "^0.24.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jest/source-map": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.2",
"resolved": "https://registry.npmjs.org/@jest/source-map/-/source-map-28.1.2.tgz",
"integrity": "sha512-cV8Lx3BeStJb8ipPHnqVw/IM2VCMWO3crWZzYodSIkxXnRcXJipCdx1JCK0K5MsJJouZQTH73mzf4vgxRaH9ww==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jridgewell/trace-mapping": "^0.3.13",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"callsites": "^3.0.0",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"graceful-fs": "^4.2.9"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jest/test-result": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/@jest/test-result/-/test-result-28.1.3.tgz",
"integrity": "sha512-kZAkxnSE+FqE8YjW8gNuoVkkC9I7S1qmenl8sGcDOLropASP+BkcGKwhXoyqQuGOGeYY0y/ixjrd/iERpEXHNg==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/console": "^28.1.3",
"@jest/types": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/istanbul-lib-coverage": "^2.0.0",
"collect-v8-coverage": "^1.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jest/test-sequencer": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/@jest/test-sequencer/-/test-sequencer-28.1.3.tgz",
"integrity": "sha512-NIMPEqqa59MWnDi1kvXXpYbqsfQmSJsIbnd85mdVGkiDfQ9WQQTXOLsvISUfonmnBT+w85WEgneCigEEdHDFxw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/test-result": "^28.1.3",
Relock dependencies
2022-02-06 22:47:06 +00:00
"graceful-fs": "^4.2.9",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-haste-map": "^28.1.3",
"slash": "^3.0.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jest/transform": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/@jest/transform/-/transform-28.1.3.tgz",
"integrity": "sha512-u5dT5di+oFI6hfcLOHGTAfmUxFRrjK+vnaP0kkVow9Md/M7V/MxqQMOz/VV25UZO8pzeA9PjfTpOu6BDuwSPQA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@babel/core": "^7.11.6",
"@jest/types": "^28.1.3",
"@jridgewell/trace-mapping": "^0.3.13",
Bump default Electron from 16.0.5 to 16.0.6 https://github.com/electron/electron/releases/tag/v16.0.6
2022-01-06 14:43:10 +00:00
"babel-plugin-istanbul": "^6.1.1",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"chalk": "^4.0.0",
"convert-source-map": "^1.4.0",
"fast-json-stable-stringify": "^2.0.0",
Relock dependencies
2022-02-06 22:47:06 +00:00
"graceful-fs": "^4.2.9",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-haste-map": "^28.1.3",
"jest-regex-util": "^28.0.2",
"jest-util": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"micromatch": "^4.0.4",
Bump default Electron from 16.0.5 to 16.0.6 https://github.com/electron/electron/releases/tag/v16.0.6
2022-01-06 14:43:10 +00:00
"pirates": "^4.0.4",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"slash": "^3.0.0",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"write-file-atomic": "^4.0.1"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jest/types": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/@jest/types/-/types-28.1.3.tgz",
"integrity": "sha512-RyjiyMUZrKz/c+zlMFO1pm70DcIlST8AeWTkoUdZevew44wcNZQHsEVOiCVtgVnlFFD82FPaXycys58cf2muVQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/schemas": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/istanbul-lib-coverage": "^2.0.0",
"@types/istanbul-reports": "^3.0.0",
"@types/node": "*",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@types/yargs": "^17.0.8",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"chalk": "^4.0.0"
re-introduce yargs fix but without upgrading jest to 28 breaking tests, to work on it separately
2022-07-23 23:27:23 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jridgewell/gen-mapping": {
Relock dependencies
2022-05-02 03:22:57 +00:00
"version": "0.1.1",
"resolved": "https://registry.npmjs.org/@jridgewell/gen-mapping/-/gen-mapping-0.1.1.tgz",
"integrity": "sha512-sQXCasFk+U8lWYEe66WxRDOE9PjVz4vSM51fTu3Hw+ClTpUSQb718772vH3pyS5pShp6lvQM7SxgIDXXXmOX7w==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock dependencies
2022-05-02 03:22:57 +00:00
"@jridgewell/set-array": "^1.0.0",
"@jridgewell/sourcemap-codec": "^1.4.10"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jridgewell/resolve-uri": {
relock cli
2022-07-23 22:39:04 +00:00
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/@jridgewell/resolve-uri/-/resolve-uri-3.1.0.tgz",
"integrity": "sha512-F2msla3tad+Mfht5cJq7LSXcdudKTWCVYUgw6pLFOOHSTtZlj6SWNYAp+AhuqLmWdBO2X5hPrLcu8cVP8fy28w==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Relock dependencies
2022-05-02 03:22:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jridgewell/set-array": {
Relock dependencies
2022-06-27 19:49:33 +00:00
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/@jridgewell/set-array/-/set-array-1.1.2.tgz",
"integrity": "sha512-xnkseuNADM0gt2bs+BvhO0p78Mk762YnZdsuzFV018NoG1Sj1SCQvpSqa7XUaTam5vAGasABV9qXASMKnFMwMw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Relock dependencies
2022-02-06 22:47:06 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jridgewell/source-map": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"version": "0.3.2",
"resolved": "https://registry.npmjs.org/@jridgewell/source-map/-/source-map-0.3.2.tgz",
"integrity": "sha512-m7O9o2uR8k2ObDysZYzdfhb08VuEml5oWGiosa1VdaPZ/A6QyPkAJuwN0Q1lhULOf6B7MtQmHENS743hWtCrgw==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"@jridgewell/gen-mapping": "^0.3.0",
"@jridgewell/trace-mapping": "^0.3.9"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"@jridgewell/gen-mapping": {
"version": "0.3.2",
"resolved": "https://registry.npmjs.org/@jridgewell/gen-mapping/-/gen-mapping-0.3.2.tgz",
"integrity": "sha512-mh65xKQAzI6iBcFzwv28KVWSmCkdRBWoOh+bYQGW3+6OZvbbN3TqMGo5hqYxQniRcH9F2VZIoJCm4pa3BPDK/A==",
"dev": true,
"requires": {
"@jridgewell/set-array": "^1.0.1",
"@jridgewell/sourcemap-codec": "^1.4.10",
"@jridgewell/trace-mapping": "^0.3.9"
}
}
Relock dependencies
2022-05-30 13:42:40 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jridgewell/sourcemap-codec": {
Relock dependencies
2022-06-27 19:49:33 +00:00
"version": "1.4.14",
"resolved": "https://registry.npmjs.org/@jridgewell/sourcemap-codec/-/sourcemap-codec-1.4.14.tgz",
"integrity": "sha512-XPSJHWmi394fuUuzDnGz1wiKqWfo1yXecHQMRf2l6hztTO+nPru658AyDngaBe7isIxEkRsPR3FZh+s7iVa4Uw==",
Relock dependencies
2022-02-06 22:47:06 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@jridgewell/trace-mapping": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "0.3.17",
"resolved": "https://registry.npmjs.org/@jridgewell/trace-mapping/-/trace-mapping-0.3.17.tgz",
"integrity": "sha512-MCNzAp77qzKca9+W/+I0+sEpaUnZoeasnghNeVc41VZCEKaCH73Vq3BZZ/SzWIgrqE4H4ceI+p+b6C0mHf9T4g==",
Relock dependencies
2022-02-06 22:47:06 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"@jridgewell/resolve-uri": "3.1.0",
"@jridgewell/sourcemap-codec": "1.4.14"
Relock dependencies
2022-02-06 22:47:06 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@malept/cross-spawn-promise": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/@malept/cross-spawn-promise/-/cross-spawn-promise-1.1.1.tgz",
"integrity": "sha512-RTBGWL5FWQcg9orDOCcp4LvItNzUPcyEU9bwaeJX0rJ1IQxzucC48Y0/sQLp/g6t99IQgAlGIaesJS+gTn7tVQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"cross-spawn": "^7.0.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@nodelib/fs.scandir": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@nodelib/fs.stat": "2.0.5",
"run-parallel": "^1.1.9"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@nodelib/fs.stat": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/@nodelib/fs.stat/-/fs.stat-2.0.5.tgz",
"integrity": "sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@nodelib/fs.walk": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@nodelib/fs.scandir": "2.1.5",
"fastq": "^1.6.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@sinclair/typebox": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "0.24.51",
"resolved": "https://registry.npmjs.org/@sinclair/typebox/-/typebox-0.24.51.tgz",
"integrity": "sha512-1P1OROm/rdubP5aFDSZQILU0vrLCJ4fvHt6EoqHEM+2D/G5MK3bIaymUKLit8Js9gbns5UyJnkP/TZROLw4tUA==",
bump jest **types**, so far it still builds
2022-07-23 22:43:04 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@sindresorhus/is": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.14.0",
"resolved": "https://registry.npmjs.org/@sindresorhus/is/-/is-0.14.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-9NET910DNaIPngYnLLPeg+Ogzqsi9uM4mSboU5y6p8S5DzMTVEsJZrawi+BoDNUVBa2DhJqQYUFvMDfgU062LQ=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@sinonjs/commons": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "1.8.6",
"resolved": "https://registry.npmjs.org/@sinonjs/commons/-/commons-1.8.6.tgz",
"integrity": "sha512-Ky+XkAkqPZSm3NLBeUng77EBQl3cmeJhITaGHdYH8kjVB+aun3S4XBRti2zt17mtt0mIUDiNxYeoJm6drVvBJQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"type-detect": "4.0.8"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@sinonjs/fake-timers": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "9.1.2",
"resolved": "https://registry.npmjs.org/@sinonjs/fake-timers/-/fake-timers-9.1.2.tgz",
"integrity": "sha512-BPS4ynJW/o92PUR4wgriz2Ud5gpST5vz6GQfMixEDK0Z8ZCUv2M7SkBLykH56T++Xs+8ln9zTGbOvNGIe02/jw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@sinonjs/commons": "^1.7.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@szmarczak/http-timer": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/@szmarczak/http-timer/-/http-timer-1.1.2.tgz",
"integrity": "sha512-XIB2XbzHTN6ieIjfIMV9hlVcfPU26s2vafYWQcZHWXHOxiaRZYEDKEwdl129Zyg50+foYV2jCgtrqSA6qNuNSA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"defer-to-connect": "^1.0.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@tokenizer/token": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.3.0",
"resolved": "https://registry.npmjs.org/@tokenizer/token/-/token-0.3.0.tgz",
"integrity": "sha512-OvjF+z51L3ov0OyAU0duzsYuvO01PH7x4t6DJx+guahgTnBHkhJdG7soQeTSFLWN3efnHyibZ4Z8l2EuWwJN3A=="
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/babel__core": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "7.20.0",
"resolved": "https://registry.npmjs.org/@types/babel__core/-/babel__core-7.20.0.tgz",
"integrity": "sha512-+n8dL/9GWblDO0iU6eZAwEIJVr5DWigtle+Q6HLOrh/pdbXOhOtqzq8VPPE2zvNJzSKY4vH/z3iT3tn0A3ypiQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@babel/parser": "^7.20.7",
"@babel/types": "^7.20.7",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/babel__generator": "*",
"@types/babel__template": "*",
"@types/babel__traverse": "*"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/babel__generator": {
Upgrade Electron from 13 to 16 (PR #1288) https://www.electronjs.org/docs/latest/breaking-changes Co-authored-by: Ronan Jouchet <ronan@jouchet.fr>
2022-01-02 11:17:06 +00:00
"version": "7.6.4",
"resolved": "https://registry.npmjs.org/@types/babel__generator/-/babel__generator-7.6.4.tgz",
"integrity": "sha512-tFkciB9j2K755yrTALxD44McOrk+gfpIpvC3sxHjRawj6PfnQxrse4Clq5y/Rq+G3mrBurMax/lG8Qn2t9mSsg==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/types": "^7.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/babel__template": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "7.4.1",
"resolved": "https://registry.npmjs.org/@types/babel__template/-/babel__template-7.4.1.tgz",
"integrity": "sha512-azBFKemX6kMg5Io+/rdGT0dkGreboUVR0Cdm3fz9QJWpaQGJRQXl7C+6hOTCZcMll7KFyEQpgbYI2lHdsS4U7g==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/parser": "^7.1.0",
"@babel/types": "^7.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/babel__traverse": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "7.18.3",
"resolved": "https://registry.npmjs.org/@types/babel__traverse/-/babel__traverse-7.18.3.tgz",
"integrity": "sha512-1kbcJ40lLB7MHsj39U4Sh1uTd2E7rLEa79kmDpI6cy+XiXsteB3POdQomoq4FxszMrO3ZYchkhYJw7A2862b3w==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/types": "^7.3.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/debug": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.1.7",
"resolved": "https://registry.npmjs.org/@types/debug/-/debug-4.1.7.tgz",
"integrity": "sha512-9AonUzyTjXXhEOa0DnqpzZi6VHlqKMswga9EXjpXnnqxwLtdvPPtlO8evrI5D9S6asFRCQ6v+wpiUKbw+vKqyg==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/ms": "*"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/eslint": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "8.21.3",
"resolved": "https://registry.npmjs.org/@types/eslint/-/eslint-8.21.3.tgz",
"integrity": "sha512-fa7GkppZVEByMWGbTtE5MbmXWJTVbrjjaS8K6uQj+XtuuUv1fsuPAxhygfqLmsb/Ufb3CV8deFCpiMfAgi00Sw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/estree": "*",
"@types/json-schema": "*"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/eslint-scope": {
relock cli
2022-07-23 22:39:04 +00:00
"version": "3.7.4",
"resolved": "https://registry.npmjs.org/@types/eslint-scope/-/eslint-scope-3.7.4.tgz",
"integrity": "sha512-9K4zoImiZc3HlIp6AVUDE4CWYx22a+lhSZMYNpbjW04+YF0KWj4pJXnEMjdnFTiQibFFmElcsasJXDbdI/EPhA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/eslint": "*",
"@types/estree": "*"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/estree": {
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-03-21 03:32:19 +00:00
"version": "0.0.51",
"resolved": "https://registry.npmjs.org/@types/estree/-/estree-0.0.51.tgz",
"integrity": "sha512-CuPgU6f3eT/XgKKPqKd/gLZV1Xmvf1a2R5POBOGQa6uv82xpls89HU5zKeVoyR8XzHd1RGNOlQlvUe3CFkjWNQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/fs-extra": {
Fix upgrade not working (#1286) * Attempt to get upgrade working right; in progress * Got it fixed in Mac * Fix some linting errors * Finish fixing upgrade + tests * Integration testing for global shortcuts * Regenerate shrinkwrap * Get rid of deprecated rmdirSync * Remove instead of rm for 12.x support * Make dereferencing platform dependent * Fix folder copy funkiness * Whoops * Whoops 2: Extra Whoops * Update Electron to 13.5.1; Fix auth manual tests * Rework relock * Add a request for help. * Update @types/node to 14
2021-11-29 17:01:20 +00:00
"version": "9.0.13",
"resolved": "https://registry.npmjs.org/@types/fs-extra/-/fs-extra-9.0.13.tgz",
"integrity": "sha512-nEnwB++1u5lVDM2UI4c1+5R+FYaKfaAzS4OococimjVm3nQw3TuzH5UNsocrcTBbhnerblyHj4A49qXbIiZdpA==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Fix upgrade not working (#1286) * Attempt to get upgrade working right; in progress * Got it fixed in Mac * Fix some linting errors * Finish fixing upgrade + tests * Integration testing for global shortcuts * Regenerate shrinkwrap * Get rid of deprecated rmdirSync * Remove instead of rm for 12.x support * Make dereferencing platform dependent * Fix folder copy funkiness * Whoops * Whoops 2: Extra Whoops * Update Electron to 13.5.1; Fix auth manual tests * Rework relock * Add a request for help. * Update @types/node to 14
2021-11-29 17:01:20 +00:00
"@types/node": "*"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/glob": {
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"version": "7.2.0",
"resolved": "https://registry.npmjs.org/@types/glob/-/glob-7.2.0.tgz",
"integrity": "sha512-ZUxbzKl0IfJILTS6t7ip5fQQM/J3TJYubDm3nMbgubNNYS62eXeUpoLUC8/7fJNiFYHTrGPQn7hspDUzIHX3UA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"optional": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/minimatch": "*",
"@types/node": "*"
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
},
"dependencies": {
"@types/node": {
"version": "18.15.10",
"resolved": "https://registry.npmjs.org/@types/node/-/node-18.15.10.tgz",
"integrity": "sha512-9avDaQJczATcXgfmMAW3MIWArOO7A+m90vuCFLr8AotWf8igO/mRoYukrk2cqZVtv38tHs33retzHEilM7FpeQ==",
"optional": true
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/graceful-fs": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "4.1.6",
"resolved": "https://registry.npmjs.org/@types/graceful-fs/-/graceful-fs-4.1.6.tgz",
"integrity": "sha512-Sig0SNORX9fdW+bQuTEovKj3uHcUL6LQKbCrrqb1X7J6/ReAbhCXRAhc+SMejhLELFj2QcyuxmUooZ4bt5ReSw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/node": "*"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/hasbin": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/@types/hasbin/-/hasbin-1.2.0.tgz",
"integrity": "sha512-QhPPTycu+tr/RnGA4mvv+4P1Vebmq9TGEbDvBS9WjPT1pW7dheWeXXWcxb9zJ+YC38LbO8mwVW/DP+FwBroFKw==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/istanbul-lib-coverage": {
Upgrade Electron from 13 to 16 (PR #1288) https://www.electronjs.org/docs/latest/breaking-changes Co-authored-by: Ronan Jouchet <ronan@jouchet.fr>
2022-01-02 11:17:06 +00:00
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/@types/istanbul-lib-coverage/-/istanbul-lib-coverage-2.0.4.tgz",
"integrity": "sha512-z/QT1XN4K4KYuslS23k62yDIDLwLFkzxOuMplDtObz0+y7VqJCaO2o+SPwHCvLFZh7xazvvoor2tA/hPz9ee7g==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/istanbul-lib-report": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/@types/istanbul-lib-report/-/istanbul-lib-report-3.0.0.tgz",
"integrity": "sha512-plGgXAPfVKFoYfa9NpYDAkseG+g6Jr294RqeqcqDixSbU34MZVJRi/P+7Y8GDpzkEwLaGZZOpKIEmeVZNtKsrg==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/istanbul-lib-coverage": "*"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/istanbul-reports": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/@types/istanbul-reports/-/istanbul-reports-3.0.1.tgz",
"integrity": "sha512-c3mAZEuK0lvBp8tmuL74XRKn1+y2dcwOUpH7x4WrF6gk1GIgiluDRgMYQtw2OFcBvAJWlt6ASU3tSqxp0Uu0Aw==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/istanbul-lib-report": "*"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/jest": {
relock cli
2022-08-29 00:41:15 +00:00
"version": "28.1.8",
"resolved": "https://registry.npmjs.org/@types/jest/-/jest-28.1.8.tgz",
"integrity": "sha512-8TJkV++s7B6XqnDrzR1m/TT0A0h948Pnl/097veySPN67VRAgQ4gZ7n2KfJo2rVq6njQjdxU3GCCyDvAeuHoiw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
relock cli
2022-08-29 00:41:15 +00:00
"expect": "^28.0.0",
bump jest **types**, so far it still builds
2022-07-23 22:43:04 +00:00
"pretty-format": "^28.0.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/json-schema": {
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-04-10 15:18:41 +00:00
"version": "7.0.11",
"resolved": "https://registry.npmjs.org/@types/json-schema/-/json-schema-7.0.11.tgz",
"integrity": "sha512-wOuvG1SN4Us4rez+tylwwwCV1psiNVOkJeM3AUWUNWg/jDQY2+HE/444y5gc+jBmRqASOm2Oeh5c1axHobwRKQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/minimatch": {
relock cli
2022-09-18 02:30:33 +00:00
"version": "5.1.2",
"resolved": "https://registry.npmjs.org/@types/minimatch/-/minimatch-5.1.2.tgz",
"integrity": "sha512-K0VQKziLUWkVKiRVrx4a40iPaxTUefQmjtkQofBkYRcoaaL/8rhwDWww9qWbrgicNOgnpIsMxyNIUM4+n6dUIA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"optional": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/ms": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.7.31",
"resolved": "https://registry.npmjs.org/@types/ms/-/ms-0.7.31.tgz",
"integrity": "sha512-iiUgKzV9AuaEkZqkOLDIvlQiL6ltuZd9tGcW3gwpnX8JbuiuhFlEGmmFXEXkN50Cvq7Os88IY2v0dkDqXYWVgA==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/ncp": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/@types/ncp/-/ncp-2.0.5.tgz",
"integrity": "sha512-ocK0p8JuFmX7UkMabFPjY0F7apPvQyLWt5qtdvuvQEBz9i4m2dbzV+6L1zNaUp042RfnL6pHnxDE53OH6XQ9VQ==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/node": "*"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/node": {
Revert node types to 12.x, from 14.x accidentally set which is wrong since we still support 12.x
2022-08-29 01:01:19 +00:00
"version": "12.20.55",
"resolved": "https://registry.npmjs.org/@types/node/-/node-12.20.55.tgz",
"integrity": "sha512-J8xLz7q2OFulZ2cyGTLE1TbbZcjpno7FaN6zdJNrgAdrJ+DZzh/uFR6YrTb4C+nXakvud8Q4+rbhoIWlYQbUFQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/page-icon": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.3.4",
"resolved": "https://registry.npmjs.org/@types/page-icon/-/page-icon-0.3.4.tgz",
"integrity": "sha512-erCUyuzZItLdJ1svtko+1LRIRb9Zvn0yGh2cyteiYSVLiVIgocc9v0vF7truw9VrH4zTpdGwPkrpb/U7MdHIow==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/node": "*"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/prettier": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "2.7.2",
"resolved": "https://registry.npmjs.org/@types/prettier/-/prettier-2.7.2.tgz",
"integrity": "sha512-KufADq8uQqo1pYKVIYzfKbJfBAc0sOeXqGbFaSpv8MRmC/zXgowNZmFcbngndGk922QDmOASEXUZCaY48gs4cg==",
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/semver": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "7.3.13",
"resolved": "https://registry.npmjs.org/@types/semver/-/semver-7.3.13.tgz",
"integrity": "sha512-21cFJr9z3g5dW8B0CVI9g2O9beqaThGQ6ZFBqHfwhzLDKUxaqTIy3vnfah/UPkfOiF2pLq+tGz+W8RyCskuslw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/stack-utils": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/@types/stack-utils/-/stack-utils-2.0.1.tgz",
"integrity": "sha512-Hl219/BT5fLAaz6NDkSuhzasy49dwQS/DSdu4MdggFB8zcXv7vflBI3xp7FEmkmdDkBUI2bPUNeMttp2knYdxw==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/tmp": {
Upgrade Electron from 13 to 16 (PR #1288) https://www.electronjs.org/docs/latest/breaking-changes Co-authored-by: Ronan Jouchet <ronan@jouchet.fr>
2022-01-02 11:17:06 +00:00
"version": "0.2.3",
"resolved": "https://registry.npmjs.org/@types/tmp/-/tmp-0.2.3.tgz",
"integrity": "sha512-dDZH/tXzwjutnuk4UacGgFRwV+JSLaXL1ikvidfJprkb7L9Nx1njcRHHmi3Dsvt7pgqqTEeucQuOrWHPFgzVHA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/yargs": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "17.0.23",
"resolved": "https://registry.npmjs.org/@types/yargs/-/yargs-17.0.23.tgz",
"integrity": "sha512-yuogunc04OnzGQCrfHx+Kk883Q4X0aSwmYZhKjI21m+SVYzjIbrWl8dOOwSv5hf2Um2pdCOXWo9isteZTNXUZQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/yargs-parser": "*"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/yargs-parser": {
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-03-21 03:32:19 +00:00
"version": "21.0.0",
"resolved": "https://registry.npmjs.org/@types/yargs-parser/-/yargs-parser-21.0.0.tgz",
"integrity": "sha512-iO9ZQHkZxHn4mSakYV0vFHAVDyEOIJQrV2uZ06HxEPcx+mt8swXoZHIbaaJ2crJYFfErySgktuTZ3BeLz+XmFA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@types/yauzl": {
macOS: universal architecture app support (fix #1384, PR #1386) As noted in `API.md`: - When specifying `universal` you must be building for the `darwin`, `mas`, `mac`, or `osx` platforms. This will generate a universal (M1 and x86) app.
2022-04-18 23:11:31 +00:00
"version": "2.10.0",
"resolved": "https://registry.npmjs.org/@types/yauzl/-/yauzl-2.10.0.tgz",
"integrity": "sha512-Cn6WYCm0tXv8p6k+A8PvbDG763EDpBoTzHdA+Q/MF6H3sapGjCm9NzoaJncJS9tUKSuCoDs9XHxYYsQDgxR6kw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"optional": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/node": "*"
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
},
"dependencies": {
"@types/node": {
"version": "18.15.10",
"resolved": "https://registry.npmjs.org/@types/node/-/node-18.15.10.tgz",
"integrity": "sha512-9avDaQJczATcXgfmMAW3MIWArOO7A+m90vuCFLr8AotWf8igO/mRoYukrk2cqZVtv38tHs33retzHEilM7FpeQ==",
"optional": true
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@typescript-eslint/eslint-plugin": {
"version": "5.57.0",
"resolved": "https://registry.npmjs.org/@typescript-eslint/eslint-plugin/-/eslint-plugin-5.57.0.tgz",
"integrity": "sha512-itag0qpN6q2UMM6Xgk6xoHa0D0/P+M17THnr4SVgqn9Rgam5k/He33MA7/D7QoJcdMxHFyX7U9imaBonAX/6qA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@eslint-community/regexpp": "^4.4.0",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@typescript-eslint/scope-manager": "5.57.0",
"@typescript-eslint/type-utils": "5.57.0",
"@typescript-eslint/utils": "5.57.0",
Relock dependencies
2022-05-30 13:42:40 +00:00
"debug": "^4.3.4",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"grapheme-splitter": "^1.0.4",
Relock dependencies
2022-05-30 13:42:40 +00:00
"ignore": "^5.2.0",
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"natural-compare-lite": "^1.4.0",
Relock dependencies
2022-05-30 13:42:40 +00:00
"semver": "^7.3.7",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"tsutils": "^3.21.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@typescript-eslint/parser": {
"version": "5.57.0",
"resolved": "https://registry.npmjs.org/@typescript-eslint/parser/-/parser-5.57.0.tgz",
"integrity": "sha512-orrduvpWYkgLCyAdNtR1QIWovcNZlEm6yL8nwH/eTxWLd8gsP+25pdLHYzL2QdkqrieaDwLpytHqycncv0woUQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
"@typescript-eslint/scope-manager": "5.57.0",
"@typescript-eslint/types": "5.57.0",
"@typescript-eslint/typescript-estree": "5.57.0",
Relock dependencies
2022-05-30 13:42:40 +00:00
"debug": "^4.3.4"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@typescript-eslint/scope-manager": {
"version": "5.57.0",
"resolved": "https://registry.npmjs.org/@typescript-eslint/scope-manager/-/scope-manager-5.57.0.tgz",
"integrity": "sha512-NANBNOQvllPlizl9LatX8+MHi7bx7WGIWYjPHDmQe5Si/0YEYfxSljJpoTyTWFTgRy3X8gLYSE4xQ2U+aCozSw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
"@typescript-eslint/types": "5.57.0",
"@typescript-eslint/visitor-keys": "5.57.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@typescript-eslint/type-utils": {
"version": "5.57.0",
"resolved": "https://registry.npmjs.org/@typescript-eslint/type-utils/-/type-utils-5.57.0.tgz",
"integrity": "sha512-kxXoq9zOTbvqzLbdNKy1yFrxLC6GDJFE2Yuo3KqSwTmDOFjUGeWSakgoXT864WcK5/NAJkkONCiKb1ddsqhLXQ==",
Bump default Electron from 16.0.5 to 16.0.6 https://github.com/electron/electron/releases/tag/v16.0.6
2022-01-06 14:43:10 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
"@typescript-eslint/typescript-estree": "5.57.0",
"@typescript-eslint/utils": "5.57.0",
Relock dependencies
2022-05-30 13:42:40 +00:00
"debug": "^4.3.4",
Bump default Electron from 16.0.5 to 16.0.6 https://github.com/electron/electron/releases/tag/v16.0.6
2022-01-06 14:43:10 +00:00
"tsutils": "^3.21.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@typescript-eslint/types": {
"version": "5.57.0",
"resolved": "https://registry.npmjs.org/@typescript-eslint/types/-/types-5.57.0.tgz",
"integrity": "sha512-mxsod+aZRSyLT+jiqHw1KK6xrANm19/+VFALVFP5qa/aiJnlP38qpyaTd0fEKhWvQk6YeNZ5LGwI1pDpBRBhtQ==",
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@typescript-eslint/typescript-estree": {
"version": "5.57.0",
"resolved": "https://registry.npmjs.org/@typescript-eslint/typescript-estree/-/typescript-estree-5.57.0.tgz",
"integrity": "sha512-LTzQ23TV82KpO8HPnWuxM2V7ieXW8O142I7hQTxWIHDcCEIjtkat6H96PFkYBQqGFLW/G/eVVOB9Z8rcvdY/Vw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
"@typescript-eslint/types": "5.57.0",
"@typescript-eslint/visitor-keys": "5.57.0",
Relock dependencies
2022-05-30 13:42:40 +00:00
"debug": "^4.3.4",
"globby": "^11.1.0",
Bump to eslint 8 https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0
2021-11-01 19:47:46 +00:00
"is-glob": "^4.0.3",
Relock dependencies
2022-05-30 13:42:40 +00:00
"semver": "^7.3.7",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"tsutils": "^3.21.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@typescript-eslint/utils": {
"version": "5.57.0",
"resolved": "https://registry.npmjs.org/@typescript-eslint/utils/-/utils-5.57.0.tgz",
"integrity": "sha512-ps/4WohXV7C+LTSgAL5CApxvxbMkl9B9AUZRtnEFonpIxZDIT7wC1xfvuJONMidrkB9scs4zhtRyIwHh4+18kw==",
Relock dependencies
2022-02-06 22:47:06 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@eslint-community/eslint-utils": "^4.2.0",
Relock dependencies
2022-02-06 22:47:06 +00:00
"@types/json-schema": "^7.0.9",
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"@types/semver": "^7.3.12",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@typescript-eslint/scope-manager": "5.57.0",
"@typescript-eslint/types": "5.57.0",
"@typescript-eslint/typescript-estree": "5.57.0",
Relock dependencies
2022-02-06 22:47:06 +00:00
"eslint-scope": "^5.1.1",
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"semver": "^7.3.7"
Relock dependencies
2022-02-06 22:47:06 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@typescript-eslint/visitor-keys": {
"version": "5.57.0",
"resolved": "https://registry.npmjs.org/@typescript-eslint/visitor-keys/-/visitor-keys-5.57.0.tgz",
"integrity": "sha512-ery2g3k0hv5BLiKpPuwYt9KBkAp2ugT6VvyShXdLOkax895EC55sP0Tx5L0fZaQueiK3fBLvHVvEl3jFS5ia+g==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
"@typescript-eslint/types": "5.57.0",
Relock dependencies
2022-05-30 13:42:40 +00:00
"eslint-visitor-keys": "^3.3.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webassemblyjs/ast": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/ast/-/ast-1.11.1.tgz",
"integrity": "sha512-ukBh14qFLjxTQNTXocdyksN5QdM28S1CxHt2rdskFyL+xFV7VremuBLVbmCePj+URalXBENx/9Lm7lnhihtCSw==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@webassemblyjs/helper-numbers": "1.11.1",
"@webassemblyjs/helper-wasm-bytecode": "1.11.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webassemblyjs/floating-point-hex-parser": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webassemblyjs/helper-api-error": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webassemblyjs/helper-buffer": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webassemblyjs/helper-numbers": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@webassemblyjs/floating-point-hex-parser": "1.11.1",
"@webassemblyjs/helper-api-error": "1.11.1",
"@xtuc/long": "4.2.2"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webassemblyjs/helper-wasm-bytecode": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webassemblyjs/helper-wasm-section": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webassemblyjs/ieee754": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/ieee754/-/ieee754-1.11.1.tgz",
"integrity": "sha512-hJ87QIPtAMKbFq6CGTkZYJivEwZDbQUgYd3qKSadTNOhVY7p+gfP6Sr0lLRVTaG1JjFj+r3YchoqRYxNH3M0GQ==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@xtuc/ieee754": "^1.2.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webassemblyjs/leb128": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/leb128/-/leb128-1.11.1.tgz",
"integrity": "sha512-BJ2P0hNZ0u+Th1YZXJpzW6miwqQUGcIHT1G/sf72gLVD9DZ5AdYTqPNbHZh6K1M5VmKvFXwGSWZADz+qBWxeRw==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@xtuc/long": "4.2.2"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webassemblyjs/utf8": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.11.1",
"resolved": "https://registry.npmjs.org/@webassemblyjs/utf8/-/utf8-1.11.1.tgz",
"integrity": "sha512-9kqcxAEdMhiwQkHpkNiorZzqpGrodQQ2IGrHHxCy+Ozng0ofyMA0lTqiLkVs1uzTRejX+/O0EOT7KxqVPuXosQ==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webassemblyjs/wasm-edit": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webassemblyjs/wasm-gen": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webassemblyjs/wasm-opt": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@webassemblyjs/ast": "1.11.1",
"@webassemblyjs/helper-buffer": "1.11.1",
"@webassemblyjs/wasm-gen": "1.11.1",
"@webassemblyjs/wasm-parser": "1.11.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webassemblyjs/wasm-parser": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webassemblyjs/wast-printer": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@webassemblyjs/ast": "1.11.1",
"@xtuc/long": "4.2.2"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webpack-cli/configtest": {
Relock dependencies
2022-06-27 19:49:33 +00:00
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/@webpack-cli/configtest/-/configtest-1.2.0.tgz",
"integrity": "sha512-4FB8Tj6xyVkyqjj1OaTqCjXYULB9FMkqQ8yGrZjRDrYh0nOE+7Lhs45WioWQQMV+ceFlE368Ukhe6xdvJM9Egg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webpack-cli/info": {
Relock dependencies
2022-06-27 19:49:33 +00:00
"version": "1.5.0",
"resolved": "https://registry.npmjs.org/@webpack-cli/info/-/info-1.5.0.tgz",
"integrity": "sha512-e8tSXZpw2hPl2uMJY6fsMswaok5FdlGNRTktvFk2sD8RjH0hE2+XistawJx1vmKteh4NmGmNUrp+Tb2w+udPcQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"envinfo": "^7.7.3"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@webpack-cli/serve": {
Relock dependencies
2022-06-27 19:49:33 +00:00
"version": "1.7.0",
"resolved": "https://registry.npmjs.org/@webpack-cli/serve/-/serve-1.7.0.tgz",
"integrity": "sha512-oxnCNGj88fL+xzV+dacXs44HcDwf1ovs3AuEzvP7mqXw7fQntqIhQ1BRmynh4qEKQSSSRSWVyXRjmTbZIX9V2Q==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@xtuc/ieee754": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/@xtuc/ieee754/-/ieee754-1.2.0.tgz",
"integrity": "sha512-DX8nKgqcGwsc0eJSqYt5lwP4DH5FlHnmuWWBRy7X0NcaGR0ZtuyeESgMwTYVEtxmsNGY+qit4QYT/MIYTOTPeA==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"@xtuc/long": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"acorn": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "8.8.2",
"resolved": "https://registry.npmjs.org/acorn/-/acorn-8.8.2.tgz",
"integrity": "sha512-xjIYgE8HBrkpd/sJqOGNspf8uHG+NOHGOw6a/Urj8taM2EXfdNAH2oFcPeIFfsv3+kz/mJrS5VuMqbNLjCa2vw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"acorn-import-assertions": {
Bump to eslint 8 https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0
2021-11-01 19:47:46 +00: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==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Bump to eslint 8 https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0
2021-11-01 19:47:46 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"acorn-jsx": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "5.3.2",
"resolved": "https://registry.npmjs.org/acorn-jsx/-/acorn-jsx-5.3.2.tgz",
"integrity": "sha512-rq9s+JNhf0IChjtDXxllJ7g41oZk5SlXtp0LHwyA5cejwn7vKmKp4pPri6YEePv2PU65sAsegbXtIinmDFDXgQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"ajv": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "6.12.6",
"resolved": "https://registry.npmjs.org/ajv/-/ajv-6.12.6.tgz",
"integrity": "sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"fast-deep-equal": "^3.1.1",
"fast-json-stable-stringify": "^2.0.0",
"json-schema-traverse": "^0.4.1",
"uri-js": "^4.2.2"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"ajv-keywords": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.5.2",
"resolved": "https://registry.npmjs.org/ajv-keywords/-/ajv-keywords-3.5.2.tgz",
"integrity": "sha512-5p6WTN0DdTGVQk6VjcEju19IgaHudalcfabD7yhDGeA6bcQnmL+CpveLJq/3hvfwd1aof6L386Ougkx6RfyMIQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"ansi-escapes": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.3.2",
"resolved": "https://registry.npmjs.org/ansi-escapes/-/ansi-escapes-4.3.2.tgz",
"integrity": "sha512-gKXj5ALrKWQLsYG9jlTRmR/xKluxHV+Z9QEwNIgCfM1/uwPMCuzVVnh5mwTd+OuBZcwSIMbqssNWRm1lE51QaQ==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"type-fest": "^0.21.3"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"type-fest": {
"version": "0.21.3",
"resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.21.3.tgz",
"integrity": "sha512-t0rzBq87m3fVcduHDUFhKmyyX+9eo6WQjZvf51Ea/M0Q7+T374Jp1aUiyUl0GKxp8M/OETVHSDvmkyPgvX+X2w==",
"dev": true
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"ansi-regex": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"ansi-styles": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz",
"integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"color-convert": "^2.0.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"anymatch": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "3.1.3",
"resolved": "https://registry.npmjs.org/anymatch/-/anymatch-3.1.3.tgz",
"integrity": "sha512-KMReFUr0B4t+D+OBkjR3KYqvocp2XaSzO55UcB6mgQMd3KbcE+mWTyvVV7D/zsdEbNnV6acZUutkiHQXvTr1Rw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"normalize-path": "^3.0.0",
"picomatch": "^2.0.4"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"argparse": {
Bump to eslint 8 https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0
2021-11-01 19:47:46 +00:00
"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
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"array-union": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/array-union/-/array-union-2.1.0.tgz",
"integrity": "sha512-HGyxoOTYUyCM6stUe6EJgnd4EoewAI7zMdfqO+kGjnlZmBDz/cR5pf8r/cR4Wq60sL/p0IkcjUEEPwS3GFrIyw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"asar": {
Relock deps to get gitcloud 0.2.4 with "fetch" log fix https://github.com/nativefier/gitcloud-client/pull/4
2022-07-30 17:27:39 +00:00
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/asar/-/asar-3.2.0.tgz",
"integrity": "sha512-COdw2ZQvKdFGFxXwX3oYh2/sOsJWJegrdJCGxnN4MZ7IULgRBp9P6665aqj9z1v9VwP4oP1hRBojRDQ//IGgAg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
"@types/glob": "^7.1.1",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"chromium-pickle-js": "^0.2.0",
"commander": "^5.0.0",
"glob": "^7.1.6",
"minimatch": "^3.0.4"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"async": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.5.2",
"resolved": "https://registry.npmjs.org/async/-/async-1.5.2.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-nSVgobk4rv61R9PUSDtYt7mPVB2olxNR5RWJcAsH676/ef11bUZwvu7+RGYrYauVdDPcO519v68wRhXQtxsV9w=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"asynckit": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.4.0",
"resolved": "https://registry.npmjs.org/asynckit/-/asynckit-0.4.0.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-Oei9OH4tRh0YqU3GxhX79dM/mwVgvbZJaSNaRk+bshkj0S5cfHcgYakreBjrHwatXKbz+IoIdYLxrKim2MjW0Q=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"at-least-node": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/at-least-node/-/at-least-node-1.0.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-+q/t7Ekv1EDY2l6Gda6LLiX14rU9TV20Wa3ofeQmwPFZbOMo9DXrLbOjFaaclkXKWidIaopwAObQDqwWtGUjqg=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"author-regex": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/author-regex/-/author-regex-1.0.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-KbWgR8wOYRAPekEmMXrYYdc7BRyhn2Ftk7KWfMUnQ43hFdojWEFRxhhRUm3/OFEdPa1r0KAvTTg9YQK57xTe0g=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"axios": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "1.3.4",
"resolved": "https://registry.npmjs.org/axios/-/axios-1.3.4.tgz",
"integrity": "sha512-toYm+Bsyl6VC5wSkfkbbNB6ROv7KY93PEBBL6xyDczaIHasAiv4wPqQ/c4RjoQzipxRD2W5g21cOqQulZ7rHwQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump axios from 0.x to 1.x. No breaking changes for us, https://github.com/axios/axios/blob/v1.x/CHANGELOG.md#100---2022-10-04
2022-11-07 23:12:12 +00:00
"follow-redirects": "^1.15.0",
"form-data": "^4.0.0",
"proxy-from-env": "^1.1.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"babel-jest": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/babel-jest/-/babel-jest-28.1.3.tgz",
"integrity": "sha512-epUaPOEWMk3cWX0M/sPvCHHCe9fMFAa/9hXEgKP8nFfNl/jlGkE9ucq9NqkZGXLDduCJYS0UvSlPUwC0S+rH6Q==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/transform": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/babel__core": "^7.1.14",
Bump default Electron from 16.0.5 to 16.0.6 https://github.com/electron/electron/releases/tag/v16.0.6
2022-01-06 14:43:10 +00:00
"babel-plugin-istanbul": "^6.1.1",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"babel-preset-jest": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"chalk": "^4.0.0",
Relock dependencies
2022-02-06 22:47:06 +00:00
"graceful-fs": "^4.2.9",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"slash": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"babel-plugin-istanbul": {
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"version": "6.1.1",
"resolved": "https://registry.npmjs.org/babel-plugin-istanbul/-/babel-plugin-istanbul-6.1.1.tgz",
"integrity": "sha512-Y1IQok9821cC9onCx5otgFfRm7Lm+I+wwxOx738M/WLPZ9Q42m4IG5W0FNX8WLL2gYMZo3JkuXIH2DOpWM+qwA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/helper-plugin-utils": "^7.0.0",
"@istanbuljs/load-nyc-config": "^1.0.0",
"@istanbuljs/schema": "^0.1.2",
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"istanbul-lib-instrument": "^5.0.4",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"test-exclude": "^6.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"babel-plugin-jest-hoist": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/babel-plugin-jest-hoist/-/babel-plugin-jest-hoist-28.1.3.tgz",
"integrity": "sha512-Ys3tUKAmfnkRUpPdpa98eYrAR0nV+sSFUZZEGuQ2EbFd1y4SOLtD5QDNHAq+bb9a+bbXvYQC4b+ID/THIMcU6Q==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/template": "^7.3.3",
"@babel/types": "^7.3.3",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@types/babel__core": "^7.1.14",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/babel__traverse": "^7.0.6"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"babel-preset-current-node-syntax": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/babel-preset-current-node-syntax/-/babel-preset-current-node-syntax-1.0.1.tgz",
"integrity": "sha512-M7LQ0bxarkxQoN+vz5aJPsLBn77n8QgTFmo8WK0/44auK2xlCXrYcUxHFxgU7qW5Yzw/CjmLRK2uJzaCd7LvqQ==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/plugin-syntax-async-generators": "^7.8.4",
"@babel/plugin-syntax-bigint": "^7.8.3",
"@babel/plugin-syntax-class-properties": "^7.8.3",
"@babel/plugin-syntax-import-meta": "^7.8.3",
"@babel/plugin-syntax-json-strings": "^7.8.3",
"@babel/plugin-syntax-logical-assignment-operators": "^7.8.3",
"@babel/plugin-syntax-nullish-coalescing-operator": "^7.8.3",
"@babel/plugin-syntax-numeric-separator": "^7.8.3",
"@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-top-level-await": "^7.8.3"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"babel-preset-jest": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/babel-preset-jest/-/babel-preset-jest-28.1.3.tgz",
"integrity": "sha512-L+fupJvlWAHbQfn74coNX3zf60LXMJsezNvvx8eIh7iOR1luJ1poxYgQk1F8PYtNq/6QODDHCqsSnTFSWC491A==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"babel-plugin-jest-hoist": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"babel-preset-current-node-syntax": "^1.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"balanced-match": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-1.0.2.tgz",
"integrity": "sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw=="
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"base64-js": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.5.1",
"resolved": "https://registry.npmjs.org/base64-js/-/base64-js-1.5.1.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-AKpaYlHn8t4SVbOHCy+b5+KKgvR4vrsD8vbvrbiQJps7fKDTkjkDry6ji0rUJjC0kzbNePLwzxq8iypo41qeWA=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"bluebird": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.7.2",
"resolved": "https://registry.npmjs.org/bluebird/-/bluebird-3.7.2.tgz",
"integrity": "sha512-XpNj6GDQzdfW+r2Wnn7xiSAd7TM3jzkxGXBGTtWKuSXv1xUV+azxAm8jdWZN06QTQk+2N2XB9jRDkvbmQmcRtg=="
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"boolbase": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/boolbase/-/boolbase-1.0.0.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-JZOSA7Mo9sNGB8+UjSgzdLtokWAky1zbztM3WRLCbZ70/3cTANmQmOdR7y2g+J0e2WXywy1yS468tY+IruqEww=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"boolean": {
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-03-21 03:32:19 +00:00
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/boolean/-/boolean-3.2.0.tgz",
"integrity": "sha512-d0II/GO9uf9lfUHH2BQsjxzRJZBdsjgsBiW4BvhWk/3qoKwQFjIDVN19PfX8F2D/r9PCMTtLWjYVCFrpeYUzsw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"optional": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"brace-expansion": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.1.11",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz",
"integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"braces": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/braces/-/braces-3.0.2.tgz",
"integrity": "sha512-b8um+L1RzM3WDSzvhm6gIz1yfTbBt6YTlcEKAvsmqCZZFw46z626lVj9j1yEPW33H5H+lBQpZMP1k8l+78Ha0A==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"fill-range": "^7.0.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"browserslist": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "4.21.5",
"resolved": "https://registry.npmjs.org/browserslist/-/browserslist-4.21.5.tgz",
"integrity": "sha512-tUkiguQGW7S3IhB7N+c2MV/HZPSCPAAiYBZXLsBhFB/PCy6ZKKsZrmBayHV9fdGV/ARIfJ14NkxKzRDjvp7L6w==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"caniuse-lite": "^1.0.30001449",
"electron-to-chromium": "^1.4.284",
"node-releases": "^2.0.8",
"update-browserslist-db": "^1.0.10"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"bser": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/bser/-/bser-2.1.1.tgz",
"integrity": "sha512-gQxTNE/GAfIIrmHLUE3oJyp5FO6HRBfhjnw4/wMmA63ZGDJnWBmgY/lyQBpnDUkGmAhbSe39tx2d/iTOAfglwQ==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"node-int64": "^0.4.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"buffer-alloc": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/buffer-alloc/-/buffer-alloc-1.2.0.tgz",
"integrity": "sha512-CFsHQgjtW1UChdXgbyJGtnm+O/uLQeZdtbDo8mfUgYXCHSM1wgrVxXm6bSyrUuErEb+4sYVGCzASBRot7zyrow==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"buffer-alloc-unsafe": "^1.1.0",
"buffer-fill": "^1.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"buffer-alloc-unsafe": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/buffer-alloc-unsafe/-/buffer-alloc-unsafe-1.1.0.tgz",
"integrity": "sha512-TEM2iMIEQdJ2yjPJoSIsldnleVaAk1oW3DBVUykyOLsEsFmEc9kn+SFFPz+gl54KQNxlDnAwCXosOS9Okx2xAg=="
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"buffer-crc32": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.2.13",
"resolved": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.13.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-VO9Ht/+p3SN7SKWqcrgEzjGbRSJYTx+Q1pTQC0wrWqHx0vpJraQ6GtHx8tvcg1rlK1byhU5gccxgOgj7B0TDkQ=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"buffer-equal": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/buffer-equal/-/buffer-equal-1.0.1.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-QoV3ptgEaQpvVwbXdSO39iqPQTCxSF7A5U99AxbHYqUdCizL/lH2Z0A2y6nbZucxMEOtNyZfG2s6gsVugGpKkg=="
macOS: universal architecture app support (fix #1384, PR #1386) As noted in `API.md`: - When specifying `universal` you must be building for the `darwin`, `mas`, `mac`, or `osx` platforms. This will generate a universal (M1 and x86) app.
2022-04-18 23:11:31 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"buffer-fill": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/buffer-fill/-/buffer-fill-1.0.0.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-T7zexNBwiiaCOGDg9xNX9PBmjrubblRkENuptryuI64URkXDFum9il/JGL8Lm8wYfAXpredVXXZz7eMHilimiQ=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"buffer-from": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/buffer-from/-/buffer-from-1.1.2.tgz",
"integrity": "sha512-E+XQCRwSbaaiChtv6k6Dwgc+bx+Bs6vuKJHHl5kox/BaKbhiXzqQOwK4cO22yElGp2OCmjwVhT3HmxgyPGnJfQ=="
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"cacheable-request": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "6.1.0",
"resolved": "https://registry.npmjs.org/cacheable-request/-/cacheable-request-6.1.0.tgz",
"integrity": "sha512-Oj3cAGPCqOZX7Rz64Uny2GYAZNliQSqfbePrgAQ1wKAihYmCUnraBtJtKcGR4xz7wF+LoJC+ssFZvv5BgF9Igg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"clone-response": "^1.0.2",
"get-stream": "^5.1.0",
"http-cache-semantics": "^4.0.0",
"keyv": "^3.0.0",
"lowercase-keys": "^2.0.0",
"normalize-url": "^4.1.0",
"responselike": "^1.0.2"
},
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"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==",
"requires": {
"pump": "^3.0.0"
}
},
"lowercase-keys": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/lowercase-keys/-/lowercase-keys-2.0.0.tgz",
"integrity": "sha512-tqNXrS78oMOE73NMxK4EMLQsQowWf8jKooH9g7xPavRT706R6bkQJ6DY2Te7QukaZsulxa30wQ7bk0pm4XiHmA=="
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"callsites": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/callsites/-/callsites-3.1.0.tgz",
"integrity": "sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"camelcase": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "5.3.1",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-5.3.1.tgz",
"integrity": "sha512-L28STB170nwWS63UjtlEOE3dldQApaJXZkOI1uMFfzf3rRuPegHaHesyee+YxQ+W6SvRDQV6UrdOdRiR153wJg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"caniuse-lite": {
"version": "1.0.30001470",
"resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001470.tgz",
"integrity": "sha512-065uNwY6QtHCBOExzbV6m236DDhYCCtPmQUCoQtwkVqzud8v5QPidoMr6CoMkC2nfp6nksjttqWQRRh75LqUmA==",
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"chalk": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.1.2",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz",
"integrity": "sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"ansi-styles": "^4.1.0",
"supports-color": "^7.1.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"char-regex": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/char-regex/-/char-regex-1.0.2.tgz",
"integrity": "sha512-kWWXztvZ5SBQV+eRgKFeh8q5sLuZY2+8WUIzlxWVTg+oGwY14qylx1KbKzHd8P6ZYkAg0xyIDU9JMHhyJMZ1jw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"cheerio": {
Relock dependencies
2022-06-27 19:49:33 +00:00
"version": "1.0.0-rc.12",
"resolved": "https://registry.npmjs.org/cheerio/-/cheerio-1.0.0-rc.12.tgz",
"integrity": "sha512-VqR8m68vM46BNnuZ5NtnGBKIE/DfN0cRIzg9n40EIq9NOv90ayxLBXA8fXC5gquFRGJSTRqBq25Jt2ECLR431Q==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"cheerio-select": "^2.1.0",
"dom-serializer": "^2.0.0",
"domhandler": "^5.0.3",
"domutils": "^3.0.1",
"htmlparser2": "^8.0.1",
"parse5": "^7.0.0",
Relock dependencies
2022-06-27 19:49:33 +00:00
"parse5-htmlparser2-tree-adapter": "^7.0.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"cheerio-select": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/cheerio-select/-/cheerio-select-2.1.0.tgz",
"integrity": "sha512-9v9kG0LvzrlcungtnJtpGNxY+fzECQKhK4EGJX2vByejiMX84MFNQw4UxPJl3bFbTMw+Dfs37XaIkCwTZfLh4g==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"boolbase": "^1.0.0",
"css-select": "^5.1.0",
"css-what": "^6.1.0",
"domelementtype": "^2.3.0",
"domhandler": "^5.0.3",
"domutils": "^3.0.1"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"chrome-trace-event": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"chromium-pickle-js": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.2.0",
"resolved": "https://registry.npmjs.org/chromium-pickle-js/-/chromium-pickle-js-0.2.0.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-1R5Fho+jBq0DDydt+/vHWj5KJNJCKdARKOCwZUen84I5BreWoLqRLANH1U87eJy1tiASPtMnGqJJq0ZsLoRPOw=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"ci-info": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "3.8.0",
"resolved": "https://registry.npmjs.org/ci-info/-/ci-info-3.8.0.tgz",
"integrity": "sha512-eXTggHWSooYhq49F2opQhuHWgzucfF2YgODK4e1566GQs5BIfP30B0oenwBJHfWxAs2fyPB1s7Mg949zLf61Yw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"cjs-module-lexer": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.2.2",
"resolved": "https://registry.npmjs.org/cjs-module-lexer/-/cjs-module-lexer-1.2.2.tgz",
"integrity": "sha512-cOU9usZw8/dXIXKtwa8pM0OTJQuJkxMN6w30csNRUerHfeQ5R6U3kkU/FtJeIf3M202OHfY2U8ccInBG7/xogA==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"cliui": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "8.0.1",
"resolved": "https://registry.npmjs.org/cliui/-/cliui-8.0.1.tgz",
"integrity": "sha512-BSeNnyus75C4//NQ9gQt1/csTXyo/8Sb+afLAkzAptFuMsod9HFokGNudZpi/oQV73hnVK+sR+5PVRMd+Dr7YQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"string-width": "^4.2.0",
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"strip-ansi": "^6.0.1",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"wrap-ansi": "^7.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"clone-deep": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/clone-deep/-/clone-deep-4.0.1.tgz",
"integrity": "sha512-neHB9xuzh/wk0dIHweyAXv2aPGZIVk3pLMe+/RNzINf17fe0OG96QroktYAUm7SM1PBnzTabaLboqqxDyMU+SQ==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"is-plain-object": "^2.0.4",
"kind-of": "^6.0.2",
"shallow-clone": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"clone-response": {
relock cli
2022-07-23 22:39:04 +00:00
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/clone-response/-/clone-response-1.0.3.tgz",
"integrity": "sha512-ROoL94jJH2dUVML2Y/5PEDNaSHgeOdSDicUyS7izcF63G6sTc/FTjLub4b8Il9S8S0beOfYt0TaA5qvFK+w0wA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"mimic-response": "^1.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"co": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.6.0",
"resolved": "https://registry.npmjs.org/co/-/co-4.6.0.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-QVb0dM5HvG+uaxitm8wONl7jltx8dqhfU33DcqtOZcLSVIKSDDLDi7+0LbAKiyI8hD9u42m2YxXSkMGWThaecQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"collect-v8-coverage": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/collect-v8-coverage/-/collect-v8-coverage-1.0.1.tgz",
"integrity": "sha512-iBPtljfCNcTKNAto0KEtDfZ3qzjJvqE3aTGZsbhjSBlorqpXJlaWWtPO35D+ZImoC3KWejX64o+yPGxhWSTzfg==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"color-convert": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz",
"integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"color-name": "~1.1.4"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"color-name": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz",
"integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA=="
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"colorette": {
Relock dependencies
2022-06-27 19:49:33 +00:00
"version": "2.0.19",
"resolved": "https://registry.npmjs.org/colorette/-/colorette-2.0.19.tgz",
"integrity": "sha512-3tlv/dIP7FWvj3BsbHrGLJ6l/oKh1O3TcgBqMn+yyCagOxc23fyzDS6HypQbgxWbkpDnf52p1LuR4eWDQ/K9WQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"combined-stream": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.8",
"resolved": "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.8.tgz",
"integrity": "sha512-FQN4MRfuJeHf7cBbBMJFXhKSDq+2kAArBlmRBvcvFE5BB1HZKXtSFASDhdlz9zOYwxh8lDdnvmMOe/+5cdoEdg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"delayed-stream": "~1.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"commander": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/commander/-/commander-5.1.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-P0CysNDQ7rtVw4QIQtm+MRxV66vKFSvlsQvGYXZWR3qFU0jlMKHZZZgw8e+8DSah4UDKMqnknRDQz+xuQXQ/Zg=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"compare-version": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.1.2",
"resolved": "https://registry.npmjs.org/compare-version/-/compare-version-0.1.2.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-pJDh5/4wrEnXX/VWRZvruAGHkzKdr46z11OlTPN+VrATlWWhSKewNCJ1futCO5C7eJB3nPMFZA1LeYtcFboZ2A=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"concat-map": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.0.1",
"resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"concat-stream": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"version": "1.6.2",
"resolved": "https://registry.npmjs.org/concat-stream/-/concat-stream-1.6.2.tgz",
"integrity": "sha512-27HBghJxjiZtIk3Ycvn/4kbJk/1uZuJFfuPEns6LaEvpvG1f0hTea8lilrouyo9mVc2GWdcEZ8OLoGmSADlrCw==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"buffer-from": "^1.0.0",
"inherits": "^2.0.3",
"readable-stream": "^2.2.2",
"typedarray": "^0.0.6"
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
},
"dependencies": {
"readable-stream": {
"version": "2.3.8",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.8.tgz",
"integrity": "sha512-8p0AUk4XODgIewSi0l8Epjs+EVnWiK7NoDIEGU0HhE7+ZyY8D1IMY7odu5lRrFXGg71L15KG8QrPmum45RTtdA==",
"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"
}
},
"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
},
"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"
}
}
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"config-chain": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.1.13",
"resolved": "https://registry.npmjs.org/config-chain/-/config-chain-1.1.13.tgz",
"integrity": "sha512-qj+f8APARXHrM0hraqXYb2/bOVSV4PvJQlNZ/DVj0QrmNM2q2euizkeuVckQ57J+W0mRH6Hvi+k50M4Jul2VRQ==",
"optional": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"ini": "^1.3.4",
"proto-list": "~1.2.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"convert-source-map": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "1.9.0",
"resolved": "https://registry.npmjs.org/convert-source-map/-/convert-source-map-1.9.0.tgz",
"integrity": "sha512-ASFBup0Mz1uyiIjANan1jzLQami9z1PoYSZCiiYW2FczPbenXc45FZdBZLzOT+r6+iciuEModtmCti+hjaAk0A==",
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"core-util-is": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.3.tgz",
"integrity": "sha512-ZQBvi1DcpJ4GDqanjucZ2Hj3wEO5pZDS89BWbkcrvdxksJorwUDDZamX9ldFkp9aw2lmBDLgkObEA4DWNJ9FYQ==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"cross-spawn": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "7.0.3",
"resolved": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.3.tgz",
"integrity": "sha512-iRDPJKUPVEND7dHPO8rkbOnPpyDygcDFtWjpeWNCgy8WP2rXcxXL8TskReQl6OrB2G7+UJrags1q15Fudc7G6w==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"path-key": "^3.1.0",
"shebang-command": "^2.0.0",
"which": "^2.0.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"cross-spawn-windows-exe": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/cross-spawn-windows-exe/-/cross-spawn-windows-exe-1.2.0.tgz",
"integrity": "sha512-mkLtJJcYbDCxEG7Js6eUnUNndWjyUZwJ3H7bErmmtOYU/Zb99DyUkpamuIZE0b3bhmJyZ7D90uS6f+CGxRRjOw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@malept/cross-spawn-promise": "^1.1.0",
"is-wsl": "^2.2.0",
"which": "^2.0.2"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"css-select": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/css-select/-/css-select-5.1.0.tgz",
"integrity": "sha512-nwoRF1rvRRnnCqqY7updORDsuqKzqYJ28+oSMaJMMgOauh3fvwHqMS7EZpIPqK8GL+g9mKxF1vP/ZjSeNjEVHg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"boolbase": "^1.0.0",
Relock dependencies
2022-05-30 13:42:40 +00:00
"css-what": "^6.1.0",
"domhandler": "^5.0.2",
"domutils": "^3.0.1",
Upgrade Electron from 13 to 16 (PR #1288) https://www.electronjs.org/docs/latest/breaking-changes Co-authored-by: Ronan Jouchet <ronan@jouchet.fr>
2022-01-02 11:17:06 +00:00
"nth-check": "^2.0.1"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"css-what": {
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-04-10 15:18:41 +00:00
"version": "6.1.0",
"resolved": "https://registry.npmjs.org/css-what/-/css-what-6.1.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-HTUrgRJ7r4dsZKU6GjmpfRK1O76h97Z8MfS1G0FozR+oF2kG6Vfe8JE6zwrkbxigziPHinCJ+gCPjA9EaBDtRw=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"debug": {
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-03-21 03:32:19 +00:00
"version": "4.3.4",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.4.tgz",
"integrity": "sha512-PRWFHuSU3eDtQJPvnNY7Jcket1j0t5OuOsFzPPzsekD52Zl8qUfFIPEiswXqIvHWGVHOgX+7G/vCNNhehwxfkQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"ms": "2.1.2"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"decompress-response": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/decompress-response/-/decompress-response-3.3.0.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-BzRPQuY1ip+qDonAOz42gRm/pg9F768C+npV/4JOsxRC2sq+Rlk+Q4ZCAsOhnIaMrgarILY+RMUIvMmmX1qAEA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"mimic-response": "^1.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dedent": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.7.0",
"resolved": "https://registry.npmjs.org/dedent/-/dedent-0.7.0.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-Q6fKUPqnAHAyhiUgFU7BUzLiv0kd8saH9al7tnu5Q/okj6dnupxyTgFIBjVzJATdfIAm9NAsvXNzjaKa+bxVyA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"deep-is": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.1.4",
"resolved": "https://registry.npmjs.org/deep-is/-/deep-is-0.1.4.tgz",
"integrity": "sha512-oIPzksmTg4/MriiaYGO+okXDT7ztn/w3Eptv/+gSIdMdKsJo0u4CfYNFJPy+4SKMuCqGw2wxnA+URMg3t8a/bQ==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"deepmerge": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "4.3.1",
"resolved": "https://registry.npmjs.org/deepmerge/-/deepmerge-4.3.1.tgz",
"integrity": "sha512-3sUqbMEc77XqpdNO7FRyRog+eW3ph+GYCbj+rK+uYyRMuwsVy0rMiVtPn+QJlKFvWP/1PYpapqYn0Me2knFn+A==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"defer-to-connect": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/defer-to-connect/-/defer-to-connect-1.1.3.tgz",
"integrity": "sha512-0ISdNousHvZT2EiFlZeZAHBUvSxmKswVCEf8hW7KWgG4a8MVEu/3Vb6uWYozkjylyCxe0JBIiRB1jV45S70WVQ=="
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"define-properties": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.2.0.tgz",
"integrity": "sha512-xvqAVKGfT1+UAvPwKTVw/njhdQ8ZhXK4lI0bCIuCMrp2up9nPnaDftrLtmpTazqd1o+UY4zgzU+avtMbDP+ldA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"optional": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"has-property-descriptors": "^1.0.0",
"object-keys": "^1.1.1"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"delayed-stream": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-ZySD7Nf91aLB0RxL4KGrKHBXl7Eds1DAmEdcoVawXnLD7SDhpNgtuII2aAkg7a7QS41jxPSZ17p4VdGnMHk3MQ=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"detect-newline": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/detect-newline/-/detect-newline-3.1.0.tgz",
"integrity": "sha512-TLz+x/vEXm/Y7P7wn1EJFNLxYpUD4TgMosxY6fAVJUnJMbupHBOncxyWUG9OpTaH9EBD7uFI5LfEgmMOc54DsA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"detect-node": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/detect-node/-/detect-node-2.1.0.tgz",
"integrity": "sha512-T0NIuQpnTvFDATNuHN5roPwSBG83rFsuO+MXXH9/3N1eFbn4wcPjttvjMLEPWJ0RGUYgQE7cGgS3tNxbqCGM7g==",
"optional": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"diff-sequences": {
bump jest **types**, so far it still builds
2022-07-23 22:43:04 +00:00
"version": "28.1.1",
"resolved": "https://registry.npmjs.org/diff-sequences/-/diff-sequences-28.1.1.tgz",
"integrity": "sha512-FU0iFaH/E23a+a718l8Qa/19bF9p06kgE0KipMOMadwa3SjnaElKzPaUC0vnibs6/B/9ni97s61mcejk8W1fQw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dir-compare": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/dir-compare/-/dir-compare-3.3.0.tgz",
"integrity": "sha512-J7/et3WlGUCxjdnD3HAAzQ6nsnc0WL6DD7WcwJb7c39iH1+AWfg+9OqzJNaI6PkBwBvm1mhZNL9iY/nRiZXlPg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"buffer-equal": "^1.0.0",
"minimatch": "^3.0.4"
macOS: universal architecture app support (fix #1384, PR #1386) As noted in `API.md`: - When specifying `universal` you must be building for the `darwin`, `mas`, `mac`, or `osx` platforms. This will generate a universal (M1 and x86) app.
2022-04-18 23:11:31 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dir-glob": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/dir-glob/-/dir-glob-3.0.1.tgz",
"integrity": "sha512-WkrWp9GR4KXfKGYzOLmTuGVi1UWFfws377n9cc55/tb6DuqyF6pcQ5AbiHEshaDpY9v6oaSr2XCDidGmMwdzIA==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"path-type": "^4.0.0"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"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
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"doctrine": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/doctrine/-/doctrine-3.0.0.tgz",
"integrity": "sha512-yS+Q5i3hBf7GBkd4KG8a7eBNNWNGLTaEwwYWUijIYM7zrlYDM0BFXHjjPWlWZ1Rg7UaddZeIDmi9jF3HmqiQ2w==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"esutils": "^2.0.2"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dom-serializer": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/dom-serializer/-/dom-serializer-2.0.0.tgz",
"integrity": "sha512-wIkAryiqt/nV5EQKqQpo3SToSOV9J0DnbJqwK7Wv/Trc92zIAYZ4FlMu+JPFW1DfGFt81ZTCGgDEabffXeLyJg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"domelementtype": "^2.3.0",
"domhandler": "^5.0.2",
"entities": "^4.2.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"domelementtype": {
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-04-10 15:18:41 +00:00
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-2.3.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-OLETBj6w0OsagBwdXnPdN0cnMfF9opN69co+7ZrbfPGrdpPVNBUj02spi6B1N7wChLQiPn4CSH/zJvXw56gmHw=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"domhandler": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"version": "5.0.3",
"resolved": "https://registry.npmjs.org/domhandler/-/domhandler-5.0.3.tgz",
"integrity": "sha512-cgwlv/1iFQiFnU96XXgROh8xTeetsnJiDsTc7TYCLFd9+/WNkIqPTxiM/8pSd8VIrhXGTf1Ny1q1hquVqDJB5w==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"domelementtype": "^2.3.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"domutils": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/domutils/-/domutils-3.0.1.tgz",
"integrity": "sha512-z08c1l761iKhDFtfXO04C7kTdPBLi41zwOZl00WS8b5eiaebNpY00HKbztwBq+e3vyqWNwWF3mP9YLUeqIrF+Q==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"dom-serializer": "^2.0.0",
"domelementtype": "^2.3.0",
"domhandler": "^5.0.1"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"duplexer3": {
relock cli
2022-07-23 22:39:04 +00:00
"version": "0.1.5",
"resolved": "https://registry.npmjs.org/duplexer3/-/duplexer3-0.1.5.tgz",
"integrity": "sha512-1A8za6ws41LQgv9HrE/66jyC5yuSjQ3L/KOpFtoBilsAK2iA2wuS5rTt1OCzIvtS2V7nVmedsUU+DGRcjBmOYA=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"electron": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "19.1.9",
"resolved": "https://registry.npmjs.org/electron/-/electron-19.1.9.tgz",
"integrity": "sha512-XT5LkTzIHB+ZtD3dTmNnKjVBWrDWReCKt9G1uAFLz6uJMEVcIUiYO+fph5pLXETiBw/QZBx8egduMEfIccLx+g==",
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Major-bump default Electron from 18 to 19 (#1438) https://github.com/electron/electron/releases/tag/v19.0.0 https://github.com/electron/electron/releases/tag/v19.0.1 https://github.com/electron/electron/releases/tag/v19.0.2 https://github.com/electron/electron/releases/tag/v19.0.3 https://github.com/electron/electron/releases/tag/v19.0.4 https://github.com/electron/electron/releases/tag/v19.0.5 https://github.com/electron/electron/releases/tag/v19.0.6 https://github.com/electron/electron/releases/tag/v19.0.7 https://github.com/electron/electron/releases/tag/v19.0.8 https://github.com/electron/electron/releases/tag/v19.0.9
2022-07-24 15:56:07 +00:00
"@electron/get": "^1.14.1",
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"@types/node": "^16.11.26",
"extract-zip": "^1.0.3"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"@types/node": {
"version": "16.18.21",
"resolved": "https://registry.npmjs.org/@types/node/-/node-16.18.21.tgz",
"integrity": "sha512-TassPGd0AEZWA10qcNnXnSNwHlLfSth8XwUaWc3gTSDmBz/rKb613Qw5qRf6o2fdRBrLbsgeC9PMZshobkuUqg==",
"dev": true
},
"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"
}
},
"extract-zip": {
"version": "1.7.0",
"resolved": "https://registry.npmjs.org/extract-zip/-/extract-zip-1.7.0.tgz",
"integrity": "sha512-xoh5G1W/PB0/27lXgMQyIhP5DSY/LhoCsOyZgb+6iMmRtCwVBo55uKaMoEYrDCKQhWvqEip5ZPKAc6eFNyf/MA==",
"dev": true,
"requires": {
"concat-stream": "^1.6.2",
"debug": "^2.6.9",
"mkdirp": "^0.5.4",
"yauzl": "^2.10.0"
}
},
"ms": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.0.0.tgz",
"integrity": "sha512-Tpp60P6IUJDTuOq/5Z8cdskzJujfwqfOTkrwIwj7IRISpnkJnT6SyJ4PCPnGMoFjC9ddhal5KVIYtAt97ix05A==",
"dev": true
}
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"electron-notarize": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "1.2.2",
"resolved": "https://registry.npmjs.org/electron-notarize/-/electron-notarize-1.2.2.tgz",
"integrity": "sha512-ZStVWYcWI7g87/PgjPJSIIhwQXOaw4/XeXU+pWqMMktSLHaGMLHdyPPN7Cmao7+Cr7fYufA16npdtMndYciHNw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"debug": "^4.1.1",
"fs-extra": "^9.0.1"
},
Fix upgrade not working (#1286) * Attempt to get upgrade working right; in progress * Got it fixed in Mac * Fix some linting errors * Finish fixing upgrade + tests * Integration testing for global shortcuts * Regenerate shrinkwrap * Get rid of deprecated rmdirSync * Remove instead of rm for 12.x support * Make dereferencing platform dependent * Fix folder copy funkiness * Whoops * Whoops 2: Extra Whoops * Update Electron to 13.5.1; Fix auth manual tests * Rework relock * Add a request for help. * Update @types/node to 14
2021-11-29 17:01:20 +00:00
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fs-extra": {
"version": "9.1.0",
"resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-9.1.0.tgz",
"integrity": "sha512-hcg3ZmepS30/7BSFqRvoo3DOMQu7IjqxO5nCDt+zM9XWjb33Wg7ziNT+Qvqbuc3+gWpzO02JubVyk2G4Zvo1OQ==",
"requires": {
"at-least-node": "^1.0.0",
"graceful-fs": "^4.2.0",
"jsonfile": "^6.0.1",
"universalify": "^2.0.0"
}
},
"jsonfile": {
"version": "6.1.0",
"resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-6.1.0.tgz",
"integrity": "sha512-5dgndWOriYSm5cnYaJNhalLNDKOqFwyDB/rr1E9ZsGciGvKPs8R2xYGCacuf3z6K1YKDz182fd+fY3cn3pMqXQ==",
"requires": {
"graceful-fs": "^4.1.6",
"universalify": "^2.0.0"
}
},
"universalify": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/universalify/-/universalify-2.0.0.tgz",
"integrity": "sha512-hAZsKq7Yy11Zu1DE0OzWjw7nnLZmJZYTDZZyEFHZdUhV8FkH5MCfoU1XMaxXovpyW5nq5scPqq0ZDP9Zyl04oQ=="
}
Fix upgrade not working (#1286) * Attempt to get upgrade working right; in progress * Got it fixed in Mac * Fix some linting errors * Finish fixing upgrade + tests * Integration testing for global shortcuts * Regenerate shrinkwrap * Get rid of deprecated rmdirSync * Remove instead of rm for 12.x support * Make dereferencing platform dependent * Fix folder copy funkiness * Whoops * Whoops 2: Extra Whoops * Update Electron to 13.5.1; Fix auth manual tests * Rework relock * Add a request for help. * Update @types/node to 14
2021-11-29 17:01:20 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"electron-osx-sign": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.5.0",
"resolved": "https://registry.npmjs.org/electron-osx-sign/-/electron-osx-sign-0.5.0.tgz",
"integrity": "sha512-icoRLHzFz/qxzDh/N4Pi2z4yVHurlsCAYQvsCSG7fCedJ4UJXBS6PoQyGH71IfcqKupcKeK7HX/NkyfG+v6vlQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"bluebird": "^3.5.0",
"compare-version": "^0.1.2",
"debug": "^2.6.8",
"isbinaryfile": "^3.0.2",
"minimist": "^1.2.0",
"plist": "^3.0.1"
},
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"debug": {
"version": "2.6.9",
"resolved": "https://registry.npmjs.org/debug/-/debug-2.6.9.tgz",
"integrity": "sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==",
"requires": {
"ms": "2.0.0"
}
},
"ms": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.0.0.tgz",
"integrity": "sha512-Tpp60P6IUJDTuOq/5Z8cdskzJujfwqfOTkrwIwj7IRISpnkJnT6SyJ4PCPnGMoFjC9ddhal5KVIYtAt97ix05A=="
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"electron-packager": {
relock cli
2022-08-29 00:41:15 +00:00
"version": "15.5.2",
"resolved": "https://registry.npmjs.org/electron-packager/-/electron-packager-15.5.2.tgz",
"integrity": "sha512-8zUdkSONn0jomu/efqoxApGzgqIb56ooMs671HeB/BXTPnWcWvqpEY08g16PL6ok2ymA5zPj8vmUszLrq99F0Q==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@electron/get": "^1.6.0",
Relock dependencies
2022-05-02 03:22:57 +00:00
"@electron/universal": "^1.2.1",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"asar": "^3.1.0",
"cross-spawn-windows-exe": "^1.2.0",
"debug": "^4.0.1",
"electron-notarize": "^1.1.1",
"electron-osx-sign": "^0.5.0",
"extract-zip": "^2.0.0",
"filenamify": "^4.1.0",
relock cli
2022-08-29 00:41:15 +00:00
"fs-extra": "^10.1.0",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"galactus": "^0.2.1",
"get-package-info": "^1.0.0",
"junk": "^3.1.0",
"parse-author": "^2.0.0",
"plist": "^3.0.0",
"rcedit": "^3.0.1",
"resolve": "^1.1.6",
"semver": "^7.1.3",
relock cli
2022-08-29 00:41:15 +00:00
"yargs-parser": "^20.2.9"
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"electron-to-chromium": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "1.4.340",
"resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.4.340.tgz",
"integrity": "sha512-zx8hqumOqltKsv/MF50yvdAlPF9S/4PXbyfzJS6ZGhbddGkRegdwImmfSVqCkEziYzrIGZ/TlrzBND4FysfkDg==",
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"emittery": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "0.10.2",
"resolved": "https://registry.npmjs.org/emittery/-/emittery-0.10.2.tgz",
"integrity": "sha512-aITqOwnLanpHLNXZJENbOgjUBeHocD+xsSJmNrjovKBW5HbSpW3d1pEls7GFQPUWXiwG9+0P4GtHfEqC/4M0Iw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"emoji-regex": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "8.0.0",
"resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-8.0.0.tgz",
"integrity": "sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A=="
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"encodeurl": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/encodeurl/-/encodeurl-1.0.2.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-TPJXq8JqFaVYm2CWmPvnP2Iyo4ZSM7/QKcSmuMLDObfpH5fi7RUGmd/rTDf+rut/saiDiQEeVTNgAmJEdAOx0w==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"optional": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"end-of-stream": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.4.4",
"resolved": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.4.4.tgz",
"integrity": "sha512-+uw1inIHVPQoaVuHzRyXd21icM+cnt4CzD5rW+NC1wjOUSTOs+Te7FOv7AhN7vS9x/oIyhLP5PR1H+phQAHu5Q==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"once": "^1.4.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"enhanced-resolve": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "5.12.0",
"resolved": "https://registry.npmjs.org/enhanced-resolve/-/enhanced-resolve-5.12.0.tgz",
"integrity": "sha512-QHTXI/sZQmko1cbDoNAa3mJ5qhWUUNAq3vR0/YiD379fWQrcfuoX1+HW2S0MTt7XmoPLapdaDKUtelUSPic7hQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"graceful-fs": "^4.2.4",
"tapable": "^2.2.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"entities": {
relock cli
2022-09-18 02:30:33 +00:00
"version": "4.4.0",
"resolved": "https://registry.npmjs.org/entities/-/entities-4.4.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-oYp7156SP8LkeGD0GF85ad1X9Ai79WtRsZ2gxJqtBuzH+98YUV6jkHEKlZkMbcrjJjIVJNIDP/3WL9wQkoPbWA=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"env-paths": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.2.1",
"resolved": "https://registry.npmjs.org/env-paths/-/env-paths-2.2.1.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-+h1lkLKhZMTYjog1VEpJNG7NZJWcuc2DDk/qsqSTRRCOXiLjeQ1d1/udrUGhqMxUgAlwKNZ0cf2uqan5GLuS2A=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"envinfo": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "7.8.1",
"resolved": "https://registry.npmjs.org/envinfo/-/envinfo-7.8.1.tgz",
"integrity": "sha512-/o+BXHmB7ocbHEAs6F2EnG0ogybVVUdkRunTT2glZU9XAaGmhqskrvKwqXuDfNjEO0LZKWdejEEpnq8aM0tOaw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"error-ex": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.3.2",
"resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.3.2.tgz",
"integrity": "sha512-7dFHNmqeFSEt2ZBsCriorKnn3Z2pj+fd9kmI6QoWw4//DL+icEBfc0U7qJCisqrTsKTjw4fNFy2pW9OqStD84g==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"is-arrayish": "^0.2.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"es-module-lexer": {
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"version": "0.9.3",
"resolved": "https://registry.npmjs.org/es-module-lexer/-/es-module-lexer-0.9.3.tgz",
"integrity": "sha512-1HQ2M2sPtxwnvOvT1ZClHyQDiggdNjURWpY2we6aMKCQiUVxTmVs2UYPLIrD84sS+kMdUwfBSylbJPwNnBrnHQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"es6-error": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.1.1",
"resolved": "https://registry.npmjs.org/es6-error/-/es6-error-4.1.1.tgz",
"integrity": "sha512-Um/+FxMr9CISWh0bi5Zv0iOD+4cFh5qLeks1qhAopKVAJw3drgKbKySikp7wGhDL0HPeaja0P5ULZrxLkniUVg==",
"optional": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"escalade": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/escalade/-/escalade-3.1.1.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-k0er2gUkLf8O0zKJiAhmkTnJlTvINGv7ygDNPbeIsX/TJjGJZHuh9B2UxbsaEkmlEo9MfhrSzmhIlhRlI2GXnw=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"escape-string-regexp": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-4.0.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"eslint": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "8.36.0",
"resolved": "https://registry.npmjs.org/eslint/-/eslint-8.36.0.tgz",
"integrity": "sha512-Y956lmS7vDqomxlaaQAHVmeb4tNMp2FWIvU/RnU5BD3IKMD/MJPr76xdyr68P8tV1iNMvN2mRK0yy3c+UjL+bw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@eslint-community/eslint-utils": "^4.2.0",
"@eslint-community/regexpp": "^4.4.0",
"@eslint/eslintrc": "^2.0.1",
"@eslint/js": "8.36.0",
"@humanwhocodes/config-array": "^0.11.8",
relock cli
2022-08-29 00:41:15 +00:00
"@humanwhocodes/module-importer": "^1.0.1",
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"@nodelib/fs.walk": "^1.2.8",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"ajv": "^6.10.0",
"chalk": "^4.0.0",
"cross-spawn": "^7.0.2",
Bump to eslint 8 https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0
2021-11-01 19:47:46 +00:00
"debug": "^4.3.2",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"doctrine": "^3.0.0",
"escape-string-regexp": "^4.0.0",
Upgrade dependencies Including axios 0.25 -> 0.25, nothing breaking for us: https://github.com/axios/axios/releases/tag/v0.26.0
2022-02-15 04:01:36 +00:00
"eslint-scope": "^7.1.1",
"eslint-visitor-keys": "^3.3.0",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"espree": "^9.5.0",
"esquery": "^1.4.2",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"esutils": "^2.0.2",
"fast-deep-equal": "^3.1.3",
"file-entry-cache": "^6.0.1",
macOS: Move handling of "universal" apps to electron-packager instead of our own thing (#1443) Supported since [electron-packager 15.5.0](https://github.com/electron/electron-packager/releases/tag/v15.5.0). This should fix #1405 as well
2022-08-02 02:44:23 +00:00
"find-up": "^5.0.0",
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"glob-parent": "^6.0.2",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"globals": "^13.19.0",
macOS: Move handling of "universal" apps to electron-packager instead of our own thing (#1443) Supported since [electron-packager 15.5.0](https://github.com/electron/electron-packager/releases/tag/v15.5.0). This should fix #1405 as well
2022-08-02 02:44:23 +00:00
"grapheme-splitter": "^1.0.4",
Relock dependencies
2022-02-06 22:47:06 +00:00
"ignore": "^5.2.0",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"import-fresh": "^3.0.0",
"imurmurhash": "^0.1.4",
"is-glob": "^4.0.0",
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"is-path-inside": "^3.0.3",
relock cli
2022-09-18 02:30:33 +00:00
"js-sdsl": "^4.1.4",
Bump to eslint 8 https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0
2021-11-01 19:47:46 +00:00
"js-yaml": "^4.1.0",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"json-stable-stringify-without-jsonify": "^1.0.1",
"levn": "^0.4.1",
"lodash.merge": "^4.6.2",
Relock dependencies
2022-05-30 13:42:40 +00:00
"minimatch": "^3.1.2",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"natural-compare": "^1.4.0",
"optionator": "^0.9.1",
Relock dependencies
2021-11-22 21:03:07 +00:00
"strip-ansi": "^6.0.1",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"strip-json-comments": "^3.1.0",
relock cli
2022-08-29 00:41:15 +00:00
"text-table": "^0.2.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"eslint-scope": {
"version": "7.1.1",
"resolved": "https://registry.npmjs.org/eslint-scope/-/eslint-scope-7.1.1.tgz",
"integrity": "sha512-QKQM/UXpIiHcLqJ5AOyIW7XZmzjkzQXYE54n1++wb0u9V/abW3l9uQnxX8Z5Xd18xyKIMTUAyQ0k1e8pz6LUrw==",
"dev": true,
"requires": {
"esrecurse": "^4.3.0",
"estraverse": "^5.2.0"
}
},
"estraverse": {
"version": "5.3.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz",
"integrity": "sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==",
"dev": true
},
"find-up": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-5.0.0.tgz",
"integrity": "sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==",
"dev": true,
"requires": {
"locate-path": "^6.0.0",
"path-exists": "^4.0.0"
}
},
"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,
"requires": {
"is-glob": "^4.0.3"
}
},
"locate-path": {
"version": "6.0.0",
"resolved": "https://registry.npmjs.org/locate-path/-/locate-path-6.0.0.tgz",
"integrity": "sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==",
"dev": true,
"requires": {
"p-locate": "^5.0.0"
}
},
"p-limit": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/p-limit/-/p-limit-3.1.0.tgz",
"integrity": "sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==",
"dev": true,
"requires": {
"yocto-queue": "^0.1.0"
}
},
"p-locate": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/p-locate/-/p-locate-5.0.0.tgz",
"integrity": "sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==",
"dev": true,
"requires": {
"p-limit": "^3.0.2"
}
},
"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
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"eslint-config-prettier": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "8.8.0",
"resolved": "https://registry.npmjs.org/eslint-config-prettier/-/eslint-config-prettier-8.8.0.tgz",
"integrity": "sha512-wLbQiFre3tdGgpDv67NQKnJuTlcUVYHas3k+DZCc2U2BadthoEY4B7hLPvAxaqdyOGCzuLfii2fqGph10va7oA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"eslint-plugin-prettier": {
relock cli
2022-07-23 22:39:04 +00:00
"version": "4.2.1",
"resolved": "https://registry.npmjs.org/eslint-plugin-prettier/-/eslint-plugin-prettier-4.2.1.tgz",
"integrity": "sha512-f/0rXLXUt0oFYs8ra4w49wYZBG5GKZpAYsJSm6rnYL5uVDjd+zowwMwVZHnAjf4edNrKpCDYfXDgmRE/Ak7QyQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"prettier-linter-helpers": "^1.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"eslint-scope": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"esrecurse": "^4.3.0",
"estraverse": "^4.1.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"eslint-visitor-keys": {
Upgrade dependencies Including axios 0.25 -> 0.25, nothing breaking for us: https://github.com/axios/axios/releases/tag/v0.26.0
2022-02-15 04:01:36 +00: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==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"espree": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "9.5.0",
"resolved": "https://registry.npmjs.org/espree/-/espree-9.5.0.tgz",
"integrity": "sha512-JPbJGhKc47++oo4JkEoTe2wjy4fmMwvFpgJT9cQzmfXKp22Dr6Hf1tdCteLz1h0P3t+mGvWZ+4Uankvh8+c6zw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
macOS: Move handling of "universal" apps to electron-packager instead of our own thing (#1443) Supported since [electron-packager 15.5.0](https://github.com/electron/electron-packager/releases/tag/v15.5.0). This should fix #1405 as well
2022-08-02 02:44:23 +00:00
"acorn": "^8.8.0",
Relock dependencies
2022-05-30 13:42:40 +00:00
"acorn-jsx": "^5.3.2",
Upgrade dependencies Including axios 0.25 -> 0.25, nothing breaking for us: https://github.com/axios/axios/releases/tag/v0.26.0
2022-02-15 04:01:36 +00:00
"eslint-visitor-keys": "^3.3.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"esprima": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/esprima/-/esprima-4.0.1.tgz",
"integrity": "sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"esquery": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "1.5.0",
"resolved": "https://registry.npmjs.org/esquery/-/esquery-1.5.0.tgz",
"integrity": "sha512-YQLXUplAwJgCydQ78IMJywZCceoqk1oH01OERdSAJc/7U2AylwjhSCLDEtqwg811idIS/9fIU5GjG73IgjKMVg==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"estraverse": "^5.1.0"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"estraverse": {
"version": "5.3.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz",
"integrity": "sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==",
"dev": true
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"esrecurse": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"estraverse": "^5.2.0"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"estraverse": {
"version": "5.3.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz",
"integrity": "sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==",
"dev": true
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"estraverse": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-4.3.0.tgz",
"integrity": "sha512-39nnKffWz8xN1BU/2c79n9nB9HDzo0niYUqx6xyqUnyoAnQyyWpOTdZEeiCch8BBu515t4wp9ZmgVfVhn9EBpw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"esutils": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/esutils/-/esutils-2.0.3.tgz",
"integrity": "sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"events": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/events/-/events-3.3.0.tgz",
"integrity": "sha512-mQw+2fkQbALzQ7V0MY0IqdnXNOeTtP4r0lN9z7AAawCXgqea7bDii20AYrIBrFd/Hx0M2Ocz6S111CaFkUcb0Q==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"execa": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "5.1.1",
"resolved": "https://registry.npmjs.org/execa/-/execa-5.1.1.tgz",
"integrity": "sha512-8uSpZZocAZRBAPIEINJj3Lo9HyGitllczc27Eh5YYojjMFMn8yHMDMaUHE2Jqfq05D/wucwI4JGURyXt1vchyg==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"cross-spawn": "^7.0.3",
"get-stream": "^6.0.0",
"human-signals": "^2.1.0",
"is-stream": "^2.0.0",
"merge-stream": "^2.0.0",
"npm-run-path": "^4.0.1",
"onetime": "^5.1.2",
"signal-exit": "^3.0.3",
"strip-final-newline": "^2.0.0"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"get-stream": {
"version": "6.0.1",
"resolved": "https://registry.npmjs.org/get-stream/-/get-stream-6.0.1.tgz",
"integrity": "sha512-ts6Wi+2j3jQjqi70w5AlN8DFnkSwC+MqmxEzdEALB2qXZYV3X/b1CTfgPLGJNMeAWxdPfU8FO1ms3NUfaHCPYg==",
"dev": true
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"exit": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.1.2",
"resolved": "https://registry.npmjs.org/exit/-/exit-0.1.2.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-Zk/eNKV2zbjpKzrsQ+n1G6poVbErQxJ0LBOJXaKZ1EViLzH+hrLu9cdXI4zw9dBQJslwBEpbQ2P1oS7nDxs6jQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"expect": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/expect/-/expect-28.1.3.tgz",
"integrity": "sha512-eEh0xn8HlsuOBxFgIss+2mX85VAS4Qy3OSkjV7rlBWljtA4oWH37glVGyOZSZvErDT/yBywZdPGwCXuTvSG85g==",
Revert "nit" and "bump jest and fix yargs typing" This reverts commit b737c40931d14eb803353b3afa8b48cb583c3b6e. This reverts commit 8eb05ded9b8b4e39749580ed71b8721fcaffd779.
2022-07-23 23:20:24 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/expect-utils": "^28.1.3",
"jest-get-type": "^28.0.2",
"jest-matcher-utils": "^28.1.3",
"jest-message-util": "^28.1.3",
"jest-util": "^28.1.3"
bump jest **types**, so far it still builds
2022-07-23 22:43:04 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"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==",
"requires": {
"@types/yauzl": "^2.9.1",
"debug": "^4.1.1",
"get-stream": "^5.1.0",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"yauzl": "^2.10.0"
},
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"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==",
"requires": {
"pump": "^3.0.0"
}
}
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fast-deep-equal": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fast-diff": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/fast-diff/-/fast-diff-1.2.0.tgz",
"integrity": "sha512-xJuoT5+L99XlZ8twedaRf6Ax2TgQVxvgZOYoPKqZufmJib0tL2tegPBOZb1pVNgIhlqDlA0eO0c3wBvQcmzx4w==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fast-glob": {
relock cli
2022-09-18 02:30:33 +00:00
"version": "3.2.12",
"resolved": "https://registry.npmjs.org/fast-glob/-/fast-glob-3.2.12.tgz",
"integrity": "sha512-DVj4CQIYYow0BlaelwK1pHl5n5cRSJfM60UA0zK891sVInoPri2Ekj7+e1CT3/3qxXenpI+nBBmQAcJPJgaj4w==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@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"
Bump to eslint 8 https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0
2021-11-01 19:47:46 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fast-json-stable-stringify": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fast-levenshtein": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.6",
"resolved": "https://registry.npmjs.org/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-DCXu6Ifhqcks7TZKY3Hxp3y6qphY5SJZmrWMDrKcERSOXWQdMhU9Ig/PYrzyw/ul9jOIyh0N4M0tbC5hodg8dw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fastest-levenshtein": {
relock cli
2022-08-29 00:41:15 +00:00
"version": "1.0.16",
"resolved": "https://registry.npmjs.org/fastest-levenshtein/-/fastest-levenshtein-1.0.16.tgz",
"integrity": "sha512-eRnCtTTtGZFpQCwhJiUOuxPQWRXVKYDn0b2PeHfXL6/Zi53SLAzAHfVhVWK2AryC/WH05kGfxhFIPvTF0SXQzg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fastq": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "1.15.0",
"resolved": "https://registry.npmjs.org/fastq/-/fastq-1.15.0.tgz",
"integrity": "sha512-wBrocU2LCXXa+lWBt8RoIRD89Fi8OdABODa/kEnyeyjS5aZO5/GNvI5sEINADqP/h8M29UHTHUb53sUu5Ihqdw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"reusify": "^1.0.4"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fb-watchman": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/fb-watchman/-/fb-watchman-2.0.2.tgz",
"integrity": "sha512-p5161BqbuCaSnB8jIbzQHOlpgsPmK5rJVDfDKO91Axs5NC1uu3HRQm6wt9cd9/+GtQQIO53JdGXXoyDpTAsgYA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"bser": "2.1.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fd-slicer": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/fd-slicer/-/fd-slicer-1.1.0.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-cE1qsB/VwyQozZ+q1dGxR8LBYNZeofhEdUNGSMbQD3Gw2lAzX9Zb3uIU6Ebc/Fmyjo9AWWfnn0AUCHqtevs/8g==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"pend": "~1.2.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"file-entry-cache": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"flat-cache": "^3.0.4"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"file-type": {
relock cli
2022-07-23 22:39:04 +00:00
"version": "16.5.4",
"resolved": "https://registry.npmjs.org/file-type/-/file-type-16.5.4.tgz",
"integrity": "sha512-/yFHK0aGjFEgDJjEKP0pWCplsPFPhwyfwevf/pVxiN0tmE4L9LmwWxWukdJSHdoCli4VgQLehjJtwQBnqmsKcw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"readable-web-to-node-stream": "^3.0.0",
"strtok3": "^6.2.4",
"token-types": "^4.1.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"filename-reserved-regex": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/filename-reserved-regex/-/filename-reserved-regex-2.0.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-lc1bnsSr4L4Bdif8Xb/qrtokGbq5zlsms/CYH8PP+WtCkGNF65DPiQY8vG3SakEdRn8Dlnm+gW/qWKKjS5sZzQ=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"filenamify": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/filenamify/-/filenamify-4.3.0.tgz",
"integrity": "sha512-hcFKyUG57yWGAzu1CMt/dPzYZuv+jAJUT85bL8mrXvNe6hWj6yEHEc4EdcgiA6Z3oi1/9wXJdZPXF2dZNgwgOg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"filename-reserved-regex": "^2.0.0",
"strip-outer": "^1.0.1",
"trim-repeated": "^1.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fill-range": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"to-regex-range": "^5.0.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"find-up": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-2.1.0.tgz",
"integrity": "sha512-NWzkk0jSJtTt08+FBFMvXoeZnOJD+jTtsRmBYbAIzJdX6l7dLgR7CTubCM5/eDdPUBvLCeVasP1brfVR/9/EZQ==",
"requires": {
"locate-path": "^2.0.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"flat-cache": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.4",
"resolved": "https://registry.npmjs.org/flat-cache/-/flat-cache-3.0.4.tgz",
"integrity": "sha512-dm9s5Pw7Jc0GvMYbshN6zchCA9RgQlzzEZX3vylR9IqFfS8XciblUXOKfW6SiuJ0e13eDYZoZV5wdrev7P3Nwg==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"flatted": "^3.1.0",
"rimraf": "^3.0.2"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"flatted": {
relock cli
2022-08-29 00:41:15 +00:00
"version": "3.2.7",
"resolved": "https://registry.npmjs.org/flatted/-/flatted-3.2.7.tgz",
"integrity": "sha512-5nqDSxl8nn5BSNxyR3n4I6eDmbolI6WT+QqR547RwxQapgjQBmtktdP+HTBb/a/zLsbzERTONyUB5pefh5TtjQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"flora-colossus": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/flora-colossus/-/flora-colossus-1.0.1.tgz",
"integrity": "sha512-d+9na7t9FyH8gBJoNDSi28mE4NgQVGGvxQ4aHtFRetjyh5SXjuus+V5EZaxFmFdXVemSOrx0lsgEl/ZMjnOWJA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"debug": "^4.1.1",
"fs-extra": "^7.0.0"
},
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fs-extra": {
"version": "7.0.1",
"resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-7.0.1.tgz",
"integrity": "sha512-YJDaCJZEnBmcbw13fvdAM9AwNOJwOzrE4pqMqBq5nFiEqXUqHwlK4B+3pUw6JNvfSPtX05xFHtYy/1ni01eGCw==",
"requires": {
"graceful-fs": "^4.1.2",
"jsonfile": "^4.0.0",
"universalify": "^0.1.0"
}
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"follow-redirects": {
relock cli
2022-09-18 02:30:33 +00:00
"version": "1.15.2",
"resolved": "https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.15.2.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-VQLG33o04KaQ8uYi2tVNbdrWp1QWxNNea+nmIB4EVM28v0hmP17z7aG1+wAkNzVq4KeXTq3221ye5qTJP91JwA=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"form-data": {
Major bump axios to 0.27.x No breaking changes for us: https://github.com/axios/axios/blob/master/CHANGELOG.md
2022-05-02 03:24:57 +00:00
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/form-data/-/form-data-4.0.0.tgz",
"integrity": "sha512-ETEklSGi5t0QMZuiXoA/Q6vcnxcLQP5vdugSpuAyi6SVGi2clPPp+xgEhuMaHC+zGgn31Kd235W35f7Hykkaww==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"asynckit": "^0.4.0",
"combined-stream": "^1.0.8",
"mime-types": "^2.1.12"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fs-extra": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"version": "10.1.0",
"resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-10.1.0.tgz",
"integrity": "sha512-oRXApq54ETRj4eMiFzGnHWGy+zo5raudjuxN0b8H7s/RU2oW0Wvsx9O0ACRN/kRq9E8Vu/ReskGB5o3ji+FzHQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"graceful-fs": "^4.2.0",
"jsonfile": "^6.0.1",
"universalify": "^2.0.0"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"jsonfile": {
"version": "6.1.0",
"resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-6.1.0.tgz",
"integrity": "sha512-5dgndWOriYSm5cnYaJNhalLNDKOqFwyDB/rr1E9ZsGciGvKPs8R2xYGCacuf3z6K1YKDz182fd+fY3cn3pMqXQ==",
"requires": {
"graceful-fs": "^4.1.6",
"universalify": "^2.0.0"
}
},
"universalify": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/universalify/-/universalify-2.0.0.tgz",
"integrity": "sha512-hAZsKq7Yy11Zu1DE0OzWjw7nnLZmJZYTDZZyEFHZdUhV8FkH5MCfoU1XMaxXovpyW5nq5scPqq0ZDP9Zyl04oQ=="
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fs.realpath": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/fs.realpath/-/fs.realpath-1.0.0.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fsevents": {
Work around "npm shrinkwrap" failing to include some packages in lockfile
2021-09-25 03:01:11 +00:00
"version": "2.3.2",
"resolved": "https://registry.npmjs.org/fsevents/-/fsevents-2.3.2.tgz",
"integrity": "sha512-xiqMQR4xAeHTuB9uWm+fFRcIOgKBMiOBP+eXiyT7jsgVCq1bkVygt00oASowB7EdtpOHaaPgKt812P9ab+DDKA==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"optional": true
Work around "npm shrinkwrap" failing to include some packages in lockfile
2021-09-25 03:01:11 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"function-bind": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/function-bind/-/function-bind-1.1.1.tgz",
"integrity": "sha512-yIovAzMX49sF8Yl58fSCWJ5svSLuaibPxXQJFLmBObTuCr0Mf1KiPopGM9NiFjiYBCbfaa2Fh6breQ6ANVTI0A=="
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"galactus": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.2.1",
"resolved": "https://registry.npmjs.org/galactus/-/galactus-0.2.1.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-mDc8EQJKtxjp9PMYS3PbpjjbX3oXhBTxoGaPahw620XZBIHJ4+nvw5KN/tRtmmSDR9dypstGNvqQ3C29QGoGHQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"debug": "^3.1.0",
"flora-colossus": "^1.0.0",
"fs-extra": "^4.0.0"
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
},
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"debug": {
"version": "3.2.7",
"resolved": "https://registry.npmjs.org/debug/-/debug-3.2.7.tgz",
"integrity": "sha512-CFjzYYAi4ThfiQvizrFQevTTXHtnCqWfe7x1AhgEscTz6ZbLbfoLRLPugTQyBth6f8ZERVUSyWHFD/7Wu4t1XQ==",
"requires": {
"ms": "^2.1.1"
}
},
"fs-extra": {
"version": "4.0.3",
"resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-4.0.3.tgz",
"integrity": "sha512-q6rbdDd1o2mAnQreO7YADIxf/Whx4AHBiRf6d+/cVT8h44ss+lHgxf1FemcqDnQt9X3ct4McHr+JMGlYSsK7Cg==",
"requires": {
"graceful-fs": "^4.1.2",
"jsonfile": "^4.0.0",
"universalify": "^0.1.0"
}
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"gensync": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"get-caller-file": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/get-caller-file/-/get-caller-file-2.0.5.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"get-intrinsic": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/get-intrinsic/-/get-intrinsic-1.2.0.tgz",
"integrity": "sha512-L049y6nFOuom5wGyRc3/gdTLO94dySVKRACj1RmJZBQXlbTMhtNIgkWkUHq+jYmZvKf14EW1EoJnnjbmoHij0Q==",
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"optional": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"function-bind": "^1.1.1",
"has": "^1.0.3",
Relock dependencies
2022-06-27 19:49:33 +00:00
"has-symbols": "^1.0.3"
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"get-package-info": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/get-package-info/-/get-package-info-1.0.0.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-SCbprXGAPdIhKAXiG+Mk6yeoFH61JlYunqdFQFHDtLjJlDjFf6x07dsS8acO+xWt52jpdVo49AlVDnUVK1sDNw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"bluebird": "^3.1.1",
"debug": "^2.2.0",
"lodash.get": "^4.0.0",
"read-pkg-up": "^2.0.0"
},
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"debug": {
"version": "2.6.9",
"resolved": "https://registry.npmjs.org/debug/-/debug-2.6.9.tgz",
"integrity": "sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==",
"requires": {
"ms": "2.0.0"
}
},
"ms": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.0.0.tgz",
"integrity": "sha512-Tpp60P6IUJDTuOq/5Z8cdskzJujfwqfOTkrwIwj7IRISpnkJnT6SyJ4PCPnGMoFjC9ddhal5KVIYtAt97ix05A=="
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"get-package-type": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.1.0",
"resolved": "https://registry.npmjs.org/get-package-type/-/get-package-type-0.1.0.tgz",
"integrity": "sha512-pjzuKtY64GYfWizNAJ0fr9VqttZkNiK2iS430LtIHzjBEr6bX8Am2zm4sW4Ro5wjWW5cAlRL1qAMTcXbjNAO2Q==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"get-stream": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/get-stream/-/get-stream-4.1.0.tgz",
"integrity": "sha512-GMat4EJ5161kIy2HevLlr4luNjBgvmj413KaQA7jt4V8B4RDsfpHk7WQ9GVqfYyyx8OS/L66Kox+rJRNklLK7w==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"pump": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"gitcloud": {
Relock deps to get gitcloud 0.2.4 with "fetch" log fix https://github.com/nativefier/gitcloud-client/pull/4
2022-07-30 17:27:39 +00:00
"version": "0.2.4",
"resolved": "https://registry.npmjs.org/gitcloud/-/gitcloud-0.2.4.tgz",
"integrity": "sha512-xtO+GTv6c/XqnGqajRpv1aoTk3wFQPdQKjHP8cRZFxsCIQvYCTvgwqFGNv0+ux9HVREW10H5EIHN1Kw0r3PKMQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock deps to get gitcloud 0.2.4 with "fetch" log fix https://github.com/nativefier/gitcloud-client/pull/4
2022-07-30 17:27:39 +00:00
"axios": "^0.27.2",
"cheerio": "^1.0.0-rc.12"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Bump axios from 0.x to 1.x. No breaking changes for us, https://github.com/axios/axios/blob/v1.x/CHANGELOG.md#100---2022-10-04
2022-11-07 23:12:12 +00:00
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"axios": {
"version": "0.27.2",
"resolved": "https://registry.npmjs.org/axios/-/axios-0.27.2.tgz",
"integrity": "sha512-t+yRIyySRTp/wua5xEr+z1q60QmLq8ABsS5O9Me1AsE5dfKqgnCFzwiCZZ/cGNd1lq4/7akDWMxdhVlucjmnOQ==",
"requires": {
"follow-redirects": "^1.14.9",
"form-data": "^4.0.0"
}
}
Bump axios from 0.x to 1.x. No breaking changes for us, https://github.com/axios/axios/blob/v1.x/CHANGELOG.md#100---2022-10-04
2022-11-07 23:12:12 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"glob": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"version": "7.2.3",
"resolved": "https://registry.npmjs.org/glob/-/glob-7.2.3.tgz",
"integrity": "sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
Relock dependencies
2022-05-30 13:42:40 +00:00
"minimatch": "^3.1.1",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"once": "^1.3.0",
"path-is-absolute": "^1.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"glob-parent": {
"version": "5.1.2",
"resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz",
"integrity": "sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
"is-glob": "^4.0.1"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"glob-to-regexp": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"global-agent": {
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/global-agent/-/global-agent-3.0.0.tgz",
"integrity": "sha512-PT6XReJ+D07JvGoxQMkT6qji/jVNfX/h364XHZOWeRzy64sSFr+xJ5OX7LI3b4MPQzdL4H8Y8M0xzPpsVMwA8Q==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"optional": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"boolean": "^3.0.1",
"es6-error": "^4.1.1",
"matcher": "^3.0.0",
"roarr": "^2.15.3",
"semver": "^7.3.2",
"serialize-error": "^7.0.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"global-tunnel-ng": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.7.1",
"resolved": "https://registry.npmjs.org/global-tunnel-ng/-/global-tunnel-ng-2.7.1.tgz",
"integrity": "sha512-4s+DyciWBV0eK148wqXxcmVAbFVPqtc3sEtUE/GTQfuU80rySLcMhUmHKSHI7/LDj8q0gDYI1lIhRRB7ieRAqg==",
"optional": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"encodeurl": "^1.0.2",
"lodash": "^4.17.10",
"npm-conf": "^1.1.3",
"tunnel": "^0.0.6"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"globals": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "13.20.0",
"resolved": "https://registry.npmjs.org/globals/-/globals-13.20.0.tgz",
"integrity": "sha512-Qg5QtVkCy/kv3FUSlu4ukeZDVf9ee0iXLAUYX13gbR17bnejFTzr4iS9bY7kwCf1NztRNm1t91fjOiyx4CSwPQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"type-fest": "^0.20.2"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"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
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"globalthis": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/globalthis/-/globalthis-1.0.3.tgz",
"integrity": "sha512-sFdI5LyBiNTHjRd7cGPWapiHWMOXKyuBNX/cWJ3NfzrZQVa8GI/8cofCl74AOVqq9W5kNmguTIzJ/1s2gyI9wA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"optional": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"define-properties": "^1.1.3"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"globby": {
Relock dependencies
2022-02-06 22:47:06 +00:00
"version": "11.1.0",
"resolved": "https://registry.npmjs.org/globby/-/globby-11.1.0.tgz",
"integrity": "sha512-jhIXaOzy1sb8IyocaruWSn1TjmnBVs8Ayhcy83rmxNJ8q2uWKCAj3CnJY+KpGSXCueAPc0i05kVvVKtP1t9S3g==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"array-union": "^2.1.0",
"dir-glob": "^3.0.1",
Relock dependencies
2022-02-06 22:47:06 +00:00
"fast-glob": "^3.2.9",
"ignore": "^5.2.0",
"merge2": "^1.4.1",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"slash": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"got": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "9.6.0",
"resolved": "https://registry.npmjs.org/got/-/got-9.6.0.tgz",
"integrity": "sha512-R7eWptXuGYxwijs0eV+v3o6+XH1IqVK8dJOEecQfTmkncw9AV4dcw/Dhxi8MdlqPthxxpZyizMzyg8RTmEsG+Q==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@sindresorhus/is": "^0.14.0",
"@szmarczak/http-timer": "^1.1.2",
"cacheable-request": "^6.0.0",
"decompress-response": "^3.3.0",
"duplexer3": "^0.1.4",
"get-stream": "^4.1.0",
"lowercase-keys": "^1.0.1",
"mimic-response": "^1.0.1",
"p-cancelable": "^1.0.0",
"to-readable-stream": "^1.0.0",
"url-parse-lax": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"graceful-fs": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "4.2.11",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.11.tgz",
"integrity": "sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ=="
macOS: universal architecture app support (fix #1384, PR #1386) As noted in `API.md`: - When specifying `universal` you must be building for the `darwin`, `mas`, `mac`, or `osx` platforms. This will generate a universal (M1 and x86) app.
2022-04-18 23:11:31 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"grapheme-splitter": {
macOS: Move handling of "universal" apps to electron-packager instead of our own thing (#1443) Supported since [electron-packager 15.5.0](https://github.com/electron/electron-packager/releases/tag/v15.5.0). This should fix #1405 as well
2022-08-02 02:44:23 +00:00
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/grapheme-splitter/-/grapheme-splitter-1.0.4.tgz",
"integrity": "sha512-bzh50DW9kTPM00T8y4o8vQg89Di9oLJVLW/KaOGIXJWP/iqCN6WKYkbNOF04vFLJhwcpYUh9ydh/+5vpOqV4YQ==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"has": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/has/-/has-1.0.3.tgz",
"integrity": "sha512-f2dvO0VU6Oej7RkWJGrehjbzMAjFp5/VKPp5tTpWIV4JHHZK1/BxbFRtf/siA2SWTe09caDmVtYYzWEIbBS4zw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"function-bind": "^1.1.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"has-flag": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz",
"integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"has-property-descriptors": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/has-property-descriptors/-/has-property-descriptors-1.0.0.tgz",
"integrity": "sha512-62DVLZGoiEBDHQyqG4w9xCuZ7eJEwNmJRWw2VY84Oedb7WFcA27fiEVe8oUQx9hAUJ4ekurquucTGwsyO1XGdQ==",
"optional": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"get-intrinsic": "^1.1.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"has-symbols": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.3.tgz",
"integrity": "sha512-l3LCuF6MgDNwTDKkdYGEihYjt5pRPbEg46rtlmnSPlUbgmB8LOIrKJbYYFBSbnPaJexMKtiPO8hmeRjRz2Td+A==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"optional": true
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"hasbin": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.2.3",
"resolved": "https://registry.npmjs.org/hasbin/-/hasbin-1.2.3.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-CCd8e/w2w28G8DyZvKgiHnQJ/5XXDz6qiUHnthvtag/6T5acUeN5lqq+HMoBqcmgWueWDhiCplrw0Kb1zDACRg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"async": "~1.5"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"hosted-git-info": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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=="
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"html-escaper": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/html-escaper/-/html-escaper-2.0.2.tgz",
"integrity": "sha512-H2iMtd0I4Mt5eYiapRdIDjp+XzelXQ0tFE4JS7YFwFevXXMmOp9myNrUvCg0D6ws8iqkRPBfKHgbwig1SmlLfg==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"htmlparser2": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "8.0.2",
"resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-8.0.2.tgz",
"integrity": "sha512-GYdjWKDkbRLkZ5geuHs5NY1puJ+PXwP7+fHPRz06Eirsb9ugf6d8kkXav6ADhcODhFFPMIXyxkxSuMf3D6NCFA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"domelementtype": "^2.3.0",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"domhandler": "^5.0.3",
Relock dependencies
2022-05-30 13:42:40 +00:00
"domutils": "^3.0.1",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"entities": "^4.4.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"http-cache-semantics": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "4.1.1",
"resolved": "https://registry.npmjs.org/http-cache-semantics/-/http-cache-semantics-4.1.1.tgz",
"integrity": "sha512-er295DKPVsV82j5kw1Gjt+ADA/XYHsajl82cGNQG2eyoPkvgUhX+nDIyelzhIWbbsXP39EHcI6l5tYs2FYqYXQ=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"human-signals": {
Revert "nit" and "bump jest and fix yargs typing" This reverts commit b737c40931d14eb803353b3afa8b48cb583c3b6e. This reverts commit 8eb05ded9b8b4e39749580ed71b8721fcaffd779.
2022-07-23 23:20:24 +00:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/human-signals/-/human-signals-2.1.0.tgz",
"integrity": "sha512-B4FFZ6q/T2jhhksgkbEW3HBvWIfDW85snkQgawt07S7J5QXTk6BkNV+0yAeZrM5QpMAdYlocGoljn0sJ/WQkFw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"ieee754": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/ieee754/-/ieee754-1.2.1.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-dcyqhDvX1C46lXZcVqCpK+FtMRQVdIMN6/Df5js2zouUsqG7I6sFxitIC+7KYK29KdXOLHdu9zL4sFnoVQnqaA=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"ignore": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "5.2.4",
"resolved": "https://registry.npmjs.org/ignore/-/ignore-5.2.4.tgz",
"integrity": "sha512-MAb38BcSbH0eHNBxn7ql2NH/kX33OkB3lZ1BNdh7ENeRChHTYsTvWrMubiIAMNS2llXEEgZ1MUOBtXChP3kaFQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"import-fresh": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/import-fresh/-/import-fresh-3.3.0.tgz",
"integrity": "sha512-veYYhQa+D1QBKznvhUHxb8faxlrwUnxseDAbAp457E0wLNio2bOSKnjYDhMj+YiAq61xrMGhQk9iXVk5FzgQMw==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"parent-module": "^1.0.0",
"resolve-from": "^4.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"import-local": {
Bump default Electron from 16.0.5 to 16.0.6 https://github.com/electron/electron/releases/tag/v16.0.6
2022-01-06 14:43:10 +00:00
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/import-local/-/import-local-3.1.0.tgz",
"integrity": "sha512-ASB07uLtnDs1o6EHjKpX34BKYDSqnFerfTOJL2HvMqF70LnxpjkzDB8J44oT9pu4AMPkQwf8jl6szgvNd2tRIg==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"pkg-dir": "^4.2.0",
"resolve-cwd": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"imurmurhash": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.1.4",
"resolved": "https://registry.npmjs.org/imurmurhash/-/imurmurhash-0.1.4.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-JmXMZ6wuvDmLiHEml9ykzqO6lwFbof0GG4IkcGaENdCRDDmMVnny7s5HsIgHCbaq0w2MyPhDqkhTUgS2LU2PHA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"inflight": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.6",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.6.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-k92I/b08q4wvFscXCLvqfsHCrjrF7yiXsQuIVvVE7N82W3+aqpzuUdBbfhWcy/FZR3/4IgflMgKLOsvPDrGCJA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"once": "^1.3.0",
"wrappy": "1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"inherits": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.4.tgz",
"integrity": "sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ=="
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"ini": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.3.8",
"resolved": "https://registry.npmjs.org/ini/-/ini-1.3.8.tgz",
"integrity": "sha512-JV/yugV2uzW5iMRSiZAyDtQd+nxtUnjeLt0acNdw98kKLrvuRVyB80tsREOE7yvGVgalhZ6RNXCmEHkUKBKxew==",
"optional": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"interpret": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/interpret/-/interpret-2.2.0.tgz",
"integrity": "sha512-Ju0Bz/cEia55xDwUWEa8+olFpCiQoypjnQySseKtmjNrnps3P+xfpUmGr90T7yjlVJmOtybRvPXhKMbHr+fWnw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"is-arrayish": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.2.1",
"resolved": "https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.2.1.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-zz06S8t0ozoDXMG+ube26zeCTNXcKIPJZJi8hBrF4idCLms4CG9QtK7qBl1boi5ODzFpjswb5JPmHCbMpjaYzg=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"is-core-module": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "2.11.0",
"resolved": "https://registry.npmjs.org/is-core-module/-/is-core-module-2.11.0.tgz",
"integrity": "sha512-RRjxlvLDkD1YJwDbroBHMb+cukurkDWNyHx7D3oNB5x9rb5ogcksMC5wHCadcXoo67gVr/+3GFySh3134zi6rw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"has": "^1.0.3"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"is-docker": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.2.1",
"resolved": "https://registry.npmjs.org/is-docker/-/is-docker-2.2.1.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-F+i2BKsFrH66iaUFc0woD8sLy8getkwTwtOBjvs56Cx4CgJDeKQeqfz8wAYiSb8JOprWhHH5p77PbmYCvvUuXQ=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"is-extglob": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/is-extglob/-/is-extglob-2.1.1.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"is-fullwidth-code-point": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"is-generator-fn": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/is-generator-fn/-/is-generator-fn-2.1.0.tgz",
"integrity": "sha512-cTIB4yPYL/Grw0EaSzASzg6bBy9gqCofvWN8okThAYIxKJZC+udlRAmGbM0XLeniEJSs8uEgHPGuHSe1XsOLSQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"is-glob": {
Update Electron to 13.5.1; Fix auth manual tests (#1287)
2021-10-03 02:17:06 +00:00
"version": "4.0.3",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz",
"integrity": "sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"is-extglob": "^2.1.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"is-number": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/is-number/-/is-number-7.0.0.tgz",
"integrity": "sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"is-path-inside": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/is-path-inside/-/is-path-inside-3.0.3.tgz",
"integrity": "sha512-Fd4gABb+ycGAmKou8eMftCupSir5lRxqf4aD/vd0cD2qc4HL07OjCeuHMr8Ro4CoMaeCKDB0/ECBOVWjTwUvPQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"is-plain-object": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"isobject": "^3.0.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"is-stream": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/is-stream/-/is-stream-2.0.1.tgz",
"integrity": "sha512-hFoiJiTl63nn+kstHGBtewWSKnQLpyb155KHheA1l39uvtO9nWIop1p3udqPcUd/xbF1VLMO4n7OI6p7RbngDg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"is-wsl": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/is-wsl/-/is-wsl-2.2.0.tgz",
"integrity": "sha512-fKzAra0rGJUUBwGBgNkHZuToZcn+TtXHpeCgmkMJMMYx1sQDYaCSyjJBSCa2nH1DGm7s3n1oBnohoVTBaN7Lww==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"is-docker": "^2.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"isarray": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-VLghIWNM6ELQzo7zwmcg0NmTVyWKYjvIeM83yjp0wRDTmUnrM678fQbcKBo6n2CJEF0szoG//ytg+TKla89ALQ==",
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"isbinaryfile": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/isbinaryfile/-/isbinaryfile-3.0.3.tgz",
"integrity": "sha512-8cJBL5tTd2OS0dM4jz07wQd5g0dCCqIhUxPIGtZfa5L6hWlvV5MHTITy/DBAsF+Oe2LS1X3krBUhNwaGUWpWxw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"buffer-alloc": "^1.2.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"isexe": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"isobject": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/isobject/-/isobject-3.0.1.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-WhB9zCku7EGTj/HQQRz5aUQEUeoQZH2bWcltRErOpymJ4boYE6wL9Tbr23krRPSZ+C5zqNSrSw+Cc7sZZ4b7vg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"istanbul-lib-coverage": {
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/istanbul-lib-coverage/-/istanbul-lib-coverage-3.2.0.tgz",
"integrity": "sha512-eOeJ5BHCmHYvQK7xt9GkdHuzuCGS1Y6g9Gvnx3Ym33fz/HpLRYxiS0wHNr+m/MBC8B647Xt608vCDEvhl9c6Mw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"istanbul-lib-instrument": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "5.2.1",
"resolved": "https://registry.npmjs.org/istanbul-lib-instrument/-/istanbul-lib-instrument-5.2.1.tgz",
"integrity": "sha512-pzqtp31nLv/XFOzXGuvhCb8qhjmTVo5vjVk19XE4CRlSWz0KoeJ3bw9XsA7nOp9YBf4qHjwBxkDzKcME/J29Yg==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump default Electron from 16.0.5 to 16.0.6 https://github.com/electron/electron/releases/tag/v16.0.6
2022-01-06 14:43:10 +00:00
"@babel/core": "^7.12.3",
"@babel/parser": "^7.14.7",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@istanbuljs/schema": "^0.1.2",
Bump default Electron from 16.0.5 to 16.0.6 https://github.com/electron/electron/releases/tag/v16.0.6
2022-01-06 14:43:10 +00:00
"istanbul-lib-coverage": "^3.2.0",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"semver": "^6.3.0"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"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
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"istanbul-lib-report": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/istanbul-lib-report/-/istanbul-lib-report-3.0.0.tgz",
"integrity": "sha512-wcdi+uAKzfiGT2abPpKZ0hSU1rGQjUQnLvtY5MpQ7QCTahD3VODhcu4wcfY1YtkGaDD5yuydOLINXsfbus9ROw==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"istanbul-lib-coverage": "^3.0.0",
"make-dir": "^3.0.0",
"supports-color": "^7.1.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"istanbul-lib-source-maps": {
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/istanbul-lib-source-maps/-/istanbul-lib-source-maps-4.0.1.tgz",
"integrity": "sha512-n3s8EwkdFIJCG3BPKBYvskgXGoy88ARzvegkitk60NxRdwltLOTaH7CUiMRXvwYorl0Q712iEjcWB+fK/MrWVw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"debug": "^4.1.1",
"istanbul-lib-coverage": "^3.0.0",
"source-map": "^0.6.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"istanbul-reports": {
relock cli
2022-07-23 22:39:04 +00:00
"version": "3.1.5",
"resolved": "https://registry.npmjs.org/istanbul-reports/-/istanbul-reports-3.1.5.tgz",
"integrity": "sha512-nUsEMa9pBt/NOHqbcbeJEgqIlY/K7rVWUX6Lql2orY5e9roQOthbR3vtY4zzf2orPELg80fnxxk9zUyPlgwD1w==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"html-escaper": "^2.0.0",
"istanbul-lib-report": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest/-/jest-28.1.3.tgz",
"integrity": "sha512-N4GT5on8UkZgH0O5LUavMRV1EDEhNTL0KEfRmDIeZHSV7p2XgLoY9t9VDUgL6o+yfdgYHVxuz81G8oB9VG5uyA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/core": "^28.1.3",
"@jest/types": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"import-local": "^3.0.2",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-cli": "^28.1.3"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"jest-cli": {
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-cli/-/jest-cli-28.1.3.tgz",
"integrity": "sha512-roY3kvrv57Azn1yPgdTebPAXvdR2xfezaKKYzVxZ6It/5NCxzJym6tUI5P1zkdWhfUYkxEI9uZWcQdaFLo8mJQ==",
"dev": true,
"requires": {
"@jest/core": "^28.1.3",
"@jest/test-result": "^28.1.3",
"@jest/types": "^28.1.3",
"chalk": "^4.0.0",
"exit": "^0.1.2",
"graceful-fs": "^4.2.9",
"import-local": "^3.0.2",
"jest-config": "^28.1.3",
"jest-util": "^28.1.3",
"jest-validate": "^28.1.3",
"prompts": "^2.0.1",
"yargs": "^17.3.1"
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-changed-files": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-changed-files/-/jest-changed-files-28.1.3.tgz",
"integrity": "sha512-esaOfUWJXk2nfZt9SPyC8gA1kNfdKLkQWyzsMlqq8msYSlNKfmZxfRgZn4Cd4MGVUF+7v6dBs0d5TOAKa7iIiA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"execa": "^5.0.0",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"p-limit": "^3.1.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"p-limit": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/p-limit/-/p-limit-3.1.0.tgz",
"integrity": "sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==",
"dev": true,
"requires": {
"yocto-queue": "^0.1.0"
}
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-circus": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-circus/-/jest-circus-28.1.3.tgz",
"integrity": "sha512-cZ+eS5zc79MBwt+IhQhiEp0OeBddpc1n8MBo1nMB8A7oPMKEO+Sre+wHaLJexQUj9Ya/8NOBY0RESUgYjB6fow==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/environment": "^28.1.3",
"@jest/expect": "^28.1.3",
"@jest/test-result": "^28.1.3",
"@jest/types": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/node": "*",
"chalk": "^4.0.0",
"co": "^4.6.0",
"dedent": "^0.7.0",
"is-generator-fn": "^2.0.0",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-each": "^28.1.3",
"jest-matcher-utils": "^28.1.3",
"jest-message-util": "^28.1.3",
"jest-runtime": "^28.1.3",
"jest-snapshot": "^28.1.3",
"jest-util": "^28.1.3",
"p-limit": "^3.1.0",
"pretty-format": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"slash": "^3.0.0",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"stack-utils": "^2.0.3"
Revert "nit" and "bump jest and fix yargs typing" This reverts commit b737c40931d14eb803353b3afa8b48cb583c3b6e. This reverts commit 8eb05ded9b8b4e39749580ed71b8721fcaffd779.
2022-07-23 23:20:24 +00:00
},
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"p-limit": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/p-limit/-/p-limit-3.1.0.tgz",
"integrity": "sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==",
"dev": true,
"requires": {
"yocto-queue": "^0.1.0"
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-config": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-config/-/jest-config-28.1.3.tgz",
"integrity": "sha512-MG3INjByJ0J4AsNBm7T3hsuxKQqFIiRo/AUqb1q9LRKI5UU6Aar9JHbr9Ivn1TVwfUD9KirRoM/T6u8XlcQPHQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@babel/core": "^7.11.6",
"@jest/test-sequencer": "^28.1.3",
"@jest/types": "^28.1.3",
"babel-jest": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"chalk": "^4.0.0",
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"ci-info": "^3.2.0",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"deepmerge": "^4.2.2",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"glob": "^7.1.3",
Relock dependencies
2022-02-06 22:47:06 +00:00
"graceful-fs": "^4.2.9",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-circus": "^28.1.3",
"jest-environment-node": "^28.1.3",
"jest-get-type": "^28.0.2",
"jest-regex-util": "^28.0.2",
"jest-resolve": "^28.1.3",
"jest-runner": "^28.1.3",
"jest-util": "^28.1.3",
"jest-validate": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"micromatch": "^4.0.4",
Upgrade dependencies Including axios 0.25 -> 0.25, nothing breaking for us: https://github.com/axios/axios/releases/tag/v0.26.0
2022-02-15 04:01:36 +00:00
"parse-json": "^5.2.0",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"pretty-format": "^28.1.3",
Upgrade dependencies Including axios 0.25 -> 0.25, nothing breaking for us: https://github.com/axios/axios/releases/tag/v0.26.0
2022-02-15 04:01:36 +00:00
"slash": "^3.0.0",
"strip-json-comments": "^3.1.1"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"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"
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-diff": {
bump jest **types**, so far it still builds
2022-07-23 22:43:04 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-diff/-/jest-diff-28.1.3.tgz",
"integrity": "sha512-8RqP1B/OXzjjTWkqMX67iqgwBVJRgCyKD3L9nq+6ZqJMdvjE8RgHktqZ6jNrkdMT+dJuYNI3rhQpxaz7drJHfw==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
bump jest **types**, so far it still builds
2022-07-23 22:43:04 +00:00
"chalk": "^4.0.0",
"diff-sequences": "^28.1.1",
"jest-get-type": "^28.0.2",
"pretty-format": "^28.1.3"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-docblock": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.1",
"resolved": "https://registry.npmjs.org/jest-docblock/-/jest-docblock-28.1.1.tgz",
"integrity": "sha512-3wayBVNiOYx0cwAbl9rwm5kKFP8yHH3d/fkEaL02NPTkDojPtheGB7HZSFY4wzX+DxyrvhXz0KSCVksmCknCuA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"detect-newline": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-each": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-each/-/jest-each-28.1.3.tgz",
"integrity": "sha512-arT1z4sg2yABU5uogObVPvSlSMQlDA48owx07BDPAiasW0yYpYHYOo4HHLz9q0BVzDVU4hILFjzJw0So9aCL/g==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/types": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"chalk": "^4.0.0",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-get-type": "^28.0.2",
"jest-util": "^28.1.3",
"pretty-format": "^28.1.3"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-environment-node": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-environment-node/-/jest-environment-node-28.1.3.tgz",
"integrity": "sha512-ugP6XOhEpjAEhGYvp5Xj989ns5cB1K6ZdjBYuS30umT4CQEETaxSiPcZ/E1kFktX4GkrcM4qu07IIlDYX1gp+A==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/environment": "^28.1.3",
"@jest/fake-timers": "^28.1.3",
"@jest/types": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/node": "*",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-mock": "^28.1.3",
"jest-util": "^28.1.3"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-get-type": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.0.2",
"resolved": "https://registry.npmjs.org/jest-get-type/-/jest-get-type-28.0.2.tgz",
"integrity": "sha512-ioj2w9/DxSYHfOm5lJKCdcAmPJzQXmbM/Url3rhlghrPvT3tt+7a/+oXc9azkKmLvoiXjtV83bEWqi+vs5nlPA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-haste-map": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-haste-map/-/jest-haste-map-28.1.3.tgz",
"integrity": "sha512-3S+RQWDXccXDKSWnkHa/dPwt+2qwA8CJzR61w3FoYCvoo3Pn8tvGcysmMF0Bj0EX5RYvAI2EIvC57OmotfdtKA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/types": "^28.1.3",
"@types/graceful-fs": "^4.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/node": "*",
"anymatch": "^3.0.3",
"fb-watchman": "^2.0.0",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"fsevents": "^2.3.2",
Relock dependencies
2022-02-06 22:47:06 +00:00
"graceful-fs": "^4.2.9",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-regex-util": "^28.0.2",
"jest-util": "^28.1.3",
"jest-worker": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"micromatch": "^4.0.4",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"walker": "^1.0.8"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-leak-detector": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-leak-detector/-/jest-leak-detector-28.1.3.tgz",
"integrity": "sha512-WFVJhnQsiKtDEo5lG2mM0v40QWnBM+zMdHHyJs8AWZ7J0QZJS59MsyKeJHWhpBZBH32S48FOVvGyOFT1h0DlqA==",
Revert "nit" and "bump jest and fix yargs typing" This reverts commit b737c40931d14eb803353b3afa8b48cb583c3b6e. This reverts commit 8eb05ded9b8b4e39749580ed71b8721fcaffd779.
2022-07-23 23:20:24 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-get-type": "^28.0.2",
"pretty-format": "^28.1.3"
bump jest **types**, so far it still builds
2022-07-23 22:43:04 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-matcher-utils": {
bump jest **types**, so far it still builds
2022-07-23 22:43:04 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-matcher-utils/-/jest-matcher-utils-28.1.3.tgz",
"integrity": "sha512-kQeJ7qHemKfbzKoGjHHrRKH6atgxMk8Enkk2iPQ3XwO6oE/KYD8lMYOziCkeSB9G4adPM4nR1DE8Tf5JeWH6Bw==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
bump jest **types**, so far it still builds
2022-07-23 22:43:04 +00:00
"chalk": "^4.0.0",
"jest-diff": "^28.1.3",
"jest-get-type": "^28.0.2",
"pretty-format": "^28.1.3"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-message-util": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-message-util/-/jest-message-util-28.1.3.tgz",
"integrity": "sha512-PFdn9Iewbt575zKPf1286Ht9EPoJmYT7P0kY+RibeYZ2XtOr53pDLEFoTWXbd1h4JiGiWpTBC84fc8xMXQMb7g==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@babel/code-frame": "^7.12.13",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/types": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/stack-utils": "^2.0.0",
"chalk": "^4.0.0",
Relock dependencies
2022-02-06 22:47:06 +00:00
"graceful-fs": "^4.2.9",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"micromatch": "^4.0.4",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"pretty-format": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"slash": "^3.0.0",
"stack-utils": "^2.0.3"
Revert "nit" and "bump jest and fix yargs typing" This reverts commit b737c40931d14eb803353b3afa8b48cb583c3b6e. This reverts commit 8eb05ded9b8b4e39749580ed71b8721fcaffd779.
2022-07-23 23:20:24 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-mock": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-mock/-/jest-mock-28.1.3.tgz",
"integrity": "sha512-o3J2jr6dMMWYVH4Lh/NKmDXdosrsJgi4AviS8oXLujcjpCMBb1FMsblDnOXKZKfSiHLxYub1eS0IHuRXsio9eA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/types": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/node": "*"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-pnp-resolver": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "1.2.3",
"resolved": "https://registry.npmjs.org/jest-pnp-resolver/-/jest-pnp-resolver-1.2.3.tgz",
"integrity": "sha512-+3NpwQEnRoIBtx4fyhblQDPgJI0H1IEIkX7ShLUjPGA7TtUTvI1oiKi3SR4oBR0hQhQR80l4WAe5RrXBwWMA8w==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-regex-util": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.0.2",
"resolved": "https://registry.npmjs.org/jest-regex-util/-/jest-regex-util-28.0.2.tgz",
"integrity": "sha512-4s0IgyNIy0y9FK+cjoVYoxamT7Zeo7MhzqRGx7YDYmaQn1wucY9rotiGkBzzcMXTtjrCAP/f7f+E0F7+fxPNdw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-resolve": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-resolve/-/jest-resolve-28.1.3.tgz",
"integrity": "sha512-Z1W3tTjE6QaNI90qo/BJpfnvpxtaFTFw5CDgwpyE/Kz8U/06N1Hjf4ia9quUhCh39qIGWF1ZuxFiBiJQwSEYKQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"chalk": "^4.0.0",
Relock dependencies
2022-02-06 22:47:06 +00:00
"graceful-fs": "^4.2.9",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-haste-map": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"jest-pnp-resolver": "^1.2.2",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-util": "^28.1.3",
"jest-validate": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"resolve": "^1.20.0",
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"resolve.exports": "^1.1.0",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"slash": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-resolve-dependencies": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-resolve-dependencies/-/jest-resolve-dependencies-28.1.3.tgz",
"integrity": "sha512-qa0QO2Q0XzQoNPouMbCc7Bvtsem8eQgVPNkwn9LnS+R2n8DaVDPL/U1gngC0LTl1RYXJU0uJa2BMC2DbTfFrHA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-regex-util": "^28.0.2",
"jest-snapshot": "^28.1.3"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-runner": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-runner/-/jest-runner-28.1.3.tgz",
"integrity": "sha512-GkMw4D/0USd62OVO0oEgjn23TM+YJa2U2Wu5zz9xsQB1MxWKDOlrnykPxnMsN0tnJllfLPinHTka61u0QhaxBA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/console": "^28.1.3",
"@jest/environment": "^28.1.3",
"@jest/test-result": "^28.1.3",
"@jest/transform": "^28.1.3",
"@jest/types": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/node": "*",
"chalk": "^4.0.0",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"emittery": "^0.10.2",
Relock dependencies
2022-02-06 22:47:06 +00:00
"graceful-fs": "^4.2.9",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-docblock": "^28.1.1",
"jest-environment-node": "^28.1.3",
"jest-haste-map": "^28.1.3",
"jest-leak-detector": "^28.1.3",
"jest-message-util": "^28.1.3",
"jest-resolve": "^28.1.3",
"jest-runtime": "^28.1.3",
"jest-util": "^28.1.3",
"jest-watcher": "^28.1.3",
"jest-worker": "^28.1.3",
"p-limit": "^3.1.0",
"source-map-support": "0.5.13"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"p-limit": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/p-limit/-/p-limit-3.1.0.tgz",
"integrity": "sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==",
"dev": true,
"requires": {
"yocto-queue": "^0.1.0"
}
},
"source-map-support": {
"version": "0.5.13",
"resolved": "https://registry.npmjs.org/source-map-support/-/source-map-support-0.5.13.tgz",
"integrity": "sha512-SHSKFHadjVA5oR4PPqhtAVdcBWwRYVd6g6cAXnIbRiIwc2EhPrTuKUBdSLvlEKyIP3GCf89fltvcZiP9MMFA1w==",
"dev": true,
"requires": {
"buffer-from": "^1.0.0",
"source-map": "^0.6.0"
}
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-runtime": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-runtime/-/jest-runtime-28.1.3.tgz",
"integrity": "sha512-NU+881ScBQQLc1JHG5eJGU7Ui3kLKrmwCPPtYsJtBykixrM2OhVQlpMmFWJjMyDfdkGgBMNjXCGB/ebzsgNGQw==",
Upgrade dependencies Including axios 0.25 -> 0.25, nothing breaking for us: https://github.com/axios/axios/releases/tag/v0.26.0
2022-02-15 04:01:36 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/environment": "^28.1.3",
"@jest/fake-timers": "^28.1.3",
"@jest/globals": "^28.1.3",
"@jest/source-map": "^28.1.2",
"@jest/test-result": "^28.1.3",
"@jest/transform": "^28.1.3",
"@jest/types": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"chalk": "^4.0.0",
"cjs-module-lexer": "^1.0.0",
"collect-v8-coverage": "^1.0.0",
"execa": "^5.0.0",
"glob": "^7.1.3",
Relock dependencies
2022-02-06 22:47:06 +00:00
"graceful-fs": "^4.2.9",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-haste-map": "^28.1.3",
"jest-message-util": "^28.1.3",
"jest-mock": "^28.1.3",
"jest-regex-util": "^28.0.2",
"jest-resolve": "^28.1.3",
"jest-snapshot": "^28.1.3",
"jest-util": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"slash": "^3.0.0",
Bump default Electron from 16.0.5 to 16.0.6 https://github.com/electron/electron/releases/tag/v16.0.6
2022-01-06 14:43:10 +00:00
"strip-bom": "^4.0.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"strip-bom": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-4.0.0.tgz",
"integrity": "sha512-3xurFv5tEgii33Zi8Jtp55wEIILR9eh34FAW00PZf+JnSsTmV/ioewSgQl97JHvgjoRGwPShsWm+IdrxB35d0w==",
"dev": true
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-snapshot": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-snapshot/-/jest-snapshot-28.1.3.tgz",
"integrity": "sha512-4lzMgtiNlc3DU/8lZfmqxN3AYD6GGLbl+72rdBpXvcV+whX7mDrREzkPdp2RnmfIiWBg1YbuFSkXduF2JcafJg==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@babel/core": "^7.11.6",
Revert "Major-bump jest to 28": breaks tsc in weird ways, will retry later. This reverts commit bd109099ceb3e13cf95b1d52810e9fe385bfaab7.
2022-05-02 03:51:04 +00:00
"@babel/generator": "^7.7.2",
"@babel/plugin-syntax-typescript": "^7.7.2",
"@babel/traverse": "^7.7.2",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@babel/types": "^7.3.3",
"@jest/expect-utils": "^28.1.3",
"@jest/transform": "^28.1.3",
"@jest/types": "^28.1.3",
"@types/babel__traverse": "^7.0.6",
Revert "Major-bump jest to 28": breaks tsc in weird ways, will retry later. This reverts commit bd109099ceb3e13cf95b1d52810e9fe385bfaab7.
2022-05-02 03:51:04 +00:00
"@types/prettier": "^2.1.5",
"babel-preset-current-node-syntax": "^1.0.0",
"chalk": "^4.0.0",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"expect": "^28.1.3",
Revert "Major-bump jest to 28": breaks tsc in weird ways, will retry later. This reverts commit bd109099ceb3e13cf95b1d52810e9fe385bfaab7.
2022-05-02 03:51:04 +00:00
"graceful-fs": "^4.2.9",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-diff": "^28.1.3",
"jest-get-type": "^28.0.2",
"jest-haste-map": "^28.1.3",
"jest-matcher-utils": "^28.1.3",
"jest-message-util": "^28.1.3",
"jest-util": "^28.1.3",
Revert "Major-bump jest to 28": breaks tsc in weird ways, will retry later. This reverts commit bd109099ceb3e13cf95b1d52810e9fe385bfaab7.
2022-05-02 03:51:04 +00:00
"natural-compare": "^1.4.0",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"pretty-format": "^28.1.3",
"semver": "^7.3.5"
Revert "nit" and "bump jest and fix yargs typing" This reverts commit b737c40931d14eb803353b3afa8b48cb583c3b6e. This reverts commit 8eb05ded9b8b4e39749580ed71b8721fcaffd779.
2022-07-23 23:20:24 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-util": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-util/-/jest-util-28.1.3.tgz",
"integrity": "sha512-XdqfpHwpcSRko/C35uLYFM2emRAltIIKZiJ9eAmhjsj0CqZMa0p1ib0R5fWIqGhn1a103DebTbpqIaP1qCQ6tQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/types": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/node": "*",
"chalk": "^4.0.0",
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"ci-info": "^3.2.0",
Relock dependencies
2022-02-06 22:47:06 +00:00
"graceful-fs": "^4.2.9",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"picomatch": "^2.2.3"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-validate": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-validate/-/jest-validate-28.1.3.tgz",
"integrity": "sha512-SZbOGBWEsaTxBGCOpsRWlXlvNkvTkY0XxRfh7zYmvd8uL5Qzyg0CHAXiXKROflh801quA6+/DsT4ODDthOC/OA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/types": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"camelcase": "^6.2.0",
"chalk": "^4.0.0",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"jest-get-type": "^28.0.2",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"leven": "^3.1.0",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"pretty-format": "^28.1.3"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"camelcase": {
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/camelcase/-/camelcase-6.3.0.tgz",
"integrity": "sha512-Gmy6FhYlCY7uOElZUSbxo2UCDH8owEk996gkbrpsgGtrJLM3J7jGxl9Ic7Qwwj4ivOE5AWZWRMecDdF7hqGjFA==",
"dev": true
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-watcher": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-watcher/-/jest-watcher-28.1.3.tgz",
"integrity": "sha512-t4qcqj9hze+jviFPUN3YAtAEeFnr/azITXQEMARf5cMwKY2SMBRnCQTXLixTl20OR6mLh9KLMrgVJgJISym+1g==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jest/test-result": "^28.1.3",
"@jest/types": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/node": "*",
"ansi-escapes": "^4.2.1",
"chalk": "^4.0.0",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"emittery": "^0.10.2",
"jest-util": "^28.1.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"string-length": "^4.0.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jest-worker": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/jest-worker/-/jest-worker-28.1.3.tgz",
"integrity": "sha512-CqRA220YV/6jCo8VWvAt1KKx6eek1VIHMPeLEbpcfSfkEeWyBNppynM/o6q+Wmw+sOhos2ml34wZbSX3G13//g==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/node": "*",
"merge-stream": "^2.0.0",
"supports-color": "^8.0.0"
},
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"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,
"requires": {
"has-flag": "^4.0.0"
}
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"js-sdsl": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "4.4.0",
"resolved": "https://registry.npmjs.org/js-sdsl/-/js-sdsl-4.4.0.tgz",
"integrity": "sha512-FfVSdx6pJ41Oa+CF7RDaFmTnCaFhua+SNYQX74riGOpl96x+2jQCqEfQ2bnXu/5DPCqlRuiqyvTJM0Qjz26IVg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
relock cli
2022-09-18 02:30:33 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"js-tokens": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/js-tokens/-/js-tokens-4.0.0.tgz",
"integrity": "sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"js-yaml": {
Bump to eslint 8 https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0
2021-11-01 19:47:46 +00:00
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.0.tgz",
"integrity": "sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump to eslint 8 https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0
2021-11-01 19:47:46 +00:00
"argparse": "^2.0.1"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jsesc": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.5.2",
"resolved": "https://registry.npmjs.org/jsesc/-/jsesc-2.5.2.tgz",
"integrity": "sha512-OYu7XEzjkCQ3C5Ps3QIZsQfNpqoJyZZA99wd9aWd05NCtC5pWOkShK2mkL6HXQR6/Cy2lbNdPlZBpuQHXE63gA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"json-buffer": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/json-buffer/-/json-buffer-3.0.0.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-CuUqjv0FUZIdXkHPI8MezCnFCdaTAacej1TZYulLoAg1h/PhwkdXFN4V/gzY4g+fMBCOV2xF+rp7t2XD2ns/NQ=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"json-parse-even-better-errors": {
Upgrade dependencies Including axios 0.25 -> 0.25, nothing breaking for us: https://github.com/axios/axios/releases/tag/v0.26.0
2022-02-15 04:01:36 +00: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==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"json-schema-traverse": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"json-stable-stringify-without-jsonify": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/json-stable-stringify-without-jsonify/-/json-stable-stringify-without-jsonify-1.0.1.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-Bdboy+l7tA3OGW6FjyFHWkP5LuByj1Tk33Ljyq0axyzdk9//JSi2u3fP1QSmd1KNwq6VOKYGlAu87CisVir6Pw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"json-stringify-safe": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-ZClg6AaYvamvYEE82d3Iyd3vSSIjQ+odgjaTzRuO3s7toCdFKczob2i0zCh7JE8kWn17yvAWhUVxvqGwUalsRA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"optional": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"json5": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "2.2.3",
"resolved": "https://registry.npmjs.org/json5/-/json5-2.2.3.tgz",
"integrity": "sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"jsonfile": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-4.0.0.tgz",
"integrity": "sha512-m6F1R3z8jjlf2imQHS2Qez5sjKWQzbuuhuJ/FKYFRZvPE3PuHcSMVZzfsLhGVOkfd20obL5SWEBew5ShlquNxg==",
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"graceful-fs": "^4.1.6"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"junk": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/junk/-/junk-3.1.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-pBxcB3LFc8QVgdggvZWyeys+hnrNWg4OcZIU/1X59k5jQdLBlCsYGRQaz234SqoRLTCgMH00fY0xRJH+F9METQ=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"keyv": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/keyv/-/keyv-3.1.0.tgz",
"integrity": "sha512-9ykJ/46SN/9KPM/sichzQ7OvXyGDYKGTaDlKMGCAlg2UK8KRy4jb0d8sFc+0Tt0YYnThq8X2RZgCg74RPxgcVA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"json-buffer": "3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"kind-of": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"kleur": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/kleur/-/kleur-3.0.3.tgz",
"integrity": "sha512-eTIzlVOSUR+JxdDFepEYcBMtZ9Qqdef+rnzWdRZuMbOywu5tO2w2N7rqjoANZ5k9vywhL6Br1VRjUIgTQx4E8w==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"leven": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/leven/-/leven-3.1.0.tgz",
"integrity": "sha512-qsda+H8jTaUaN/x5vzW2rzc+8Rw4TAQ/4KjB46IwK5VH+IlVeeeje/EoZRpiXvIqjFgK84QffqPztGI3VBLG1A==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"levn": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"prelude-ls": "^1.2.1",
"type-check": "~0.4.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"lines-and-columns": {
Upgrade dependencies Including axios 0.25 -> 0.25, nothing breaking for us: https://github.com/axios/axios/releases/tag/v0.26.0
2022-02-15 04:01:36 +00:00
"version": "1.2.4",
"resolved": "https://registry.npmjs.org/lines-and-columns/-/lines-and-columns-1.2.4.tgz",
"integrity": "sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"load-json-file": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/load-json-file/-/load-json-file-2.0.0.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-3p6ZOGNbiX4CdvEd1VcE6yi78UrGNpjHO33noGwHCnT/o2fyllJDepsm8+mFFv/DvtwFHht5HIHSyOy5a+ChVQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"graceful-fs": "^4.1.2",
"parse-json": "^2.2.0",
"pify": "^2.0.0",
"strip-bom": "^3.0.0"
},
Relock dependencies
2022-05-02 03:22:57 +00:00
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"pify": {
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"integrity": "sha512-udgsAY+fTnvv7kI7aaxbqwWNb0AHiB0qBO89PZKPkoTmGOgdbrHDKD+0B2X4uTfJ/FT1R09r9gTsjUjNJotuog=="
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"loader-runner": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/loader-runner/-/loader-runner-4.3.0.tgz",
"integrity": "sha512-3R/1M+yS3j5ou80Me59j7F9IMs4PXs3VqRrm0TU3AbKPxlmpoY1TNscJV/oGJXo8qCatFGTfDbY6W6ipGOYXfg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"locate-path": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/locate-path/-/locate-path-2.0.0.tgz",
"integrity": "sha512-NCI2kiDkyR7VeEKm27Kda/iQHyKJe1Bu0FlTbYp3CqJu+9IFe9bLyAjMxf5ZDDbEg+iMPzB5zYyUTSm8wVTKmA==",
"requires": {
"p-locate": "^2.0.0",
"path-exists": "^3.0.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"lodash": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.17.21",
"resolved": "https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz",
"integrity": "sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"optional": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"lodash.get": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.4.2",
"resolved": "https://registry.npmjs.org/lodash.get/-/lodash.get-4.4.2.tgz",
Relock dependencies
2022-05-30 13:42:40 +00:00
"integrity": "sha512-z+Uw/vLuy6gQe8cfaFWD7p0wVv8fJl3mbzXh33RS+0oW2wvUqiRXiQ69gLWSLpgB5/6sU+r6BlQR0MBILadqTQ=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"lodash.merge": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"loglevel": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "1.8.1",
"resolved": "https://registry.npmjs.org/loglevel/-/loglevel-1.8.1.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-tCRIJM51SHjAayKwC+QAg8hT8vg6z7GSgLJKGvzuPb1Wc+hLzqtuVLxp6/HzSPOozuK+8ErAhy7U/sVzw8Dgfg=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"lowercase-keys": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/lowercase-keys/-/lowercase-keys-1.0.1.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-G2Lj61tXDnVFFOi8VZds+SoQjtQC3dgokKdDG2mTm1tx4m50NUHBOZSBwQQHyy0V12A0JTG4icfZQH+xPyh8VA=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"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==",
"requires": {
"yallist": "^4.0.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"make-dir": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"semver": "^6.0.0"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"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
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"makeerror": {
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"version": "1.0.12",
"resolved": "https://registry.npmjs.org/makeerror/-/makeerror-1.0.12.tgz",
"integrity": "sha512-JmqCvUhmt43madlpFzG4BQzG2Z3m6tvQDNKdClZnO3VbIudJYmxsT0FNJMeiB2+JTSlTQTSbU8QdesVmwJcmLg==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"tmpl": "1.0.5"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"matcher": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/matcher/-/matcher-3.0.0.tgz",
"integrity": "sha512-OkeDaAZ/bQCxeFAozM55PKcKU0yJMPGifLwV4Qgjitu+5MoAfSQN4lsLJeXZ1b8w0x+/Emda6MZgXS1jvsapng==",
"optional": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"escape-string-regexp": "^4.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"merge-stream": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"merge2": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.4.1",
"resolved": "https://registry.npmjs.org/merge2/-/merge2-1.4.1.tgz",
"integrity": "sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"micromatch": {
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-04-10 15:18:41 +00:00
"version": "4.0.5",
"resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.5.tgz",
"integrity": "sha512-DMy+ERcEW2q8Z2Po+WNXuw3c5YaUSFjAO5GsJqfEl7UjvtIuFKO6ZrKvcItdy98dwFI2N1tg3zNIdKaQT+aNdA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-04-10 15:18:41 +00:00
"braces": "^3.0.2",
"picomatch": "^2.3.1"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"mime-db": {
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-03-21 03:32:19 +00:00
"version": "1.52.0",
"resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.52.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-sPU4uV7dYlvtWJxwwxHD0PuihVNiE7TyAbQ5SWxDCB9mUYvOgroQOwYQQOKPJ8CIbE+1ETVlOoK1UC2nU3gYvg=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"mime-types": {
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-03-21 03:32:19 +00:00
"version": "2.1.35",
"resolved": "https://registry.npmjs.org/mime-types/-/mime-types-2.1.35.tgz",
"integrity": "sha512-ZDY+bPm5zTTF+YpCrAU9nK0UgICYPT0QtT1NZWFv4s++TNkcgVaT0g6+4R2uI4MjQjzysHB1zxuWL50hzaeXiw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-03-21 03:32:19 +00:00
"mime-db": "1.52.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"mimic-fn": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/mimic-fn/-/mimic-fn-2.1.0.tgz",
"integrity": "sha512-OqbOk5oEQeAZ8WXWydlu9HJjz9WVdEIvamMCcXmuqUYjTknH/sqsWvhQ3vgwKFRR1HpjvNBKQ37nbJgYzGqGcg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"mimic-response": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/mimic-response/-/mimic-response-1.0.1.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-j5EctnkH7amfV/q5Hgmoal1g2QHFJRraOtmx0JpIqkxhBhI/lJSl1nMpQ45hVarwNETOoWEimndZ4QK0RHxuxQ=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"minimatch": {
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-03-21 03:32:19 +00:00
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz",
"integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"brace-expansion": "^1.1.7"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"minimist": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "1.2.8",
"resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.8.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-2yyAR8qBkN3YuheJanUpWC5U3bb5osDywNB8RzDVlDwDHbocAJveqqj1u8+SVD7jkWT4yvsHCpWqqWqAxb0zCA=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"mkdirp": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"version": "0.5.6",
"resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.6.tgz",
"integrity": "sha512-FP+p8RB8OWpF3YZBCrP5gtADmtXApB5AMLn+vdyA+PyxCjrCs00mjyUozssO33cwDeT3wNGdLxJ5M//YqtHAJw==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"minimist": "^1.2.6"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"ms": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w=="
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"natural-compare": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/natural-compare/-/natural-compare-1.4.0.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-OWND8ei3VtNC9h7V60qff3SVobHr996CTwgxubgyQYEpg290h9J0buyECNNJexkFm5sOajh5G116RYA1c8ZMSw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"natural-compare-lite": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/natural-compare-lite/-/natural-compare-lite-1.4.0.tgz",
"integrity": "sha512-Tj+HTDSJJKaZnfiuw+iaF9skdPpTo2GtEly5JHnWV/hfv2Qj/9RKsGISQtLh2ox3l5EAGw487hnBee0sIJ6v2g==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"ncp": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/ncp/-/ncp-2.0.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-zIdGUrPRFTUELUvr3Gmc7KZ2Sw/h1PiVM0Af/oHB6zgnV1ikqSfRk+TOufi79aHYCW3NiOXmr1BP5nWbzojLaA=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"neo-async": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"node-int64": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.4.0",
"resolved": "https://registry.npmjs.org/node-int64/-/node-int64-0.4.0.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-O5lz91xSOeoXP6DulyHfllpq+Eg00MWitZIbtPfoSEvqIHdl5gfcY6hYzDWnj0qD5tz52PI08u9qUvSVeUBeHw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"node-releases": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "2.0.10",
"resolved": "https://registry.npmjs.org/node-releases/-/node-releases-2.0.10.tgz",
"integrity": "sha512-5GFldHPXVG/YZmFzJvKK2zDSzPKhEp0+ZR5SVaoSag9fsL5YgHbUHDfnG5494ISANDcK4KwPXAx2xqVEydmd7w==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"normalize-package-data": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"hosted-git-info": "^2.1.4",
"resolve": "^1.10.0",
"semver": "2 || 3 || 4 || 5",
"validate-npm-package-license": "^3.0.1"
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
},
"dependencies": {
"semver": {
"version": "5.7.1",
"resolved": "https://registry.npmjs.org/semver/-/semver-5.7.1.tgz",
"integrity": "sha512-sauaDf/PZdVgrLTNYHRtpXa1iRiKcaebiKQ1BJdpQlWH2lCvexQdX55snPFyK7QzpudqbCI0qXFfOasHdyNDGQ=="
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"normalize-path": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/normalize-path/-/normalize-path-3.0.0.tgz",
"integrity": "sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"normalize-url": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.5.1",
"resolved": "https://registry.npmjs.org/normalize-url/-/normalize-url-4.5.1.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-9UZCFRHQdNrfTpGg8+1INIg93B6zE0aXMVFkw1WFwvO4SlZywU6aLg5Of0Ap/PgcbSw4LNxvMWXMeugwMCX0AA=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"npm-conf": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/npm-conf/-/npm-conf-1.1.3.tgz",
"integrity": "sha512-Yic4bZHJOt9RCFbRP3GgpqhScOY4HH3V2P8yBj6CeYq118Qr+BLXqT2JvpJ00mryLESpgOxf5XlFv4ZjXxLScw==",
"optional": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"config-chain": "^1.1.11",
"pify": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"npm-run-path": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/npm-run-path/-/npm-run-path-4.0.1.tgz",
"integrity": "sha512-S48WzZW777zhNIrn7gxOlISNAqi9ZC/uQFnRdbeIHhZhCA6UqpkOT8T1G7BvfdgP4Er8gF4sUbaS0i7QvIfCWw==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"path-key": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"nth-check": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.1.1.tgz",
"integrity": "sha512-lqjrjmaOoAnWfMmBPL+XNnynZh2+swxiX3WUE0s4yEHI6m+AwrK2UZOimIRl3X/4QctVqS8AiZjFqyOGrMXb/w==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"boolbase": "^1.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"object-keys": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz",
"integrity": "sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"optional": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"once": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/once/-/once-1.4.0.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"wrappy": "1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"onetime": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "5.1.2",
"resolved": "https://registry.npmjs.org/onetime/-/onetime-5.1.2.tgz",
"integrity": "sha512-kbpaSSGJTWdAY5KPVeMOKXSrPtr8C8C7wodJbcsd51jRnmD+GZu8Y0VoU6Dm5Z4vWr0Ig/1NKuWRKf7j5aaYSg==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"mimic-fn": "^2.1.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"optionator": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.9.1",
"resolved": "https://registry.npmjs.org/optionator/-/optionator-0.9.1.tgz",
"integrity": "sha512-74RlY5FCnhq4jRxVUPKDaRwrVNXMqsGsiW6AJw4XK8hmtm10wC0ypZBLw5IIp85NZMr91+qd1RvvENwg7jjRFw==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"p-cancelable": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/p-cancelable/-/p-cancelable-1.1.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-s73XxOZ4zpt1edZYZzvhqFa6uvQc1vwUa0K0BdtIZgQMAJj9IbebH+JkgKZc9h+B05PKHLOTl4ajG1BmNrVZlw=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"p-limit": {
"version": "1.3.0",
"resolved": "https://registry.npmjs.org/p-limit/-/p-limit-1.3.0.tgz",
"integrity": "sha512-vvcXsLAJ9Dr5rQOPk7toZQZJApBl2K4J6dANSsEuh6QI41JYcsS/qhTGa9ErIUUgK3WNQoJYvylxvjqmiqEA9Q==",
"requires": {
"p-try": "^1.0.0"
bump jest and fix yargs typing
2022-07-23 23:07:54 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"p-locate": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/p-locate/-/p-locate-2.0.0.tgz",
"integrity": "sha512-nQja7m7gSKuewoVRen45CtVfODR3crN3goVQ0DDZ9N3yHxgpkuBhZqsaiotSQRrADUrne346peY7kT3TSACykg==",
"requires": {
"p-limit": "^1.1.0"
bump jest and fix yargs typing
2022-07-23 23:07:54 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"p-try": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/p-try/-/p-try-1.0.0.tgz",
"integrity": "sha512-U1etNYuMJoIz3ZXSrrySFjsXQTWOx2/jdi86L+2pRvph/qMKL6sbcCYdH23fqsbm8TH2Gn0OybpT4eSFlCVHww=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"page-icon": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.4.0",
"resolved": "https://registry.npmjs.org/page-icon/-/page-icon-0.4.0.tgz",
"integrity": "sha512-dPY5pK+AT8Z1YFXTIfN4vmth8JngNny4qKm1EXBuOUyfiVdO5X3/Rq+tirHUN5A7b7eKQ+pZMsA74RPdHU17Sw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"axios": "^0.21.1",
"cheerio": "^1.0.0-rc.5",
"file-type": "^16.2.0"
},
Bump axios to 0.24.0 https://github.com/axios/axios/blob/master/CHANGELOG.md
2021-11-01 19:54:03 +00:00
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"axios": {
"version": "0.21.4",
"resolved": "https://registry.npmjs.org/axios/-/axios-0.21.4.tgz",
"integrity": "sha512-ut5vewkiu8jjGBdqpM44XxjuCjq9LAKeHVmoVfHVzy8eHgxxq8SbAVQNovDA8mVi05kP0Ea/n/UzcSHcTJQfNg==",
"requires": {
"follow-redirects": "^1.14.0"
}
}
Bump axios to 0.24.0 https://github.com/axios/axios/blob/master/CHANGELOG.md
2021-11-01 19:54:03 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"parent-module": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"callsites": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"parse-author": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/parse-author/-/parse-author-2.0.0.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-yx5DfvkN8JsHL2xk2Os9oTia467qnvRgey4ahSm2X8epehBLx/gWLcy5KI+Y36ful5DzGbCS6RazqZGgy1gHNw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"author-regex": "^1.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"parse-json": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"integrity": "sha512-QR/GGaKCkhwk1ePQNYDRKYZ3mwU9ypsKhB0XyFnLQdomyEqk3e8wpW3V5Jp88zbxK4n5ST1nqo+g9juTpownhQ==",
"requires": {
"error-ex": "^1.2.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"parse5": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "7.1.2",
"resolved": "https://registry.npmjs.org/parse5/-/parse5-7.1.2.tgz",
"integrity": "sha512-Czj1WaSVpaoj0wbhMzLmWD69anp2WH7FXMB9n1Sy8/ZFF9jolSQVMu1Ij5WIyGmcBmhk7EOndpO4mIpihVqAXw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
relock cli
2022-09-18 02:30:33 +00:00
"entities": "^4.4.0"
Relock dependencies
2022-05-30 13:42:40 +00:00
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"parse5-htmlparser2-tree-adapter": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/parse5-htmlparser2-tree-adapter/-/parse5-htmlparser2-tree-adapter-7.0.0.tgz",
"integrity": "sha512-B77tOZrqqfUfnVcOrUvfdLbz4pu4RopLD/4vmu3HUPswwTA8OH0EMW9BlWR2B0RCoiZRAHEUu7IxeP1Pd1UU+g==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"domhandler": "^5.0.2",
"parse5": "^7.0.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"path-exists": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-3.0.0.tgz",
"integrity": "sha512-bpC7GYwiDYQ4wYLe+FA8lhRjhQCMcQGuSgGGqDkg/QerRWw9CmGRT0iSOVRSZJ29NMLZgIzqaljJ63oaL4NIJQ=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"path-is-absolute": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.1.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"path-key": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/path-key/-/path-key-3.1.1.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"path-parse": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.7",
"resolved": "https://registry.npmjs.org/path-parse/-/path-parse-1.0.7.tgz",
"integrity": "sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw=="
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"path-type": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-2.0.0.tgz",
"integrity": "sha512-dUnb5dXUf+kzhC/W/F4e5/SkluXIFf5VUHolW1Eg1irn1hGWjPGdsRcvYJ1nD6lhk8Ir7VM0bHJKsYTx8Jx9OQ==",
"requires": {
"pify": "^2.0.0"
},
"dependencies": {
"pify": {
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"integrity": "sha512-udgsAY+fTnvv7kI7aaxbqwWNb0AHiB0qBO89PZKPkoTmGOgdbrHDKD+0B2X4uTfJ/FT1R09r9gTsjUjNJotuog=="
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"peek-readable": {
Relock dependencies
2022-02-06 22:47:06 +00:00
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/peek-readable/-/peek-readable-4.1.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-ZI3LnwUv5nOGbQzD9c2iDG6toheuXSZP5esSHBjopsXH4dg19soufvpUGA3uohi5anFtGb2lhAVdHzH6R/Evvg=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"pend": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/pend/-/pend-1.2.0.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-F3asv42UuXchdzt+xXqfW1OGlVBe+mxa2mqI0pg5yAHZPvFmY3Y6drSf/GQ1A86WgWEN9Kzh/WrgKa6iGcHXLg=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"picocolors": {
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/picocolors/-/picocolors-1.0.0.tgz",
"integrity": "sha512-1fygroTLlHu66zi26VoTDv8yRgm0Fccecssto+MhsZ0D/DGW2sm8E8AjW7NU5VVTRt5GxbeZ5qBuJr+HyLYkjQ==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"picomatch": {
Bump default Electron from 16.0.5 to 16.0.6 https://github.com/electron/electron/releases/tag/v16.0.6
2022-01-06 14:43:10 +00:00
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/picomatch/-/picomatch-2.3.1.tgz",
"integrity": "sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"pify": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/pify/-/pify-3.0.0.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-C3FsVNH1udSEX48gGX1xfvwTWfsYWj5U+8/uK15BGzIGrKoUpghX8hWZwa/OFnakBiiVNmBvemTJR5mcy7iPcg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"optional": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"pirates": {
Relock dependencies
2022-02-06 22:47:06 +00:00
"version": "4.0.5",
"resolved": "https://registry.npmjs.org/pirates/-/pirates-4.0.5.tgz",
"integrity": "sha512-8V9+HQPupnaXMA23c5hvl69zXvTwTzyAYasnkb0Tts4XvO4CliqONMOnvlq26rkhLC3nWDFBJf73LU1e1VZLaQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"pkg-dir": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"find-up": "^4.0.0"
},
macOS: Move handling of "universal" apps to electron-packager instead of our own thing (#1443) Supported since [electron-packager 15.5.0](https://github.com/electron/electron-packager/releases/tag/v15.5.0). This should fix #1405 as well
2022-08-02 02:44:23 +00:00
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"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
}
macOS: Move handling of "universal" apps to electron-packager instead of our own thing (#1443) Supported since [electron-packager 15.5.0](https://github.com/electron/electron-packager/releases/tag/v15.5.0). This should fix #1405 as well
2022-08-02 02:44:23 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"playwright": {
"version": "1.32.1",
"resolved": "https://registry.npmjs.org/playwright/-/playwright-1.32.1.tgz",
"integrity": "sha512-GnEizysWMvoqHC3I9l8+4/ZxeLwLNdJJG76xdKGxzOcIZDcw5RSk/FKrFb5CuA+zcLpjIM2p9eR9Z4CuUDkWXg==",
macOS: Move handling of "universal" apps to electron-packager instead of our own thing (#1443) Supported since [electron-packager 15.5.0](https://github.com/electron/electron-packager/releases/tag/v15.5.0). This should fix #1405 as well
2022-08-02 02:44:23 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
"playwright-core": "1.32.1"
macOS: Move handling of "universal" apps to electron-packager instead of our own thing (#1443) Supported since [electron-packager 15.5.0](https://github.com/electron/electron-packager/releases/tag/v15.5.0). This should fix #1405 as well
2022-08-02 02:44:23 +00:00
},
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"playwright-core": {
"version": "1.32.1",
"resolved": "https://registry.npmjs.org/playwright-core/-/playwright-core-1.32.1.tgz",
"integrity": "sha512-KZYUQC10mXD2Am1rGlidaalNGYk3LU1vZqqNk0gT4XPty1jOqgup8KDP8l2CUlqoNKhXM5IfGjWgW37xvGllBA==",
"dev": true
}
Revert "Major-bump jest to 28": breaks tsc in weird ways, will retry later. This reverts commit bd109099ceb3e13cf95b1d52810e9fe385bfaab7.
2022-05-02 03:51:04 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"plist": {
relock cli
2022-07-23 22:39:04 +00:00
"version": "3.0.6",
"resolved": "https://registry.npmjs.org/plist/-/plist-3.0.6.tgz",
"integrity": "sha512-WiIVYyrp8TD4w8yCvyeIr+lkmrGRd5u0VbRnU+tP/aRLxP/YadJUYOMZJ/6hIa3oUyVCsycXvtNRgd5XBJIbiA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"base64-js": "^1.5.1",
relock cli
2022-07-23 22:39:04 +00:00
"xmlbuilder": "^15.1.1"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"prelude-ls": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.2.1.tgz",
"integrity": "sha512-vkcDPrRZo1QZLbn5RLGPpg/WmIQ65qoWWhcGKf/b5eplkkarX0m9z8ppCat4mlOqUsWpyNuYgO3VRyrYHSzX5g==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"prepend-http": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/prepend-http/-/prepend-http-2.0.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-ravE6m9Atw9Z/jjttRUZ+clIXogdghyZAuWJ3qEzjT+jI/dL1ifAqhZeC5VHzQp1MSt1+jxKkFNemj/iO7tVUA=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"prettier": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "2.8.7",
"resolved": "https://registry.npmjs.org/prettier/-/prettier-2.8.7.tgz",
"integrity": "sha512-yPngTo3aXUUmyuTjeTUT75txrf+aMh9FiD7q9ZE/i6r0bPb22g4FsE6Y338PQX1bmfy08i9QQCB7/rcUAVntfw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"prettier-linter-helpers": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"fast-diff": "^1.1.2"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"pretty-format": {
bump jest **types**, so far it still builds
2022-07-23 22:43:04 +00:00
"version": "28.1.3",
"resolved": "https://registry.npmjs.org/pretty-format/-/pretty-format-28.1.3.tgz",
"integrity": "sha512-8gFb/To0OmxHR9+ZTb14Df2vNxdGCX8g1xWGUTqUw5TiZvcQf5sHKObd5UcPyLLyowNwDAMTF3XWOG1B6mxl1Q==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
bump jest **types**, so far it still builds
2022-07-23 22:43:04 +00:00
"@jest/schemas": "^28.1.3",
Update Electron to 13.5.1; Fix auth manual tests (#1287)
2021-10-03 02:17:06 +00:00
"ansi-regex": "^5.0.1",
Deps bumps: @types/jest, eslint-plugin-prettier
2021-09-20 15:32:47 +00:00
"ansi-styles": "^5.0.0",
bump jest **types**, so far it still builds
2022-07-23 22:43:04 +00:00
"react-is": "^18.0.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"ansi-styles": {
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-5.2.0.tgz",
"integrity": "sha512-Cxwpt2SfTzTtXcfOlzGEee8O+c+MmUgGrNiBcXnuWxuFJHe6a5Hz7qwhwe5OgaSYI0IJvkLqWX1ASG+cJOkEiA==",
"dev": true
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"process-nextick-args": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-2.0.1.tgz",
"integrity": "sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"progress": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/progress/-/progress-2.0.3.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-7PiHtLll5LdnKIMw100I+8xJXR5gW2QwWYkT6iJva0bXitZKa/XMrSbdmg3r2Xnaidz9Qumd0VPaMrZlF9V9sA=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"prompts": {
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"version": "2.4.2",
"resolved": "https://registry.npmjs.org/prompts/-/prompts-2.4.2.tgz",
"integrity": "sha512-NxNv/kLguCA7p3jE8oL2aEBsrJWgAakBpgmgK6lpPWV+WuOmY6r2/zbAVnP+T8bQlA0nzHXSJSJW0Hq7ylaD2Q==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"kleur": "^3.0.3",
"sisteransi": "^1.0.5"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"proto-list": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.2.4",
"resolved": "https://registry.npmjs.org/proto-list/-/proto-list-1.2.4.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-vtK/94akxsTMhe0/cbfpR+syPuszcuwhqVjJq26CuNDgFGj682oRBXOP5MJpv2r7JtE8MsiepGIqvvOTBwn2vA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"optional": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"proxy-from-env": {
Bump axios from 0.x to 1.x. No breaking changes for us, https://github.com/axios/axios/blob/v1.x/CHANGELOG.md#100---2022-10-04
2022-11-07 23:12:12 +00:00
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/proxy-from-env/-/proxy-from-env-1.1.0.tgz",
"integrity": "sha512-D+zkORCbA9f1tdWRK0RaCR3GPv50cMxcrz4X8k5LTSUD1Dkw47mKJEZQNunItRTkWwgtaUSo1RVFRIG9ZXiFYg=="
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"pump": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/pump/-/pump-3.0.0.tgz",
"integrity": "sha512-LwZy+p3SFs1Pytd/jYct4wpv49HiYCqd9Rlc5ZVdk0V+8Yzv6jR5Blk3TRmPL1ft69TxP0IMZGJ+WPFU2BFhww==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"end-of-stream": "^1.1.0",
"once": "^1.3.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"punycode": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/punycode/-/punycode-2.3.0.tgz",
"integrity": "sha512-rRV+zQD8tVFys26lAGR9WUuS4iUAngJScM+ZRSKtvl5tKeZ2t5bvdNFdNHBW9FWR4guGHlgmsZ1G7BSm2wTbuA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"queue-microtask": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.2.3",
"resolved": "https://registry.npmjs.org/queue-microtask/-/queue-microtask-1.2.3.tgz",
"integrity": "sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"randombytes": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/randombytes/-/randombytes-2.1.0.tgz",
"integrity": "sha512-vYl3iOX+4CKUWuxGi9Ukhie6fsqXqS9FE2Zaic4tNFD2N2QQaXOMFbuKK4QmDHC0JO6B1Zp41J0LpT0oR68amQ==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"safe-buffer": "^5.1.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"rcedit": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/rcedit/-/rcedit-3.0.1.tgz",
"integrity": "sha512-XM0Jv40/y4hVAqj/MO70o/IWs4uOsaSoo2mLyk3klFDW+SStLnCtzuQu+1OBTIMGlM8CvaK9ftlYCp6DJ+cMsw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"cross-spawn-windows-exe": "^1.1.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"react-is": {
bump jest **types**, so far it still builds
2022-07-23 22:43:04 +00:00
"version": "18.2.0",
"resolved": "https://registry.npmjs.org/react-is/-/react-is-18.2.0.tgz",
"integrity": "sha512-xWGDIW6x921xtzPkhiULtthJHoJvBbF3q26fzloPCK0hsvxtPVelvftw3zjbHWSkR2km9Z+4uxbDDK/6Zw9B8w==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"read-pkg": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-2.0.0.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-eFIBOPW7FGjzBuk3hdXEuNSiTZS/xEMlH49HxMyzb0hyPfu4EhVjT2DH32K1hSSmVq4sebAWnZuuY5auISUTGA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"load-json-file": "^2.0.0",
"normalize-package-data": "^2.3.2",
"path-type": "^2.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"read-pkg-up": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-2.0.0.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-1orxQfbWGUiTn9XsPlChs6rLie/AV9jwZTGmu2NZw/CUDJQchXJFYE0Fq5j7+n558T1JhDWLdhyd1Zj+wLY//w==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"find-up": "^2.0.0",
"read-pkg": "^2.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"readable-stream": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "3.6.2",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-3.6.2.tgz",
"integrity": "sha512-9u/sniCrY3D5WdsERHzHE4G2YCXqoG5FTHUiCC4SIbr6XcLZBY05ya9EKjYek9O5xOAwjGq+1JdGBAS7Q9ScoA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"inherits": "^2.0.3",
"string_decoder": "^1.1.1",
"util-deprecate": "^1.0.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"readable-web-to-node-stream": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/readable-web-to-node-stream/-/readable-web-to-node-stream-3.0.2.tgz",
"integrity": "sha512-ePeK6cc1EcKLEhJFt/AebMCLL+GgSKhuygrZ/GLaKZYEecIgIECf4UaUuaByiGtzckwR4ain9VzUh95T1exYGw==",
"requires": {
"readable-stream": "^3.6.0"
}
},
"rechoir": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.7.1",
"resolved": "https://registry.npmjs.org/rechoir/-/rechoir-0.7.1.tgz",
"integrity": "sha512-/njmZ8s1wVeR6pjTZ+0nCnv8SpZNRMT2D1RLOJQESlYFDBvwpTA4KWJpZ+sBJ4+vhjILRcK7JIFdGCdxEAAitg==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"resolve": "^1.9.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"require-directory": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/require-directory/-/require-directory-2.1.1.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-fGxEI7+wsG9xrvdjsrlmL22OMTTiHRwAMroiEeMgq8gzoLC/PQr7RsRDSTLUg/bZAZtF+TVIkHc6/4RIKrui+Q=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"resolve": {
Relock dependencies
2022-06-27 19:49:33 +00:00
"version": "1.22.1",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.22.1.tgz",
"integrity": "sha512-nBpuuYuY5jFsli/JIs1oldw6fOQCBioohqWZg/2hiaOybXOft4lonv85uDOKXdf8rhyK159cxU5cDcK/NKk8zw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock dependencies
2022-06-27 19:49:33 +00:00
"is-core-module": "^2.9.0",
Bump default Electron from 16.0.5 to 16.0.6 https://github.com/electron/electron/releases/tag/v16.0.6
2022-01-06 14:43:10 +00:00
"path-parse": "^1.0.7",
"supports-preserve-symlinks-flag": "^1.0.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"resolve-cwd": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/resolve-cwd/-/resolve-cwd-3.0.0.tgz",
"integrity": "sha512-OrZaX2Mb+rJCpH/6CpSqt9xFVpN++x01XnN2ie9g6P5/3xelLAkXWVADpdz1IHD/KFfEXyE6V0U01OQ3UO2rEg==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"resolve-from": "^5.0.0"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"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
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"resolve-from": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-4.0.0.tgz",
"integrity": "sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"resolve.exports": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/resolve.exports/-/resolve.exports-1.1.1.tgz",
"integrity": "sha512-/NtpHNDN7jWhAaQ9BvBUYZ6YTXsRBgfqWFWP7BZBaoMJO/I3G5OFzvTuWNlZC3aPjins1F+TNrLKsGbH4rfsRQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"responselike": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/responselike/-/responselike-1.0.2.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-/Fpe5guzJk1gPqdJLJR5u7eG/gNY4nImjbRDaVWVMRhne55TCmj2i9Q+54PBRfatRC8v/rIiv9BN0pMd9OV5EQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"lowercase-keys": "^1.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"reusify": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/reusify/-/reusify-1.0.4.tgz",
"integrity": "sha512-U9nH88a3fc/ekCF1l0/UP1IosiuIjyTh7hBvXVMHYgVcfGvt897Xguj2UOLDeI5BG2m7/uwyaLVT6fbtCwTyzw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"rimraf": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-3.0.2.tgz",
"integrity": "sha512-JZkJMZkAGFFPP2YqXZXPbMlMBgsxzE8ILs4lMIX/2o0L9UBw9O/Y3o6wFw/i9YLapcUJWwqbi3kdxIPdC62TIA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
"glob": "^7.1.3"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"roarr": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.15.4",
"resolved": "https://registry.npmjs.org/roarr/-/roarr-2.15.4.tgz",
"integrity": "sha512-CHhPh+UNHD2GTXNYhPWLnU8ONHdI+5DI+4EYIAOaiD63rHeYlZvyh8P+in5999TTSFgUYuKUAjzRI4mdh/p+2A==",
"optional": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"boolean": "^3.0.1",
"detect-node": "^2.0.4",
"globalthis": "^1.0.1",
"json-stringify-safe": "^5.0.1",
"semver-compare": "^1.0.0",
"sprintf-js": "^1.1.2"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"run-parallel": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"queue-microtask": "^1.2.2"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"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=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"sanitize-filename": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.6.3",
"resolved": "https://registry.npmjs.org/sanitize-filename/-/sanitize-filename-1.6.3.tgz",
"integrity": "sha512-y/52Mcy7aw3gRm7IrcGDFx/bCk4AhRh2eI9luHOQM86nZsqwiRkkq2GekHXBBD+SmPidc8i2PqtYZl+pWJ8Oeg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"truncate-utf8-bytes": "^1.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"schema-utils": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/schema-utils/-/schema-utils-3.1.1.tgz",
"integrity": "sha512-Y5PQxS4ITlC+EahLuXaY86TXfR7Dc5lw294alXOq86JAHCihAIZfqv8nNCWvaEJvaC51uN9hbLGeV0cFBdH+Fw==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/json-schema": "^7.0.8",
"ajv": "^6.12.5",
"ajv-keywords": "^3.5.2"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"semver": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "7.3.8",
"resolved": "https://registry.npmjs.org/semver/-/semver-7.3.8.tgz",
"integrity": "sha512-NB1ctGL5rlHrPJtFDVIVzTyQylMLu9N9VICA6HSFJo8MCGVTMW6gfpicwKmmK/dAjTOrqu5l63JJOpDSrAis3A==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"lru-cache": "^6.0.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"semver-compare": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/semver-compare/-/semver-compare-1.0.0.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-YM3/ITh2MJ5MtzaM429anh+x2jiLVjqILF4m4oyQB18W7Ggea7BfqdH/wGMK7dDiMghv/6WG7znWMwUDzJiXow==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"optional": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"serialize-error": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "7.0.1",
"resolved": "https://registry.npmjs.org/serialize-error/-/serialize-error-7.0.1.tgz",
"integrity": "sha512-8I8TjW5KMOKsZQTvoxjuSIa7foAwPWGOts+6o7sgjz41/qMD9VQHEDxi6PBvK2l0MXUmqZyNpUK+T2tQaaElvw==",
"optional": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"type-fest": "^0.13.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"serialize-javascript": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "6.0.1",
"resolved": "https://registry.npmjs.org/serialize-javascript/-/serialize-javascript-6.0.1.tgz",
"integrity": "sha512-owoXEFjWRllis8/M1Q+Cw5k8ZH40e3zhp/ovX+Xr/vi1qj6QesbyXXViFbpNvWvPNAD62SutwEXavefrLJWj7w==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"randombytes": "^2.1.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"shallow-clone": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/shallow-clone/-/shallow-clone-3.0.1.tgz",
"integrity": "sha512-/6KqX+GVUdqPuPPd2LxDDxzX6CAbjJehAAOKlNpqqUpAqPM6HeL8f+o3a+JsyGjn2lv0WY8UsTgUJjU9Ok55NA==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"kind-of": "^6.0.2"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"shebang-command": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/shebang-command/-/shebang-command-2.0.0.tgz",
"integrity": "sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"shebang-regex": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"shebang-regex": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/shebang-regex/-/shebang-regex-3.0.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"signal-exit": {
Relock dependencies
2022-02-06 22:47:06 +00: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==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"sisteransi": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/sisteransi/-/sisteransi-1.0.5.tgz",
"integrity": "sha512-bLGGlR1QxBcynn2d5YmDX4MGjlZvy2MRBDRNHLJ8VI6l6+9FUiyTFNJ0IveOSP0bcXgVDPRcfGqA0pjaqUpfVg==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"slash": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/slash/-/slash-3.0.0.tgz",
"integrity": "sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"source-map": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.6.1",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.6.1.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"source-map-support": {
Relock dependencies
2021-11-22 21:03:07 +00:00
"version": "0.5.21",
"resolved": "https://registry.npmjs.org/source-map-support/-/source-map-support-0.5.21.tgz",
"integrity": "sha512-uBHU3L3czsIyYXKX88fdrGovxdSCoTGDRZ6SYXtSRxLZUzHg5P/66Ht6uoUlHu9EZod+inXhKo3qQgwXUT/y1w==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"buffer-from": "^1.0.0",
"source-map": "^0.6.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"spdx-correct": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-3.2.0.tgz",
"integrity": "sha512-kN9dJbvnySHULIluDHy32WHRUu3Og7B9sbY7tsFLctQkIqnMh3hErYgdMjTYuqmcXX+lK5T1lnUt3G7zNswmZA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"spdx-expression-parse": "^3.0.0",
"spdx-license-ids": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"spdx-exceptions": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-2.3.0.tgz",
"integrity": "sha512-/tTrYOC7PPI1nUAgx34hUpqXuyJG+DTHJTnIULG4rDygi4xu/tfgmq1e1cIRwRzwZgo4NLySi+ricLkZkw4i5A=="
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"spdx-expression-parse": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-3.0.1.tgz",
"integrity": "sha512-cbqHunsQWnJNE6KhVSMsMeH5H/L9EpymbzqTQ3uLwNCLZ1Q481oWaofqH7nO6V07xlXwY6PhQdQ2IedWx/ZK4Q==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"spdx-exceptions": "^2.1.0",
"spdx-license-ids": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"spdx-license-ids": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "3.0.13",
"resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-3.0.13.tgz",
"integrity": "sha512-XkD+zwiqXHikFZm4AX/7JSCXA98U5Db4AFd5XUg/+9UNtnH75+Z9KxtpYiJZx36mUDVOwH83pl7yvCer6ewM3w=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"sprintf-js": {
Bump to eslint 8 https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0
2021-11-01 19:47:46 +00:00
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.1.2.tgz",
"integrity": "sha512-VE0SOVEHCk7Qc8ulkWw3ntAzXuqf7S2lvwQaDLRnUeIEaKNQJzV6BwmLKhOqT61aGhfUMrXeaBk+oDGCzvhcug==",
"optional": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"stack-utils": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "2.0.6",
"resolved": "https://registry.npmjs.org/stack-utils/-/stack-utils-2.0.6.tgz",
"integrity": "sha512-XlkWvfIm6RmsWtNJx+uqtKLS8eqFbxUg0ZzLXqY0caEy9l7hruX8IpiDnjsLavoBgqCCR71TqWO8MaXYheJ3RQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"escape-string-regexp": "^2.0.0"
},
"dependencies": {
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00: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
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"string-length": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.0.2",
"resolved": "https://registry.npmjs.org/string-length/-/string-length-4.0.2.tgz",
"integrity": "sha512-+l6rNN5fYHNhZZy41RXsYptCjA2Igmq4EG7kZAYFQI1E1VTXarr6ZPXBg6eq7Y6eK4FEhY6AJlyuFIb/v/S0VQ==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"char-regex": "^1.0.2",
"strip-ansi": "^6.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"string-width": {
Actually actually (TM) include lockfile in npm artifacts Previous attempt failed by design of `npm pack` / `npm publish`, as documented at https://docs.npmjs.com/cli/v6/configuring-npm/package-lock-json : > One key detail about package-lock.json is that it cannot be published, > and it will be ignored if found in any place other than the toplevel > package. It shares a format with npm-shrinkwrap.json, which is > essentially the same file, but allows publication. > > This is not recommended unless deploying a CLI tool or otherwise using > the publication process for producing production packages. , and we are a CLI tool. Switching to shrinkwrap.
2021-09-25 02:38:26 +00: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==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"emoji-regex": "^8.0.0",
"is-fullwidth-code-point": "^3.0.0",
Actually actually (TM) include lockfile in npm artifacts Previous attempt failed by design of `npm pack` / `npm publish`, as documented at https://docs.npmjs.com/cli/v6/configuring-npm/package-lock-json : > One key detail about package-lock.json is that it cannot be published, > and it will be ignored if found in any place other than the toplevel > package. It shares a format with npm-shrinkwrap.json, which is > essentially the same file, but allows publication. > > This is not recommended unless deploying a CLI tool or otherwise using > the publication process for producing production packages. , and we are a CLI tool. Switching to shrinkwrap.
2021-09-25 02:38:26 +00:00
"strip-ansi": "^6.0.1"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"string_decoder": {
"version": "1.3.0",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-1.3.0.tgz",
"integrity": "sha512-hkRX8U1WjJFd8LsDJ2yQ/wWWxaopEsABU1XfkM8A+j0+85JAGppt16cr1Whg6KIbb4okU6Mql6BOj+uup/wKeA==",
"requires": {
"safe-buffer": "~5.2.0"
}
},
"strip-ansi": {
Actually actually (TM) include lockfile in npm artifacts Previous attempt failed by design of `npm pack` / `npm publish`, as documented at https://docs.npmjs.com/cli/v6/configuring-npm/package-lock-json : > One key detail about package-lock.json is that it cannot be published, > and it will be ignored if found in any place other than the toplevel > package. It shares a format with npm-shrinkwrap.json, which is > essentially the same file, but allows publication. > > This is not recommended unless deploying a CLI tool or otherwise using > the publication process for producing production packages. , and we are a CLI tool. Switching to shrinkwrap.
2021-09-25 02:38:26 +00:00
"version": "6.0.1",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
"integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Actually actually (TM) include lockfile in npm artifacts Previous attempt failed by design of `npm pack` / `npm publish`, as documented at https://docs.npmjs.com/cli/v6/configuring-npm/package-lock-json : > One key detail about package-lock.json is that it cannot be published, > and it will be ignored if found in any place other than the toplevel > package. It shares a format with npm-shrinkwrap.json, which is > essentially the same file, but allows publication. > > This is not recommended unless deploying a CLI tool or otherwise using > the publication process for producing production packages. , and we are a CLI tool. Switching to shrinkwrap.
2021-09-25 02:38:26 +00:00
"ansi-regex": "^5.0.1"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"strip-bom": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-3.0.0.tgz",
"integrity": "sha512-vavAMRXOgBVNF6nyEEmL3DBK19iRpDcoIwW+swQ+CbGiu7lju6t+JklA1MHweoWtadgt4ISVUsXLyDq34ddcwA=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"strip-final-newline": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/strip-final-newline/-/strip-final-newline-2.0.0.tgz",
"integrity": "sha512-BrpvfNAE3dcvq7ll3xVumzjKjZQ5tI1sEUIKr3Uoks0XUl45St3FlatVqef9prk4jRDzhW6WZg+3bk93y6pLjA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"strip-json-comments": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00: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==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"strip-outer": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/strip-outer/-/strip-outer-1.0.1.tgz",
"integrity": "sha512-k55yxKHwaXnpYGsOzg4Vl8+tDrWylxDEpknGjhTiZB8dFRU5rTo9CAzeycivxV3s+zlTKwrs6WxMxR95n26kwg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"escape-string-regexp": "^1.0.2"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"escape-string-regexp": {
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz",
"integrity": "sha512-vbRorB5FUQWvla16U8R/qgaFIya2qGzwDrNmCZuYKrbdSUMG6I1ZCGQRefkRVhuOkIGVne7BQ35DSfo1qvJqFg=="
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"strtok3": {
Relock dependencies
2022-02-06 22:47:06 +00:00
"version": "6.3.0",
"resolved": "https://registry.npmjs.org/strtok3/-/strtok3-6.3.0.tgz",
"integrity": "sha512-fZtbhtvI9I48xDSywd/somNqgUHl2L2cstmXCCif0itOf96jeW18MBSyrLuNicYQVkvpOxkZtkzujiTJ9LW5Jw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@tokenizer/token": "^0.3.0",
Relock dependencies
2022-02-06 22:47:06 +00:00
"peek-readable": "^4.1.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"sumchecker": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/sumchecker/-/sumchecker-3.0.1.tgz",
"integrity": "sha512-MvjXzkz/BOfyVDkG0oFOtBxHX2u3gKbMHIF/dXblZsgD3BWOFLmHovIpZY7BykJdAjcqRCBi1WYBNdEC9yI7vg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"debug": "^4.1.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"supports-color": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"has-flag": "^4.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"supports-hyperlinks": {
relock cli
2022-09-18 02:30:33 +00:00
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/supports-hyperlinks/-/supports-hyperlinks-2.3.0.tgz",
"integrity": "sha512-RpsAZlpWcDwOPQA22aCH4J0t7L8JmAvsCxfOSEwm7cQs3LshN36QaTkwd70DnBOXDWGssw2eUoc8CaRWT0XunA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"has-flag": "^4.0.0",
"supports-color": "^7.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"supports-preserve-symlinks-flag": {
Bump default Electron from 16.0.5 to 16.0.6 https://github.com/electron/electron/releases/tag/v16.0.6
2022-01-06 14:43:10 +00:00
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/supports-preserve-symlinks-flag/-/supports-preserve-symlinks-flag-1.0.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-ot0WnXS9fgdkgIcePe6RHNk1WA8+muPa6cSjeR3V8K27q9BB1rTE3R1p7Hv0z1ZyAc8s6Vvv8DIyWf681MAt0w=="
Bump default Electron from 16.0.5 to 16.0.6 https://github.com/electron/electron/releases/tag/v16.0.6
2022-01-06 14:43:10 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"tapable": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.2.1",
"resolved": "https://registry.npmjs.org/tapable/-/tapable-2.2.1.tgz",
"integrity": "sha512-GNzQvQTOIP6RyTfE2Qxb8ZVlNmw0n88vp1szwWRimP02mnTsx3Wtn5qRdqY9w2XduFNUgvOwhNnQsjwCp+kqaQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"terminal-link": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/terminal-link/-/terminal-link-2.1.1.tgz",
"integrity": "sha512-un0FmiRUQNr5PJqy9kP7c40F5BOfpGlYTrxonDChEZB7pzZxRNp/bt+ymiy9/npwXya9KH99nJ/GXFIiUkYGFQ==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"ansi-escapes": "^4.2.1",
"supports-hyperlinks": "^2.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"terser": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "5.16.8",
"resolved": "https://registry.npmjs.org/terser/-/terser-5.16.8.tgz",
"integrity": "sha512-QI5g1E/ef7d+PsDifb+a6nnVgC4F22Bg6T0xrBrz6iloVB4PUkkunp6V8nzoOOZJIzjWVdAGqCdlKlhLq/TbIA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock dependencies
2022-05-30 13:42:40 +00:00
"@jridgewell/source-map": "^0.3.2",
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-03-21 03:32:19 +00:00
"acorn": "^8.5.0",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"commander": "^2.20.0",
"source-map-support": "~0.5.20"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"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
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"terser-webpack-plugin": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "5.3.7",
"resolved": "https://registry.npmjs.org/terser-webpack-plugin/-/terser-webpack-plugin-5.3.7.tgz",
"integrity": "sha512-AfKwIktyP7Cu50xNjXF/6Qb5lBNzYaWpU6YfoX3uZicTx0zTy0stDDCsvjDapKsSDvOeWo5MEq4TmdBy2cNoHw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"@jridgewell/trace-mapping": "^0.3.17",
Relock dependencies
2022-02-06 22:47:06 +00:00
"jest-worker": "^27.4.5",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"schema-utils": "^3.1.1",
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"serialize-javascript": "^6.0.1",
"terser": "^5.16.5"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"jest-worker": {
"version": "27.5.1",
"resolved": "https://registry.npmjs.org/jest-worker/-/jest-worker-27.5.1.tgz",
"integrity": "sha512-7vuh85V5cdDofPyxn58nrPjBktZo0u9x1g8WtjQol+jZDaE+fhN+cIvTj11GndBnMnyfrUOG1sZQxCdjKh+DKg==",
"dev": true,
"requires": {
"@types/node": "*",
"merge-stream": "^2.0.0",
"supports-color": "^8.0.0"
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"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,
"requires": {
"has-flag": "^4.0.0"
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"test-exclude": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "6.0.0",
"resolved": "https://registry.npmjs.org/test-exclude/-/test-exclude-6.0.0.tgz",
"integrity": "sha512-cAGWPIyOHU6zlmg88jwm7VRyXnMN7iV68OGAbYDk/Mh/xC/pzVPlQtY6ngoIH/5/tciuhGfvESU8GrHrcxD56w==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@istanbuljs/schema": "^0.1.2",
"glob": "^7.1.4",
"minimatch": "^3.0.4"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"text-table": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.2.0",
"resolved": "https://registry.npmjs.org/text-table/-/text-table-0.2.0.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-N+8UisAXDGk8PFXP4HAzVR9nbfmVJ3zYLAWiTIoqC5v5isinhr+r5uaO8+7r3BMfuNIufIsA7RdpVgacC2cSpw==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"tmp": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.2.1",
"resolved": "https://registry.npmjs.org/tmp/-/tmp-0.2.1.tgz",
"integrity": "sha512-76SUhtfqR2Ijn+xllcI5P1oyannHNHByD80W1q447gU3mp9G9PSpGdWmjUOHRDPiHYacIk66W7ubDTuPF3BEtQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"rimraf": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"tmpl": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/tmpl/-/tmpl-1.0.5.tgz",
"integrity": "sha512-3f0uOEAQwIqGuWW2MVzYg8fV/QNnc/IpuJNG837rLuczAaLVHslWHZQj4IGiEl5Hs3kkbhwL9Ab7Hrsmuj+Smw==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"to-fast-properties": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/to-fast-properties/-/to-fast-properties-2.0.0.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-/OaKK0xYrs3DmxRYqL/yDc+FxFUVYhDlXMhRmv3z915w2HF1tnN1omB354j8VUGO/hbRzyD6Y3sA7v7GS/ceog==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"to-readable-stream": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/to-readable-stream/-/to-readable-stream-1.0.0.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-Iq25XBt6zD5npPhlLVXGFN3/gyR2/qODcKNNyTMd4vbm39HUaOiAM4PMq0eMVC/Tkxz+Zjdsc55g9yyz+Yq00Q=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"to-regex-range": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"is-number": "^7.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"token-types": {
relock cli
2022-08-29 00:41:15 +00:00
"version": "4.2.1",
"resolved": "https://registry.npmjs.org/token-types/-/token-types-4.2.1.tgz",
"integrity": "sha512-6udB24Q737UD/SDsKAHI9FCRP7Bqc9D/MQUV02ORQg5iskjtLJlZJNdN4kKtcdtwCeWIwIHDGaUsTsCCAa8sFQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@tokenizer/token": "^0.3.0",
"ieee754": "^1.2.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"trim-repeated": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/trim-repeated/-/trim-repeated-1.0.0.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-pkonvlKk8/ZuR0D5tLW8ljt5I8kmxp2XKymhepUeOdCEfKpZaktSArkLHZt76OB1ZvO9bssUsDty4SWhLvZpLg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"escape-string-regexp": "^1.0.2"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"escape-string-regexp": {
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz",
"integrity": "sha512-vbRorB5FUQWvla16U8R/qgaFIya2qGzwDrNmCZuYKrbdSUMG6I1ZCGQRefkRVhuOkIGVne7BQ35DSfo1qvJqFg=="
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"truncate-utf8-bytes": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/truncate-utf8-bytes/-/truncate-utf8-bytes-1.0.2.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-95Pu1QXQvruGEhv62XCMO3Mm90GscOCClvrIUwCM0PYOXK3kaF3l3sIHxx71ThJfcbM2O5Au6SO3AWCSEfW4mQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"utf8-byte-length": "^1.0.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"ts-loader": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "9.4.2",
"resolved": "https://registry.npmjs.org/ts-loader/-/ts-loader-9.4.2.tgz",
"integrity": "sha512-OmlC4WVmFv5I0PpaxYb+qGeGOdm5giHU7HwDDUjw59emP2UYMHy9fFSDcYgSNoH8sXcj4hGCSEhlDZ9ULeDraA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"chalk": "^4.1.0",
"enhanced-resolve": "^5.0.0",
"micromatch": "^4.0.0",
"semver": "^7.3.4"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"tslib": {
Relock dependencies
2022-06-27 19:49:33 +00:00
"version": "1.14.1",
"resolved": "https://registry.npmjs.org/tslib/-/tslib-1.14.1.tgz",
"integrity": "sha512-Xni35NKzjgMrwevysHTCArtLDpPvye8zV/0E4EyYn43P7/7qvQwPh9BGkHewbMulVntbigmcT7rdX3BNo9wRJg==",
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"tsutils": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.21.0",
"resolved": "https://registry.npmjs.org/tsutils/-/tsutils-3.21.0.tgz",
"integrity": "sha512-mHKK3iUXL+3UF6xL5k0PEhKRUBKPBCv/+RkEOpjRWxxx27KKRBmmA60A9pgOUvMi8GKhRMPEmjBRPzs2W7O1OA==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"tslib": "^1.8.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"tunnel": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.0.6",
"resolved": "https://registry.npmjs.org/tunnel/-/tunnel-0.0.6.tgz",
"integrity": "sha512-1h/Lnq9yajKY2PEbBadPXj3VxsDDu844OnaAo52UVmIzIvwwtBPIuNvkjuzBlTWpfJyUbG3ez0KSBibQkj4ojg==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"optional": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"type-check": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "0.4.0",
"resolved": "https://registry.npmjs.org/type-check/-/type-check-0.4.0.tgz",
"integrity": "sha512-XleUoc9uwGXqjWwXaUTZAmzMcFZ5858QA2vvx1Ur5xIcixXIP+8LnFDgRplU30us6teqdlskFfu+ae4K79Ooew==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"prelude-ls": "^1.2.1"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"type-detect": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.0.8",
"resolved": "https://registry.npmjs.org/type-detect/-/type-detect-4.0.8.tgz",
"integrity": "sha512-0fr/mIH1dlO+x7TlcMy+bIDqKPsw/70tVyeHW787goQjhmqaZe10uwLujubK9q9Lg6Fiho1KUKDYz0Z7k7g5/g==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"type-fest": {
"version": "0.13.1",
"resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.13.1.tgz",
"integrity": "sha512-34R7HTnG0XIJcBSn5XhDd7nNFPRcXYRZrBB2O2jdKqYODldSzBAqzsWoZYYvduky73toYS/ESqxPvkDf/F0XMg==",
"optional": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"typedarray": {
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"version": "0.0.6",
"resolved": "https://registry.npmjs.org/typedarray/-/typedarray-0.0.6.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-/aCDEGatGvZ2BIk+HmLf4ifCJFwvKFNb9/JeZPMulfgFracn9QFcAf5GO8B/mweUjSoblS5In0cWhqpfs/5PQA==",
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"typescript": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "4.9.5",
"resolved": "https://registry.npmjs.org/typescript/-/typescript-4.9.5.tgz",
"integrity": "sha512-1FXk9E2Hm+QzZQ7z+McJiHL4NW1F2EzMu9Nq9i3zAaGqibafqYwCVU6WyWAuyQRRzOlxou8xZSyXLEN8oKj24g==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"universalify": {
"version": "0.1.2",
"resolved": "https://registry.npmjs.org/universalify/-/universalify-0.1.2.tgz",
"integrity": "sha512-rBJeI5CXAlmy1pV+617WB9J63U6XcazHHF2f2dbJix4XzpUF0RS3Zbj0FGIOCAva5P/d/GBOYaACQ1w+0azUkg=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"update-browserslist-db": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"version": "1.0.10",
"resolved": "https://registry.npmjs.org/update-browserslist-db/-/update-browserslist-db-1.0.10.tgz",
"integrity": "sha512-OztqDenkfFkbSG+tRxBeAnCVPckDBcvibKd35yDONx6OU8N7sqgwc7rCbkJ/WcYtVRZ4ba68d6byhC21GFh7sQ==",
Relock dependencies
2022-06-27 19:49:33 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock dependencies
2022-06-27 19:49:33 +00:00
"escalade": "^3.1.1",
"picocolors": "^1.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"uri-js": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "4.4.1",
"resolved": "https://registry.npmjs.org/uri-js/-/uri-js-4.4.1.tgz",
"integrity": "sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"punycode": "^2.1.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"url-parse-lax": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/url-parse-lax/-/url-parse-lax-3.0.0.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-NjFKA0DidqPa5ciFcSrXnAltTtzz84ogy+NebPvfEgAck0+TNg4UJ4IN+fB7zRZfbgUf0syOo9MDxFkDSMuFaQ==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"prepend-http": "^2.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"utf8-byte-length": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/utf8-byte-length/-/utf8-byte-length-1.0.4.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-4+wkEYLBbWxqTahEsWrhxepcoVOJ+1z5PGIjPZxRkytcdSUaNjIjBM7Xn8E+pdSuV7SzvWovBFA54FO0JSoqhA=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"util-deprecate": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"v8-to-istanbul": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "9.1.0",
"resolved": "https://registry.npmjs.org/v8-to-istanbul/-/v8-to-istanbul-9.1.0.tgz",
"integrity": "sha512-6z3GW9x8G1gd+JIIgQQQxXuiJtCXeAjp6RaPEPLv62mH3iPHPxV6W3robxtCzNErRo6ZwTmzWhsbNvjyEBKzKA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"@jridgewell/trace-mapping": "^0.3.12",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@types/istanbul-lib-coverage": "^2.0.1",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"convert-source-map": "^1.6.0"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"validate-npm-package-license": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "3.0.4",
"resolved": "https://registry.npmjs.org/validate-npm-package-license/-/validate-npm-package-license-3.0.4.tgz",
"integrity": "sha512-DpKm2Ui/xN7/HQKCtpZxoRWBhZ9Z0kqtygG8XCgNQ8ZlDnxuQmWhj566j8fN4Cu3/JmbhsDo7fcAJq4s9h27Ew==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"spdx-correct": "^3.0.0",
"spdx-expression-parse": "^3.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"walker": {
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"version": "1.0.8",
"resolved": "https://registry.npmjs.org/walker/-/walker-1.0.8.tgz",
"integrity": "sha512-ts/8E8l5b7kY0vlWLewOkDXMmPdLcVV4GmOQLyxuSswIJsweeFZtAsMF7k1Nszz+TYBQrlYRmzOnr398y1JemQ==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"makeerror": "1.0.12"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"watchpack": {
Relock dependencies
2022-06-27 19:49:33 +00:00
"version": "2.4.0",
"resolved": "https://registry.npmjs.org/watchpack/-/watchpack-2.4.0.tgz",
"integrity": "sha512-Lcvm7MGST/4fup+ifyKi2hjyIAwcdI4HRgtvTpIUxBRhB+RFtUh8XtDOxUfctVCnhVi+QQj49i91OyvzkJl6cg==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"glob-to-regexp": "^0.4.1",
"graceful-fs": "^4.1.2"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"webpack": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "5.76.3",
"resolved": "https://registry.npmjs.org/webpack/-/webpack-5.76.3.tgz",
"integrity": "sha512-18Qv7uGPU8b2vqGeEEObnfICyw2g39CHlDEK4I7NK13LOur1d0HGmGNKGT58Eluwddpn3oEejwvBPoP4M7/KSA==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Upgrade dependencies lockfiles with the usual `npm run relock` . No major/breaking chages this time.
2022-03-21 03:32:19 +00:00
"@types/eslint-scope": "^3.7.3",
"@types/estree": "^0.0.51",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@webassemblyjs/ast": "1.11.1",
"@webassemblyjs/wasm-edit": "1.11.1",
"@webassemblyjs/wasm-parser": "1.11.1",
Relock deps to get gitcloud 0.2.4 with "fetch" log fix https://github.com/nativefier/gitcloud-client/pull/4
2022-07-30 17:27:39 +00:00
"acorn": "^8.7.1",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"acorn-import-assertions": "^1.7.6",
"browserslist": "^4.14.5",
"chrome-trace-event": "^1.0.2",
Relock deps to get gitcloud 0.2.4 with "fetch" log fix https://github.com/nativefier/gitcloud-client/pull/4
2022-07-30 17:27:39 +00:00
"enhanced-resolve": "^5.10.0",
Actually actually (TM) include lockfile in npm artifacts Previous attempt failed by design of `npm pack` / `npm publish`, as documented at https://docs.npmjs.com/cli/v6/configuring-npm/package-lock-json : > One key detail about package-lock.json is that it cannot be published, > and it will be ignored if found in any place other than the toplevel > package. It shares a format with npm-shrinkwrap.json, which is > essentially the same file, but allows publication. > > This is not recommended unless deploying a CLI tool or otherwise using > the publication process for producing production packages. , and we are a CLI tool. Switching to shrinkwrap.
2021-09-25 02:38:26 +00:00
"es-module-lexer": "^0.9.0",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"eslint-scope": "5.1.1",
"events": "^3.2.0",
"glob-to-regexp": "^0.4.1",
Relock dependencies
2022-02-06 22:47:06 +00:00
"graceful-fs": "^4.2.9",
Relock dependencies
2022-05-30 13:42:40 +00:00
"json-parse-even-better-errors": "^2.3.1",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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",
Relock deps to get gitcloud 0.2.4 with "fetch" log fix https://github.com/nativefier/gitcloud-client/pull/4
2022-07-30 17:27:39 +00:00
"watchpack": "^2.4.0",
Relock dependencies
2022-02-06 22:47:06 +00:00
"webpack-sources": "^3.2.3"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"webpack-cli": {
Relock dependencies
2022-06-27 19:49:33 +00:00
"version": "4.10.0",
"resolved": "https://registry.npmjs.org/webpack-cli/-/webpack-cli-4.10.0.tgz",
"integrity": "sha512-NLhDfH/h4O6UOy+0LSso42xvYypClINuMNBVVzX4vX98TmTaTUxwRbXdhucbFMd2qLaCTcLq/PdYrvi8onw90w==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"@discoveryjs/json-ext": "^0.5.0",
Relock dependencies
2022-06-27 19:49:33 +00:00
"@webpack-cli/configtest": "^1.2.0",
"@webpack-cli/info": "^1.5.0",
"@webpack-cli/serve": "^1.7.0",
Bump default Electron to 13.6.1, with security fixes - 13.5.2: https://github.com/electron/electron/releases/tag/v13.5.2 - 13.6.0: https://github.com/electron/electron/releases/tag/v13.6.0 - 13.6.1: https://github.com/electron/electron/releases/tag/v13.6.1
2021-11-01 19:34:19 +00:00
"colorette": "^2.0.14",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"commander": "^7.0.0",
Relock dependencies
2022-06-27 19:49:33 +00:00
"cross-spawn": "^7.0.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"fastest-levenshtein": "^1.0.12",
"import-local": "^3.0.2",
"interpret": "^2.2.0",
"rechoir": "^0.7.0",
"webpack-merge": "^5.7.3"
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"commander": {
"version": "7.2.0",
"resolved": "https://registry.npmjs.org/commander/-/commander-7.2.0.tgz",
"integrity": "sha512-QrWXB+ZQSVPmIWIhtEO9H+gwHaMGYiF5ChvoJ+K9ZGHG/sVsa6yiesAD1GC/x46sET00Xlwo1u49RVVVzvcSkw==",
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"webpack-merge": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "5.8.0",
"resolved": "https://registry.npmjs.org/webpack-merge/-/webpack-merge-5.8.0.tgz",
"integrity": "sha512-/SaI7xY0831XwP6kzuwhKWVKDP9t1QY1h65lAFLbZqMPIuYcD9QAW4u9STIbU9kaJbPBB/geU/gLr1wDjOhQ+Q==",
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"clone-deep": "^4.0.1",
"wildcard": "^2.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"webpack-sources": {
Relock dependencies
2022-02-06 22:47:06 +00: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==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"which": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/which/-/which-2.0.2.tgz",
"integrity": "sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"isexe": "^2.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"wildcard": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/wildcard/-/wildcard-2.0.0.tgz",
"integrity": "sha512-JcKqAHLPxcdb9KM49dufGXn2x3ssnfjbcaQdLlfZsL9rH9wgDQjUtDxbo8NE0F6SFvydeu1VhZe7hZuHsB2/pw==",
"dev": true
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"word-wrap": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"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==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"wrap-ansi": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-7.0.0.tgz",
"integrity": "sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"ansi-styles": "^4.0.0",
"string-width": "^4.1.0",
"strip-ansi": "^6.0.0"
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"wrappy": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.2.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"write-file-atomic": {
relock cli
2022-08-29 00:41:15 +00:00
"version": "4.0.2",
"resolved": "https://registry.npmjs.org/write-file-atomic/-/write-file-atomic-4.0.2.tgz",
"integrity": "sha512-7KxauUdBmSdWnmpaGFg+ppNjKF8uNLry8LyzjauQDOVONfFLNKrKvQOxZ/VuTIcS/gge/YNahf5RIIQWTSarlg==",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"dev": true,
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"imurmurhash": "^0.1.4",
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"signal-exit": "^3.0.7"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"xmlbuilder": {
relock cli
2022-07-23 22:39:04 +00:00
"version": "15.1.1",
"resolved": "https://registry.npmjs.org/xmlbuilder/-/xmlbuilder-15.1.1.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-yMqGBqtXyeN1e3TGYvgNgDVZ3j84W4cwkOXQswghol6APgZWaff9lnbvN7MHYJOiXsvGPXtjTYJEiC9J2wv9Eg=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"y18n": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "5.0.8",
"resolved": "https://registry.npmjs.org/y18n/-/y18n-5.0.8.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-0pfFzegeDWJHJIAmTLRP2DwHjdF5s7jo9tuztdQxAhINCdvS+3nGINqPd00AphqJR/0LhANUS6/+7SCb98YOfA=="
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"yallist": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/yallist/-/yallist-4.0.0.tgz",
"integrity": "sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A=="
Add playwright integration testing to the app (PR #1397) This PR allows us to code playwright integration tests that can potentially replace some of our manual tests and allow us automated testing of the app itself. Current technical limitations: * No app level keyboard simulation support (e.g, zoom in, zoom out, etc.) * No code coverage support, so even though we are testing the app, the code coverage does not reflect this fact
2022-04-21 02:03:49 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"yargs": {
Update outdated shrinkwrap files
2023-03-24 20:19:05 +00:00
"version": "17.7.1",
"resolved": "https://registry.npmjs.org/yargs/-/yargs-17.7.1.tgz",
"integrity": "sha512-cwiTb08Xuv5fqF4AovYacTFNxk62th7LKJ6BL9IGUpTJrWoU7/7WdQGTP2SjKf1dUNBGzDd28p/Yfs/GI6JrLw==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"cliui": "^8.0.1",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"escalade": "^3.1.1",
"get-caller-file": "^2.0.5",
"require-directory": "^2.1.1",
relock dependencies
2021-12-06 20:56:02 +00:00
"string-width": "^4.2.3",
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"y18n": "^5.0.5",
Relock CLI dependencies
2022-11-07 23:07:51 +00:00
"yargs-parser": "^21.1.1"
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dependencies": {
"yargs-parser": {
"version": "21.1.1",
"resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-21.1.1.tgz",
"integrity": "sha512-tVpsJW7DdjecAiFpbIB1e3qxIQsE6NoPc5/eTdrbbIC4h0LVsWhnoa3g+m2HclBIujHzsxZ4VJVA+GUuc2/LBw=="
}
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"yargs-parser": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "20.2.9",
"resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-20.2.9.tgz",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"integrity": "sha512-y11nGElTIV+CT3Zv9t7VKl+Q3hTQoT9a1Qzezhhl6Rp21gJ/IVTW7Z3y9EWXhuUBC2Shnf+DX0antecpAwSP8w=="
relock dependencies
2021-12-06 20:56:02 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"yauzl": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"version": "2.10.0",
"resolved": "https://registry.npmjs.org/yauzl/-/yauzl-2.10.0.tgz",
Relock dependencies
2022-06-27 19:49:33 +00:00
"integrity": "sha512-p4a9I6X6nu6IhoGmBqAcbJy1mlC4j27vEPZX9F4L4/vZT3Lyq1VkFHw/V/PUcB9Buo+DG3iHkT0x3Qya58zc3g==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"requires": {
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
"buffer-crc32": "~0.2.3",
"fd-slicer": "~1.1.0"
}
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
},
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"yocto-queue": {
Bump jest to 28 (#1437) https://jestjs.io/blog/2022/04/25/jest-28 https://jestjs.io/docs/upgrading-to-jest28 https://github.com/facebook/jest/blob/main/CHANGELOG.md#2800 Co-authored-by: Adam Weeden <adamweeden@gmail.com>
2022-07-24 15:24:59 +00:00
"version": "0.1.0",
"resolved": "https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz",
"integrity": "sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==",
Fix shrinkwrap versions back to lockfileVersion 1 (node 12)
2023-03-27 17:27:15 +00:00
"dev": true
Build: re-introduce a package-lock.json file They were used a long time ago, then I scrapped them for simplicity to new contributors. I'm re-considering this and re-introducing one, for two (maybe three) reasons: 1. Reading on supply chain attacks 2. Build broken because of a dep change (see previous commit broken because of a change in yargs @ 17.1.0) (3.) Performance
2021-09-20 15:15:57 +00:00
}
}
}
Copy Permalink