maride/gotty
1
0
Fork 0
mirror of https://github.com/sorenisanerd/gotty.git synced 2024-11-24 04:54:25 +00:00
Code Issues Packages Projects Releases Wiki Activity
0a9f5be727
gotty/js/package-lock.json

4525 lines
192 KiB
JSON
Raw Normal View History

Add xterm itegration * Move to TypeScript from legacy JavaScript * Add support of xterm.js * Hterm is still available for backward compatibility
2017-05-21 23:16:24 +00:00
{
Update typescript, webpack, and asset building
2021-04-16 13:49:17 +00:00
"name": "gotty",
Bump terser from 5.12.1 to 5.14.2 in /js Bumps [terser](https://github.com/terser/terser) from 5.12.1 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-07-21 02:54:00 +00:00
"version": "1.4.0",
npm update
2024-02-12 02:04:48 +00:00
"lockfileVersion": 3,
Update typescript, webpack, and asset building
2021-04-16 13:49:17 +00:00
"requires": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"packages": {
"": {
"name": "gotty",
Bump terser from 5.12.1 to 5.14.2 in /js Bumps [terser](https://github.com/terser/terser) from 5.12.1 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-07-21 02:54:00 +00:00
"version": "1.4.0",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@popperjs/core": "^2.11.8",
"bootstrap": "^5.3.2",
"css-loader": "^5.2.7",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"debounce": "^1.2.1",
npm update
2024-02-12 02:04:48 +00:00
"preact": "^10.19.4",
"react-bootstrap": "^2.10.1",
Add generated data to git
2022-03-28 22:05:51 +00:00
"style-loader": "^2.0.0",
npm update
2024-02-12 02:04:48 +00:00
"xterm": "^4.19.0",
Add generated data to git
2022-03-28 22:05:51 +00:00
"xterm-addon-fit": "^0.5.0",
"xterm-addon-web-links": "^0.4.0",
feat(zmodem): Allow file uploads/downloads Using zmodem (rz and sz commands from lrzsz) you can now send and receive files.
2022-03-29 20:59:22 +00:00
"xterm-addon-webgl": "^0.10.0",
"zmodem.js": "^0.1.10"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"devDependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@types/bootstrap": "^5.2.10",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"compression-webpack-plugin": "^9.2.0",
Add generated data to git
2022-03-28 22:05:51 +00:00
"license-loader": "^0.5.0",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"license-webpack-plugin": "^4.0.2",
"purgecss": "^4.1.3",
npm update
2024-02-12 02:04:48 +00:00
"sass": "^1.70.0",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"sass-loader": "^12.6.0",
npm update
2024-02-12 02:04:48 +00:00
"terser-webpack-plugin": "^5.3.10",
"ts-loader": "^8.4.0",
"typescript": "^4.9.5",
"webpack": "^5.90.1",
"webpack-cli": "^4.10.0",
"webpack-dev-server": "^4.15.1"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/@babel/runtime": {
npm update
2024-02-12 02:04:48 +00:00
"version": "7.23.9",
"resolved": "https://registry.npmjs.org/@babel/runtime/-/runtime-7.23.9.tgz",
"integrity": "sha512-0CX6F+BI2s9dkUqr08KFrAIZgNFj75rdBU/DjCyYLIaV/quFjkk6T+EJ2LkZHyZTbEV4L5p97mNkUsHl2wLFAw==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"regenerator-runtime": "^0.14.0"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
"engines": {
"node": ">=6.9.0"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/@discoveryjs/json-ext": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"version": "0.5.7",
"resolved": "https://registry.npmjs.org/@discoveryjs/json-ext/-/json-ext-0.5.7.tgz",
"integrity": "sha512-dBVuXR082gk3jsFp7Rd/JI4kytwGHecnCoTtXFb7DB6CNHp4rg5k1bhg0nWdLGLnOV71lmDzGQaLMy8iPLY0pw==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dev": true,
"engines": {
"node": ">=10.0.0"
}
},
Bump terser from 5.12.1 to 5.14.2 in /js Bumps [terser](https://github.com/terser/terser) from 5.12.1 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-07-21 02:54:00 +00:00
"node_modules/@jridgewell/gen-mapping": {
npm update
2024-02-12 02:04:48 +00:00
"version": "0.3.3",
"resolved": "https://registry.npmjs.org/@jridgewell/gen-mapping/-/gen-mapping-0.3.3.tgz",
"integrity": "sha512-HLhSWOLRi875zjjMG/r+Nv0oCW8umGb0BgEhyX3dDX3egwZtB8PqLnjz3yedt8R5StBrzcg4aBpnh8UA9D1BoQ==",
Bump terser from 5.12.1 to 5.14.2 in /js Bumps [terser](https://github.com/terser/terser) from 5.12.1 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-07-21 02:54:00 +00:00
"dependencies": {
"@jridgewell/set-array": "^1.0.1",
"@jridgewell/sourcemap-codec": "^1.4.10",
"@jridgewell/trace-mapping": "^0.3.9"
},
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/@jridgewell/resolve-uri": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/@jridgewell/resolve-uri/-/resolve-uri-3.1.1.tgz",
"integrity": "sha512-dSYZh7HhCDtCKm4QakX0xFpsRDqjjtZf/kjI/v3T3Nwt5r8/qz/M19F9ySyOqU94SXBmeG9ttTul+YnR4LOxFA==",
Bump terser from 5.12.1 to 5.14.2 in /js Bumps [terser](https://github.com/terser/terser) from 5.12.1 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-07-21 02:54:00 +00:00
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/@jridgewell/set-array": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/@jridgewell/set-array/-/set-array-1.1.2.tgz",
"integrity": "sha512-xnkseuNADM0gt2bs+BvhO0p78Mk762YnZdsuzFV018NoG1Sj1SCQvpSqa7XUaTam5vAGasABV9qXASMKnFMwMw==",
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/@jridgewell/source-map": {
npm update
2024-02-12 02:04:48 +00:00
"version": "0.3.5",
"resolved": "https://registry.npmjs.org/@jridgewell/source-map/-/source-map-0.3.5.tgz",
"integrity": "sha512-UTYAUj/wviwdsMfzoSJspJxbkH5o1snzwX0//0ENX1u/55kkZZkcTZP6u9bwKGkv+dkk9at4m1Cpt0uY80kcpQ==",
Bump terser from 5.12.1 to 5.14.2 in /js Bumps [terser](https://github.com/terser/terser) from 5.12.1 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-07-21 02:54:00 +00:00
"dependencies": {
"@jridgewell/gen-mapping": "^0.3.0",
"@jridgewell/trace-mapping": "^0.3.9"
}
},
"node_modules/@jridgewell/sourcemap-codec": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.4.15",
"resolved": "https://registry.npmjs.org/@jridgewell/sourcemap-codec/-/sourcemap-codec-1.4.15.tgz",
"integrity": "sha512-eF2rxCRulEKXHTRiDrDy6erMYWqNw4LPdQ8UQA4huuxaQsVeRPFl2oM8oDGxMFhJUWZf9McpLtJasDDZb/Bpeg=="
Bump terser from 5.12.1 to 5.14.2 in /js Bumps [terser](https://github.com/terser/terser) from 5.12.1 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-07-21 02:54:00 +00:00
},
"node_modules/@jridgewell/trace-mapping": {
npm update
2024-02-12 02:04:48 +00:00
"version": "0.3.22",
"resolved": "https://registry.npmjs.org/@jridgewell/trace-mapping/-/trace-mapping-0.3.22.tgz",
"integrity": "sha512-Wf963MzWtA2sjrNt+g18IAln9lKnlRp+K2eH4jjIoF1wYeq3aMREpG09xhlhdzS0EjwU7qmUJYangWa+151vZw==",
Bump terser from 5.12.1 to 5.14.2 in /js Bumps [terser](https://github.com/terser/terser) from 5.12.1 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-07-21 02:54:00 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@jridgewell/resolve-uri": "^3.1.0",
"@jridgewell/sourcemap-codec": "^1.4.14"
Bump terser from 5.12.1 to 5.14.2 in /js Bumps [terser](https://github.com/terser/terser) from 5.12.1 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-07-21 02:54:00 +00:00
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/@leichtgewicht/ip-codec": {
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/@leichtgewicht/ip-codec/-/ip-codec-2.0.4.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-Hcv+nVC0kZnQ3tD9GVu5xSMR4VVYOteQIr/hwFPVEvPdlXqgGEuRjiheChHgdM+JyqdgNcmzZOX/tnl0JOiI7A==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/@popperjs/core": {
npm update
2024-02-12 02:04:48 +00:00
"version": "2.11.8",
"resolved": "https://registry.npmjs.org/@popperjs/core/-/core-2.11.8.tgz",
"integrity": "sha512-P1st0aksCrn9sGZhp8GMYwBnQsbvAWsZAX44oXNNvLHGqAOcoVxmjZiohstwQ7SqKnbR47akdNi+uleWD8+g6A==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/popperjs"
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/@react-aria/ssr": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.9.1",
"resolved": "https://registry.npmjs.org/@react-aria/ssr/-/ssr-3.9.1.tgz",
"integrity": "sha512-NqzkLFP8ZVI4GSorS0AYljC13QW2sc8bDqJOkBvkAt3M8gbcAXJWVRGtZBCRscki9RZF+rNlnPdg0G0jYkhJcg==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@swc/helpers": "^0.5.0"
},
"engines": {
"node": ">= 12"
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
},
"peerDependencies": {
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/@restart/hooks": {
npm update
2024-02-12 02:04:48 +00:00
"version": "0.4.16",
"resolved": "https://registry.npmjs.org/@restart/hooks/-/hooks-0.4.16.tgz",
"integrity": "sha512-f7aCv7c+nU/3mF7NWLtVVr0Ra80RqsO89hO72r+Y/nvQr5+q0UFGkocElTH6MJApvReVh6JHUFYn2cw1WdHF3w==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"dequal": "^2.0.3"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
"peerDependencies": {
"react": ">=16.8.0"
}
},
"node_modules/@restart/ui": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.6.6",
"resolved": "https://registry.npmjs.org/@restart/ui/-/ui-1.6.6.tgz",
"integrity": "sha512-eC3puKuWE1SRYbojWHXnvCNHGgf3uzHCb6JOhnF4OXPibOIPEkR1sqDSkL643ydigxwh+ruCa1CmYHlzk7ikKA==",
"dependencies": {
"@babel/runtime": "^7.21.0",
"@popperjs/core": "^2.11.6",
"@react-aria/ssr": "^3.5.0",
"@restart/hooks": "^0.4.9",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"@types/warning": "^3.0.0",
npm update
2024-02-12 02:04:48 +00:00
"dequal": "^2.0.3",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dom-helpers": "^5.2.0",
npm update
2024-02-12 02:04:48 +00:00
"uncontrollable": "^8.0.1",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"warning": "^4.0.3"
},
"peerDependencies": {
"react": ">=16.14.0",
"react-dom": ">=16.14.0"
}
},
npm update
2024-02-12 02:04:48 +00:00
"node_modules/@restart/ui/node_modules/uncontrollable": {
"version": "8.0.4",
"resolved": "https://registry.npmjs.org/uncontrollable/-/uncontrollable-8.0.4.tgz",
"integrity": "sha512-ulRWYWHvscPFc0QQXvyJjY6LIXU56f0h8pQFvhxiKk5V1fcI8gp9Ht9leVAhrVjzqMw0BgjspBINx9r6oyJUvQ==",
"peerDependencies": {
"react": ">=16.14.0"
}
},
"node_modules/@swc/helpers": {
"version": "0.5.6",
"resolved": "https://registry.npmjs.org/@swc/helpers/-/helpers-0.5.6.tgz",
"integrity": "sha512-aYX01Ke9hunpoCexYAgQucEpARGQ5w/cqHFrIR+e9gdKb1QWTsVJuTJ2ozQzIAxLyRQe/m+2RqzkyOOGiMKRQA==",
"dependencies": {
"tslib": "^2.4.0"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/@types/body-parser": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.19.5",
"resolved": "https://registry.npmjs.org/@types/body-parser/-/body-parser-1.19.5.tgz",
"integrity": "sha512-fB3Zu92ucau0iQ0JMCFQE7b/dv8Ot07NI3KaZIkIUNXq82k4eBAqUaneXfleGY9JWskeS9y+u0nXMyspcuQrCg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"@types/connect": "*",
"@types/node": "*"
}
},
"node_modules/@types/bonjour": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.5.13",
"resolved": "https://registry.npmjs.org/@types/bonjour/-/bonjour-3.5.13.tgz",
"integrity": "sha512-z9fJ5Im06zvUL548KvYNecEVlA7cVDkGUi6kZusb04mpyEFKCIZJvloCcmpmLaIahDpOQGHaHmG6imtPMmPXGQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"@types/node": "*"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/@types/bootstrap": {
npm update
2024-02-12 02:04:48 +00:00
"version": "5.2.10",
"resolved": "https://registry.npmjs.org/@types/bootstrap/-/bootstrap-5.2.10.tgz",
"integrity": "sha512-F2X+cd6551tep0MvVZ6nM8v7XgGN/twpdNDjqS1TUM7YFNEtQYWk+dKAnH+T1gr6QgCoGMPl487xw/9hXooa2g==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dev": true,
"dependencies": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"@popperjs/core": "^2.9.2"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/@types/connect": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.4.38",
"resolved": "https://registry.npmjs.org/@types/connect/-/connect-3.4.38.tgz",
"integrity": "sha512-K6uROf1LD88uDQqJCktA4yzL1YYAK6NgfsI0v/mTgyPKWsX1CnJ0XPSDhViejru1GcRkLWb8RlzFYJRqGUbaug==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"@types/node": "*"
}
},
"node_modules/@types/connect-history-api-fallback": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.5.4",
"resolved": "https://registry.npmjs.org/@types/connect-history-api-fallback/-/connect-history-api-fallback-1.5.4.tgz",
"integrity": "sha512-n6Cr2xS1h4uAulPRdlw6Jl6s1oG8KrVilPN2yUITEs+K48EzMJJ3W1xy8K5eWuFvjp3R74AOIGSmp2UfBJ8HFw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"@types/express-serve-static-core": "*",
"@types/node": "*"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/@types/eslint": {
npm update
2024-02-12 02:04:48 +00:00
"version": "8.56.2",
"resolved": "https://registry.npmjs.org/@types/eslint/-/eslint-8.56.2.tgz",
"integrity": "sha512-uQDwm1wFHmbBbCZCqAlq6Do9LYwByNZHWzXppSnay9SuwJ+VRbjkbLABer54kcPnMSlG6Fdiy2yaFXm/z9Z5gw==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"@types/estree": "*",
"@types/json-schema": "*"
}
},
"node_modules/@types/eslint-scope": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.7.7",
"resolved": "https://registry.npmjs.org/@types/eslint-scope/-/eslint-scope-3.7.7.tgz",
"integrity": "sha512-MzMFlSLBqNF2gcHWO0G1vP/YQyfvrxZ0bF+u7mzUdZ1/xK4A4sru+nraZz5i3iEIk1l1uyicaDVTB4QbbEkAYg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"@types/eslint": "*",
"@types/estree": "*"
}
},
"node_modules/@types/estree": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/@types/estree/-/estree-1.0.5.tgz",
"integrity": "sha512-/kYRxGDLWzHOB7q+wtSUQlFrtcdUccpfy+X+9iMBpHK8QLLhx2wIPYuS5DYtR9Wa/YlZAbIovy7qVdB1Aq6Lyw=="
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/@types/express": {
npm update
2024-02-12 02:04:48 +00:00
"version": "4.17.21",
"resolved": "https://registry.npmjs.org/@types/express/-/express-4.17.21.tgz",
"integrity": "sha512-ejlPM315qwLpaQlQDTjPdsUFSc6ZsP4AN6AlWnogPjQ7CVi7PYF3YVz+CY3jE2pwYf7E/7HlDAN0rV2GxTG0HQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"@types/body-parser": "*",
npm update
2024-02-12 02:04:48 +00:00
"@types/express-serve-static-core": "^4.17.33",
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"@types/qs": "*",
"@types/serve-static": "*"
}
},
"node_modules/@types/express-serve-static-core": {
npm update
2024-02-12 02:04:48 +00:00
"version": "4.17.43",
"resolved": "https://registry.npmjs.org/@types/express-serve-static-core/-/express-serve-static-core-4.17.43.tgz",
"integrity": "sha512-oaYtiBirUOPQGSWNGPWnzyAFJ0BP3cwvN4oWZQY+zUBwpVIGsKUkpBpSztp74drYcjavs7SKFZ4DX1V2QeN8rg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"@types/node": "*",
"@types/qs": "*",
npm update
2024-02-12 02:04:48 +00:00
"@types/range-parser": "*",
"@types/send": "*"
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
}
},
npm update
2024-02-12 02:04:48 +00:00
"node_modules/@types/http-errors": {
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/@types/http-errors/-/http-errors-2.0.4.tgz",
"integrity": "sha512-D0CFMMtydbJAegzOyHjtiKPLlvnm3iTZyZRSZoLq2mRhDdmLfIWOCYPfQJ4cu2erKghU++QvjcUjp/5h7hESpA==",
"dev": true
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/@types/http-proxy": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.17.14",
"resolved": "https://registry.npmjs.org/@types/http-proxy/-/http-proxy-1.17.14.tgz",
"integrity": "sha512-SSrD0c1OQzlFX7pGu1eXxSEjemej64aaNPRhhVYUGqXh0BtldAAx37MG8btcumvpgKyZp1F5Gn3JkktdxiFv6w==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"@types/node": "*"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/@types/json-schema": {
npm update
2024-02-12 02:04:48 +00:00
"version": "7.0.15",
"resolved": "https://registry.npmjs.org/@types/json-schema/-/json-schema-7.0.15.tgz",
"integrity": "sha512-5+fP8P8MFNC+AyZCDxrB2pkZFPGzqQWUzpSeuuVLvm8VMcorNYavBqoFcxK8bQz4Qsbn4oUEEem4wDLfcysGHA=="
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/@types/mime": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.3.5",
"resolved": "https://registry.npmjs.org/@types/mime/-/mime-1.3.5.tgz",
"integrity": "sha512-/pyBZWSLD2n0dcHE3hq8s8ZvcETHtEuF+3E7XVt0Ig2nvsVQXdghHVcEkIWjy9A0wKfTn97a/PSDYohKIlnP/w==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/@types/node": {
npm update
2024-02-12 02:04:48 +00:00
"version": "20.11.17",
"resolved": "https://registry.npmjs.org/@types/node/-/node-20.11.17.tgz",
"integrity": "sha512-QmgQZGWu1Yw9TDyAP9ZzpFJKynYNeOvwMJmaxABfieQoVoiVOS6MN1WSpqpRcbeA5+RW82kraAVxCCJg+780Qw==",
"dependencies": {
"undici-types": "~5.26.4"
}
},
"node_modules/@types/node-forge": {
"version": "1.3.11",
"resolved": "https://registry.npmjs.org/@types/node-forge/-/node-forge-1.3.11.tgz",
"integrity": "sha512-FQx220y22OKNTqaByeBGqHWYz4cl94tpcxeFdvBo3wjG6XPBuZ0BNgNZRV5J5TFmmcsJ4IzsLkmGRiQbnYsBEQ==",
"dev": true,
"dependencies": {
"@types/node": "*"
}
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
"node_modules/@types/prop-types": {
npm update
2024-02-12 02:04:48 +00:00
"version": "15.7.11",
"resolved": "https://registry.npmjs.org/@types/prop-types/-/prop-types-15.7.11.tgz",
"integrity": "sha512-ga8y9v9uyeiLdpKddhxYQkxNDrfvuPrlFb0N1qnZZByvcElJaXthF1UhvCh9TLWJBEHeNtdnbysW7Y6Uq8CVng=="
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/@types/qs": {
npm update
2024-02-12 02:04:48 +00:00
"version": "6.9.11",
"resolved": "https://registry.npmjs.org/@types/qs/-/qs-6.9.11.tgz",
"integrity": "sha512-oGk0gmhnEJK4Yyk+oI7EfXsLayXatCWPHary1MtcmbAifkobT9cM9yutG/hZKIseOU0MqbIwQ/u2nn/Gb+ltuQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"node_modules/@types/range-parser": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.2.7",
"resolved": "https://registry.npmjs.org/@types/range-parser/-/range-parser-1.2.7.tgz",
"integrity": "sha512-hKormJbkJqzQGhziax5PItDUTMAM9uE2XXQmM37dyd4hVM+5aVl7oVxMVUiVQn2oCQFN/LKCZdvSM0pFRqbSmQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/@types/react": {
npm update
2024-02-12 02:04:48 +00:00
"version": "18.2.55",
"resolved": "https://registry.npmjs.org/@types/react/-/react-18.2.55.tgz",
"integrity": "sha512-Y2Tz5P4yz23brwm2d7jNon39qoAtMMmalOQv6+fEFt1mT+FcM3D841wDpoUvFXhaYenuROCy3FZYqdTjM7qVyA==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
"@types/prop-types": "*",
"@types/scheduler": "*",
"csstype": "^3.0.2"
}
},
"node_modules/@types/react-transition-group": {
npm update
2024-02-12 02:04:48 +00:00
"version": "4.4.10",
"resolved": "https://registry.npmjs.org/@types/react-transition-group/-/react-transition-group-4.4.10.tgz",
"integrity": "sha512-hT/+s0VQs2ojCX823m60m5f0sL5idt9SO6Tj6Dg+rdphGPIeJbJ6CxvBYkgkGKrYeDjvIpKTR38UzmtHJOGW3Q==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
"@types/react": "*"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/@types/retry": {
"version": "0.12.0",
"resolved": "https://registry.npmjs.org/@types/retry/-/retry-0.12.0.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-wWKOClTTiizcZhXnPY4wikVAwmdYHp8q6DmC+EJUzAMsycb7HB32Kh9RN4+0gExjmPmZSAQjgURXIGATPegAvA==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/@types/scheduler": {
npm update
2024-02-12 02:04:48 +00:00
"version": "0.16.8",
"resolved": "https://registry.npmjs.org/@types/scheduler/-/scheduler-0.16.8.tgz",
"integrity": "sha512-WZLiwShhwLRmeV6zH+GkbOFT6Z6VklCItrDioxUnv+u4Ll+8vKeFySoFyK/0ctcRpOmwAicELfmys1sDc/Rw+A=="
},
"node_modules/@types/send": {
"version": "0.17.4",
"resolved": "https://registry.npmjs.org/@types/send/-/send-0.17.4.tgz",
"integrity": "sha512-x2EM6TJOybec7c52BX0ZspPodMsQUd5L6PRwOunVyVUhXiBSKf3AezDL8Dgvgt5o0UfKNfuA0eMLr2wLT4AiBA==",
"dev": true,
"dependencies": {
"@types/mime": "^1",
"@types/node": "*"
}
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/@types/serve-index": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.9.4",
"resolved": "https://registry.npmjs.org/@types/serve-index/-/serve-index-1.9.4.tgz",
"integrity": "sha512-qLpGZ/c2fhSs5gnYsQxtDEq3Oy8SXPClIXkW5ghvAvsNuVSA8k+gCONcUCS/UjLEYvYps+e8uBtfgXgvhwfNug==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"@types/express": "*"
}
},
"node_modules/@types/serve-static": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.15.5",
"resolved": "https://registry.npmjs.org/@types/serve-static/-/serve-static-1.15.5.tgz",
"integrity": "sha512-PDRk21MnK70hja/YF8AHfC7yIsiQHn1rcXx7ijCFBX/k+XQJhQT/gw3xekXKJvx+5SXaMMS8oqQy09Mzvz2TuQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@types/http-errors": "*",
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"@types/mime": "*",
"@types/node": "*"
}
},
"node_modules/@types/sockjs": {
npm update
2024-02-12 02:04:48 +00:00
"version": "0.3.36",
"resolved": "https://registry.npmjs.org/@types/sockjs/-/sockjs-0.3.36.tgz",
"integrity": "sha512-MK9V6NzAS1+Ud7JV9lJLFqW85VbC9dq3LmwZCuBe4wBDgKC0Kj/jd8Xl+nSviU+Qc3+m7umHHyHg//2KSa0a0Q==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"@types/node": "*"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/@types/warning": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/@types/warning/-/warning-3.0.3.tgz",
"integrity": "sha512-D1XC7WK8K+zZEveUPY+cf4+kgauk8N4eHr/XIHXGlGYkHLud6hK9lYfZk1ry1TNh798cZUCgb6MqGEG8DkJt6Q=="
Add generated data to git
2022-03-28 22:05:51 +00:00
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/@types/ws": {
npm update
2024-02-12 02:04:48 +00:00
"version": "8.5.10",
"resolved": "https://registry.npmjs.org/@types/ws/-/ws-8.5.10.tgz",
"integrity": "sha512-vmQSUcfalpIq0R9q7uTo2lXs6eGIpt9wtnLdMv9LVpIjCA/+ufZRozlVoVelIYixx1ugCBKDhn89vnsEGOCx9A==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"@types/node": "*"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/@webassemblyjs/ast": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.11.6",
"resolved": "https://registry.npmjs.org/@webassemblyjs/ast/-/ast-1.11.6.tgz",
"integrity": "sha512-IN1xI7PwOvLPgjcf180gC1bqn3q/QaOCwYUahIOhbYUu8KA/3tw2RT/T0Gidi1l7Hhj5D/INhJxiICObqpMu4Q==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@webassemblyjs/helper-numbers": "1.11.6",
"@webassemblyjs/helper-wasm-bytecode": "1.11.6"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
"node_modules/@webassemblyjs/floating-point-hex-parser": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.11.6",
"resolved": "https://registry.npmjs.org/@webassemblyjs/floating-point-hex-parser/-/floating-point-hex-parser-1.11.6.tgz",
"integrity": "sha512-ejAj9hfRJ2XMsNHk/v6Fu2dGS+i4UaXBXGemOfQ/JfQ6mdQg/WXtwleQRLLS4OvfDhv8rYnVwH27YJLMyYsxhw=="
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"node_modules/@webassemblyjs/helper-api-error": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.11.6",
"resolved": "https://registry.npmjs.org/@webassemblyjs/helper-api-error/-/helper-api-error-1.11.6.tgz",
"integrity": "sha512-o0YkoP4pVu4rN8aTJgAyj9hC2Sv5UlkzCHhxqWj8butaLvnpdc2jOwh4ewE6CX0txSfLn/UYaV/pheS2Txg//Q=="
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"node_modules/@webassemblyjs/helper-buffer": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.11.6",
"resolved": "https://registry.npmjs.org/@webassemblyjs/helper-buffer/-/helper-buffer-1.11.6.tgz",
"integrity": "sha512-z3nFzdcp1mb8nEOFFk8DrYLpHvhKC3grJD2ardfKOzmbmJvEf/tPIqCY+sNcwZIY8ZD7IkB2l7/pqhUhqm7hLA=="
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"node_modules/@webassemblyjs/helper-numbers": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.11.6",
"resolved": "https://registry.npmjs.org/@webassemblyjs/helper-numbers/-/helper-numbers-1.11.6.tgz",
"integrity": "sha512-vUIhZ8LZoIWHBohiEObxVm6hwP034jwmc9kuq5GdHZH0wiLVLIPcMCdpJzG4C11cHoQ25TFIQj9kaVADVX7N3g==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@webassemblyjs/floating-point-hex-parser": "1.11.6",
"@webassemblyjs/helper-api-error": "1.11.6",
Add generated data to git
2022-03-28 22:05:51 +00:00
"@xtuc/long": "4.2.2"
}
},
"node_modules/@webassemblyjs/helper-wasm-bytecode": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.11.6",
"resolved": "https://registry.npmjs.org/@webassemblyjs/helper-wasm-bytecode/-/helper-wasm-bytecode-1.11.6.tgz",
"integrity": "sha512-sFFHKwcmBprO9e7Icf0+gddyWYDViL8bpPjJJl0WHxCdETktXdmtWLGVzoHbqUcY4Be1LkNfwTmXOJUFZYSJdA=="
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"node_modules/@webassemblyjs/helper-wasm-section": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.11.6",
"resolved": "https://registry.npmjs.org/@webassemblyjs/helper-wasm-section/-/helper-wasm-section-1.11.6.tgz",
"integrity": "sha512-LPpZbSOwTpEC2cgn4hTydySy1Ke+XEu+ETXuoyvuyezHO3Kjdu90KK95Sh9xTbmjrCsUwvWwCOQQNta37VrS9g==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@webassemblyjs/ast": "1.11.6",
"@webassemblyjs/helper-buffer": "1.11.6",
"@webassemblyjs/helper-wasm-bytecode": "1.11.6",
"@webassemblyjs/wasm-gen": "1.11.6"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
"node_modules/@webassemblyjs/ieee754": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.11.6",
"resolved": "https://registry.npmjs.org/@webassemblyjs/ieee754/-/ieee754-1.11.6.tgz",
"integrity": "sha512-LM4p2csPNvbij6U1f19v6WR56QZ8JcHg3QIJTlSwzFcmx6WSORicYj6I63f9yU1kEUtrpG+kjkiIAkevHpDXrg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"@xtuc/ieee754": "^1.2.0"
}
},
"node_modules/@webassemblyjs/leb128": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.11.6",
"resolved": "https://registry.npmjs.org/@webassemblyjs/leb128/-/leb128-1.11.6.tgz",
"integrity": "sha512-m7a0FhE67DQXgouf1tbN5XQcdWoNgaAuoULHIfGFIEVKA6tu/edls6XnIlkmS6FrXAquJRPni3ZZKjw6FSPjPQ==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"@xtuc/long": "4.2.2"
}
},
"node_modules/@webassemblyjs/utf8": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.11.6",
"resolved": "https://registry.npmjs.org/@webassemblyjs/utf8/-/utf8-1.11.6.tgz",
"integrity": "sha512-vtXf2wTQ3+up9Zsg8sa2yWiQpzSsMyXj0qViVP6xKGCUT8p8YJ6HqI7l5eCnWx1T/FYdsv07HQs2wTFbbof/RA=="
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"node_modules/@webassemblyjs/wasm-edit": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.11.6",
"resolved": "https://registry.npmjs.org/@webassemblyjs/wasm-edit/-/wasm-edit-1.11.6.tgz",
"integrity": "sha512-Ybn2I6fnfIGuCR+Faaz7YcvtBKxvoLV3Lebn1tM4o/IAJzmi9AWYIPWpyBfU8cC+JxAO57bk4+zdsTjJR+VTOw==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@webassemblyjs/ast": "1.11.6",
"@webassemblyjs/helper-buffer": "1.11.6",
"@webassemblyjs/helper-wasm-bytecode": "1.11.6",
"@webassemblyjs/helper-wasm-section": "1.11.6",
"@webassemblyjs/wasm-gen": "1.11.6",
"@webassemblyjs/wasm-opt": "1.11.6",
"@webassemblyjs/wasm-parser": "1.11.6",
"@webassemblyjs/wast-printer": "1.11.6"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
"node_modules/@webassemblyjs/wasm-gen": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.11.6",
"resolved": "https://registry.npmjs.org/@webassemblyjs/wasm-gen/-/wasm-gen-1.11.6.tgz",
"integrity": "sha512-3XOqkZP/y6B4F0PBAXvI1/bky7GryoogUtfwExeP/v7Nzwo1QLcq5oQmpKlftZLbT+ERUOAZVQjuNVak6UXjPA==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@webassemblyjs/ast": "1.11.6",
"@webassemblyjs/helper-wasm-bytecode": "1.11.6",
"@webassemblyjs/ieee754": "1.11.6",
"@webassemblyjs/leb128": "1.11.6",
"@webassemblyjs/utf8": "1.11.6"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
"node_modules/@webassemblyjs/wasm-opt": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.11.6",
"resolved": "https://registry.npmjs.org/@webassemblyjs/wasm-opt/-/wasm-opt-1.11.6.tgz",
"integrity": "sha512-cOrKuLRE7PCe6AsOVl7WasYf3wbSo4CeOk6PkrjS7g57MFfVUF9u6ysQBBODX0LdgSvQqRiGz3CXvIDKcPNy4g==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@webassemblyjs/ast": "1.11.6",
"@webassemblyjs/helper-buffer": "1.11.6",
"@webassemblyjs/wasm-gen": "1.11.6",
"@webassemblyjs/wasm-parser": "1.11.6"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
"node_modules/@webassemblyjs/wasm-parser": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.11.6",
"resolved": "https://registry.npmjs.org/@webassemblyjs/wasm-parser/-/wasm-parser-1.11.6.tgz",
"integrity": "sha512-6ZwPeGzMJM3Dqp3hCsLgESxBGtT/OeCvCZ4TA1JUPYgmhAx38tTPR9JaKy0S5H3evQpO/h2uWs2j6Yc/fjkpTQ==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@webassemblyjs/ast": "1.11.6",
"@webassemblyjs/helper-api-error": "1.11.6",
"@webassemblyjs/helper-wasm-bytecode": "1.11.6",
"@webassemblyjs/ieee754": "1.11.6",
"@webassemblyjs/leb128": "1.11.6",
"@webassemblyjs/utf8": "1.11.6"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
"node_modules/@webassemblyjs/wast-printer": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.11.6",
"resolved": "https://registry.npmjs.org/@webassemblyjs/wast-printer/-/wast-printer-1.11.6.tgz",
"integrity": "sha512-JM7AhRcE+yW2GWYaKeHL5vt4xqee5N2WcezptmgyhNS+ScggqcT1OtXykhAb13Sn5Yas0j2uv9tHgrjwvzAP4A==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@webassemblyjs/ast": "1.11.6",
Add generated data to git
2022-03-28 22:05:51 +00:00
"@xtuc/long": "4.2.2"
}
},
"node_modules/@webpack-cli/configtest": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/@webpack-cli/configtest/-/configtest-1.2.0.tgz",
"integrity": "sha512-4FB8Tj6xyVkyqjj1OaTqCjXYULB9FMkqQ8yGrZjRDrYh0nOE+7Lhs45WioWQQMV+ceFlE368Ukhe6xdvJM9Egg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dev": true,
"peerDependencies": {
"webpack": "4.x.x || 5.x.x",
"webpack-cli": "4.x.x"
}
},
"node_modules/@webpack-cli/info": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +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==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dev": true,
"dependencies": {
"envinfo": "^7.7.3"
},
"peerDependencies": {
"webpack-cli": "4.x.x"
}
},
"node_modules/@webpack-cli/serve": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"version": "1.7.0",
"resolved": "https://registry.npmjs.org/@webpack-cli/serve/-/serve-1.7.0.tgz",
"integrity": "sha512-oxnCNGj88fL+xzV+dacXs44HcDwf1ovs3AuEzvP7mqXw7fQntqIhQ1BRmynh4qEKQSSSRSWVyXRjmTbZIX9V2Q==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dev": true,
"peerDependencies": {
"webpack-cli": "4.x.x"
},
"peerDependenciesMeta": {
"webpack-dev-server": {
"optional": true
}
}
},
"node_modules/@xtuc/ieee754": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/@xtuc/ieee754/-/ieee754-1.2.0.tgz",
"integrity": "sha512-DX8nKgqcGwsc0eJSqYt5lwP4DH5FlHnmuWWBRy7X0NcaGR0ZtuyeESgMwTYVEtxmsNGY+qit4QYT/MIYTOTPeA=="
},
"node_modules/@xtuc/long": {
"version": "4.2.2",
"resolved": "https://registry.npmjs.org/@xtuc/long/-/long-4.2.2.tgz",
"integrity": "sha512-NuHqBY1PB/D8xU6s/thBgOAiAP7HOYDQ32+BFZILJ8ivkUkAHQnWfn6WhL79Owj1qmUnoN/YPhktdIoucipkAQ=="
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/accepts": {
"version": "1.3.8",
"resolved": "https://registry.npmjs.org/accepts/-/accepts-1.3.8.tgz",
"integrity": "sha512-PYAthTa2m2VKxuvSD3DPC/Gy+U+sOA1LAuT8mkmRuvw+NACSaeXEQ+NHcVF7rONl6qcaxV3Uuemwawk+7+SJLw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"mime-types": "~2.1.34",
"negotiator": "0.6.3"
},
"engines": {
"node": ">= 0.6"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/acorn": {
npm update
2024-02-12 02:04:48 +00:00
"version": "8.11.3",
"resolved": "https://registry.npmjs.org/acorn/-/acorn-8.11.3.tgz",
"integrity": "sha512-Y9rRfJG5jcKOE0CLisYbojUjIrIEE7AGMzA/Sm4BslANhbS+cDMpgBdcPT91oJ7OuJ9hYJBx59RjbhxVnrF8Xg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"bin": {
"acorn": "bin/acorn"
},
"engines": {
"node": ">=0.4.0"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/acorn-import-assertions": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.9.0",
"resolved": "https://registry.npmjs.org/acorn-import-assertions/-/acorn-import-assertions-1.9.0.tgz",
"integrity": "sha512-cmMwop9x+8KFhxvKrKfPYmN6/pKTYYHBqLa0DfvVZcKMJWNyWLnaqND7dx/qn66R7ewM1UX5XMaDVP5wlVTaVA==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"peerDependencies": {
"acorn": "^8"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/ajv": {
npm update
2024-02-12 02:04:48 +00:00
"version": "8.12.0",
"resolved": "https://registry.npmjs.org/ajv/-/ajv-8.12.0.tgz",
"integrity": "sha512-sRu1kpcO9yLtYxBKvqfTeh9KzZEwO3STyX1HT+4CaDzC6HpTGYhIhPIzj9XuKU7KYDwnaeh5hcOwjy1QuJzBPA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"fast-deep-equal": "^3.1.1",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"json-schema-traverse": "^1.0.0",
"require-from-string": "^2.0.2",
Add generated data to git
2022-03-28 22:05:51 +00:00
"uri-js": "^4.2.2"
},
"funding": {
"type": "github",
"url": "https://github.com/sponsors/epoberezkin"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/ajv-formats": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/ajv-formats/-/ajv-formats-2.1.1.tgz",
"integrity": "sha512-Wx0Kx52hxE7C18hkMEggYlEifqWZtYaRgouJor+WMdPnQyEK13vgEWyVNup7SoeeoLMsr4kf5h6dOW11I15MUA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
"ajv": "^8.0.0"
},
"peerDependencies": {
"ajv": "^8.0.0"
},
"peerDependenciesMeta": {
"ajv": {
"optional": true
}
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/ajv-keywords": {
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/ajv-keywords/-/ajv-keywords-5.1.0.tgz",
"integrity": "sha512-YCS/JNFAUyr5vAuhk1DWm1CBxRHW9LbJ2ozWeemrIqpbsqKjHVxYPyi5GC0rjZIT5JxJ3virVTS8wk4i/Z+krw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"fast-deep-equal": "^3.1.3"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"peerDependencies": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"ajv": "^8.8.2"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
Add generated data to git
2022-03-28 22:05:51 +00:00
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/ansi-html-community": {
"version": "0.0.8",
"resolved": "https://registry.npmjs.org/ansi-html-community/-/ansi-html-community-0.0.8.tgz",
"integrity": "sha512-1APHAyr3+PCamwNw3bXCPp4HFLONZt/yIH0sZp0/469KWNTEy+qN5jQ3GVX6DMZ1UXAi34yVwtTeaG/HpBuuzw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": [
"node >= 0.8.0"
],
"bin": {
"ansi-html": "bin/ansi-html"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/ansi-styles": {
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz",
"integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"color-convert": "^2.0.1"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/chalk/ansi-styles?sponsor=1"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/anymatch": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.1.3",
"resolved": "https://registry.npmjs.org/anymatch/-/anymatch-3.1.3.tgz",
"integrity": "sha512-KMReFUr0B4t+D+OBkjR3KYqvocp2XaSzO55UcB6mgQMd3KbcE+mWTyvVV7D/zsdEbNnV6acZUutkiHQXvTr1Rw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
"normalize-path": "^3.0.0",
"picomatch": "^2.0.4"
},
"engines": {
"node": ">= 8"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/array-flatten": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/array-flatten/-/array-flatten-1.1.1.tgz",
"integrity": "sha512-PCVAQswWemu6UdxsDFFX/+gVeYqKAod3D3UVm91jHwynguOwAvYPhx8nNlM++NqRcK6CxxpUafjmhIdKiHibqg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/balanced-match": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-1.0.2.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"node_modules/batch": {
"version": "0.6.1",
"resolved": "https://registry.npmjs.org/batch/-/batch-0.6.1.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-x+VAiMRL6UPkx+kudNvxTl6hB2XNNCG2r+7wixVfIYwu/2HKRXimwQyaumLjMveWvT2Hkd/cAJw+QBMfJ/EKVw==",
"dev": true
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/big.js": {
"version": "5.2.2",
"resolved": "https://registry.npmjs.org/big.js/-/big.js-5.2.2.tgz",
"integrity": "sha512-vyL2OymJxmarO8gxMr0mhChsO9QGwhynfuu4+MHTAW6czfq9humCB7rKpUjDd9YUiDPU4mzpyupFSvOClAwbmQ==",
"engines": {
"node": "*"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/binary-extensions": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/binary-extensions/-/binary-extensions-2.2.0.tgz",
"integrity": "sha512-jDctJ/IVQbZoJykoeHbhXpOlNBqGNcwXJKJog42E5HDPUwQTSdjCHdihjj0DlnheQ7blbT6dHOafNAiS8ooQKA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"engines": {
"node": ">=8"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/body-parser": {
"version": "1.20.1",
"resolved": "https://registry.npmjs.org/body-parser/-/body-parser-1.20.1.tgz",
"integrity": "sha512-jWi7abTbYwajOytWCQc37VulmWiRae5RyTpaCyDcS5/lMdtwSz5lOpDE67srw/HYe35f1z3fDQw+3txg7gNtWw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"bytes": "3.1.2",
"content-type": "~1.0.4",
"debug": "2.6.9",
"depd": "2.0.0",
"destroy": "1.2.0",
"http-errors": "2.0.0",
"iconv-lite": "0.4.24",
"on-finished": "2.4.1",
"qs": "6.11.0",
"raw-body": "2.5.1",
"type-is": "~1.6.18",
"unpipe": "1.0.0"
},
"engines": {
"node": ">= 0.8",
"npm": "1.2.8000 || >= 1.4.16"
}
},
"node_modules/body-parser/node_modules/bytes": {
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/bytes/-/bytes-3.1.2.tgz",
"integrity": "sha512-/Nf7TyzTx6S3yRJObOAV7956r8cr2+Oj8AC5dt8wSP3BQAoeX58NoHyCU8P8zGkNXStjTSi6fzO6F0pBdcYbEg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.8"
}
},
"node_modules/bonjour-service": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/bonjour-service/-/bonjour-service-1.2.1.tgz",
"integrity": "sha512-oSzCS2zV14bh2kji6vNe7vrpJYCHGvcZnlffFQ1MEoX/WOeQ/teD8SYWKR942OI3INjq8OMNJlbPK5LLLUxFDw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"fast-deep-equal": "^3.1.3",
"multicast-dns": "^7.2.5"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/bootstrap": {
npm update
2024-02-12 02:04:48 +00:00
"version": "5.3.2",
"resolved": "https://registry.npmjs.org/bootstrap/-/bootstrap-5.3.2.tgz",
"integrity": "sha512-D32nmNWiQHo94BKHLmOrdjlL05q1c8oxbtBphQFb9Z5to6eGRDCm0QgeaZ4zFBHzfg2++rqa2JkqCcxDy0sH0g==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/twbs"
},
{
"type": "opencollective",
"url": "https://opencollective.com/bootstrap"
}
],
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"peerDependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@popperjs/core": "^2.11.8"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
},
"node_modules/brace-expansion": {
"version": "1.1.11",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz",
"integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/braces": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/braces/-/braces-3.0.2.tgz",
"integrity": "sha512-b8um+L1RzM3WDSzvhm6gIz1yfTbBt6YTlcEKAvsmqCZZFw46z626lVj9j1yEPW33H5H+lBQpZMP1k8l+78Ha0A==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"fill-range": "^7.0.1"
},
"engines": {
"node": ">=8"
}
},
"node_modules/browserslist": {
npm update
2024-02-12 02:04:48 +00:00
"version": "4.22.3",
"resolved": "https://registry.npmjs.org/browserslist/-/browserslist-4.22.3.tgz",
"integrity": "sha512-UAp55yfwNv0klWNapjs/ktHoguxuQNGnOzxYmfnXIS+8AsRDZkSDxg7R1AX3GKzn078SBI5dzwzj/Yx0Or0e3A==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"funding": [
{
"type": "opencollective",
"url": "https://opencollective.com/browserslist"
},
{
"type": "tidelift",
"url": "https://tidelift.com/funding/github/npm/browserslist"
npm update
2024-02-12 02:04:48 +00:00
},
{
"type": "github",
"url": "https://github.com/sponsors/ai"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
],
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"caniuse-lite": "^1.0.30001580",
"electron-to-chromium": "^1.4.648",
"node-releases": "^2.0.14",
"update-browserslist-db": "^1.0.13"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"bin": {
"browserslist": "cli.js"
},
"engines": {
"node": "^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7"
}
},
"node_modules/buffer-from": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +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=="
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/bytes": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/bytes/-/bytes-3.0.0.tgz",
"integrity": "sha512-pMhOfFDPiv9t5jjIXkHosWmkSyQbvsgEVNkz0ERHbuLh2T/7j4Mqqpz523Fe8MVY89KC6Sh/QfS2sM+SjgFDcw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.8"
}
},
"node_modules/call-bind": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.0.6",
"resolved": "https://registry.npmjs.org/call-bind/-/call-bind-1.0.6.tgz",
"integrity": "sha512-Mj50FLHtlsoVfRfnHaZvyrooHcrlceNZdL/QBvJJVd9Ta55qCQK0gs4ss2oZDeV9zFCs6ewzYgVE5yfVmfFpVg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"es-errors": "^1.3.0",
"function-bind": "^1.1.2",
"get-intrinsic": "^1.2.3",
"set-function-length": "^1.2.0"
},
"engines": {
"node": ">= 0.4"
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/caniuse-lite": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.0.30001585",
"resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001585.tgz",
"integrity": "sha512-yr2BWR1yLXQ8fMpdS/4ZZXpseBgE7o4g41x3a6AJOqZuOi+iE/WdJYAuZ6Y95i4Ohd2Y+9MzIWRR+uGABH4s3Q==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"funding": [
{
"type": "opencollective",
"url": "https://opencollective.com/browserslist"
},
{
"type": "tidelift",
"url": "https://tidelift.com/funding/github/npm/caniuse-lite"
npm update
2024-02-12 02:04:48 +00:00
},
{
"type": "github",
"url": "https://github.com/sponsors/ai"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
]
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/chalk": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"version": "4.1.2",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz",
"integrity": "sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"ansi-styles": "^4.1.0",
"supports-color": "^7.1.0"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/chalk/chalk?sponsor=1"
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/chalk/node_modules/supports-color": {
"version": "7.2.0",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-7.2.0.tgz",
"integrity": "sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==",
"dev": true,
"dependencies": {
"has-flag": "^4.0.0"
},
"engines": {
"node": ">=8"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/chokidar": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.6.0",
"resolved": "https://registry.npmjs.org/chokidar/-/chokidar-3.6.0.tgz",
"integrity": "sha512-7VT13fmjotKpGipCW9JEQAusEPE+Ei8nl6/g4FBAmIm0GOOLMua9NDDo/DWp0ZAxCr3cPq5ZpBqmPAQgDda2Pw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
"anymatch": "~3.1.2",
"braces": "~3.0.2",
"glob-parent": "~5.1.2",
"is-binary-path": "~2.1.0",
"is-glob": "~4.0.1",
"normalize-path": "~3.0.0",
"readdirp": "~3.6.0"
},
"engines": {
"node": ">= 8.10.0"
},
npm update
2024-02-12 02:04:48 +00:00
"funding": {
"url": "https://paulmillr.com/funding/"
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"optionalDependencies": {
"fsevents": "~2.3.2"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/chrome-trace-event": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/chrome-trace-event/-/chrome-trace-event-1.0.3.tgz",
"integrity": "sha512-p3KULyQg4S7NIHixdwbGX+nFHkoBiA4YQmyWtjb8XngSKV124nJmRysgAeujbUVb15vh+RvFUfCPqU7rXk+hZg==",
"engines": {
"node": ">=6.0"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/classnames": {
npm update
2024-02-12 02:04:48 +00:00
"version": "2.5.1",
"resolved": "https://registry.npmjs.org/classnames/-/classnames-2.5.1.tgz",
"integrity": "sha512-saHYOzhIQs6wy2sVxTM6bUDsQO4F50V9RQ22qBpEdCW+I+/Wmke2HOl6lS6dTpdxVhb88/I6+Hs+438c3lfUow=="
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/clone-deep": {
"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,
"dependencies": {
"is-plain-object": "^2.0.4",
"kind-of": "^6.0.2",
"shallow-clone": "^3.0.0"
},
"engines": {
"node": ">=6"
}
},
"node_modules/color-convert": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz",
"integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"color-name": "~1.1.4"
},
"engines": {
"node": ">=7.0.0"
}
},
"node_modules/color-name": {
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==",
"dev": true
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"node_modules/colorette": {
npm update
2024-02-12 02:04:48 +00:00
"version": "2.0.20",
"resolved": "https://registry.npmjs.org/colorette/-/colorette-2.0.20.tgz",
"integrity": "sha512-IfEDxwoWIjkeXL1eXcDiow4UbKjhLdq6/EuSVR9GMN7KVH3r9gQ83e73hsz1Nd1T3ijd5xv1wcWRYO+D6kCI2w==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/commander": {
"version": "8.3.0",
"resolved": "https://registry.npmjs.org/commander/-/commander-8.3.0.tgz",
"integrity": "sha512-OkTL9umf+He2DZkUq8f8J9of7yL6RJKI24dVITBmNfZBmri9zYZQrKkuXiKhyfPSu8tUhnVBB1iKXevvnlR4Ww==",
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"engines": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node": ">= 12"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
Add generated data to git
2022-03-28 22:05:51 +00:00
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/compressible": {
"version": "2.0.18",
"resolved": "https://registry.npmjs.org/compressible/-/compressible-2.0.18.tgz",
"integrity": "sha512-AF3r7P5dWxL8MxyITRMlORQNaOA2IkAFaTr4k7BUumjPtRpGDTZpl0Pb1XCO6JeDCBdp126Cgs9sMxqSjgYyRg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"mime-db": ">= 1.43.0 < 2"
},
"engines": {
"node": ">= 0.6"
}
},
"node_modules/compression": {
"version": "1.7.4",
"resolved": "https://registry.npmjs.org/compression/-/compression-1.7.4.tgz",
"integrity": "sha512-jaSIDzP9pZVS4ZfQ+TzvtiWhdpFhE2RDHz8QJkpX9SIpLq88VueF5jJw6t+6CUQcAoA6t+x89MLrWAqpfDE8iQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"accepts": "~1.3.5",
"bytes": "3.0.0",
"compressible": "~2.0.16",
"debug": "2.6.9",
"on-headers": "~1.0.2",
"safe-buffer": "5.1.2",
"vary": "~1.1.2"
},
"engines": {
"node": ">= 0.8.0"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/compression-webpack-plugin": {
"version": "9.2.0",
"resolved": "https://registry.npmjs.org/compression-webpack-plugin/-/compression-webpack-plugin-9.2.0.tgz",
"integrity": "sha512-R/Oi+2+UHotGfu72fJiRoVpuRifZT0tTC6UqFD/DUo+mv8dbOow9rVOuTvDv5nPPm3GZhHL/fKkwxwIHnJ8Nyw==",
"dev": true,
"dependencies": {
"schema-utils": "^4.0.0",
"serialize-javascript": "^6.0.0"
},
"engines": {
"node": ">= 12.13.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
},
"peerDependencies": {
"webpack": "^5.1.0"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/compression/node_modules/safe-buffer": {
"version": "5.1.2",
"resolved": "https://registry.npmjs.org/safe-buffer/-/safe-buffer-5.1.2.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/concat-map": {
"version": "0.0.1",
"resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"node_modules/connect-history-api-fallback": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/connect-history-api-fallback/-/connect-history-api-fallback-2.0.0.tgz",
"integrity": "sha512-U73+6lQFmfiNPrYbXqr6kZ1i1wiRqXnp2nhMsINseWXO8lDau0LGEffJ8kQi4EjLZympVgRdvqjAgiZ1tgzDDA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">=0.8"
}
},
"node_modules/content-disposition": {
"version": "0.5.4",
"resolved": "https://registry.npmjs.org/content-disposition/-/content-disposition-0.5.4.tgz",
"integrity": "sha512-FveZTNuGw04cxlAiWbzi6zTAL/lhehaWbTtgluJh4/E95DqMwTmha3KZN1aAWA8cFIhHzMZUvLevkw5Rqk+tSQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"safe-buffer": "5.2.1"
},
"engines": {
"node": ">= 0.6"
}
},
"node_modules/content-type": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/content-type/-/content-type-1.0.5.tgz",
"integrity": "sha512-nTjqfcBFEipKdXCv4YDQWCfmcLZKm81ldF0pAopTvyrFGVbcR6P/VAAd5G7N+0tTr8QqiU0tFadD6FK4NtJwOA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.6"
}
},
"node_modules/cookie": {
"version": "0.5.0",
"resolved": "https://registry.npmjs.org/cookie/-/cookie-0.5.0.tgz",
"integrity": "sha512-YZ3GUyn/o8gfKJlnlX7g7xq4gyO6OSuhGPKaaGssGB2qgDUS0gPgtTvoyZLTt9Ab6dC4hfc9dV5arkvc/OCmrw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.6"
}
},
"node_modules/cookie-signature": {
"version": "1.0.6",
"resolved": "https://registry.npmjs.org/cookie-signature/-/cookie-signature-1.0.6.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-QADzlaHc8icV8I7vbaJXJwod9HWYp8uCqf1xa4OfNu1T7JVxQIrUgOWtHdNDtPiywmFbiS12VjotIXLrKM3orQ==",
"dev": true
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/core-util-is": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.3.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-ZQBvi1DcpJ4GDqanjucZ2Hj3wEO5pZDS89BWbkcrvdxksJorwUDDZamX9ldFkp9aw2lmBDLgkObEA4DWNJ9FYQ==",
"dev": true
Add generated data to git
2022-03-28 22:05:51 +00:00
},
feat(zmodem): Allow file uploads/downloads Using zmodem (rz and sz commands from lrzsz) you can now send and receive files.
2022-03-29 20:59:22 +00:00
"node_modules/crc-32": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"version": "1.2.2",
"resolved": "https://registry.npmjs.org/crc-32/-/crc-32-1.2.2.tgz",
"integrity": "sha512-ROmzCKrTnOwybPcJApAA6WBWij23HVfGVNKqqrZpuyZOHqK2CwHSvpGuyt/UNNvaIjEd8X5IFGp4Mh+Ie1IHJQ==",
feat(zmodem): Allow file uploads/downloads Using zmodem (rz and sz commands from lrzsz) you can now send and receive files.
2022-03-29 20:59:22 +00:00
"bin": {
"crc32": "bin/crc32.njs"
},
"engines": {
"node": ">=0.8"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/cross-spawn": {
"version": "7.0.3",
"resolved": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.3.tgz",
"integrity": "sha512-iRDPJKUPVEND7dHPO8rkbOnPpyDygcDFtWjpeWNCgy8WP2rXcxXL8TskReQl6OrB2G7+UJrags1q15Fudc7G6w==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"path-key": "^3.1.0",
"shebang-command": "^2.0.0",
"which": "^2.0.1"
},
"engines": {
"node": ">= 8"
}
},
"node_modules/css-loader": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"version": "5.2.7",
"resolved": "https://registry.npmjs.org/css-loader/-/css-loader-5.2.7.tgz",
"integrity": "sha512-Q7mOvpBNBG7YrVGMxRxcBJZFL75o+cH2abNASdibkj/fffYD8qWbInZrD0S9ccI6vZclF3DsHE7njGlLtaHbhg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"icss-utils": "^5.1.0",
"loader-utils": "^2.0.0",
"postcss": "^8.2.15",
"postcss-modules-extract-imports": "^3.0.0",
"postcss-modules-local-by-default": "^4.0.0",
"postcss-modules-scope": "^3.0.0",
"postcss-modules-values": "^4.0.0",
"postcss-value-parser": "^4.1.0",
"schema-utils": "^3.0.0",
"semver": "^7.3.5"
},
"engines": {
"node": ">= 10.13.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
},
"peerDependencies": {
"webpack": "^4.27.0 || ^5.0.0"
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/css-loader/node_modules/ajv": {
"version": "6.12.6",
"resolved": "https://registry.npmjs.org/ajv/-/ajv-6.12.6.tgz",
"integrity": "sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==",
"dependencies": {
"fast-deep-equal": "^3.1.1",
"fast-json-stable-stringify": "^2.0.0",
"json-schema-traverse": "^0.4.1",
"uri-js": "^4.2.2"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"funding": {
"type": "github",
"url": "https://github.com/sponsors/epoberezkin"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/css-loader/node_modules/ajv-keywords": {
"version": "3.5.2",
"resolved": "https://registry.npmjs.org/ajv-keywords/-/ajv-keywords-3.5.2.tgz",
"integrity": "sha512-5p6WTN0DdTGVQk6VjcEju19IgaHudalcfabD7yhDGeA6bcQnmL+CpveLJq/3hvfwd1aof6L386Ougkx6RfyMIQ==",
"peerDependencies": {
"ajv": "^6.9.1"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/css-loader/node_modules/json-schema-traverse": {
"version": "0.4.1",
"resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz",
"integrity": "sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg=="
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/css-loader/node_modules/schema-utils": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/schema-utils/-/schema-utils-3.3.0.tgz",
"integrity": "sha512-pN/yOAvcC+5rQ5nERGuwrjLlYvLTbCibnZ1I7B1LaiAz9BRBlE9GMgE/eqV30P7aJQUf7Ddimy/RsbYO/GrVGg==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"@types/json-schema": "^7.0.8",
"ajv": "^6.12.5",
"ajv-keywords": "^3.5.2"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
"engines": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node": ">= 10.13.0"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/cssesc": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/cssesc/-/cssesc-3.0.0.tgz",
"integrity": "sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==",
"bin": {
"cssesc": "bin/cssesc"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
"engines": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node": ">=4"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/csstype": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.1.3",
"resolved": "https://registry.npmjs.org/csstype/-/csstype-3.1.3.tgz",
"integrity": "sha512-M1uQkMl8rQK/szD0LNhtqxIPLpimGm8sOBwU7lLnCpSbTyY3yeU1Vc7l4KT5zT4s/yOxHH5O7tIuuLOCnLADRw=="
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/debounce": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/debounce/-/debounce-1.2.1.tgz",
"integrity": "sha512-XRRe6Glud4rd/ZGQfiV1ruXSfbvfJedlV9Y6zOlP+2K04vBYiJEte6stfFkCP03aMnY5tsipamumUjL14fofug=="
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/debug": {
"version": "2.6.9",
"resolved": "https://registry.npmjs.org/debug/-/debug-2.6.9.tgz",
"integrity": "sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"ms": "2.0.0"
}
},
"node_modules/default-gateway": {
"version": "6.0.3",
"resolved": "https://registry.npmjs.org/default-gateway/-/default-gateway-6.0.3.tgz",
"integrity": "sha512-fwSOJsbbNzZ/CUFpqFBqYfYNLj1NbMPm8MMCIzHjC83iSJRBEGmDUxU+WP661BaBQImeC2yHwXtz+P/O9o+XEg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"execa": "^5.0.0"
},
"engines": {
"node": ">= 10"
}
},
npm update
2024-02-12 02:04:48 +00:00
"node_modules/define-data-property": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/define-data-property/-/define-data-property-1.1.2.tgz",
"integrity": "sha512-SRtsSqsDbgpJBbW3pABMCOt6rQyeM8s8RiyeSN8jYG8sYmt/kGJejbydttUsnDs1tadr19tvhT4ShwMyoqAm4g==",
"dev": true,
"dependencies": {
"es-errors": "^1.3.0",
"get-intrinsic": "^1.2.2",
"gopd": "^1.0.1",
"has-property-descriptors": "^1.0.1"
},
"engines": {
"node": ">= 0.4"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/define-lazy-prop": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/define-lazy-prop/-/define-lazy-prop-2.0.0.tgz",
"integrity": "sha512-Ds09qNh8yw3khSjiJjiUInaGX9xlqZDY7JVryGxdxV7NPeuqQfplOpQ66yJFZut3jLa5zOwkXw1g9EI2uKh4Og==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">=8"
}
},
"node_modules/depd": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/depd/-/depd-2.0.0.tgz",
"integrity": "sha512-g7nH6P6dyDioJogAAGprGpCtVImJhpPk/roCzdb3fIh61/s/nPsfR6onyMwkCAR/OlC3yBC0lESvUoQEAssIrw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.8"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/dequal": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/dequal/-/dequal-2.0.3.tgz",
"integrity": "sha512-0je+qPKHEMohvfRTCEo3CrPG6cAzAYgmzKyxRiYSSDkS6eGJdyVJm7WaYA5ECaAD9wLB2T4EEeymA5aFVcYXCA==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"engines": {
"node": ">=6"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/destroy": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/destroy/-/destroy-1.2.0.tgz",
"integrity": "sha512-2sJGJTaXIIaR1w4iJSNoN0hnMY7Gpc/n8D4qSCJw8QqFWXf7cuAgnEHxBpweaVcPevC2l3KpjYCx3NypQQgaJg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.8",
"npm": "1.2.8000 || >= 1.4.16"
}
},
"node_modules/detect-node": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/detect-node/-/detect-node-2.1.0.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-T0NIuQpnTvFDATNuHN5roPwSBG83rFsuO+MXXH9/3N1eFbn4wcPjttvjMLEPWJ0RGUYgQE7cGgS3tNxbqCGM7g==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"node_modules/dns-packet": {
npm update
2024-02-12 02:04:48 +00:00
"version": "5.6.1",
"resolved": "https://registry.npmjs.org/dns-packet/-/dns-packet-5.6.1.tgz",
"integrity": "sha512-l4gcSouhcgIKRvyy99RNVOgxXiicE+2jZoNmaNmZ6JXiGajBOJAesk1OBlJuM5k2c+eudGdLxDqXuPCKIj6kpw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"@leichtgewicht/ip-codec": "^2.0.1"
},
"engines": {
"node": ">=6"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/dom-helpers": {
"version": "5.2.1",
"resolved": "https://registry.npmjs.org/dom-helpers/-/dom-helpers-5.2.1.tgz",
"integrity": "sha512-nRCa7CK3VTrM2NmGkIy4cbK7IZlgBE/PYMn55rrXefr5xXDP0LdtfPnblFDoVdcAfslJ7or6iqAUnx0CCGIWQA==",
"dependencies": {
"@babel/runtime": "^7.8.7",
"csstype": "^3.0.2"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/ee-first": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/ee-first/-/ee-first-1.1.1.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-WMwm9LhRUo+WUaRN+vRuETqG89IgZphVSNkdFgeb6sS/E4OrDIN7t48CAewSHXc6C8lefD8KKfr5vY61brQlow==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/electron-to-chromium": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.4.665",
"resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.4.665.tgz",
"integrity": "sha512-UpyCWObBoD+nSZgOC2ToaIdZB0r9GhqT2WahPKiSki6ckkSuKhQNso8V2PrFcHBMleI/eqbKgVQgVC4Wni4ilw=="
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"node_modules/emojis-list": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/emojis-list/-/emojis-list-3.0.0.tgz",
"integrity": "sha512-/kyM18EfinwXZbno9FyUGeFh87KC8HRQBQGildHZbEuRyWFOmv1U10o9BBp8XVZDVNNuQKyIGIu5ZYAAXJ0V2Q==",
"engines": {
"node": ">= 4"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/encodeurl": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/encodeurl/-/encodeurl-1.0.2.tgz",
"integrity": "sha512-TPJXq8JqFaVYm2CWmPvnP2Iyo4ZSM7/QKcSmuMLDObfpH5fi7RUGmd/rTDf+rut/saiDiQEeVTNgAmJEdAOx0w==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.8"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/enhanced-resolve": {
"version": "4.5.0",
"resolved": "https://registry.npmjs.org/enhanced-resolve/-/enhanced-resolve-4.5.0.tgz",
"integrity": "sha512-Nv9m36S/vxpsI+Hc4/ZGRs0n9mXqSWGGq49zxb/cJfPAQMbUtttJAlNPS4AQzaBdw/pKskw5bMbekT/Y7W/Wlg==",
"dev": true,
"dependencies": {
"graceful-fs": "^4.1.2",
"memory-fs": "^0.5.0",
"tapable": "^1.0.0"
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/envinfo": {
npm update
2024-02-12 02:04:48 +00:00
"version": "7.11.1",
"resolved": "https://registry.npmjs.org/envinfo/-/envinfo-7.11.1.tgz",
"integrity": "sha512-8PiZgZNIB4q/Lw4AhOvAfB/ityHAd2bli3lESSWmWSzSsl5dKpy5N1d1Rfkd2teq/g9xN90lc6o98DOjMeYHpg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dev": true,
"bin": {
"envinfo": "dist/cli.js"
},
"engines": {
"node": ">=4"
}
},
"node_modules/errno": {
"version": "0.1.8",
"resolved": "https://registry.npmjs.org/errno/-/errno-0.1.8.tgz",
"integrity": "sha512-dJ6oBr5SQ1VSd9qkk7ByRgb/1SH4JZjCHSW/mr63/QcXO9zLVxvJ6Oy13nio03rxpSnVDDjFor75SjVeZWPW/A==",
"dev": true,
"dependencies": {
"prr": "~1.0.1"
},
"bin": {
"errno": "cli.js"
}
},
npm update
2024-02-12 02:04:48 +00:00
"node_modules/es-errors": {
"version": "1.3.0",
"resolved": "https://registry.npmjs.org/es-errors/-/es-errors-1.3.0.tgz",
"integrity": "sha512-Zf5H2Kxt2xjTvbJvP2ZWLEICxA6j+hAmMzIlypy4xcBg1vKVnx89Wy0GbS+kf5cwCVFFzdCFh2XSCFNULS6csw==",
"dev": true,
"engines": {
"node": ">= 0.4"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/es-module-lexer": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.4.1",
"resolved": "https://registry.npmjs.org/es-module-lexer/-/es-module-lexer-1.4.1.tgz",
"integrity": "sha512-cXLGjP0c4T3flZJKQSuziYoq7MlT+rnvfZjfp7h+I7K9BNX54kP9nyWvdbwjQ4u1iWbOL4u96fgeZLToQlZC7w=="
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"node_modules/escalade": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/escalade/-/escalade-3.1.2.tgz",
"integrity": "sha512-ErCHMCae19vR8vQGe50xIsVomy19rg6gFu3+r3jkEO46suLMWBksvVyoGgQV+jOfl84ZSOSlmv6Gxa89PmTGmA==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
"node": ">=6"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/escape-html": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/escape-html/-/escape-html-1.0.3.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-NiSupZ4OeuGwr68lGIeym/ksIZMJodUGOSCZ/FSnTxcrekbvqrgdUxlJOMpijaKZVjAJrWrGs/6Jy8OMuyj9ow==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/eslint-scope": {
"version": "5.1.1",
"resolved": "https://registry.npmjs.org/eslint-scope/-/eslint-scope-5.1.1.tgz",
"integrity": "sha512-2NxwbF/hZ0KpepYN0cNbo+FN6XoK7GaHlQhgx/hIZl6Va0bF45RQOOwhLIy8lQDbuCiadSLCBnH2CFYquit5bw==",
"dependencies": {
"esrecurse": "^4.3.0",
"estraverse": "^4.1.1"
},
"engines": {
"node": ">=8.0.0"
}
},
"node_modules/esrecurse": {
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/esrecurse/-/esrecurse-4.3.0.tgz",
"integrity": "sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag==",
"dependencies": {
"estraverse": "^5.2.0"
},
"engines": {
"node": ">=4.0"
}
},
"node_modules/esrecurse/node_modules/estraverse": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"version": "5.3.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz",
"integrity": "sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
"node": ">=4.0"
}
},
"node_modules/estraverse": {
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-4.3.0.tgz",
"integrity": "sha512-39nnKffWz8xN1BU/2c79n9nB9HDzo0niYUqx6xyqUnyoAnQyyWpOTdZEeiCch8BBu515t4wp9ZmgVfVhn9EBpw==",
"engines": {
"node": ">=4.0"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/etag": {
"version": "1.8.1",
"resolved": "https://registry.npmjs.org/etag/-/etag-1.8.1.tgz",
"integrity": "sha512-aIL5Fx7mawVa300al2BnEE4iNvo1qETxLrPI/o05L7z6go7fCw1J6EQmbK4FmJ2AS7kgVF/KEZWufBfdClMcPg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.6"
}
},
"node_modules/eventemitter3": {
"version": "4.0.7",
"resolved": "https://registry.npmjs.org/eventemitter3/-/eventemitter3-4.0.7.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-8guHBZCwKnFhYdHr2ysuRWErTwhoN2X8XELRlrRwpmfeY2jjuUN4taQMsULKUVo1K4DvZl+0pgfyoysHxvmvEw==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/events": {
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/events/-/events-3.3.0.tgz",
"integrity": "sha512-mQw+2fkQbALzQ7V0MY0IqdnXNOeTtP4r0lN9z7AAawCXgqea7bDii20AYrIBrFd/Hx0M2Ocz6S111CaFkUcb0Q==",
"engines": {
"node": ">=0.8.x"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/execa": {
"version": "5.1.1",
"resolved": "https://registry.npmjs.org/execa/-/execa-5.1.1.tgz",
"integrity": "sha512-8uSpZZocAZRBAPIEINJj3Lo9HyGitllczc27Eh5YYojjMFMn8yHMDMaUHE2Jqfq05D/wucwI4JGURyXt1vchyg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"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"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sindresorhus/execa?sponsor=1"
}
},
"node_modules/express": {
"version": "4.18.2",
"resolved": "https://registry.npmjs.org/express/-/express-4.18.2.tgz",
"integrity": "sha512-5/PsL6iGPdfQ/lKM1UuielYgv3BUoJfz1aUwU9vHZ+J7gyvwdQXFEBIEIaxeGf0GIcreATNyBExtalisDbuMqQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"accepts": "~1.3.8",
"array-flatten": "1.1.1",
"body-parser": "1.20.1",
"content-disposition": "0.5.4",
"content-type": "~1.0.4",
"cookie": "0.5.0",
"cookie-signature": "1.0.6",
"debug": "2.6.9",
"depd": "2.0.0",
"encodeurl": "~1.0.2",
"escape-html": "~1.0.3",
"etag": "~1.8.1",
"finalhandler": "1.2.0",
"fresh": "0.5.2",
"http-errors": "2.0.0",
"merge-descriptors": "1.0.1",
"methods": "~1.1.2",
"on-finished": "2.4.1",
"parseurl": "~1.3.3",
"path-to-regexp": "0.1.7",
"proxy-addr": "~2.0.7",
"qs": "6.11.0",
"range-parser": "~1.2.1",
"safe-buffer": "5.2.1",
"send": "0.18.0",
"serve-static": "1.15.0",
"setprototypeof": "1.2.0",
"statuses": "2.0.1",
"type-is": "~1.6.18",
"utils-merge": "1.0.1",
"vary": "~1.1.2"
},
"engines": {
"node": ">= 0.10.0"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/fast-deep-equal": {
"version": "3.1.3",
"resolved": "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz",
"integrity": "sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q=="
feat(zmodem): Allow file uploads/downloads Using zmodem (rz and sz commands from lrzsz) you can now send and receive files.
2022-03-29 20:59:22 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/fast-json-stable-stringify": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/fast-json-stable-stringify/-/fast-json-stable-stringify-2.1.0.tgz",
"integrity": "sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw=="
},
"node_modules/fastest-levenshtein": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"version": "1.0.16",
"resolved": "https://registry.npmjs.org/fastest-levenshtein/-/fastest-levenshtein-1.0.16.tgz",
"integrity": "sha512-eRnCtTTtGZFpQCwhJiUOuxPQWRXVKYDn0b2PeHfXL6/Zi53SLAzAHfVhVWK2AryC/WH05kGfxhFIPvTF0SXQzg==",
"dev": true,
"engines": {
"node": ">= 4.9.1"
}
Add generated data to git
2022-03-28 22:05:51 +00:00
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/faye-websocket": {
"version": "0.11.4",
"resolved": "https://registry.npmjs.org/faye-websocket/-/faye-websocket-0.11.4.tgz",
"integrity": "sha512-CzbClwlXAuiRQAlUyfqPgvPoNKTckTPGfwZV4ZdAhVcP2lh9KUxJg2b5GkE7XbjKQ3YJnQ9z6D9ntLAlB+tP8g==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"websocket-driver": ">=0.5.1"
},
"engines": {
"node": ">=0.8.0"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/fill-range": {
"version": "7.0.1",
"resolved": "https://registry.npmjs.org/fill-range/-/fill-range-7.0.1.tgz",
"integrity": "sha512-qOo9F+dMUmC2Lcb4BbVvnKJxTPjCm+RRpe4gDuGrzkL7mEVl/djYSu2OdQ2Pa302N4oqkSg9ir6jaLWJ2USVpQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"to-regex-range": "^5.0.1"
},
"engines": {
"node": ">=8"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/finalhandler": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/finalhandler/-/finalhandler-1.2.0.tgz",
"integrity": "sha512-5uXcUVftlQMFnWC9qu/svkWv3GTd2PfUhK/3PLkYNAe7FbqJMt3515HaxE6eRL74GdsriiwujiawdaB1BpEISg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"debug": "2.6.9",
"encodeurl": "~1.0.2",
"escape-html": "~1.0.3",
"on-finished": "2.4.1",
"parseurl": "~1.3.3",
"statuses": "2.0.1",
"unpipe": "~1.0.0"
},
"engines": {
"node": ">= 0.8"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/find-up": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-4.1.0.tgz",
"integrity": "sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"locate-path": "^5.0.0",
"path-exists": "^4.0.0"
},
"engines": {
"node": ">=8"
}
},
npm update
2024-02-12 02:04:48 +00:00
"node_modules/flat": {
"version": "5.0.2",
"resolved": "https://registry.npmjs.org/flat/-/flat-5.0.2.tgz",
"integrity": "sha512-b6suED+5/3rTpUBdG1gupIl8MPFCAMA0QXwmljLhvCUKcUvdE4gWky9zpuGCcXHOsz4J9wPGNWq6OKpmIzz3hQ==",
"dev": true,
"bin": {
"flat": "cli.js"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/follow-redirects": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.15.5",
"resolved": "https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.15.5.tgz",
"integrity": "sha512-vSFWUON1B+yAw1VN4xMfxgn5fTUiaOzAJCKBwIIgT/+7CuGy9+r+5gITvP62j3RmaD5Ph65UaERdOSRGUzZtgw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"funding": [
{
"type": "individual",
"url": "https://github.com/sponsors/RubenVerborgh"
}
],
"engines": {
"node": ">=4.0"
},
"peerDependenciesMeta": {
"debug": {
"optional": true
}
}
},
"node_modules/forwarded": {
"version": "0.2.0",
"resolved": "https://registry.npmjs.org/forwarded/-/forwarded-0.2.0.tgz",
"integrity": "sha512-buRG0fpBtRHSTCOASe6hD258tEubFoRLb4ZNA6NxMVHNw2gOcwHo9wyablzMzOA5z9xA9L1KNjk/Nt6MT9aYow==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.6"
}
},
"node_modules/fresh": {
"version": "0.5.2",
"resolved": "https://registry.npmjs.org/fresh/-/fresh-0.5.2.tgz",
"integrity": "sha512-zJ2mQYM18rEFOudeV4GShTGIQ7RbzA7ozbU9I/XBpm7kqgMywgmylMwXHxZJmkVoYkna9d2pVXVXPdYTP9ej8Q==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.6"
}
},
"node_modules/fs-monkey": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/fs-monkey/-/fs-monkey-1.0.5.tgz",
"integrity": "sha512-8uMbBjrhzW76TYgEV27Y5E//W2f/lTFmx78P2w19FZSxarhI/798APGQyuGCwmkNxgwGRhrLfvWyLBvNtuOmew==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/fs.realpath": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/fs.realpath/-/fs.realpath-1.0.0.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw==",
"dev": true
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
"node_modules/fsevents": {
npm update
2024-02-12 02:04:48 +00:00
"version": "2.3.3",
"resolved": "https://registry.npmjs.org/fsevents/-/fsevents-2.3.3.tgz",
"integrity": "sha512-5xoDfX+fL7faATnagmWPpbFtwh/R77WmMMqqHGS65C3vvB0YHrgF+B1YmZ3441tMj5n63k0212XNoJwzlhffQw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"hasInstallScript": true,
"optional": true,
"os": [
"darwin"
],
"engines": {
"node": "^8.16.0 || ^10.6.0 || >=11.0.0"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/function-bind": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/function-bind/-/function-bind-1.1.2.tgz",
"integrity": "sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA==",
"dev": true,
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"node_modules/get-intrinsic": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.2.4",
"resolved": "https://registry.npmjs.org/get-intrinsic/-/get-intrinsic-1.2.4.tgz",
"integrity": "sha512-5uYhsJH8VJBTv7oslg4BznJYhDoRI6waYCxMmCdnTrcCrHA/fCFKoTFz2JKKE0HdDFUF7/oQuhzumXJK7paBRQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"es-errors": "^1.3.0",
"function-bind": "^1.1.2",
"has-proto": "^1.0.1",
"has-symbols": "^1.0.3",
"hasown": "^2.0.0"
},
"engines": {
"node": ">= 0.4"
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/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==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
"node_modules/glob": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"version": "7.2.3",
"resolved": "https://registry.npmjs.org/glob/-/glob-7.2.3.tgz",
"integrity": "sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"minimatch": "^3.1.1",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"once": "^1.3.0",
"path-is-absolute": "^1.0.0"
},
"engines": {
"node": "*"
},
"funding": {
"url": "https://github.com/sponsors/isaacs"
}
},
"node_modules/glob-parent": {
"version": "5.1.2",
"resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz",
"integrity": "sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
"is-glob": "^4.0.1"
},
"engines": {
"node": ">= 6"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/glob-to-regexp": {
"version": "0.4.1",
"resolved": "https://registry.npmjs.org/glob-to-regexp/-/glob-to-regexp-0.4.1.tgz",
"integrity": "sha512-lkX1HJXwyMcprw/5YUZc2s7DrpAiHB21/V+E1rHUrVNokkvB6bqMzT0VfV6/86ZNabt1k14YOIaT7nDvOX3Iiw=="
},
npm update
2024-02-12 02:04:48 +00:00
"node_modules/gopd": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/gopd/-/gopd-1.0.1.tgz",
"integrity": "sha512-d65bNlIadxvpb/A2abVdlqKqV563juRnZ1Wtk6s1sIR8uNsXR70xqIzVqxVf1eTqDunwT2MkczEeaezCKTZhwA==",
"dev": true,
"dependencies": {
"get-intrinsic": "^1.1.3"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/graceful-fs": {
npm update
2024-02-12 02:04:48 +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=="
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/handle-thing": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/handle-thing/-/handle-thing-2.0.1.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-9Qn4yBxelxoh2Ow62nP+Ka/kMnOXRi8BXnRaUwezLNhqelnN49xKz4F/dPP8OYLxLxq6JDtZb2i9XznUQbNPTg==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/has-flag": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz",
"integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==",
"engines": {
"node": ">=8"
}
},
npm update
2024-02-12 02:04:48 +00:00
"node_modules/has-property-descriptors": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/has-property-descriptors/-/has-property-descriptors-1.0.1.tgz",
"integrity": "sha512-VsX8eaIewvas0xnvinAe9bw4WfIeODpGYikiWYLH+dma0Jw6KHYqWiWfhQlgOVK8D6PvjubK5Uc4P0iIhIcNVg==",
"dev": true,
"dependencies": {
"get-intrinsic": "^1.2.2"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/has-proto": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/has-proto/-/has-proto-1.0.1.tgz",
"integrity": "sha512-7qE+iP+O+bgF9clE5+UoBFzE65mlBiVj3tKCrlNQ0Ogwm0BjpT/gK4SlLYDMybDh5I3TCTKnPPa0oMG7JDYrhg==",
"dev": true,
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/has-symbols": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.3.tgz",
"integrity": "sha512-l3LCuF6MgDNwTDKkdYGEihYjt5pRPbEg46rtlmnSPlUbgmB8LOIrKJbYYFBSbnPaJexMKtiPO8hmeRjRz2Td+A==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node": ">= 0.4"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"funding": {
"url": "https://github.com/sponsors/ljharb"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
npm update
2024-02-12 02:04:48 +00:00
"node_modules/hasown": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/hasown/-/hasown-2.0.1.tgz",
"integrity": "sha512-1/th4MHjnwncwXsIW6QMzlvYL9kG5e/CpVvLRZe4XPa8TOUNbCELqmvhDmnkNsAjwaG4+I8gJJL0JBvTTLO9qA==",
"dev": true,
"dependencies": {
"function-bind": "^1.1.2"
},
"engines": {
"node": ">= 0.4"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/hpack.js": {
"version": "2.1.6",
"resolved": "https://registry.npmjs.org/hpack.js/-/hpack.js-2.1.6.tgz",
"integrity": "sha512-zJxVehUdMGIKsRaNt7apO2Gqp0BdqW5yaiGHXXmbpvxgBYVZnAql+BJb4RO5ad2MgpbZKn5G6nMnegrH1FcNYQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"inherits": "^2.0.1",
"obuf": "^1.0.0",
"readable-stream": "^2.0.1",
"wbuf": "^1.1.0"
}
},
"node_modules/html-entities": {
npm update
2024-02-12 02:04:48 +00:00
"version": "2.4.0",
"resolved": "https://registry.npmjs.org/html-entities/-/html-entities-2.4.0.tgz",
"integrity": "sha512-igBTJcNNNhvZFRtm8uA6xMY6xYleeDwn3PeBCkDz7tHttv4F2hsDI2aPgNERWzvRcNYHNT3ymRaQzllmXj4YsQ==",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/mdevils"
},
{
"type": "patreon",
"url": "https://patreon.com/mdevils"
}
]
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"node_modules/http-deceiver": {
"version": "1.2.7",
"resolved": "https://registry.npmjs.org/http-deceiver/-/http-deceiver-1.2.7.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-LmpOGxTfbpgtGVxJrj5k7asXHCgNZp5nLfp+hWc8QQRqtb7fUy6kRY3BO1h9ddF6yIPYUARgxGOwB42DnxIaNw==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"node_modules/http-errors": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/http-errors/-/http-errors-2.0.0.tgz",
"integrity": "sha512-FtwrG/euBzaEjYeRqOgly7G0qviiXoJWnvEH2Z1plBdXgbyjv34pHTSb9zoeHMyDy33+DWy5Wt9Wo+TURtOYSQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"depd": "2.0.0",
"inherits": "2.0.4",
"setprototypeof": "1.2.0",
"statuses": "2.0.1",
"toidentifier": "1.0.1"
},
"engines": {
"node": ">= 0.8"
}
},
"node_modules/http-parser-js": {
"version": "0.5.8",
"resolved": "https://registry.npmjs.org/http-parser-js/-/http-parser-js-0.5.8.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-SGeBX54F94Wgu5RH3X5jsDtf4eHyRogWX1XGT3b4HuW3tQPM4AaBzoUji/4AAJNXCEOWZ5O0DgZmJw1947gD5Q==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"node_modules/http-proxy": {
"version": "1.18.1",
"resolved": "https://registry.npmjs.org/http-proxy/-/http-proxy-1.18.1.tgz",
"integrity": "sha512-7mz/721AbnJwIVbnaSv1Cz3Am0ZLT/UBwkC92VlxhXv/k/BBQfM2fXElQNC27BVGr0uwUpplYPQM9LnaBMR5NQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"eventemitter3": "^4.0.0",
"follow-redirects": "^1.0.0",
"requires-port": "^1.0.0"
},
"engines": {
"node": ">=8.0.0"
}
},
"node_modules/http-proxy-middleware": {
"version": "2.0.6",
"resolved": "https://registry.npmjs.org/http-proxy-middleware/-/http-proxy-middleware-2.0.6.tgz",
"integrity": "sha512-ya/UeJ6HVBYxrgYotAZo1KvPWlgB48kUJLDePFeneHsVujFaW5WNj2NgWCAE//B1Dl02BIfYlpNgBy8Kf8Rjmw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"@types/http-proxy": "^1.17.8",
"http-proxy": "^1.18.1",
"is-glob": "^4.0.1",
"is-plain-obj": "^3.0.0",
"micromatch": "^4.0.2"
},
"engines": {
"node": ">=12.0.0"
},
"peerDependencies": {
"@types/express": "^4.17.13"
},
"peerDependenciesMeta": {
"@types/express": {
"optional": true
}
}
},
"node_modules/human-signals": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/human-signals/-/human-signals-2.1.0.tgz",
"integrity": "sha512-B4FFZ6q/T2jhhksgkbEW3HBvWIfDW85snkQgawt07S7J5QXTk6BkNV+0yAeZrM5QpMAdYlocGoljn0sJ/WQkFw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">=10.17.0"
}
},
"node_modules/iconv-lite": {
"version": "0.4.24",
"resolved": "https://registry.npmjs.org/iconv-lite/-/iconv-lite-0.4.24.tgz",
"integrity": "sha512-v3MXnZAcvnywkTUEZomIActle7RXXeedOR31wwl7VlyoXO4Qi9arvSenNQWne1TcRwhCL1HwLI21bEqdpj8/rA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"safer-buffer": ">= 2.1.2 < 3"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/icss-utils": {
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/icss-utils/-/icss-utils-5.1.0.tgz",
"integrity": "sha512-soFhflCVWLfRNOPU3iv5Z9VUdT44xFRbzjLsEzSr5AQmgqPMTHdU3PMT1Cf1ssx8fLNJDA1juftYl+PUcv3MqA==",
"engines": {
"node": "^10 || ^12 || >= 14"
},
"peerDependencies": {
"postcss": "^8.1.0"
}
},
"node_modules/immutable": {
npm update
2024-02-12 02:04:48 +00:00
"version": "4.3.5",
"resolved": "https://registry.npmjs.org/immutable/-/immutable-4.3.5.tgz",
"integrity": "sha512-8eabxkth9gZatlwl5TBuJnCsoTADlL6ftEr7A4qgdaTsPyreilDSnUk57SO+jfKcNtxPa22U5KK6DSeAYhpBJw==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dev": true
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/import-local": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/import-local/-/import-local-3.1.0.tgz",
"integrity": "sha512-ASB07uLtnDs1o6EHjKpX34BKYDSqnFerfTOJL2HvMqF70LnxpjkzDB8J44oT9pu4AMPkQwf8jl6szgvNd2tRIg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dev": true,
"dependencies": {
"pkg-dir": "^4.2.0",
"resolve-cwd": "^3.0.0"
},
"bin": {
"import-local-fixture": "fixtures/cli.js"
},
"engines": {
"node": ">=8"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/inflight": {
"version": "1.0.6",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.6.tgz",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"integrity": "sha512-k92I/b08q4wvFscXCLvqfsHCrjrF7yiXsQuIVvVE7N82W3+aqpzuUdBbfhWcy/FZR3/4IgflMgKLOsvPDrGCJA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
"once": "^1.3.0",
"wrappy": "1"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
"node_modules/inherits": {
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.4.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==",
"dev": true
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"node_modules/interpret": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/interpret/-/interpret-2.2.0.tgz",
"integrity": "sha512-Ju0Bz/cEia55xDwUWEa8+olFpCiQoypjnQySseKtmjNrnps3P+xfpUmGr90T7yjlVJmOtybRvPXhKMbHr+fWnw==",
"dev": true,
"engines": {
"node": ">= 0.10"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/invariant": {
"version": "2.2.4",
"resolved": "https://registry.npmjs.org/invariant/-/invariant-2.2.4.tgz",
"integrity": "sha512-phJfQVBuaJM5raOpJjSfkiD6BpbCE4Ns//LaXl6wGYtUBY83nWS6Rf9tXm2e8VaK60JEjYldbPif/A2B1C2gNA==",
"dependencies": {
"loose-envify": "^1.0.0"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/ipaddr.js": {
npm update
2024-02-12 02:04:48 +00:00
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/ipaddr.js/-/ipaddr.js-2.1.0.tgz",
"integrity": "sha512-LlbxQ7xKzfBusov6UMi4MFpEg0m+mAm9xyNGEduwXMEDuf4WfzB/RZwMVYEd7IKGvh4IUkEXYxtAVu9T3OelJQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 10"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/is-binary-path": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/is-binary-path/-/is-binary-path-2.1.0.tgz",
"integrity": "sha512-ZMERYes6pDydyuGidse7OsHxtbI7WVeUEozgR/g7rd0xUimYNlvZRE/K2MgZTjWy725IfelLeVcEM97mmtRGXw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
"binary-extensions": "^2.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/is-core-module": {
npm update
2024-02-12 02:04:48 +00:00
"version": "2.13.1",
"resolved": "https://registry.npmjs.org/is-core-module/-/is-core-module-2.13.1.tgz",
"integrity": "sha512-hHrIjvZsftOsvKSn2TRYl63zvxsgE0K+0mYMoH6gD4omR5IWB2KynivBQczo3+wF1cCkjzvptnI9Q0sPU66ilw==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"hasown": "^2.0.0"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/is-docker": {
"version": "2.2.1",
"resolved": "https://registry.npmjs.org/is-docker/-/is-docker-2.2.1.tgz",
"integrity": "sha512-F+i2BKsFrH66iaUFc0woD8sLy8getkwTwtOBjvs56Cx4CgJDeKQeqfz8wAYiSb8JOprWhHH5p77PbmYCvvUuXQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"bin": {
"is-docker": "cli.js"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/is-extglob": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/is-extglob/-/is-extglob-2.1.1.tgz",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"integrity": "sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/is-glob": {
"version": "4.0.3",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz",
"integrity": "sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
"is-extglob": "^2.1.1"
},
"engines": {
"node": ">=0.10.0"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/is-number": {
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/is-number/-/is-number-7.0.0.tgz",
"integrity": "sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
"node": ">=0.12.0"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/is-plain-obj": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/is-plain-obj/-/is-plain-obj-3.0.0.tgz",
"integrity": "sha512-gwsOE28k+23GP1B6vFl1oVh/WOzmawBrKwo5Ev6wMKzPkaXaCDIQKzLnvsA42DRlbVTWorkgTKIviAKCWkfUwA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/is-plain-object": {
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/is-plain-object/-/is-plain-object-2.0.4.tgz",
"integrity": "sha512-h5PpgXkWitc38BBMYawTYMWJHFZJVnBquFE57xFpjB8pJFiF6gZ+bU+WyI/yqXiFR5mdLsgYNaPe8uao6Uv9Og==",
"dev": true,
"dependencies": {
"isobject": "^3.0.1"
},
"engines": {
"node": ">=0.10.0"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/is-stream": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/is-stream/-/is-stream-2.0.1.tgz",
"integrity": "sha512-hFoiJiTl63nn+kstHGBtewWSKnQLpyb155KHheA1l39uvtO9nWIop1p3udqPcUd/xbF1VLMO4n7OI6p7RbngDg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/is-wsl": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/is-wsl/-/is-wsl-2.2.0.tgz",
"integrity": "sha512-fKzAra0rGJUUBwGBgNkHZuToZcn+TtXHpeCgmkMJMMYx1sQDYaCSyjJBSCa2nH1DGm7s3n1oBnohoVTBaN7Lww==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"is-docker": "^2.0.0"
},
"engines": {
"node": ">=8"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/isarray": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-VLghIWNM6ELQzo7zwmcg0NmTVyWKYjvIeM83yjp0wRDTmUnrM678fQbcKBo6n2CJEF0szoG//ytg+TKla89ALQ==",
"dev": true
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"node_modules/isexe": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==",
"dev": true
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"node_modules/isobject": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/isobject/-/isobject-3.0.1.tgz",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"integrity": "sha512-WhB9zCku7EGTj/HQQRz5aUQEUeoQZH2bWcltRErOpymJ4boYE6wL9Tbr23krRPSZ+C5zqNSrSw+Cc7sZZ4b7vg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/jest-worker": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"version": "27.5.1",
"resolved": "https://registry.npmjs.org/jest-worker/-/jest-worker-27.5.1.tgz",
"integrity": "sha512-7vuh85V5cdDofPyxn58nrPjBktZo0u9x1g8WtjQol+jZDaE+fhN+cIvTj11GndBnMnyfrUOG1sZQxCdjKh+DKg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"@types/node": "*",
"merge-stream": "^2.0.0",
"supports-color": "^8.0.0"
},
"engines": {
"node": ">= 10.13.0"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/js-tokens": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/js-tokens/-/js-tokens-4.0.0.tgz",
"integrity": "sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ=="
},
"node_modules/json-parse-even-better-errors": {
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/json-parse-even-better-errors/-/json-parse-even-better-errors-2.3.1.tgz",
"integrity": "sha512-xyFwyhro/JEof6Ghe2iz2NcXoj2sloNsWr/XsERDK/oiPCfaNhl5ONfp+jQdAZRQQ0IJWNzH9zIZF7li91kh2w=="
},
"node_modules/json-schema-traverse": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-1.0.0.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug==",
"dev": true
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/json5": {
Bump json5 from 2.2.1 to 2.2.3 in /js Bumps [json5](https://github.com/json5/json5) from 2.2.1 to 2.2.3. - [Release notes](https://github.com/json5/json5/releases) - [Changelog](https://github.com/json5/json5/blob/main/CHANGELOG.md) - [Commits](https://github.com/json5/json5/compare/v2.2.1...v2.2.3) --- updated-dependencies: - dependency-name: json5 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2023-01-08 16:20:35 +00:00
"version": "2.2.3",
"resolved": "https://registry.npmjs.org/json5/-/json5-2.2.3.tgz",
"integrity": "sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"bin": {
"json5": "lib/cli.js"
},
"engines": {
"node": ">=6"
}
},
"node_modules/kind-of": {
"version": "6.0.3",
"resolved": "https://registry.npmjs.org/kind-of/-/kind-of-6.0.3.tgz",
"integrity": "sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
"node": ">=0.10.0"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/klona": {
npm update
2024-02-12 02:04:48 +00:00
"version": "2.0.6",
"resolved": "https://registry.npmjs.org/klona/-/klona-2.0.6.tgz",
"integrity": "sha512-dhG34DXATL5hSxJbIexCft8FChFXtmskoZYnoPWjXQuebWYCNkVeV3KkGegCK9CP1oswI/vQibS2GY7Em/sJJA==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dev": true,
"engines": {
"node": ">= 8"
}
},
npm update
2024-02-12 02:04:48 +00:00
"node_modules/launch-editor": {
"version": "2.6.1",
"resolved": "https://registry.npmjs.org/launch-editor/-/launch-editor-2.6.1.tgz",
"integrity": "sha512-eB/uXmFVpY4zezmGp5XtU21kwo7GBbKB+EQ+UZeWtGb9yAM5xt/Evk+lYH3eRNAtId+ej4u7TYPFZ07w4s7rRw==",
"dev": true,
"dependencies": {
"picocolors": "^1.0.0",
"shell-quote": "^1.8.1"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/license-loader": {
"version": "0.5.0",
"resolved": "https://registry.npmjs.org/license-loader/-/license-loader-0.5.0.tgz",
"integrity": "sha512-4p+estbTHilHxOXv/wh8qHndksfINzBT6HGvgIU4sfwWu28kCByHGV57K/HVgSujoFFv2wCITghGbK/qRiRbUQ==",
"dev": true
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/license-webpack-plugin": {
"version": "4.0.2",
"resolved": "https://registry.npmjs.org/license-webpack-plugin/-/license-webpack-plugin-4.0.2.tgz",
"integrity": "sha512-771TFWFD70G1wLTC4oU2Cw4qvtmNrIw+wRvBtn+okgHl7slJVi7zfNcdmqDL72BojM30VNJ2UHylr1o77U37Jw==",
"dev": true,
"dependencies": {
"webpack-sources": "^3.0.0"
},
"peerDependenciesMeta": {
"webpack": {
"optional": true
},
"webpack-sources": {
"optional": true
}
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/loader-runner": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +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==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
"node": ">=6.11.5"
}
},
"node_modules/loader-utils": {
Bump loader-utils from 2.0.3 to 2.0.4 in /js Bumps [loader-utils](https://github.com/webpack/loader-utils) from 2.0.3 to 2.0.4. - [Release notes](https://github.com/webpack/loader-utils/releases) - [Changelog](https://github.com/webpack/loader-utils/blob/v2.0.4/CHANGELOG.md) - [Commits](https://github.com/webpack/loader-utils/compare/v2.0.3...v2.0.4) --- updated-dependencies: - dependency-name: loader-utils dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-18 00:42:09 +00:00
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.4.tgz",
"integrity": "sha512-xXqpXoINfFhgua9xiqD8fPFHgkoq1mmmpE92WlDbm9rNRd/EbRb+Gqf908T2DMfuHjjJlksiK2RbHVOdD/MqSw==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"big.js": "^5.2.2",
"emojis-list": "^3.0.0",
"json5": "^2.1.2"
},
"engines": {
"node": ">=8.9.0"
}
},
"node_modules/locate-path": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/locate-path/-/locate-path-5.0.0.tgz",
"integrity": "sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"p-locate": "^4.1.0"
},
"engines": {
"node": ">=8"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/loose-envify": {
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/loose-envify/-/loose-envify-1.4.0.tgz",
"integrity": "sha512-lyuxPGr/Wfhrlem2CL/UcnUc1zcqKAImBDzukY7Y5F/yQiNdko6+fRLevlw1HgMySw7f611UIY408EtxRSoK3Q==",
"dependencies": {
"js-tokens": "^3.0.0 || ^4.0.0"
},
"bin": {
"loose-envify": "cli.js"
}
},
npm update
2024-02-12 02:04:48 +00:00
"node_modules/lru-cache": {
"version": "6.0.0",
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-6.0.0.tgz",
"integrity": "sha512-Jo6dJ04CmSjuznwJSS3pUeWmd/H0ffTlkXXgwZi+eq1UCmqQwCh+eLsYOYCwY991i2Fah4h1BEMCx4qThGbsiA==",
"dependencies": {
"yallist": "^4.0.0"
},
"engines": {
"node": ">=10"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/media-typer": {
"version": "0.3.0",
"resolved": "https://registry.npmjs.org/media-typer/-/media-typer-0.3.0.tgz",
"integrity": "sha512-dq+qelQ9akHpcOl/gUVRTxVIOkAJ1wR3QAvb4RsVjS8oVoFjDGTc679wJYmUmknUF5HwMLOgb5O+a3KxfWapPQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.6"
}
},
"node_modules/memfs": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.5.3",
"resolved": "https://registry.npmjs.org/memfs/-/memfs-3.5.3.tgz",
"integrity": "sha512-UERzLsxzllchadvbPs5aolHh65ISpKpM+ccLbOJ8/vvpBKmAWf+la7dXFy7Mr0ySHbdHrFv5kGFCUHHe6GFEmw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"fs-monkey": "^1.0.4"
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"engines": {
"node": ">= 4.0.0"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/memory-fs": {
"version": "0.5.0",
"resolved": "https://registry.npmjs.org/memory-fs/-/memory-fs-0.5.0.tgz",
"integrity": "sha512-jA0rdU5KoQMC0e6ppoNRtpp6vjFq6+NY7r8hywnC7V+1Xj/MtHwGIbB1QaK/dunyjWteJzmkpd7ooeWg10T7GA==",
"dev": true,
"dependencies": {
"errno": "^0.1.3",
"readable-stream": "^2.0.1"
},
"engines": {
"node": ">=4.3.0 <5.0.0 || >=5.10"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/merge-descriptors": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/merge-descriptors/-/merge-descriptors-1.0.1.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-cCi6g3/Zr1iqQi6ySbseM1Xvooa98N0w31jzUYrXPX2xqObmFGHJ0tQ5u74H3mVh7wLouTseZyYIq39g8cNp1w==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/merge-stream": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/merge-stream/-/merge-stream-2.0.0.tgz",
"integrity": "sha512-abv/qOcuPfk3URPfDzmZU1LKmuw8kT+0nIHvKrKgFrwifol/doWcdA4ZqsWQ8ENrFKkd67Mfpo/LovbIUsbt3w=="
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/methods": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/methods/-/methods-1.1.2.tgz",
"integrity": "sha512-iclAHeNqNm68zFtnZ0e+1L2yUIdvzNoauKU4WBA3VvH/vPFieF7qfRlwUZU+DA9P9bPXIS90ulxoUoCH23sV2w==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.6"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/micromatch": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"version": "4.0.5",
"resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.5.tgz",
"integrity": "sha512-DMy+ERcEW2q8Z2Po+WNXuw3c5YaUSFjAO5GsJqfEl7UjvtIuFKO6ZrKvcItdy98dwFI2N1tg3zNIdKaQT+aNdA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"braces": "^3.0.2",
"picomatch": "^2.3.1"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"engines": {
"node": ">=8.6"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/mime": {
"version": "1.6.0",
"resolved": "https://registry.npmjs.org/mime/-/mime-1.6.0.tgz",
"integrity": "sha512-x0Vn8spI+wuJ1O6S7gnbaQg8Pxh4NNHb7KSINmEWKiPE4RKOplvijn+NkmYmmRgP68mc70j2EbeTFRsrswaQeg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"bin": {
"mime": "cli.js"
},
"engines": {
"node": ">=4"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/mime-db": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"version": "1.52.0",
"resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.52.0.tgz",
"integrity": "sha512-sPU4uV7dYlvtWJxwwxHD0PuihVNiE7TyAbQ5SWxDCB9mUYvOgroQOwYQQOKPJ8CIbE+1ETVlOoK1UC2nU3gYvg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
"node": ">= 0.6"
}
},
"node_modules/mime-types": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +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==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"mime-db": "1.52.0"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"engines": {
"node": ">= 0.6"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/mimic-fn": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/mimic-fn/-/mimic-fn-2.1.0.tgz",
"integrity": "sha512-OqbOk5oEQeAZ8WXWydlu9HJjz9WVdEIvamMCcXmuqUYjTknH/sqsWvhQ3vgwKFRR1HpjvNBKQ37nbJgYzGqGcg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">=6"
}
},
"node_modules/minimalistic-assert": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/minimalistic-assert/-/minimalistic-assert-1.0.1.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-UtJcAD4yEaGtjPezWuO9wC4nwUnVH/8/Im3yEHQP4b67cXlD/Qr9hdITCU1xDbSEXg2XKNaP8jsReV7vQd00/A==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/minimatch": {
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz",
"integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
"brace-expansion": "^1.1.7"
},
"engines": {
"node": "*"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/ms": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.0.0.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-Tpp60P6IUJDTuOq/5Z8cdskzJujfwqfOTkrwIwj7IRISpnkJnT6SyJ4PCPnGMoFjC9ddhal5KVIYtAt97ix05A==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"node_modules/multicast-dns": {
"version": "7.2.5",
"resolved": "https://registry.npmjs.org/multicast-dns/-/multicast-dns-7.2.5.tgz",
"integrity": "sha512-2eznPJP8z2BFLX50tf0LuODrpINqP1RVIm/CObbTcBRITQgmC/TjcREF1NeTBzIcR5XO/ukWo+YHOjBbFwIupg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"dns-packet": "^5.2.2",
"thunky": "^1.0.2"
},
"bin": {
"multicast-dns": "cli.js"
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/nanoid": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.3.7",
"resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.3.7.tgz",
"integrity": "sha512-eSRppjcPIatRIMC1U6UngP8XFcz8MQWGQdt1MTBQ7NaAmvXDfvNxbvWV3x2y6CdEUciCSsDHDQZbhYaB8QEo2g==",
Bump postcss from 8.4.16 to 8.4.31 in /js Bumps [postcss](https://github.com/postcss/postcss) from 8.4.16 to 8.4.31. - [Release notes](https://github.com/postcss/postcss/releases) - [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md) - [Commits](https://github.com/postcss/postcss/compare/8.4.16...8.4.31) --- updated-dependencies: - dependency-name: postcss dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2023-10-07 03:47:51 +00:00
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/ai"
}
],
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"bin": {
"nanoid": "bin/nanoid.cjs"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
"engines": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node": "^10 || ^12 || ^13.7 || ^14 || >=15.0.1"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/negotiator": {
"version": "0.6.3",
"resolved": "https://registry.npmjs.org/negotiator/-/negotiator-0.6.3.tgz",
"integrity": "sha512-+EUsqGPLsM+j/zdChZjsnX51g4XrHFOIXwfnCVPGlQk/k5giakcKsuxCObBRu6DSm9opw/O6slWbJdghQM4bBg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.6"
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/neo-async": {
"version": "2.6.2",
"resolved": "https://registry.npmjs.org/neo-async/-/neo-async-2.6.2.tgz",
"integrity": "sha512-Yd3UES5mWCSqR+qNT93S3UoYUkqAZ9lLg8a7g9rimsWmYGK8cVToA4/sF3RrshdyV3sAGMXVUmpMYOw+dLpOuw=="
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/node-forge": {
"version": "1.3.1",
"resolved": "https://registry.npmjs.org/node-forge/-/node-forge-1.3.1.tgz",
"integrity": "sha512-dPEtOeMvF9VMcYV/1Wb8CPoVAXtp6MKMlcbAt4ddqmGqUJ6fQZFXkNZNkNlfevtNkGtaSoXf/vNNNSvgrdXwtA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 6.13.0"
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/node-releases": {
npm update
2024-02-12 02:04:48 +00:00
"version": "2.0.14",
"resolved": "https://registry.npmjs.org/node-releases/-/node-releases-2.0.14.tgz",
"integrity": "sha512-y10wOWt8yZpqXmOgRo77WaHEmhYQYGNA6y421PKsKYWEK8aW+cqAphborZDhqfyKrbZEN92CN1X2KbafY2s7Yw=="
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
},
"node_modules/normalize-path": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/normalize-path/-/normalize-path-3.0.0.tgz",
"integrity": "sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"engines": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node": ">=0.10.0"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/npm-run-path": {
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/npm-run-path/-/npm-run-path-4.0.1.tgz",
"integrity": "sha512-S48WzZW777zhNIrn7gxOlISNAqi9ZC/uQFnRdbeIHhZhCA6UqpkOT8T1G7BvfdgP4Er8gF4sUbaS0i7QvIfCWw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"path-key": "^3.0.0"
},
"engines": {
"node": ">=8"
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/object-assign": {
"version": "4.1.1",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.1.1.tgz",
"integrity": "sha512-rJgTQnkUnH1sFw8yT6VSU3zD3sWmu6sZhIseY8VX+GRu3P6F7Fu+JNDoXfklElbLJSnc3FUQHVe4cU5hj+BcUg==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"engines": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node": ">=0.10.0"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/object-inspect": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.13.1",
"resolved": "https://registry.npmjs.org/object-inspect/-/object-inspect-1.13.1.tgz",
"integrity": "sha512-5qoj1RUiKOMsCCNLV1CBiPYE10sziTsnmNxkAI/rZhiD63CF7IqdFGC/XzjWjpSgLf0LxXX3bDFIh0E18f6UhQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/obuf": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/obuf/-/obuf-1.1.2.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-PX1wu0AmAdPqOL1mWhqmlOd8kOIZQwGZw6rh7uby9fTc5lhaOWFLX3I6R1hrF9k3zUY40e6igsLGkDXK92LJNg==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"node_modules/on-finished": {
"version": "2.4.1",
"resolved": "https://registry.npmjs.org/on-finished/-/on-finished-2.4.1.tgz",
"integrity": "sha512-oVlzkg3ENAhCk2zdv7IJwd/QUD4z2RxRwpkcGY8psCVcCYZNq4wYnVWALHM+brtuJjePWiYF/ClmuDr8Ch5+kg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"ee-first": "1.1.1"
},
"engines": {
"node": ">= 0.8"
}
},
"node_modules/on-headers": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/on-headers/-/on-headers-1.0.2.tgz",
"integrity": "sha512-pZAE+FJLoyITytdqK0U5s+FIpjN0JP3OzFi/u8Rx+EV5/W+JTWGXG8xFzevE7AjBfDqHv/8vL8qQsIhHnqRkrA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.8"
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/once": {
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/once/-/once-1.4.0.tgz",
"integrity": "sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"wrappy": "1"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/onetime": {
"version": "5.1.2",
"resolved": "https://registry.npmjs.org/onetime/-/onetime-5.1.2.tgz",
"integrity": "sha512-kbpaSSGJTWdAY5KPVeMOKXSrPtr8C8C7wodJbcsd51jRnmD+GZu8Y0VoU6Dm5Z4vWr0Ig/1NKuWRKf7j5aaYSg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"mimic-fn": "^2.1.0"
},
"engines": {
"node": ">=6"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/open": {
npm update
2024-02-12 02:04:48 +00:00
"version": "8.4.2",
"resolved": "https://registry.npmjs.org/open/-/open-8.4.2.tgz",
"integrity": "sha512-7x81NCL719oNbsq/3mh+hVrAWmFuEYUqrq/Iw3kUzH8ReypT9QQ0BLoJS7/G9k6N81XjW4qHWtjWwe/9eLy1EQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"define-lazy-prop": "^2.0.0",
"is-docker": "^2.1.1",
"is-wsl": "^2.2.0"
},
"engines": {
"node": ">=12"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/p-limit": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/p-limit/-/p-limit-2.3.0.tgz",
"integrity": "sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"p-try": "^2.0.0"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"engines": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node": ">=6"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/p-locate": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/p-locate/-/p-locate-4.1.0.tgz",
"integrity": "sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"p-limit": "^2.2.0"
},
"engines": {
"node": ">=8"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/p-retry": {
"version": "4.6.2",
"resolved": "https://registry.npmjs.org/p-retry/-/p-retry-4.6.2.tgz",
"integrity": "sha512-312Id396EbJdvRONlngUx0NydfrIQ5lsYu0znKVUzVvArzEIt08V1qhtyESbGVd1FGX7UKtiFp5uwKZdM8wIuQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"@types/retry": "0.12.0",
"retry": "^0.13.1"
},
"engines": {
"node": ">=8"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/p-try": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/p-try/-/p-try-2.2.0.tgz",
"integrity": "sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
"node": ">=6"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/parseurl": {
"version": "1.3.3",
"resolved": "https://registry.npmjs.org/parseurl/-/parseurl-1.3.3.tgz",
"integrity": "sha512-CiyeOxFT/JZyN5m0z9PfXw4SCBJ6Sygz1Dpl0wqjlhDEGGBP1GnsUVEL0p63hoG1fcj3fHynXi9NYO4nWOL+qQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.8"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/path-exists": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-4.0.0.tgz",
"integrity": "sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
"node": ">=8"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/path-is-absolute": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.1.tgz",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"integrity": "sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"engines": {
"node": ">=0.10.0"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/path-key": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/path-key/-/path-key-3.1.1.tgz",
"integrity": "sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
"node": ">=8"
}
},
"node_modules/path-parse": {
"version": "1.0.7",
"resolved": "https://registry.npmjs.org/path-parse/-/path-parse-1.0.7.tgz",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"integrity": "sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==",
"dev": true
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/path-to-regexp": {
"version": "0.1.7",
"resolved": "https://registry.npmjs.org/path-to-regexp/-/path-to-regexp-0.1.7.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-5DFkuoqlv1uYQKxy8omFBeJPQcdoE07Kv2sferDCrAq1ohOU+MSDswDIbnx3YAM60qIOnYa53wBhXW0EbMonrQ==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/picocolors": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/picocolors/-/picocolors-1.0.0.tgz",
"integrity": "sha512-1fygroTLlHu66zi26VoTDv8yRgm0Fccecssto+MhsZ0D/DGW2sm8E8AjW7NU5VVTRt5GxbeZ5qBuJr+HyLYkjQ=="
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"node_modules/picomatch": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/picomatch/-/picomatch-2.3.1.tgz",
"integrity": "sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
"node": ">=8.6"
},
"funding": {
"url": "https://github.com/sponsors/jonschlinkert"
}
},
"node_modules/pkg-dir": {
"version": "4.2.0",
"resolved": "https://registry.npmjs.org/pkg-dir/-/pkg-dir-4.2.0.tgz",
"integrity": "sha512-HRDzbaKjC+AOWVXxAU/x54COGeIv9eb+6CkDSQoNTt4XyWoIJvuPsXizxu/Fr23EiekbtZwmh1IcIG/l/a10GQ==",
"dev": true,
"dependencies": {
"find-up": "^4.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/postcss": {
npm update
2024-02-12 02:04:48 +00:00
"version": "8.4.35",
"resolved": "https://registry.npmjs.org/postcss/-/postcss-8.4.35.tgz",
"integrity": "sha512-u5U8qYpBCpN13BsiEB0CbR1Hhh4Gc0zLFuedrHJKMctHCHAGrMdG0PRM/KErzAL3CU6/eckEtmHNB3x6e3c0vA==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"funding": [
{
"type": "opencollective",
"url": "https://opencollective.com/postcss/"
},
{
"type": "tidelift",
"url": "https://tidelift.com/funding/github/npm/postcss"
Bump postcss from 8.4.16 to 8.4.31 in /js Bumps [postcss](https://github.com/postcss/postcss) from 8.4.16 to 8.4.31. - [Release notes](https://github.com/postcss/postcss/releases) - [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md) - [Commits](https://github.com/postcss/postcss/compare/8.4.16...8.4.31) --- updated-dependencies: - dependency-name: postcss dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2023-10-07 03:47:51 +00:00
},
{
"type": "github",
"url": "https://github.com/sponsors/ai"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
],
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"nanoid": "^3.3.7",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"picocolors": "^1.0.0",
"source-map-js": "^1.0.2"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"engines": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node": "^10 || ^12 || >=14"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
"node_modules/postcss-modules-extract-imports": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/postcss-modules-extract-imports/-/postcss-modules-extract-imports-3.0.0.tgz",
"integrity": "sha512-bdHleFnP3kZ4NYDhuGlVK+CMrQ/pqUm8bx/oGL93K6gVwiclvX5x0n76fYMKuIGKzlABOy13zsvqjb0f92TEXw==",
"engines": {
"node": "^10 || ^12 || >= 14"
},
"peerDependencies": {
"postcss": "^8.1.0"
}
},
"node_modules/postcss-modules-local-by-default": {
npm update
2024-02-12 02:04:48 +00:00
"version": "4.0.4",
"resolved": "https://registry.npmjs.org/postcss-modules-local-by-default/-/postcss-modules-local-by-default-4.0.4.tgz",
"integrity": "sha512-L4QzMnOdVwRm1Qb8m4x8jsZzKAaPAgrUF1r/hjDR2Xj7R+8Zsf97jAlSQzWtKx5YNiNGN8QxmPFIc/sh+RQl+Q==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"icss-utils": "^5.0.0",
"postcss-selector-parser": "^6.0.2",
"postcss-value-parser": "^4.1.0"
},
"engines": {
"node": "^10 || ^12 || >= 14"
},
"peerDependencies": {
"postcss": "^8.1.0"
}
},
"node_modules/postcss-modules-scope": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/postcss-modules-scope/-/postcss-modules-scope-3.1.1.tgz",
"integrity": "sha512-uZgqzdTleelWjzJY+Fhti6F3C9iF1JR/dODLs/JDefozYcKTBCdD8BIl6nNPbTbcLnGrk56hzwZC2DaGNvYjzA==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"postcss-selector-parser": "^6.0.4"
},
"engines": {
"node": "^10 || ^12 || >= 14"
},
"peerDependencies": {
"postcss": "^8.1.0"
}
},
"node_modules/postcss-modules-values": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/postcss-modules-values/-/postcss-modules-values-4.0.0.tgz",
"integrity": "sha512-RDxHkAiEGI78gS2ofyvCsu7iycRv7oqw5xMWn9iMoR0N/7mf9D50ecQqUo5BZ9Zh2vH4bCUR/ktCqbB9m8vJjQ==",
"dependencies": {
"icss-utils": "^5.0.0"
},
"engines": {
"node": "^10 || ^12 || >= 14"
},
"peerDependencies": {
"postcss": "^8.1.0"
}
},
"node_modules/postcss-selector-parser": {
npm update
2024-02-12 02:04:48 +00:00
"version": "6.0.15",
"resolved": "https://registry.npmjs.org/postcss-selector-parser/-/postcss-selector-parser-6.0.15.tgz",
"integrity": "sha512-rEYkQOMUCEMhsKbK66tbEU9QVIxbhN18YiniAwA7XQYTVBqrBy+P2p5JcdqsHgKM2zWylp8d7J6eszocfds5Sw==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"cssesc": "^3.0.0",
"util-deprecate": "^1.0.2"
},
"engines": {
"node": ">=4"
}
},
"node_modules/postcss-value-parser": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"version": "4.2.0",
"resolved": "https://registry.npmjs.org/postcss-value-parser/-/postcss-value-parser-4.2.0.tgz",
"integrity": "sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ=="
Add generated data to git
2022-03-28 22:05:51 +00:00
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/preact": {
npm update
2024-02-12 02:04:48 +00:00
"version": "10.19.4",
"resolved": "https://registry.npmjs.org/preact/-/preact-10.19.4.tgz",
"integrity": "sha512-dwaX5jAh0Ga8uENBX1hSOujmKWgx9RtL80KaKUFLc6jb4vCEAc3EeZ0rnQO/FO4VgjfPMfoLFWnNG8bHuZ9VLw==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/preact"
feat(zmodem): Allow file uploads/downloads Using zmodem (rz and sz commands from lrzsz) you can now send and receive files.
2022-03-29 20:59:22 +00:00
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/process-nextick-args": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-2.0.1.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag==",
"dev": true
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
"node_modules/prop-types": {
"version": "15.8.1",
"resolved": "https://registry.npmjs.org/prop-types/-/prop-types-15.8.1.tgz",
"integrity": "sha512-oj87CgZICdulUohogVAR7AjlC0327U4el4L6eAvOqCeudMDVU0NThNaV+b9Df4dXgSP1gXMTnPdhfe/2qDH5cg==",
"dependencies": {
"loose-envify": "^1.4.0",
"object-assign": "^4.1.1",
"react-is": "^16.13.1"
}
},
"node_modules/prop-types-extra": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/prop-types-extra/-/prop-types-extra-1.1.1.tgz",
"integrity": "sha512-59+AHNnHYCdiC+vMwY52WmvP5dM3QLeoumYuEyceQDi9aEhtwN9zIQ2ZNo25sMyXnbh32h+P1ezDsUpUH3JAew==",
"dependencies": {
"react-is": "^16.3.2",
"warning": "^4.0.0"
},
"peerDependencies": {
"react": ">=0.14.0"
}
Add generated data to git
2022-03-28 22:05:51 +00:00
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/proxy-addr": {
"version": "2.0.7",
"resolved": "https://registry.npmjs.org/proxy-addr/-/proxy-addr-2.0.7.tgz",
"integrity": "sha512-llQsMLSUDUPT44jdrU/O37qlnifitDP+ZwrmmZcoSKyLKvtZxpyV0n2/bD/N4tBAAZ/gJEdZU7KMraoK1+XYAg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"forwarded": "0.2.0",
"ipaddr.js": "1.9.1"
},
"engines": {
"node": ">= 0.10"
}
},
"node_modules/proxy-addr/node_modules/ipaddr.js": {
"version": "1.9.1",
"resolved": "https://registry.npmjs.org/ipaddr.js/-/ipaddr.js-1.9.1.tgz",
"integrity": "sha512-0KI/607xoxSToH7GjN1FfSbLoU0+btTicjsQSWQlh/hZykN8KpmMf7uYwPW3R+akZ6R/w18ZlXSHBYXiYUPO3g==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.10"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/prr": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/prr/-/prr-1.0.1.tgz",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"integrity": "sha512-yPw4Sng1gWghHQWj0B3ZggWUm4qVbPwPFcRG8KyxiU7J2OHFSoEHKS+EZ3fv5l1t9CyCiop6l/ZYeWbrgoQejw==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dev": true
},
"node_modules/punycode": {
npm update
2024-02-12 02:04:48 +00:00
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/punycode/-/punycode-2.3.1.tgz",
"integrity": "sha512-vYt7UD1U9Wg6138shLtLOvdAu+8DsC/ilFtEVHcH+wydcSpNE20AfSOduf6MkRFahL5FY7X1oU7nKVZFtfq8Fg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
"node": ">=6"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/purgecss": {
"version": "4.1.3",
"resolved": "https://registry.npmjs.org/purgecss/-/purgecss-4.1.3.tgz",
"integrity": "sha512-99cKy4s+VZoXnPxaoM23e5ABcP851nC2y2GROkkjS8eJaJtlciGavd7iYAw2V84WeBqggZ12l8ef44G99HmTaw==",
"dev": true,
"dependencies": {
"commander": "^8.0.0",
"glob": "^7.1.7",
"postcss": "^8.3.5",
"postcss-selector-parser": "^6.0.6"
},
"bin": {
"purgecss": "bin/purgecss.js"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/qs": {
"version": "6.11.0",
"resolved": "https://registry.npmjs.org/qs/-/qs-6.11.0.tgz",
"integrity": "sha512-MvjoMCJwEarSbUYk5O+nmoSzSutSsTwF85zcHPQ9OrlFoZOYIjaqBAJIqIXjptyD5vThxGq52Xu/MaJzRkIk4Q==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"side-channel": "^1.0.4"
},
"engines": {
"node": ">=0.6"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/randombytes": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/randombytes/-/randombytes-2.1.0.tgz",
"integrity": "sha512-vYl3iOX+4CKUWuxGi9Ukhie6fsqXqS9FE2Zaic4tNFD2N2QQaXOMFbuKK4QmDHC0JO6B1Zp41J0LpT0oR68amQ==",
"dependencies": {
"safe-buffer": "^5.1.0"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/range-parser": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/range-parser/-/range-parser-1.2.1.tgz",
"integrity": "sha512-Hrgsx+orqoygnmhFbKaHE6c296J+HTAQXoxEF6gNupROmmGJRoyzfG3ccAveqCBrwr/2yxQ5BVd/GTl5agOwSg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.6"
}
},
"node_modules/raw-body": {
"version": "2.5.1",
"resolved": "https://registry.npmjs.org/raw-body/-/raw-body-2.5.1.tgz",
"integrity": "sha512-qqJBtEyVgS0ZmPGdCFPWJ3FreoqvG4MVQln/kCgF7Olq95IbOp0/BWyMwbdtn4VTvkM8Y7khCQ2Xgk/tcrCXig==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"bytes": "3.1.2",
"http-errors": "2.0.0",
"iconv-lite": "0.4.24",
"unpipe": "1.0.0"
},
"engines": {
"node": ">= 0.8"
}
},
"node_modules/raw-body/node_modules/bytes": {
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/bytes/-/bytes-3.1.2.tgz",
"integrity": "sha512-/Nf7TyzTx6S3yRJObOAV7956r8cr2+Oj8AC5dt8wSP3BQAoeX58NoHyCU8P8zGkNXStjTSi6fzO6F0pBdcYbEg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.8"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/react": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"version": "18.2.0",
"resolved": "https://registry.npmjs.org/react/-/react-18.2.0.tgz",
"integrity": "sha512-/3IjMdb2L9QbBdWiW5e3P2/npwMBaU9mHCSCUzNln0ZCYbcfTsGbTJrU/kGemdH2IWmB2ioZ+zkxtmq6g09fGQ==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"peer": true,
"dependencies": {
"loose-envify": "^1.1.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/react-bootstrap": {
npm update
2024-02-12 02:04:48 +00:00
"version": "2.10.1",
"resolved": "https://registry.npmjs.org/react-bootstrap/-/react-bootstrap-2.10.1.tgz",
"integrity": "sha512-J3OpRZIvCTQK+Tg/jOkRUvpYLHMdGeU9KqFUBQrV0d/Qr/3nsINpiOJyZMWnM5SJ3ctZdhPA6eCIKpEJR3Ellg==",
"dependencies": {
"@babel/runtime": "^7.22.5",
"@restart/hooks": "^0.4.9",
"@restart/ui": "^1.6.6",
"@types/react-transition-group": "^4.4.6",
"classnames": "^2.3.2",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dom-helpers": "^5.2.1",
"invariant": "^2.2.4",
"prop-types": "^15.8.1",
"prop-types-extra": "^1.1.0",
npm update
2024-02-12 02:04:48 +00:00
"react-transition-group": "^4.4.5",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"uncontrollable": "^7.2.1",
"warning": "^4.0.3"
},
"peerDependencies": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"@types/react": ">=16.14.8",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"react": ">=16.14.0",
"react-dom": ">=16.14.0"
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
},
"peerDependenciesMeta": {
"@types/react": {
"optional": true
}
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
},
"node_modules/react-dom": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"version": "18.2.0",
"resolved": "https://registry.npmjs.org/react-dom/-/react-dom-18.2.0.tgz",
"integrity": "sha512-6IMTriUmvsjHUjNtEDudZfuDQUoWXVxKHhlEGSk81n4YFS+r/Kl99wXiwlVXtPBtJenozv2P+hxDsw9eA7Xo6g==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"peer": true,
"dependencies": {
"loose-envify": "^1.1.0",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"scheduler": "^0.23.0"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
"peerDependencies": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"react": "^18.2.0"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
},
"node_modules/react-is": {
"version": "16.13.1",
"resolved": "https://registry.npmjs.org/react-is/-/react-is-16.13.1.tgz",
"integrity": "sha512-24e6ynE2H+OKt4kqsOvNd8kBpV65zoxbA4BVsEOB3ARVWQki/DHzaUoC5KuON/BiccDaCCTZBuOcfZs70kR8bQ=="
},
"node_modules/react-lifecycles-compat": {
"version": "3.0.4",
"resolved": "https://registry.npmjs.org/react-lifecycles-compat/-/react-lifecycles-compat-3.0.4.tgz",
"integrity": "sha512-fBASbA6LnOU9dOU2eW7aQ8xmYBSXUIWr+UmF9b1efZBazGNO+rcXT/icdKnYm2pTwcRylVUYwW7H1PHfLekVzA=="
},
"node_modules/react-transition-group": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"version": "4.4.5",
"resolved": "https://registry.npmjs.org/react-transition-group/-/react-transition-group-4.4.5.tgz",
"integrity": "sha512-pZcd1MCJoiKiBR2NRxeCRg13uCXbydPnmB4EOeRrY7480qNWO8IIgQG6zlDkm6uRMsURXPuKq0GWtiM59a5Q6g==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
"@babel/runtime": "^7.5.5",
"dom-helpers": "^5.0.1",
"loose-envify": "^1.4.0",
"prop-types": "^15.6.2"
},
"peerDependencies": {
"react": ">=16.6.0",
"react-dom": ">=16.6.0"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/readable-stream": {
npm update
2024-02-12 02:04:48 +00:00
"version": "2.3.8",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.8.tgz",
"integrity": "sha512-8p0AUk4XODgIewSi0l8Epjs+EVnWiK7NoDIEGU0HhE7+ZyY8D1IMY7odu5lRrFXGg71L15KG8QrPmum45RTtdA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"node_modules/readable-stream/node_modules/safe-buffer": {
"version": "5.1.2",
"resolved": "https://registry.npmjs.org/safe-buffer/-/safe-buffer-5.1.2.tgz",
"integrity": "sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==",
"dev": true
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/readdirp": {
"version": "3.6.0",
"resolved": "https://registry.npmjs.org/readdirp/-/readdirp-3.6.0.tgz",
"integrity": "sha512-hOS089on8RduqdbhvQ5Z37A0ESjsqz6qnRcffsMU3495FuTdqSm+7bhJ29JvIOsBDEEnan5DPu9t3To9VRlMzA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"picomatch": "^2.2.1"
},
"engines": {
"node": ">=8.10.0"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
"node_modules/rechoir": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"version": "0.7.1",
"resolved": "https://registry.npmjs.org/rechoir/-/rechoir-0.7.1.tgz",
"integrity": "sha512-/njmZ8s1wVeR6pjTZ+0nCnv8SpZNRMT2D1RLOJQESlYFDBvwpTA4KWJpZ+sBJ4+vhjILRcK7JIFdGCdxEAAitg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dev": true,
"dependencies": {
"resolve": "^1.9.0"
},
"engines": {
"node": ">= 0.10"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/regenerator-runtime": {
npm update
2024-02-12 02:04:48 +00:00
"version": "0.14.1",
"resolved": "https://registry.npmjs.org/regenerator-runtime/-/regenerator-runtime-0.14.1.tgz",
"integrity": "sha512-dYnhHh0nJoMfnkZs6GmmhFknAGRrLznOu5nc9ML+EJxGvrx6H7teuevqVqCuPcPK//3eDrrjQhehXVx9cnkGdw=="
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
"node_modules/require-from-string": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/require-from-string/-/require-from-string-2.0.2.tgz",
"integrity": "sha512-Xf0nWe6RseziFMu+Ap9biiUbmplq6S9/p+7w7YXP/JBHhrUDDUhwa+vANyubuqfZWTveU//DYVGsDG7RKL/vEw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"engines": {
"node": ">=0.10.0"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/requires-port": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/requires-port/-/requires-port-1.0.0.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-KigOCHcocU3XODJxsu8i/j8T9tzT4adHiecwORRQ0ZZFcp7ahwXuRU1m+yuO90C5ZUyGeGfocHDI14M3L3yDAQ==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/resolve": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.22.8",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.22.8.tgz",
"integrity": "sha512-oKWePCxqpd6FlLvGV1VU0x7bkPmmCNolxzjMf4NczoDnQcIWrAF+cPtZn5i6n+RfD2d9i0tzpKnG6Yk168yIyw==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"is-core-module": "^2.13.0",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"path-parse": "^1.0.7",
"supports-preserve-symlinks-flag": "^1.0.0"
},
"bin": {
"resolve": "bin/resolve"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/resolve-cwd": {
"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,
"dependencies": {
"resolve-from": "^5.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/resolve-from": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-5.0.0.tgz",
"integrity": "sha512-qYg9KP24dD5qka9J47d0aVky0N+b4fTU89LN9iDnjB5waksiC49rvMB0PrUJQGoTmH50XPiqOvAjDfaijGxYZw==",
"dev": true,
"engines": {
"node": ">=8"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/retry": {
"version": "0.13.1",
"resolved": "https://registry.npmjs.org/retry/-/retry-0.13.1.tgz",
"integrity": "sha512-XQBQ3I8W1Cge0Seh+6gjj03LbmRFWuoszgK9ooCpwYIrhhoO80pfq4cUkU5DkknwfOfFteRwlZ56PYOGYyFWdg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 4"
}
},
"node_modules/rimraf": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-3.0.2.tgz",
"integrity": "sha512-JZkJMZkAGFFPP2YqXZXPbMlMBgsxzE8ILs4lMIX/2o0L9UBw9O/Y3o6wFw/i9YLapcUJWwqbi3kdxIPdC62TIA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"glob": "^7.1.3"
},
"bin": {
"rimraf": "bin.js"
},
"funding": {
"url": "https://github.com/sponsors/isaacs"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/safe-buffer": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"version": "5.2.1",
"resolved": "https://registry.npmjs.org/safe-buffer/-/safe-buffer-5.2.1.tgz",
"integrity": "sha512-rp3So07KcdmmKbGvgaNxQSJr7bGVSVk5S9Eq1F+ppbRo70+YeaDxkw5Dd8NPN+GD6bjnYm2VuPuCXmpuYvmCXQ==",
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
]
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/safer-buffer": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/safer-buffer/-/safer-buffer-2.1.2.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/sass": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.70.0",
"resolved": "https://registry.npmjs.org/sass/-/sass-1.70.0.tgz",
"integrity": "sha512-uUxNQ3zAHeAx5nRFskBnrWzDUJrrvpCPD5FNAoRvTi0WwremlheES3tg+56PaVtCs5QDRX5CBLxxKMDJMEa1WQ==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dev": true,
"dependencies": {
"chokidar": ">=3.0.0 <4.0.0",
"immutable": "^4.0.0",
"source-map-js": ">=0.6.2 <2.0.0"
},
"bin": {
"sass": "sass.js"
},
"engines": {
npm update
2024-02-12 02:04:48 +00:00
"node": ">=14.0.0"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
},
"node_modules/sass-loader": {
"version": "12.6.0",
"resolved": "https://registry.npmjs.org/sass-loader/-/sass-loader-12.6.0.tgz",
"integrity": "sha512-oLTaH0YCtX4cfnJZxKSLAyglED0naiYfNG1iXfU5w1LNZ+ukoA5DtyDIN5zmKVZwYNJP4KRc5Y3hkWga+7tYfA==",
"dev": true,
"dependencies": {
"klona": "^2.0.4",
"neo-async": "^2.6.2"
},
"engines": {
"node": ">= 12.13.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
},
"peerDependencies": {
"fibers": ">= 3.1.0",
"node-sass": "^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0",
"sass": "^1.3.0",
"sass-embedded": "*",
"webpack": "^5.0.0"
},
"peerDependenciesMeta": {
"fibers": {
"optional": true
},
"node-sass": {
"optional": true
},
"sass": {
"optional": true
},
"sass-embedded": {
"optional": true
}
}
},
"node_modules/scheduler": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"version": "0.23.0",
"resolved": "https://registry.npmjs.org/scheduler/-/scheduler-0.23.0.tgz",
"integrity": "sha512-CtuThmgHNg7zIZWAXi3AsyIzA3n4xx7aNyjwC2VJldO2LMVDhFK+63xGqq6CsJH4rTAt6/M+N4GhZiDYPx9eUw==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"peer": true,
"dependencies": {
"loose-envify": "^1.1.0"
}
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"node_modules/schema-utils": {
npm update
2024-02-12 02:04:48 +00:00
"version": "4.2.0",
"resolved": "https://registry.npmjs.org/schema-utils/-/schema-utils-4.2.0.tgz",
"integrity": "sha512-L0jRsrPpjdckP3oPug3/VxNKt2trR8TcabrM6FOAAlvC/9Phcmm+cuAgTlxBqdBR1WJx7Naj9WHw+aOmheSVbw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"@types/json-schema": "^7.0.9",
npm update
2024-02-12 02:04:48 +00:00
"ajv": "^8.9.0",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"ajv-formats": "^2.1.1",
npm update
2024-02-12 02:04:48 +00:00
"ajv-keywords": "^5.1.0"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"engines": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node": ">= 12.13.0"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/select-hose": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/select-hose/-/select-hose-2.0.0.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-mEugaLK+YfkijB4fx0e6kImuJdCIt2LxCRcbEYPqRGCs4F2ogyfZU5IAZRdjCP8JPq2AtdNoC/Dux63d9Kiryg==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"node_modules/selfsigned": {
npm update
2024-02-12 02:04:48 +00:00
"version": "2.4.1",
"resolved": "https://registry.npmjs.org/selfsigned/-/selfsigned-2.4.1.tgz",
"integrity": "sha512-th5B4L2U+eGLq1TVh7zNRGBapioSORUeymIydxgFpwww9d2qyKvtuPU2jJuHvYAwwqi2Y596QBL3eEqcPEYL8Q==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@types/node-forge": "^1.3.0",
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node-forge": "^1"
},
"engines": {
"node": ">=10"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/semver": {
npm update
2024-02-12 02:04:48 +00:00
"version": "7.6.0",
"resolved": "https://registry.npmjs.org/semver/-/semver-7.6.0.tgz",
"integrity": "sha512-EnwXhrlwXMk9gKu5/flx5sv/an57AkRplG3hTK68W7FRDN+k+OWBj65M7719OkA82XLBxrcX0KSHj+X5COhOVg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"lru-cache": "^6.0.0"
},
"bin": {
"semver": "bin/semver.js"
},
"engines": {
"node": ">=10"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/send": {
"version": "0.18.0",
"resolved": "https://registry.npmjs.org/send/-/send-0.18.0.tgz",
"integrity": "sha512-qqWzuOjSFOuqPjFe4NOsMLafToQQwBSOEpS+FwEt3A2V3vKubTquT3vmLTQpFgMXp8AlFWFuP1qKaJZOtPpVXg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"debug": "2.6.9",
"depd": "2.0.0",
"destroy": "1.2.0",
"encodeurl": "~1.0.2",
"escape-html": "~1.0.3",
"etag": "~1.8.1",
"fresh": "0.5.2",
"http-errors": "2.0.0",
"mime": "1.6.0",
"ms": "2.1.3",
"on-finished": "2.4.1",
"range-parser": "~1.2.1",
"statuses": "2.0.1"
},
"engines": {
"node": ">= 0.8.0"
}
},
"node_modules/send/node_modules/ms": {
"version": "2.1.3",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.3.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/serialize-javascript": {
npm update
2024-02-12 02:04:48 +00:00
"version": "6.0.2",
"resolved": "https://registry.npmjs.org/serialize-javascript/-/serialize-javascript-6.0.2.tgz",
"integrity": "sha512-Saa1xPByTTq2gdeFZYLLo+RFE35NHZkAbqZeWNd3BpzppeVisAqpDjcp8dyf6uIvEqJRd46jemmyA4iFIeVk8g==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"randombytes": "^2.1.0"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/serve-index": {
"version": "1.9.1",
"resolved": "https://registry.npmjs.org/serve-index/-/serve-index-1.9.1.tgz",
"integrity": "sha512-pXHfKNP4qujrtteMrSBb0rc8HJ9Ms/GrXwcUtUtD5s4ewDJI8bT3Cz2zTVRMKtri49pLx2e0Ya8ziP5Ya2pZZw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"accepts": "~1.3.4",
"batch": "0.6.1",
"debug": "2.6.9",
"escape-html": "~1.0.3",
"http-errors": "~1.6.2",
"mime-types": "~2.1.17",
"parseurl": "~1.3.2"
},
"engines": {
"node": ">= 0.8.0"
}
},
"node_modules/serve-index/node_modules/depd": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/depd/-/depd-1.1.2.tgz",
"integrity": "sha512-7emPTl6Dpo6JRXOXjLRxck+FlLRX5847cLKEn00PLAgc3g2hTZZgr+e4c2v6QpSmLeFP3n5yUo7ft6avBK/5jQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.6"
}
},
"node_modules/serve-index/node_modules/http-errors": {
"version": "1.6.3",
"resolved": "https://registry.npmjs.org/http-errors/-/http-errors-1.6.3.tgz",
"integrity": "sha512-lks+lVC8dgGyh97jxvxeYTWQFvh4uw4yC12gVl63Cg30sjPX4wuGcdkICVXDAESr6OJGjqGA8Iz5mkeN6zlD7A==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"depd": "~1.1.2",
"inherits": "2.0.3",
"setprototypeof": "1.1.0",
"statuses": ">= 1.4.0 < 2"
},
"engines": {
"node": ">= 0.6"
}
},
"node_modules/serve-index/node_modules/inherits": {
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.3.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-x00IRNXNy63jwGkJmzPigoySHbaqpNuzKbBOmzK+g2OdZpQ9w+sxCN+VSB3ja7IAge2OP2qpfxTjeNcyjmW1uw==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"node_modules/serve-index/node_modules/setprototypeof": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/setprototypeof/-/setprototypeof-1.1.0.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-BvE/TwpZX4FXExxOxZyRGQQv651MSwmWKZGqvmPcRIjDqWub67kTKuIMx43cZZrS/cBBzwBcNDWoFxt2XEFIpQ==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"node_modules/serve-index/node_modules/statuses": {
"version": "1.5.0",
"resolved": "https://registry.npmjs.org/statuses/-/statuses-1.5.0.tgz",
"integrity": "sha512-OpZ3zP+jT1PI7I8nemJX4AKmAX070ZkYPVWV/AaKTJl+tXCTGyVdC1a4SL8RUQYEwk/f34ZX8UTykN68FwrqAA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.6"
}
},
"node_modules/serve-static": {
"version": "1.15.0",
"resolved": "https://registry.npmjs.org/serve-static/-/serve-static-1.15.0.tgz",
"integrity": "sha512-XGuRDNjXUijsUL0vl6nSD7cwURuzEgglbOaFuZM9g3kwDXOWVTck0jLzjPzGD+TazWbboZYu52/9/XPdUgne9g==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"encodeurl": "~1.0.2",
"escape-html": "~1.0.3",
"parseurl": "~1.3.3",
"send": "0.18.0"
},
"engines": {
"node": ">= 0.8.0"
}
},
npm update
2024-02-12 02:04:48 +00:00
"node_modules/set-function-length": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/set-function-length/-/set-function-length-1.2.1.tgz",
"integrity": "sha512-j4t6ccc+VsKwYHso+kElc5neZpjtq9EnRICFZtWyBsLojhmeF/ZBd/elqm22WJh/BziDe/SBiOeAt0m2mfLD0g==",
"dev": true,
"dependencies": {
"define-data-property": "^1.1.2",
"es-errors": "^1.3.0",
"function-bind": "^1.1.2",
"get-intrinsic": "^1.2.3",
"gopd": "^1.0.1",
"has-property-descriptors": "^1.0.1"
},
"engines": {
"node": ">= 0.4"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/setprototypeof": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/setprototypeof/-/setprototypeof-1.2.0.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-E5LDX7Wrp85Kil5bhZv46j8jOeboKq5JMmYM3gVGdGH8xFpPWXUMsNrlODCrkoxMEeNi/XZIwuRvY4XNwYMJpw==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/shallow-clone": {
"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,
"dependencies": {
"kind-of": "^6.0.2"
},
"engines": {
"node": ">=8"
}
},
"node_modules/shebang-command": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/shebang-command/-/shebang-command-2.0.0.tgz",
"integrity": "sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"shebang-regex": "^3.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/shebang-regex": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/shebang-regex/-/shebang-regex-3.0.0.tgz",
"integrity": "sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
"node": ">=8"
}
},
npm update
2024-02-12 02:04:48 +00:00
"node_modules/shell-quote": {
"version": "1.8.1",
"resolved": "https://registry.npmjs.org/shell-quote/-/shell-quote-1.8.1.tgz",
"integrity": "sha512-6j1W9l1iAs/4xYBI1SYOVZyFcCis9b4KCLQ8fgAGG07QvzaRLVVRQvAy85yNmmZSjYjg4MWh4gNvlPujU/5LpA==",
"dev": true,
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/side-channel": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/side-channel/-/side-channel-1.0.5.tgz",
"integrity": "sha512-QcgiIWV4WV7qWExbN5llt6frQB/lBven9pqliLXfGPB+K9ZYXxDozp0wLkHS24kWCm+6YXH/f0HhnObZnZOBnQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"call-bind": "^1.0.6",
"es-errors": "^1.3.0",
"get-intrinsic": "^1.2.4",
"object-inspect": "^1.13.1"
},
"engines": {
"node": ">= 0.4"
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/signal-exit": {
"version": "3.0.7",
"resolved": "https://registry.npmjs.org/signal-exit/-/signal-exit-3.0.7.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-wnD2ZE+l+SPC/uoS0vXeE9L1+0wuaMqKlfz9AMUo38JsyLSBWSFcHR1Rri62LZc12vLr1gb3jl7iwQhgwpAbGQ==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"node_modules/sockjs": {
"version": "0.3.24",
"resolved": "https://registry.npmjs.org/sockjs/-/sockjs-0.3.24.tgz",
"integrity": "sha512-GJgLTZ7vYb/JtPSSZ10hsOYIvEYsjbNU+zPdIHcUaWVNUEPivzxku31865sSSud0Da0W4lEeOPlmw93zLQchuQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"faye-websocket": "^0.11.3",
"uuid": "^8.3.2",
"websocket-driver": "^0.7.4"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/source-map": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"version": "0.6.1",
"resolved": "https://registry.npmjs.org/source-map/-/source-map-0.6.1.tgz",
"integrity": "sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"engines": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node": ">=0.10.0"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
},
"node_modules/source-map-js": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/source-map-js/-/source-map-js-1.0.2.tgz",
"integrity": "sha512-R0XvVJ9WusLiqTCEiGCmICCMplcCkIwwR11mOSD9CR5u+IXYdiseeEuXCVAjS54zqwkLcPNnmU4OeJ6tUrWhDw==",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/source-map-support": {
"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==",
"dependencies": {
"buffer-from": "^1.0.0",
"source-map": "^0.6.0"
}
Add generated data to git
2022-03-28 22:05:51 +00:00
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/spdy": {
"version": "4.0.2",
"resolved": "https://registry.npmjs.org/spdy/-/spdy-4.0.2.tgz",
"integrity": "sha512-r46gZQZQV+Kl9oItvl1JZZqJKGr+oEkB08A6BzkiR7593/7IbtuncXHd2YoYeTsG4157ZssMu9KYvUHLcjcDoA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"debug": "^4.1.0",
"handle-thing": "^2.0.0",
"http-deceiver": "^1.2.7",
"select-hose": "^2.0.0",
"spdy-transport": "^3.0.0"
},
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/spdy-transport": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/spdy-transport/-/spdy-transport-3.0.0.tgz",
"integrity": "sha512-hsLVFE5SjA6TCisWeJXFKniGGOpBgMLmerfO2aCyCU5s7nJ/rpAepqmFifv/GCbSbueEeAJJnmSQ2rKC/g8Fcw==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"debug": "^4.1.0",
"detect-node": "^2.0.4",
"hpack.js": "^2.1.6",
"obuf": "^1.1.2",
"readable-stream": "^3.0.6",
"wbuf": "^1.7.3"
}
},
"node_modules/spdy-transport/node_modules/debug": {
"version": "4.3.4",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.4.tgz",
"integrity": "sha512-PRWFHuSU3eDtQJPvnNY7Jcket1j0t5OuOsFzPPzsekD52Zl8qUfFIPEiswXqIvHWGVHOgX+7G/vCNNhehwxfkQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/spdy-transport/node_modules/ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
npm update
2024-02-12 02:04:48 +00:00
"node_modules/spdy-transport/node_modules/readable-stream": {
"version": "3.6.2",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-3.6.2.tgz",
"integrity": "sha512-9u/sniCrY3D5WdsERHzHE4G2YCXqoG5FTHUiCC4SIbr6XcLZBY05ya9EKjYek9O5xOAwjGq+1JdGBAS7Q9ScoA==",
"dev": true,
"dependencies": {
"inherits": "^2.0.3",
"string_decoder": "^1.1.1",
"util-deprecate": "^1.0.1"
},
"engines": {
"node": ">= 6"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/spdy/node_modules/debug": {
"version": "4.3.4",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.4.tgz",
"integrity": "sha512-PRWFHuSU3eDtQJPvnNY7Jcket1j0t5OuOsFzPPzsekD52Zl8qUfFIPEiswXqIvHWGVHOgX+7G/vCNNhehwxfkQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"ms": "2.1.2"
},
"engines": {
"node": ">=6.0"
},
"peerDependenciesMeta": {
"supports-color": {
"optional": true
}
}
},
"node_modules/spdy/node_modules/ms": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"node_modules/statuses": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/statuses/-/statuses-2.0.1.tgz",
"integrity": "sha512-RwNA9Z/7PrK06rYLIzFMlaF+l73iwpzsqRIFgbMLbTcLD6cOao82TaWefPXQvB2fOC4AjuYSEndS7N/mTCbkdQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.8"
}
},
"node_modules/string_decoder": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-1.1.1.tgz",
"integrity": "sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"safe-buffer": "~5.1.0"
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
}
},
npm update
2024-02-12 02:04:48 +00:00
"node_modules/string_decoder/node_modules/safe-buffer": {
"version": "5.1.2",
"resolved": "https://registry.npmjs.org/safe-buffer/-/safe-buffer-5.1.2.tgz",
"integrity": "sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==",
"dev": true
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/strip-final-newline": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/strip-final-newline/-/strip-final-newline-2.0.0.tgz",
"integrity": "sha512-BrpvfNAE3dcvq7ll3xVumzjKjZQ5tI1sEUIKr3Uoks0XUl45St3FlatVqef9prk4jRDzhW6WZg+3bk93y6pLjA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">=6"
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/style-loader": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/style-loader/-/style-loader-2.0.0.tgz",
"integrity": "sha512-Z0gYUJmzZ6ZdRUqpg1r8GsaFKypE+3xAzuFeMuoHgjc9KZv3wMyCRjQIWEbhoFSq7+7yoHXySDJyyWQaPajeiQ==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"loader-utils": "^2.0.0",
"schema-utils": "^3.0.0"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node": ">= 10.13.0"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"peerDependencies": {
"webpack": "^4.0.0 || ^5.0.0"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/style-loader/node_modules/ajv": {
"version": "6.12.6",
"resolved": "https://registry.npmjs.org/ajv/-/ajv-6.12.6.tgz",
"integrity": "sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +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"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"funding": {
"type": "github",
"url": "https://github.com/sponsors/epoberezkin"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/style-loader/node_modules/ajv-keywords": {
"version": "3.5.2",
"resolved": "https://registry.npmjs.org/ajv-keywords/-/ajv-keywords-3.5.2.tgz",
"integrity": "sha512-5p6WTN0DdTGVQk6VjcEju19IgaHudalcfabD7yhDGeA6bcQnmL+CpveLJq/3hvfwd1aof6L386Ougkx6RfyMIQ==",
"peerDependencies": {
"ajv": "^6.9.1"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/style-loader/node_modules/json-schema-traverse": {
"version": "0.4.1",
"resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz",
"integrity": "sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg=="
},
"node_modules/style-loader/node_modules/schema-utils": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/schema-utils/-/schema-utils-3.3.0.tgz",
"integrity": "sha512-pN/yOAvcC+5rQ5nERGuwrjLlYvLTbCibnZ1I7B1LaiAz9BRBlE9GMgE/eqV30P7aJQUf7Ddimy/RsbYO/GrVGg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"@types/json-schema": "^7.0.8",
"ajv": "^6.12.5",
"ajv-keywords": "^3.5.2"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"engines": {
"node": ">= 10.13.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
}
},
"node_modules/supports-color": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"version": "8.1.1",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-8.1.1.tgz",
"integrity": "sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"has-flag": "^4.0.0"
},
"engines": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node": ">=10"
},
"funding": {
"url": "https://github.com/chalk/supports-color?sponsor=1"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/supports-preserve-symlinks-flag": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/supports-preserve-symlinks-flag/-/supports-preserve-symlinks-flag-1.0.0.tgz",
"integrity": "sha512-ot0WnXS9fgdkgIcePe6RHNk1WA8+muPa6cSjeR3V8K27q9BB1rTE3R1p7Hv0z1ZyAc8s6Vvv8DIyWf681MAt0w==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"dev": true,
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/tapable": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/tapable/-/tapable-1.1.3.tgz",
"integrity": "sha512-4WK/bYZmj8xLr+HUCODHGF1ZFzsYffasLUgEiMBY4fgtltdO6B4WJtlSbPaDTLpYTcGVwM2qLnFTICEcNxs3kA==",
"dev": true,
"engines": {
"node": ">=6"
}
},
"node_modules/terser": {
npm update
2024-02-12 02:04:48 +00:00
"version": "5.27.0",
"resolved": "https://registry.npmjs.org/terser/-/terser-5.27.0.tgz",
"integrity": "sha512-bi1HRwVRskAjheeYl291n3JC4GgO/Ty4z1nVs5AAsmonJulGxpSektecnNedrwK9C7vpvVtcX3cw00VSLt7U2A==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@jridgewell/source-map": "^0.3.3",
"acorn": "^8.8.2",
Add generated data to git
2022-03-28 22:05:51 +00:00
"commander": "^2.20.0",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"source-map-support": "~0.5.20"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"bin": {
"terser": "bin/terser"
},
"engines": {
"node": ">=10"
}
},
"node_modules/terser-webpack-plugin": {
npm update
2024-02-12 02:04:48 +00:00
"version": "5.3.10",
"resolved": "https://registry.npmjs.org/terser-webpack-plugin/-/terser-webpack-plugin-5.3.10.tgz",
"integrity": "sha512-BKFPWlPDndPs+NGGCr1U59t0XScL5317Y0UReNrHaw9/FwhPENlq6bfgs+4yPfyP51vqC1bQ4rp1EfXW5ZSH9w==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
npm update
2024-02-12 02:04:48 +00:00
"@jridgewell/trace-mapping": "^0.3.20",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"jest-worker": "^27.4.5",
"schema-utils": "^3.1.1",
npm update
2024-02-12 02:04:48 +00:00
"serialize-javascript": "^6.0.1",
"terser": "^5.26.0"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"engines": {
"node": ">= 10.13.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
},
"peerDependencies": {
"webpack": "^5.1.0"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
"peerDependenciesMeta": {
"@swc/core": {
"optional": true
},
"esbuild": {
"optional": true
},
"uglify-js": {
"optional": true
}
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/terser-webpack-plugin/node_modules/ajv": {
"version": "6.12.6",
"resolved": "https://registry.npmjs.org/ajv/-/ajv-6.12.6.tgz",
"integrity": "sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==",
"dependencies": {
"fast-deep-equal": "^3.1.1",
"fast-json-stable-stringify": "^2.0.0",
"json-schema-traverse": "^0.4.1",
"uri-js": "^4.2.2"
},
"funding": {
"type": "github",
"url": "https://github.com/sponsors/epoberezkin"
}
},
"node_modules/terser-webpack-plugin/node_modules/ajv-keywords": {
"version": "3.5.2",
"resolved": "https://registry.npmjs.org/ajv-keywords/-/ajv-keywords-3.5.2.tgz",
"integrity": "sha512-5p6WTN0DdTGVQk6VjcEju19IgaHudalcfabD7yhDGeA6bcQnmL+CpveLJq/3hvfwd1aof6L386Ougkx6RfyMIQ==",
"peerDependencies": {
"ajv": "^6.9.1"
}
},
"node_modules/terser-webpack-plugin/node_modules/json-schema-traverse": {
"version": "0.4.1",
"resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz",
"integrity": "sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg=="
},
"node_modules/terser-webpack-plugin/node_modules/schema-utils": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/schema-utils/-/schema-utils-3.3.0.tgz",
"integrity": "sha512-pN/yOAvcC+5rQ5nERGuwrjLlYvLTbCibnZ1I7B1LaiAz9BRBlE9GMgE/eqV30P7aJQUf7Ddimy/RsbYO/GrVGg==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"dependencies": {
"@types/json-schema": "^7.0.8",
"ajv": "^6.12.5",
"ajv-keywords": "^3.5.2"
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node": ">= 10.13.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/terser/node_modules/commander": {
"version": "2.20.3",
"resolved": "https://registry.npmjs.org/commander/-/commander-2.20.3.tgz",
"integrity": "sha512-GpVkmM8vF2vQUkj2LvZmD35JxeJOLCwJ9cUkugyk2nuhbv3+mJvpLYYt+0+USMxE+oj+ey/lJEnhZw75x/OMcQ=="
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/thunky": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/thunky/-/thunky-1.1.0.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-eHY7nBftgThBqOyHGVN+l8gF0BucP09fMo0oO/Lb0w1OF80dJv+lDVpXG60WMQvkcxAkNybKsrEIE3ZtKGmPrA==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/to-regex-range": {
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/to-regex-range/-/to-regex-range-5.0.1.tgz",
"integrity": "sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"is-number": "^7.0.0"
},
"engines": {
"node": ">=8.0"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/toidentifier": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/toidentifier/-/toidentifier-1.0.1.tgz",
"integrity": "sha512-o5sSPKEkg/DIQNmH43V0/uerLrpzVedkUh8tGNvaeXpfpuwjKenlSox/2O/BTlZUtEe+JG7s5YhEz608PlAHRA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">=0.6"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/ts-loader": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"version": "8.4.0",
"resolved": "https://registry.npmjs.org/ts-loader/-/ts-loader-8.4.0.tgz",
"integrity": "sha512-6nFY3IZ2//mrPc+ImY3hNWx1vCHyEhl6V+wLmL4CZcm6g1CqX7UKrkc6y0i4FwcfOhxyMPCfaEvh20f4r9GNpw==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dev": true,
"dependencies": {
"chalk": "^4.1.0",
"enhanced-resolve": "^4.0.0",
"loader-utils": "^2.0.0",
"micromatch": "^4.0.0",
"semver": "^7.3.4"
},
"engines": {
"node": ">=10.0.0"
},
"peerDependencies": {
"typescript": "*",
"webpack": "*"
}
},
npm update
2024-02-12 02:04:48 +00:00
"node_modules/tslib": {
"version": "2.6.2",
"resolved": "https://registry.npmjs.org/tslib/-/tslib-2.6.2.tgz",
"integrity": "sha512-AEYxH93jGFPn/a2iVAwW87VuUIkR1FVUKB77NwMF7nBTDkDrrT/Hpt/IrCJ0QXhW27jTBDcf5ZY7w6RiqTMw2Q=="
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/type-is": {
"version": "1.6.18",
"resolved": "https://registry.npmjs.org/type-is/-/type-is-1.6.18.tgz",
"integrity": "sha512-TkRKr9sUTxEH8MdfuCSP7VizJyzRNMjj2J2do2Jr3Kym598JVdEksuzPQCnlFPW4ky9Q+iA+ma9BGm06XQBy8g==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"media-typer": "0.3.0",
"mime-types": "~2.1.24"
},
"engines": {
"node": ">= 0.6"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/typescript": {
npm update
2024-02-12 02:04:48 +00:00
"version": "4.9.5",
"resolved": "https://registry.npmjs.org/typescript/-/typescript-4.9.5.tgz",
"integrity": "sha512-1FXk9E2Hm+QzZQ7z+McJiHL4NW1F2EzMu9Nq9i3zAaGqibafqYwCVU6WyWAuyQRRzOlxou8xZSyXLEN8oKj24g==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dev": true,
"bin": {
"tsc": "bin/tsc",
"tsserver": "bin/tsserver"
},
"engines": {
"node": ">=4.2.0"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/uncontrollable": {
"version": "7.2.1",
"resolved": "https://registry.npmjs.org/uncontrollable/-/uncontrollable-7.2.1.tgz",
"integrity": "sha512-svtcfoTADIB0nT9nltgjujTi7BzVmwjZClOmskKu/E8FW9BXzg9os8OLr4f8Dlnk0rYWJIWr4wv9eKUXiQvQwQ==",
"dependencies": {
"@babel/runtime": "^7.6.3",
"@types/react": ">=16.9.11",
"invariant": "^2.2.4",
"react-lifecycles-compat": "^3.0.4"
},
"peerDependencies": {
"react": ">=15.0.0"
}
},
npm update
2024-02-12 02:04:48 +00:00
"node_modules/undici-types": {
"version": "5.26.5",
"resolved": "https://registry.npmjs.org/undici-types/-/undici-types-5.26.5.tgz",
"integrity": "sha512-JlCMO+ehdEIKqlFxk6IfVoAUVmgz7cU7zD/h9XZ0qzeosSHmUJVOzSQvvYSYWXkFXC+IfLKSIffhv0sVZup6pA=="
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/unpipe": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/unpipe/-/unpipe-1.0.0.tgz",
"integrity": "sha512-pjy2bYhSsufwWlKwPc+l3cN7+wuJlK6uz0YdJEOlQDbl6jo/YlPi4mb8agUkVC8BF7V8NuzeyPNqRksA3hztKQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.8"
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/update-browserslist-db": {
npm update
2024-02-12 02:04:48 +00:00
"version": "1.0.13",
"resolved": "https://registry.npmjs.org/update-browserslist-db/-/update-browserslist-db-1.0.13.tgz",
"integrity": "sha512-xebP81SNcPuNpPP3uzeW1NYXxI3rxyJzF3pD6sH4jE7o/IX+WtSpwnVU+qIsDPyk0d3hmFQ7mjqc6AtV604hbg==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"funding": [
{
"type": "opencollective",
"url": "https://opencollective.com/browserslist"
},
{
"type": "tidelift",
"url": "https://tidelift.com/funding/github/npm/browserslist"
npm update
2024-02-12 02:04:48 +00:00
},
{
"type": "github",
"url": "https://github.com/sponsors/ai"
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
}
],
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"escalade": "^3.1.1",
"picocolors": "^1.0.0"
},
"bin": {
npm update
2024-02-12 02:04:48 +00:00
"update-browserslist-db": "cli.js"
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
},
"peerDependencies": {
"browserslist": ">= 4.21.0"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/uri-js": {
"version": "4.4.1",
"resolved": "https://registry.npmjs.org/uri-js/-/uri-js-4.4.1.tgz",
"integrity": "sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==",
"dependencies": {
"punycode": "^2.1.0"
}
},
"node_modules/util-deprecate": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"integrity": "sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw=="
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/utils-merge": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/utils-merge/-/utils-merge-1.0.1.tgz",
"integrity": "sha512-pMZTvIkT1d+TFGvDOqodOclx0QWkkgi6Tdoa8gC8ffGAAqz9pzPTZWAybbsHHoED/ztMtkv/VoYTYyShUn81hA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.4.0"
}
},
"node_modules/uuid": {
"version": "8.3.2",
"resolved": "https://registry.npmjs.org/uuid/-/uuid-8.3.2.tgz",
"integrity": "sha512-+NYs2QeMWy+GWFOEm9xnn6HCDp0l7QBD7ml8zLUmJ+93Q5NF0NocErnwkTkXVFNiX3/fpC6afS8Dhb/gz7R7eg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"bin": {
"uuid": "dist/bin/uuid"
}
},
"node_modules/vary": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/vary/-/vary-1.1.2.tgz",
"integrity": "sha512-BNGbWLfd0eUPabhkXUVm0j8uuvREyTh5ovRa/dyow/BqAbZJyC+5fU+IzQOzmAKzYqYRAISoRhdQr3eIZ/PXqg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">= 0.8"
}
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/warning": {
"version": "4.0.3",
"resolved": "https://registry.npmjs.org/warning/-/warning-4.0.3.tgz",
"integrity": "sha512-rpJyN222KWIvHJ/F53XSZv0Zl/accqHR8et1kpaMTD/fLCRxtV8iX8czMzY7sVZupTI3zcUTg8eycS2kNF9l6w==",
"dependencies": {
"loose-envify": "^1.0.0"
}
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"node_modules/watchpack": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"version": "2.4.0",
"resolved": "https://registry.npmjs.org/watchpack/-/watchpack-2.4.0.tgz",
"integrity": "sha512-Lcvm7MGST/4fup+ifyKi2hjyIAwcdI4HRgtvTpIUxBRhB+RFtUh8XtDOxUfctVCnhVi+QQj49i91OyvzkJl6cg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"glob-to-regexp": "^0.4.1",
"graceful-fs": "^4.1.2"
},
"engines": {
"node": ">=10.13.0"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/wbuf": {
"version": "1.7.3",
"resolved": "https://registry.npmjs.org/wbuf/-/wbuf-1.7.3.tgz",
"integrity": "sha512-O84QOnr0icsbFGLS0O3bI5FswxzRr8/gHwWkDlQFskhSPryQXvrTMxjxGP4+iWYoauLoBvfDpkrOauZ+0iZpDA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"minimalistic-assert": "^1.0.0"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/webpack": {
npm update
2024-02-12 02:04:48 +00:00
"version": "5.90.1",
"resolved": "https://registry.npmjs.org/webpack/-/webpack-5.90.1.tgz",
"integrity": "sha512-SstPdlAC5IvgFnhiRok8hqJo/+ArAbNv7rhU4fnWGHNVfN59HSQFaxZDSAL3IFG2YmqxuRs+IU33milSxbPlog==",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"dependencies": {
"@types/eslint-scope": "^3.7.3",
npm update
2024-02-12 02:04:48 +00:00
"@types/estree": "^1.0.5",
"@webassemblyjs/ast": "^1.11.5",
"@webassemblyjs/wasm-edit": "^1.11.5",
"@webassemblyjs/wasm-parser": "^1.11.5",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"acorn": "^8.7.1",
npm update
2024-02-12 02:04:48 +00:00
"acorn-import-assertions": "^1.9.0",
"browserslist": "^4.21.10",
Add generated data to git
2022-03-28 22:05:51 +00:00
"chrome-trace-event": "^1.0.2",
npm update
2024-02-12 02:04:48 +00:00
"enhanced-resolve": "^5.15.0",
"es-module-lexer": "^1.2.1",
Add generated data to git
2022-03-28 22:05:51 +00:00
"eslint-scope": "5.1.1",
"events": "^3.2.0",
"glob-to-regexp": "^0.4.1",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"graceful-fs": "^4.2.9",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"json-parse-even-better-errors": "^2.3.1",
Add generated data to git
2022-03-28 22:05:51 +00:00
"loader-runner": "^4.2.0",
"mime-types": "^2.1.27",
"neo-async": "^2.6.2",
npm update
2024-02-12 02:04:48 +00:00
"schema-utils": "^3.2.0",
Add generated data to git
2022-03-28 22:05:51 +00:00
"tapable": "^2.1.1",
npm update
2024-02-12 02:04:48 +00:00
"terser-webpack-plugin": "^5.3.10",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"watchpack": "^2.4.0",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"webpack-sources": "^3.2.3"
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"bin": {
"webpack": "bin/webpack.js"
},
"engines": {
"node": ">=10.13.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
},
"peerDependenciesMeta": {
"webpack-cli": {
"optional": true
}
}
},
"node_modules/webpack-cli": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +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==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dev": true,
"dependencies": {
"@discoveryjs/json-ext": "^0.5.0",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"@webpack-cli/configtest": "^1.2.0",
"@webpack-cli/info": "^1.5.0",
"@webpack-cli/serve": "^1.7.0",
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"colorette": "^2.0.14",
Add generated data to git
2022-03-28 22:05:51 +00:00
"commander": "^7.0.0",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"cross-spawn": "^7.0.3",
Add generated data to git
2022-03-28 22:05:51 +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"
},
"bin": {
"webpack-cli": "bin/cli.js"
},
"engines": {
"node": ">=10.13.0"
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"peerDependencies": {
"webpack": "4.x.x || 5.x.x"
},
"peerDependenciesMeta": {
"@webpack-cli/generators": {
"optional": true
},
"@webpack-cli/migrate": {
"optional": true
},
"webpack-bundle-analyzer": {
"optional": true
},
"webpack-dev-server": {
"optional": true
}
}
},
"node_modules/webpack-cli/node_modules/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,
"engines": {
"node": ">= 10"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/webpack-dev-middleware": {
"version": "5.3.3",
"resolved": "https://registry.npmjs.org/webpack-dev-middleware/-/webpack-dev-middleware-5.3.3.tgz",
"integrity": "sha512-hj5CYrY0bZLB+eTO+x/j67Pkrquiy7kWepMHmUMoPsmcUaeEnQJqFzHJOyxgWlq746/wUuA64p9ta34Kyb01pA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"colorette": "^2.0.10",
"memfs": "^3.4.3",
"mime-types": "^2.1.31",
"range-parser": "^1.2.1",
"schema-utils": "^4.0.0"
},
"engines": {
"node": ">= 12.13.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
},
"peerDependencies": {
"webpack": "^4.0.0 || ^5.0.0"
}
},
"node_modules/webpack-dev-server": {
npm update
2024-02-12 02:04:48 +00:00
"version": "4.15.1",
"resolved": "https://registry.npmjs.org/webpack-dev-server/-/webpack-dev-server-4.15.1.tgz",
"integrity": "sha512-5hbAst3h3C3L8w6W4P96L5vaV0PxSmJhxZvWKYIdgxOQm8pNZ5dEOmmSLBVpP85ReeyRt6AS1QJNyo/oFFPeVA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"@types/bonjour": "^3.5.9",
"@types/connect-history-api-fallback": "^1.3.5",
"@types/express": "^4.17.13",
"@types/serve-index": "^1.9.1",
"@types/serve-static": "^1.13.10",
"@types/sockjs": "^0.3.33",
npm update
2024-02-12 02:04:48 +00:00
"@types/ws": "^8.5.5",
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"ansi-html-community": "^0.0.8",
"bonjour-service": "^1.0.11",
"chokidar": "^3.5.3",
"colorette": "^2.0.10",
"compression": "^1.7.4",
"connect-history-api-fallback": "^2.0.0",
"default-gateway": "^6.0.3",
"express": "^4.17.3",
"graceful-fs": "^4.2.6",
"html-entities": "^2.3.2",
"http-proxy-middleware": "^2.0.3",
"ipaddr.js": "^2.0.1",
npm update
2024-02-12 02:04:48 +00:00
"launch-editor": "^2.6.0",
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"open": "^8.0.9",
"p-retry": "^4.5.0",
"rimraf": "^3.0.2",
"schema-utils": "^4.0.0",
"selfsigned": "^2.1.1",
"serve-index": "^1.9.1",
"sockjs": "^0.3.24",
"spdy": "^4.0.2",
"webpack-dev-middleware": "^5.3.1",
npm update
2024-02-12 02:04:48 +00:00
"ws": "^8.13.0"
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"bin": {
"webpack-dev-server": "bin/webpack-dev-server.js"
},
"engines": {
"node": ">= 12.13.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
},
"peerDependencies": {
"webpack": "^4.37.0 || ^5.0.0"
},
"peerDependenciesMeta": {
npm update
2024-02-12 02:04:48 +00:00
"webpack": {
"optional": true
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"webpack-cli": {
"optional": true
}
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/webpack-merge": {
npm update
2024-02-12 02:04:48 +00:00
"version": "5.10.0",
"resolved": "https://registry.npmjs.org/webpack-merge/-/webpack-merge-5.10.0.tgz",
"integrity": "sha512-+4zXKdx7UnO+1jaN4l2lHVD+mFvnlZQP/6ljaJVb4SZiwIKeUnrT5l0gkT8z+n4hKpC+jpOv6O9R+gLtag7pSA==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dev": true,
"dependencies": {
"clone-deep": "^4.0.1",
npm update
2024-02-12 02:04:48 +00:00
"flat": "^5.0.2",
Add generated data to git
2022-03-28 22:05:51 +00:00
"wildcard": "^2.0.0"
},
"engines": {
"node": ">=10.0.0"
}
},
"node_modules/webpack-sources": {
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +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==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
"node": ">=10.13.0"
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/webpack/node_modules/ajv": {
"version": "6.12.6",
"resolved": "https://registry.npmjs.org/ajv/-/ajv-6.12.6.tgz",
"integrity": "sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==",
"dependencies": {
"fast-deep-equal": "^3.1.1",
"fast-json-stable-stringify": "^2.0.0",
"json-schema-traverse": "^0.4.1",
"uri-js": "^4.2.2"
},
"funding": {
"type": "github",
"url": "https://github.com/sponsors/epoberezkin"
}
},
"node_modules/webpack/node_modules/ajv-keywords": {
"version": "3.5.2",
"resolved": "https://registry.npmjs.org/ajv-keywords/-/ajv-keywords-3.5.2.tgz",
"integrity": "sha512-5p6WTN0DdTGVQk6VjcEju19IgaHudalcfabD7yhDGeA6bcQnmL+CpveLJq/3hvfwd1aof6L386Ougkx6RfyMIQ==",
"peerDependencies": {
"ajv": "^6.9.1"
}
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/webpack/node_modules/enhanced-resolve": {
npm update
2024-02-12 02:04:48 +00:00
"version": "5.15.0",
"resolved": "https://registry.npmjs.org/enhanced-resolve/-/enhanced-resolve-5.15.0.tgz",
"integrity": "sha512-LXYT42KJ7lpIKECr2mAXIaMldcNCh/7E0KBKOu4KSfkHmP+mZmSs+8V5gBAqisWBy0OO4W5Oyys0GO1Y8KtdKg==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"graceful-fs": "^4.2.4",
"tapable": "^2.2.0"
},
"engines": {
"node": ">=10.13.0"
}
},
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"node_modules/webpack/node_modules/json-schema-traverse": {
"version": "0.4.1",
"resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz",
"integrity": "sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg=="
},
"node_modules/webpack/node_modules/schema-utils": {
npm update
2024-02-12 02:04:48 +00:00
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/schema-utils/-/schema-utils-3.3.0.tgz",
"integrity": "sha512-pN/yOAvcC+5rQ5nERGuwrjLlYvLTbCibnZ1I7B1LaiAz9BRBlE9GMgE/eqV30P7aJQUf7Ddimy/RsbYO/GrVGg==",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"dependencies": {
"@types/json-schema": "^7.0.8",
"ajv": "^6.12.5",
"ajv-keywords": "^3.5.2"
},
"engines": {
"node": ">= 10.13.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/webpack"
}
},
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node_modules/webpack/node_modules/tapable": {
"version": "2.2.1",
"resolved": "https://registry.npmjs.org/tapable/-/tapable-2.2.1.tgz",
"integrity": "sha512-GNzQvQTOIP6RyTfE2Qxb8ZVlNmw0n88vp1szwWRimP02mnTsx3Wtn5qRdqY9w2XduFNUgvOwhNnQsjwCp+kqaQ==",
"engines": {
"node": ">=6"
}
},
"node_modules/websocket-driver": {
"version": "0.7.4",
"resolved": "https://registry.npmjs.org/websocket-driver/-/websocket-driver-0.7.4.tgz",
"integrity": "sha512-b17KeDIQVjvb0ssuSDF2cYXSg2iztliJ4B9WdsuB6J952qCPKmnVq4DyW5motImXHDC1cBT/1UezrJVsKw5zjg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"dependencies": {
"http-parser-js": ">=0.5.1",
"safe-buffer": ">=5.1.0",
"websocket-extensions": ">=0.1.1"
},
"engines": {
"node": ">=0.8.0"
}
},
"node_modules/websocket-extensions": {
"version": "0.1.4",
"resolved": "https://registry.npmjs.org/websocket-extensions/-/websocket-extensions-0.1.4.tgz",
"integrity": "sha512-OqedPIGOfsDlo31UNwYbCFMSaO9m9G/0faIHj5/dZFDMFqPTcx6UwqyOy3COEaEOg/9VsGIpdqn62W5KhoKSpg==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"engines": {
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"node": ">=0.8.0"
Add generated data to git
2022-03-28 22:05:51 +00:00
}
},
"node_modules/which": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/which/-/which-2.0.2.tgz",
"integrity": "sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Add generated data to git
2022-03-28 22:05:51 +00:00
"dependencies": {
"isexe": "^2.0.0"
},
"bin": {
"node-which": "bin/node-which"
},
"engines": {
"node": ">= 8"
}
},
"node_modules/wildcard": {
npm update
2024-02-12 02:04:48 +00:00
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/wildcard/-/wildcard-2.0.1.tgz",
"integrity": "sha512-CC1bOL87PIWSBhDcTrdeLo6eGT7mCFtrg0uIJtqJUFyK+eJnzl8A1niH56uu7KMa5XFrtiV+AQuHO3n7DsHnLQ==",
Add generated data to git
2022-03-28 22:05:51 +00:00
"dev": true
},
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
"node_modules/wrappy": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.2.tgz",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"integrity": "sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ==",
"dev": true
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"node_modules/ws": {
npm update
2024-02-12 02:04:48 +00:00
"version": "8.16.0",
"resolved": "https://registry.npmjs.org/ws/-/ws-8.16.0.tgz",
"integrity": "sha512-HS0c//TP7Ina87TfiPUz1rQzMhHrl/SG2guqRcTOIUYD2q8uhUdNHZYJUaQ8aTGPzCh+c6oawMKW35nFl1dxyQ==",
Ensure prod builds don't use inline source maps The bundle grew by a factor of 4, so let's only do that while we're developing.
2022-11-26 23:21:59 +00:00
"dev": true,
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
"engines": {
"node": ">=10.0.0"
},
"peerDependencies": {
"bufferutil": "^4.0.1",
npm update
2024-02-12 02:04:48 +00:00
"utf-8-validate": ">=5.0.2"
Improve JS workflow Now we can launch Chrome from vscode and also set breakpoints and have them be respected. Work still to be done: The "Launch Chrome" task should compile the typescript stuff. It takes too long to rebuild the typescript stuff. It is bothersome during development. If we can work around that with webpack, that's great. If generating the gotty bundle is what makes it all time consuming, we should skip the bundle generation for development and change the index.html to point to a not-bundled version. Partially fixes #3
2022-11-26 22:51:10 +00:00
},
"peerDependenciesMeta": {
"bufferutil": {
"optional": true
},
"utf-8-validate": {
"optional": true
}
}
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
},
Add generated data to git
2022-03-28 22:05:51 +00:00
"node_modules/xterm": {
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"version": "4.19.0",
"resolved": "https://registry.npmjs.org/xterm/-/xterm-4.19.0.tgz",
"integrity": "sha512-c3Cp4eOVsYY5Q839dR5IejghRPpxciGmLWWaP9g+ppfMeBChMeLa1DCA+pmX/jyDZ+zxFOmlJL/82qVdayVoGQ=="
Add generated data to git
2022-03-28 22:05:51 +00:00
},
"node_modules/xterm-addon-fit": {
"version": "0.5.0",
"resolved": "https://registry.npmjs.org/xterm-addon-fit/-/xterm-addon-fit-0.5.0.tgz",
"integrity": "sha512-DsS9fqhXHacEmsPxBJZvfj2la30Iz9xk+UKjhQgnYNkrUIN5CYLbw7WEfz117c7+S86S/tpHPfvNxJsF5/G8wQ==",
"peerDependencies": {
"xterm": "^4.0.0"
}
},
"node_modules/xterm-addon-web-links": {
"version": "0.4.0",
"resolved": "https://registry.npmjs.org/xterm-addon-web-links/-/xterm-addon-web-links-0.4.0.tgz",
"integrity": "sha512-xv8GeiINmx0zENO9hf5k+5bnkaE8mRzF+OBAr9WeFq2eLaQSudioQSiT34M1ofKbzcdjSsKiZm19Rw3i4eXamg==",
"peerDependencies": {
"xterm": "^4.0.0"
}
},
"node_modules/xterm-addon-webgl": {
"version": "0.10.0",
"resolved": "https://registry.npmjs.org/xterm-addon-webgl/-/xterm-addon-webgl-0.10.0.tgz",
"integrity": "sha512-MJzyWie5yw+PH6p//fXlXzmsULLtpBo992EWEKl2uv5M5Zj9etTwfuutCUK7o98mr6itDl+vS/CYIMP68jCf8w==",
"peerDependencies": {
"xterm": "^4.0.0"
}
},
"node_modules/yallist": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/yallist/-/yallist-4.0.0.tgz",
"integrity": "sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A=="
},
feat(zmodem): Allow file uploads/downloads Using zmodem (rz and sz commands from lrzsz) you can now send and receive files.
2022-03-29 20:59:22 +00:00
"node_modules/zmodem.js": {
"version": "0.1.10",
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
"resolved": "https://registry.npmjs.org/zmodem.js/-/zmodem.js-0.1.10.tgz",
"integrity": "sha512-Z1DWngunZ/j3BmIzSJpFZVNV73iHkj89rxXX4IciJdU9ga3nZ7rJ5LkfjV/QDsKhc7bazDWTTJCLJ+iRXD82dw==",
"dependencies": {
"crc-32": "^1.1.1"
Use bootstrap components for up- and downloads
2022-04-09 10:10:03 +00:00
}
Refresh dependencies, drop node-sass `npm audit` revealed some vulnerabilities: ``` scss-tokenizer <=0.4.2 Severity: high Regular expression denial of service in scss-tokenizer - https://github.com/advisories/GHSA-7mwh-4pqv-wmr8 fix available via `npm audit fix --force` Will install node-sass@4.5.3, which is a breaking change node_modules/scss-tokenizer sass-graph >=2.2.0 Depends on vulnerable versions of scss-tokenizer node_modules/sass-graph node-sass >=4.6.0 Depends on vulnerable versions of sass-graph node_modules/node-sass 3 high severity vulnerabilities ``` We don't need node-sass, and sass-loader is just as happy using another sass implementation. The preferred one is dart-sass which is simply called sass in npm. In the process, I also did an `npm update` just for good measure.
2022-08-27 08:58:27 +00:00
}
Add xterm itegration * Move to TypeScript from legacy JavaScript * Add support of xterm.js * Hterm is still available for backward compatibility
2017-05-21 23:16:24 +00:00
}
}
Reference in New Issue Copy Permalink