MyFavMirrors
/
moonfire-nvr
mirror of https://github.com/scottlamb/moonfire-nvr.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
moonfire-nvr/ui/package.json

116 lines
3.3 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": {
Extra change for Moonfire WebUI
2024-04-05 03:41:19 -04:00
"@emotion/react": "^11.11.4",
"@emotion/styled": "^11.11.5",
"@fontsource/roboto": "^4.5.8",
"@mui/icons-material": "^5.15.15",
"@mui/lab": "5.0.0-alpha.170",
"@mui/material": "^5.15.15",
"@mui/x-date-pickers": "^6.19.8",
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",
Extra change for Moonfire WebUI
2024-04-05 03:41:19 -04:00
"date-fns": "^2.30.0",
"date-fns-tz": "^2.0.1",
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",
Extra change for Moonfire WebUI
2024-04-05 03:41:19 -04:00
"react-hook-form": "^7.51.2",
"react-hook-form-mui": "^6.8.0",
"react-router-dom": "^6.22.3"
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": {
Extra change for Moonfire WebUI
2024-04-05 03:41:19 -04:00
"@babel/core": "^7.24.4",
"@babel/preset-env": "^7.24.4",
"@babel/preset-react": "^7.24.1",
"@babel/preset-typescript": "^7.24.1",
"@swc/core": "^1.4.12",
"@testing-library/dom": "^8.20.1",
"@testing-library/jest-dom": "^6.4.2",
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",
Extra change for Moonfire WebUI
2024-04-05 03:41:19 -04:00
"@testing-library/user-event": "^14.5.2",
"@types/node": "^18.19.29",
"@types/react": "^18.2.74",
"@types/react-dom": "^18.2.24",
"@typescript-eslint/eslint-plugin": "^6.21.0",
"@typescript-eslint/parser": "^6.21.0",
"@vitejs/plugin-legacy": "^5.3.2",
"@vitejs/plugin-react-swc": "^3.6.0",
"eslint": "^8.57.0",
"eslint-plugin-react": "^7.34.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
"eslint-plugin-react-hooks": "^4.6.0",
Extra change for Moonfire WebUI
2024-04-05 03:41:19 -04:00
"eslint-plugin-react-refresh": "^0.4.6",
"eslint-plugin-vitest": "^0.3.26",
"http-proxy-middleware": "^2.0.6",
added `jsdom` to dev deps
2024-04-13 22:54:10 -04:00
"jsdom": "^24.0.0",
Extra change for Moonfire WebUI
2024-04-05 03:41:19 -04:00
"msw": "^2.2.13",
"prettier": "^2.8.8",
"terser": "^5.30.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
"ts-node": "^10.9.2",
Extra change for Moonfire WebUI
2024-04-05 03:41:19 -04:00
"typescript": "^5.4.4",
"vite": "^5.2.8",
switch to vitest
2023-12-18 02:07:28 -05:00
"vite-plugin-compression": "^0.5.1",
Extra change for Moonfire WebUI
2024-04-05 03:41:19 -04:00
"vitest": "^1.4.0"
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
}
}