MyFavMirrors/moonfire-nvr
1
0
Fork 0
mirror of https://github.com/scottlamb/moonfire-nvr.git synced 2024-12-26 23:25:55 -05:00
Code Issues Packages Projects Releases Wiki Activity
e9a25322b5
moonfire-nvr/ui/package.json

113 lines
3.2 KiB
JSON
Raw Normal View History

add a basic Javascript UI The Javascript is pretty amateurish I'm sure but at least it's something to iterate from. It's already much more pleasant for browsing through videos in several ways: * more responsive to load only a day at a time rather than 90+ days * much easier to see the same time segment on several cameras * more pleasant to have the videos load as a popup rather than a link that blows away your position in an enormous list * exposes the fancier .mp4 generation options: splitting at lengths other than the default, trimming to an arbitrary start and end time, including a subtitle track with timestamps. There's a slight regression in functionality: I didn't match the former top-level page which showed how much camera used of its disk allocation and the total duration of video. This is exposed in the JSON API, so it shouldn't be too hard to add back.
2017-10-22 00:54:27 -04:00
{
start a new React-based UI (#111) This doesn't do much yet but should provide a better foundation for improvement than the jQuery UI, as described in the github issue.
2021-02-01 00:55:25 -05:00
"name": "ui",
"version": "0.1.0",
"private": true,
switch from create-react-app to vite create-react-app is apparently deprecated, so the cool kids use vite, I guess.
2023-12-17 21:07:25 -05:00
"type": "module",
start a new React-based UI (#111) This doesn't do much yet but should provide a better foundation for improvement than the jQuery UI, as described in the github issue.
2021-02-01 00:55:25 -05:00
"dependencies": {
npm upgrade
2022-03-16 18:46:42 -04:00
"@emotion/react": "^11.8.2",
upgrade almost all frontend deps typescript isn't at the latest because eslint warns about it.
2022-03-04 11:55:06 -05:00
"@emotion/styled": "^11.8.1",
"@fontsource/roboto": "^4.5.3",
update @mui/material and @mui/icons-material This works much better with a working lockfile...
2022-10-03 20:59:28 -04:00
"@mui/icons-material": "^5.10.6",
update @mui/lab This is now only used for LoadingButton.
2022-10-03 23:55:10 -04:00
"@mui/lab": "^5.0.0-alpha.102",
update @mui/material and @mui/icons-material This works much better with a working lockfile...
2022-10-03 20:59:28 -04:00
"@mui/material": "^5.10.8",
upgrade `@mui/x-date-pickers` to v6 beta Fixes #256
2023-10-21 02:06:01 -04:00
"@mui/x-date-pickers": "^6.16.3",
switch from create-react-app to vite create-react-app is apparently deprecated, so the cool kids use vite, I guess.
2023-12-17 21:07:25 -05:00
"@react-hook/resize-observer": "^1.2.6",
upgrade almost all frontend deps typescript isn't at the latest because eslint warns about it.
2022-03-04 11:55:06 -05:00
"date-fns": "^2.28.0",
switch from create-react-app to vite create-react-app is apparently deprecated, so the cool kids use vite, I guess.
2023-12-17 21:07:25 -05:00
"date-fns-tz": "^2.0.0",
upgrade to react 18 * new root rendering api * components are now allowed to return undefine * testing library changes for userEvent.type
2023-01-12 01:25:56 -05:00
"react": "^18.2.0",
"react-dom": "^18.2.0",
react-hook-form-mui in ChangePassword
2023-01-08 14:50:05 -05:00
"react-hook-form": "^7.41.5",
upgrade `@mui/x-date-pickers` to v6 beta Fixes #256
2023-10-21 02:06:01 -04:00
"react-hook-form-mui": "^6.5.2",
switch from create-react-app to vite create-react-app is apparently deprecated, so the cool kids use vite, I guess.
2023-12-17 21:07:25 -05:00
"react-router-dom": "^6.2.2"
add a basic Javascript UI The Javascript is pretty amateurish I'm sure but at least it's something to iterate from. It's already much more pleasant for browsing through videos in several ways: * more responsive to load only a day at a time rather than 90+ days * much easier to see the same time segment on several cameras * more pleasant to have the videos load as a popup rather than a link that blows away your position in an enormous list * exposes the fancier .mp4 generation options: splitting at lengths other than the default, trimming to an arbitrary start and end time, including a subtitle track with timestamps. There's a slight regression in functionality: I didn't match the former top-level page which showed how much camera used of its disk allocation and the total duration of video. This is exposed in the JSON API, so it shouldn't be too hard to add back.
2017-10-22 00:54:27 -04:00
},
"scripts": {
switch from create-react-app to vite create-react-app is apparently deprecated, so the cool kids use vite, I guess.
2023-12-17 21:07:25 -05:00
"check-format": "prettier --check --ignore-path .gitignore .",
"dev": "vite",
"build": "tsc && vite build",
"format": "prettier --write --ignore-path .gitignore .",
"lint": "eslint . --ext ts,tsx --report-unused-disable-directives --max-warnings 0",
"preview": "vite preview",
switch to vitest
2023-12-18 02:07:28 -05:00
"test": "vitest"
add a basic Javascript UI The Javascript is pretty amateurish I'm sure but at least it's something to iterate from. It's already much more pleasant for browsing through videos in several ways: * more responsive to load only a day at a time rather than 90+ days * much easier to see the same time segment on several cameras * more pleasant to have the videos load as a popup rather than a link that blows away your position in an enormous list * exposes the fancier .mp4 generation options: splitting at lengths other than the default, trimming to an arbitrary start and end time, including a subtitle track with timestamps. There's a slight regression in functionality: I didn't match the former top-level page which showed how much camera used of its disk allocation and the total duration of video. This is exposed in the JSON API, so it shouldn't be too hard to add back.
2017-10-22 00:54:27 -04:00
},
start a new React-based UI (#111) This doesn't do much yet but should provide a better foundation for improvement than the jQuery UI, as described in the github issue.
2021-02-01 00:55:25 -05:00
"eslintConfig": {
"extends": [
switch from create-react-app to vite create-react-app is apparently deprecated, so the cool kids use vite, I guess.
2023-12-17 21:07:25 -05:00
"eslint:recommended",
switch to vitest
2023-12-18 02:07:28 -05:00
"plugin:vitest/recommended",
switch from create-react-app to vite create-react-app is apparently deprecated, so the cool kids use vite, I guess.
2023-12-17 21:07:25 -05:00
"plugin:react/recommended",
"plugin:react/jsx-runtime",
"plugin:react-hooks/recommended"
start a new React-based UI (#111) This doesn't do much yet but should provide a better foundation for improvement than the jQuery UI, as described in the github issue.
2021-02-01 00:55:25 -05:00
],
switch from create-react-app to vite create-react-app is apparently deprecated, so the cool kids use vite, I guess.
2023-12-17 21:07:25 -05:00
"overrides": [
{
"files": [
"*.ts",
"*.tsx"
],
"rules": {
"no-undef": "off"
}
}
],
"parser": "@typescript-eslint/parser",
"parserOptions": {
"ecmaVersion": "latest",
"sourceType": "module"
},
start a new React-based UI (#111) This doesn't do much yet but should provide a better foundation for improvement than the jQuery UI, as described in the github issue.
2021-02-01 00:55:25 -05:00
"rules": {
"no-restricted-imports": [
"error",
{
upgrade to @mui v5 release This requires a bunch of package name changes. See [https://mui.com/blog/material-ui-is-now-mui/] for their rationale. [https://mui.com/guides/migration-v4/] lists the changes: ``` @material-ui/core -> @mui/material @material-ui/system -> @mui/system @material-ui/unstyled -> @mui/core @material-ui/styles -> @mui/styles @material-ui/icons -> @mui/icons-material @material-ui/lab -> @mui/lab @material-ui/types -> @mui/types @material-ui/styled-engine -> @mui/styled-engine @material-ui/styled-engine-sc ->@mui/styled-engine-sc @material-ui/private-theming -> @mui/private-theming @material-ui/codemod -> @mui/codemod @material-ui/docs -> @mui/docs @material-ui/envinfo -> @mui/envinfo ``` We only use a few of these.
2021-09-24 13:57:29 -04:00
"name": "@mui/material",
start a new React-based UI (#111) This doesn't do much yet but should provide a better foundation for improvement than the jQuery UI, as described in the github issue.
2021-02-01 00:55:25 -05:00
"message": "Please use the 'import Button from \"material-ui/core/Button\";' style instead; see https://material-ui.com/guides/minimizing-bundle-size/#option-1"
},
{
upgrade to @mui v5 release This requires a bunch of package name changes. See [https://mui.com/blog/material-ui-is-now-mui/] for their rationale. [https://mui.com/guides/migration-v4/] lists the changes: ``` @material-ui/core -> @mui/material @material-ui/system -> @mui/system @material-ui/unstyled -> @mui/core @material-ui/styles -> @mui/styles @material-ui/icons -> @mui/icons-material @material-ui/lab -> @mui/lab @material-ui/types -> @mui/types @material-ui/styled-engine -> @mui/styled-engine @material-ui/styled-engine-sc ->@mui/styled-engine-sc @material-ui/private-theming -> @mui/private-theming @material-ui/codemod -> @mui/codemod @material-ui/docs -> @mui/docs @material-ui/envinfo -> @mui/envinfo ``` We only use a few of these.
2021-09-24 13:57:29 -04:00
"name": "@mui/icons-material",
start a new React-based UI (#111) This doesn't do much yet but should provide a better foundation for improvement than the jQuery UI, as described in the github issue.
2021-02-01 00:55:25 -05:00
"message": "Please use the 'import MenuIcon from \"material-ui/icons/Menu\";' style instead; see https://material-ui.com/guides/minimizing-bundle-size/#option-1"
}
switch from create-react-app to vite create-react-app is apparently deprecated, so the cool kids use vite, I guess.
2023-12-17 21:07:25 -05:00
],
"no-unused-vars": [
"error",
{
"args": "none"
}
],
"react/no-unescaped-entities": "off"
},
"settings": {
"react": {
"version": "detect"
}
start a new React-based UI (#111) This doesn't do much yet but should provide a better foundation for improvement than the jQuery UI, as described in the github issue.
2021-02-01 00:55:25 -05:00
}
},
add a basic Javascript UI The Javascript is pretty amateurish I'm sure but at least it's something to iterate from. It's already much more pleasant for browsing through videos in several ways: * more responsive to load only a day at a time rather than 90+ days * much easier to see the same time segment on several cameras * more pleasant to have the videos load as a popup rather than a link that blows away your position in an enormous list * exposes the fancier .mp4 generation options: splitting at lengths other than the default, trimming to an arbitrary start and end time, including a subtitle track with timestamps. There's a slight regression in functionality: I didn't match the former top-level page which showed how much camera used of its disk allocation and the total duration of video. This is exposed in the JSON API, so it shouldn't be too hard to add back.
2017-10-22 00:54:27 -04:00
"devDependencies": {
switch from create-react-app to vite create-react-app is apparently deprecated, so the cool kids use vite, I guess.
2023-12-17 21:07:25 -05:00
"@babel/core": "^7.23.5",
"@babel/preset-env": "^7.23.6",
"@babel/preset-react": "^7.23.3",
"@babel/preset-typescript": "^7.23.3",
"@swc/core": "^1.3.100",
upgrade to create-react-scripts v5 I had to disable more of the Login tests to get this to work. Frustrating, but I just can't figure out how to fake jest timers, msw, and the testing libraries to all get along anymore.
2022-03-03 17:39:08 -05:00
"@testing-library/dom": "^8.11.3",
switch to vitest
2023-12-18 02:07:28 -05:00
"@testing-library/jest-dom": "^6.1.5",
upgrade to react 18 * new root rendering api * components are now allowed to return undefine * testing library changes for userEvent.type
2023-01-12 01:25:56 -05:00
"@testing-library/react": "^13.4.0",
"@testing-library/user-event": "^14.4.3",
switch from create-react-app to vite create-react-app is apparently deprecated, so the cool kids use vite, I guess.
2023-12-17 21:07:25 -05:00
"@types/node": "^18.8.1",
"@types/react": "^18.0.26",
"@types/react-dom": "^18.0.10",
"@typescript-eslint/eslint-plugin": "^6.14.0",
"@typescript-eslint/parser": "^6.14.0",
"@vitejs/plugin-react-swc": "^3.5.0",
"eslint": "^8.55.0",
"eslint-plugin-react": "^7.33.2",
"eslint-plugin-react-hooks": "^4.6.0",
"eslint-plugin-react-refresh": "^0.4.5",
switch to vitest
2023-12-18 02:07:28 -05:00
"eslint-plugin-vitest": "^0.3.18",
npm upgrade
2022-03-16 18:46:42 -04:00
"http-proxy-middleware": "^2.0.4",
upgrade msw 1->2, fix network error case In the upgrade I managed to dust off some tests that I'd been skipping for quite a while. It turns out one of them was pointing out a real problem: in the network error case, we didn't display the error to the user properly. It's really sad this reaches our code as a `TypeError`, but it is what it is.
2023-12-18 02:37:07 -05:00
"msw": "^2.0.0",
switch from create-react-app to vite create-react-app is apparently deprecated, so the cool kids use vite, I guess.
2023-12-17 21:07:25 -05:00
"prettier": "^2.6.0",
"ts-node": "^10.9.2",
"typescript": "^5.1.0",
"vite": "^5.0.8",
switch to vitest
2023-12-18 02:07:28 -05:00
"vite-plugin-compression": "^0.5.1",
"vitest": "^1.0.4"
add a basic Javascript UI The Javascript is pretty amateurish I'm sure but at least it's something to iterate from. It's already much more pleasant for browsing through videos in several ways: * more responsive to load only a day at a time rather than 90+ days * much easier to see the same time segment on several cameras * more pleasant to have the videos load as a popup rather than a link that blows away your position in an enormous list * exposes the fancier .mp4 generation options: splitting at lengths other than the default, trimming to an arbitrary start and end time, including a subtitle track with timestamps. There's a slight regression in functionality: I didn't match the former top-level page which showed how much camera used of its disk allocation and the total duration of video. This is exposed in the JSON API, so it shouldn't be too hard to add back.
2017-10-22 00:54:27 -04:00
}
}
Reference in New Issue Copy Permalink