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/yarn.lock

6033 lines
255 KiB
Plaintext
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
# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
# yarn lockfile v1
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/code-frame@^7.0.0", "@babel/code-frame@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.8.3.tgz#33e25903d7481181534e12ec0a25f16b6fcf419e"
integrity sha512-a9gxpmdXtZEInkCSHUJDLHZVBgb1QS0jhss4cPP93EW7s+uC5bikET2twEF3KV+7rDblJcmNvTR7VJejqd2C2g==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/highlight" "^7.8.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/compat-data@^7.8.6":
version "7.8.6"
resolved "https://registry.yarnpkg.com/@babel/compat-data/-/compat-data-7.8.6.tgz#7eeaa0dfa17e50c7d9c0832515eee09b56f04e35"
integrity sha512-CurCIKPTkS25Mb8mz267vU95vy+TyUpnctEX2lV33xWNmHAfjruztgiPBbXZRh3xZZy1CYvGx6XfxyTVS+sk7Q==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
browserslist "^4.8.5"
invariant "^2.2.4"
semver "^5.5.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/core@^7.8.6":
version "7.8.6"
resolved "https://registry.yarnpkg.com/@babel/core/-/core-7.8.6.tgz#27d7df9258a45c2e686b6f18b6c659e563aa4636"
integrity sha512-Sheg7yEJD51YHAvLEV/7Uvw95AeWqYPL3Vk3zGujJKIhJ+8oLw2ALaf3hbucILhKsgSoADOvtKRJuNVdcJkOrg==
dependencies:
"@babel/code-frame" "^7.8.3"
"@babel/generator" "^7.8.6"
"@babel/helpers" "^7.8.4"
"@babel/parser" "^7.8.6"
"@babel/template" "^7.8.6"
"@babel/traverse" "^7.8.6"
"@babel/types" "^7.8.6"
convert-source-map "^1.7.0"
debug "^4.1.0"
gensync "^1.0.0-beta.1"
json5 "^2.1.0"
lodash "^4.17.13"
resolve "^1.3.2"
semver "^5.4.1"
source-map "^0.5.0"
"@babel/generator@^7.8.6":
version "7.8.6"
resolved "https://registry.yarnpkg.com/@babel/generator/-/generator-7.8.6.tgz#57adf96d370c9a63c241cd719f9111468578537a"
integrity sha512-4bpOR5ZBz+wWcMeVtcf7FbjcFzCp+817z2/gHNncIRcM9MmKzUhtWCYAq27RAfUrAFwb+OCG1s9WEaVxfi6cjg==
dependencies:
"@babel/types" "^7.8.6"
jsesc "^2.5.1"
lodash "^4.17.13"
source-map "^0.5.0"
"@babel/helper-annotate-as-pure@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-annotate-as-pure/-/helper-annotate-as-pure-7.8.3.tgz#60bc0bc657f63a0924ff9a4b4a0b24a13cf4deee"
integrity sha512-6o+mJrZBxOoEX77Ezv9zwW7WV8DdluouRKNY/IR5u/YTMuKHgugHOzYWlYvYLpLA9nPsQCAAASpCIbjI9Mv+Uw==
dependencies:
"@babel/types" "^7.8.3"
"@babel/helper-builder-binary-assignment-operator-visitor@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-builder-binary-assignment-operator-visitor/-/helper-builder-binary-assignment-operator-visitor-7.8.3.tgz#c84097a427a061ac56a1c30ebf54b7b22d241503"
integrity sha512-5eFOm2SyFPK4Rh3XMMRDjN7lBH0orh3ss0g3rTYZnBQ+r6YPj7lgDyCvPphynHvUrobJmeMignBr6Acw9mAPlw==
dependencies:
"@babel/helper-explode-assignable-expression" "^7.8.3"
"@babel/types" "^7.8.3"
"@babel/helper-call-delegate@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-call-delegate/-/helper-call-delegate-7.8.3.tgz#de82619898aa605d409c42be6ffb8d7204579692"
integrity sha512-6Q05px0Eb+N4/GTyKPPvnkig7Lylw+QzihMpws9iiZQv7ZImf84ZsZpQH7QoWN4n4tm81SnSzPgHw2qtO0Zf3A==
dependencies:
"@babel/helper-hoist-variables" "^7.8.3"
"@babel/traverse" "^7.8.3"
"@babel/types" "^7.8.3"
"@babel/helper-compilation-targets@^7.8.6":
version "7.8.6"
resolved "https://registry.yarnpkg.com/@babel/helper-compilation-targets/-/helper-compilation-targets-7.8.6.tgz#015b85db69e3a34240d5c2b761fc53eb9695f09c"
integrity sha512-UrJdk27hKVJSnibFcUWYLkCL0ZywTUoot8yii1lsHJcvwrypagmYKjHLMWivQPm4s6GdyygCL8fiH5EYLxhQwQ==
dependencies:
"@babel/compat-data" "^7.8.6"
browserslist "^4.8.5"
invariant "^2.2.4"
levenary "^1.1.1"
semver "^5.5.0"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/helper-create-regexp-features-plugin@^7.8.3":
version "7.8.6"
resolved "https://registry.yarnpkg.com/@babel/helper-create-regexp-features-plugin/-/helper-create-regexp-features-plugin-7.8.6.tgz#7fa040c97fb8aebe1247a5c645330c32d083066b"
integrity sha512-bPyujWfsHhV/ztUkwGHz/RPV1T1TDEsSZDsN42JPehndA+p1KKTh3npvTadux0ZhCrytx9tvjpWNowKby3tM6A==
dependencies:
"@babel/helper-annotate-as-pure" "^7.8.3"
"@babel/helper-regex" "^7.8.3"
regexpu-core "^4.6.0"
"@babel/helper-define-map@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-define-map/-/helper-define-map-7.8.3.tgz#a0655cad5451c3760b726eba875f1cd8faa02c15"
integrity sha512-PoeBYtxoZGtct3md6xZOCWPcKuMuk3IHhgxsRRNtnNShebf4C8YonTSblsK4tvDbm+eJAw2HAPOfCr+Q/YRG/g==
dependencies:
"@babel/helper-function-name" "^7.8.3"
"@babel/types" "^7.8.3"
lodash "^4.17.13"
"@babel/helper-explode-assignable-expression@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-explode-assignable-expression/-/helper-explode-assignable-expression-7.8.3.tgz#a728dc5b4e89e30fc2dfc7d04fa28a930653f982"
integrity sha512-N+8eW86/Kj147bO9G2uclsg5pwfs/fqqY5rwgIL7eTBklgXjcOJ3btzS5iM6AitJcftnY7pm2lGsrJVYLGjzIw==
dependencies:
"@babel/traverse" "^7.8.3"
"@babel/types" "^7.8.3"
"@babel/helper-function-name@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-function-name/-/helper-function-name-7.8.3.tgz#eeeb665a01b1f11068e9fb86ad56a1cb1a824cca"
integrity sha512-BCxgX1BC2hD/oBlIFUgOCQDOPV8nSINxCwM3o93xP4P9Fq6aV5sgv2cOOITDMtCfQ+3PvHp3l689XZvAM9QyOA==
dependencies:
"@babel/helper-get-function-arity" "^7.8.3"
"@babel/template" "^7.8.3"
"@babel/types" "^7.8.3"
"@babel/helper-get-function-arity@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-get-function-arity/-/helper-get-function-arity-7.8.3.tgz#b894b947bd004381ce63ea1db9f08547e920abd5"
integrity sha512-FVDR+Gd9iLjUMY1fzE2SR0IuaJToR4RkCDARVfsBBPSP53GEqSFjD8gNyxg246VUyc/ALRxFaAK8rVG7UT7xRA==
dependencies:
"@babel/types" "^7.8.3"
"@babel/helper-hoist-variables@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-hoist-variables/-/helper-hoist-variables-7.8.3.tgz#1dbe9b6b55d78c9b4183fc8cdc6e30ceb83b7134"
integrity sha512-ky1JLOjcDUtSc+xkt0xhYff7Z6ILTAHKmZLHPxAhOP0Nd77O+3nCsd6uSVYur6nJnCI029CrNbYlc0LoPfAPQg==
dependencies:
"@babel/types" "^7.8.3"
"@babel/helper-member-expression-to-functions@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-member-expression-to-functions/-/helper-member-expression-to-functions-7.8.3.tgz#659b710498ea6c1d9907e0c73f206eee7dadc24c"
integrity sha512-fO4Egq88utkQFjbPrSHGmGLFqmrshs11d46WI+WZDESt7Wu7wN2G2Iu+NMMZJFDOVRHAMIkB5SNh30NtwCA7RA==
dependencies:
"@babel/types" "^7.8.3"
"@babel/helper-module-imports@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-module-imports/-/helper-module-imports-7.8.3.tgz#7fe39589b39c016331b6b8c3f441e8f0b1419498"
integrity sha512-R0Bx3jippsbAEtzkpZ/6FIiuzOURPcMjHp+Z6xPe6DtApDJx+w7UYyOLanZqO8+wKR9G10s/FmHXvxaMd9s6Kg==
dependencies:
"@babel/types" "^7.8.3"
"@babel/helper-module-transforms@^7.8.3":
version "7.8.6"
resolved "https://registry.yarnpkg.com/@babel/helper-module-transforms/-/helper-module-transforms-7.8.6.tgz#6a13b5eecadc35692047073a64e42977b97654a4"
integrity sha512-RDnGJSR5EFBJjG3deY0NiL0K9TO8SXxS9n/MPsbPK/s9LbQymuLNtlzvDiNS7IpecuL45cMeLVkA+HfmlrnkRg==
dependencies:
"@babel/helper-module-imports" "^7.8.3"
"@babel/helper-replace-supers" "^7.8.6"
"@babel/helper-simple-access" "^7.8.3"
"@babel/helper-split-export-declaration" "^7.8.3"
"@babel/template" "^7.8.6"
"@babel/types" "^7.8.6"
lodash "^4.17.13"
"@babel/helper-optimise-call-expression@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-optimise-call-expression/-/helper-optimise-call-expression-7.8.3.tgz#7ed071813d09c75298ef4f208956006b6111ecb9"
integrity sha512-Kag20n86cbO2AvHca6EJsvqAd82gc6VMGule4HwebwMlwkpXuVqrNRj6CkCV2sKxgi9MyAUnZVnZ6lJ1/vKhHQ==
dependencies:
"@babel/types" "^7.8.3"
"@babel/helper-plugin-utils@^7.8.0", "@babel/helper-plugin-utils@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-plugin-utils/-/helper-plugin-utils-7.8.3.tgz#9ea293be19babc0f52ff8ca88b34c3611b208670"
integrity sha512-j+fq49Xds2smCUNYmEHF9kGNkhbet6yVIBp4e6oeQpH1RUs/Ir06xUKzDjDkGcaaokPiTNs2JBWHjaE4csUkZQ==
"@babel/helper-regex@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-regex/-/helper-regex-7.8.3.tgz#139772607d51b93f23effe72105b319d2a4c6965"
integrity sha512-BWt0QtYv/cg/NecOAZMdcn/waj/5P26DR4mVLXfFtDokSR6fyuG0Pj+e2FqtSME+MqED1khnSMulkmGl8qWiUQ==
dependencies:
lodash "^4.17.13"
"@babel/helper-remap-async-to-generator@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-remap-async-to-generator/-/helper-remap-async-to-generator-7.8.3.tgz#273c600d8b9bf5006142c1e35887d555c12edd86"
integrity sha512-kgwDmw4fCg7AVgS4DukQR/roGp+jP+XluJE5hsRZwxCYGg+Rv9wSGErDWhlI90FODdYfd4xG4AQRiMDjjN0GzA==
dependencies:
"@babel/helper-annotate-as-pure" "^7.8.3"
"@babel/helper-wrap-function" "^7.8.3"
"@babel/template" "^7.8.3"
"@babel/traverse" "^7.8.3"
"@babel/types" "^7.8.3"
"@babel/helper-replace-supers@^7.8.3", "@babel/helper-replace-supers@^7.8.6":
version "7.8.6"
resolved "https://registry.yarnpkg.com/@babel/helper-replace-supers/-/helper-replace-supers-7.8.6.tgz#5ada744fd5ad73203bf1d67459a27dcba67effc8"
integrity sha512-PeMArdA4Sv/Wf4zXwBKPqVj7n9UF/xg6slNRtZW84FM7JpE1CbG8B612FyM4cxrf4fMAMGO0kR7voy1ForHHFA==
dependencies:
"@babel/helper-member-expression-to-functions" "^7.8.3"
"@babel/helper-optimise-call-expression" "^7.8.3"
"@babel/traverse" "^7.8.6"
"@babel/types" "^7.8.6"
"@babel/helper-simple-access@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-simple-access/-/helper-simple-access-7.8.3.tgz#7f8109928b4dab4654076986af575231deb639ae"
integrity sha512-VNGUDjx5cCWg4vvCTR8qQ7YJYZ+HBjxOgXEl7ounz+4Sn7+LMD3CFrCTEU6/qXKbA2nKg21CwhhBzO0RpRbdCw==
dependencies:
"@babel/template" "^7.8.3"
"@babel/types" "^7.8.3"
"@babel/helper-split-export-declaration@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-split-export-declaration/-/helper-split-export-declaration-7.8.3.tgz#31a9f30070f91368a7182cf05f831781065fc7a9"
integrity sha512-3x3yOeyBhW851hroze7ElzdkeRXQYQbFIb7gLK1WQYsw2GWDay5gAJNw1sWJ0VFP6z5J1whqeXH/WCdCjZv6dA==
dependencies:
"@babel/types" "^7.8.3"
"@babel/helper-wrap-function@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/helper-wrap-function/-/helper-wrap-function-7.8.3.tgz#9dbdb2bb55ef14aaa01fe8c99b629bd5352d8610"
integrity sha512-LACJrbUET9cQDzb6kG7EeD7+7doC3JNvUgTEQOx2qaO1fKlzE/Bf05qs9w1oXQMmXlPO65lC3Tq9S6gZpTErEQ==
dependencies:
"@babel/helper-function-name" "^7.8.3"
"@babel/template" "^7.8.3"
"@babel/traverse" "^7.8.3"
"@babel/types" "^7.8.3"
"@babel/helpers@^7.8.4":
version "7.8.4"
resolved "https://registry.yarnpkg.com/@babel/helpers/-/helpers-7.8.4.tgz#754eb3ee727c165e0a240d6c207de7c455f36f73"
integrity sha512-VPbe7wcQ4chu4TDQjimHv/5tj73qz88o12EPkO2ValS2QiQS/1F2SsjyIGNnAD0vF/nZS6Cf9i+vW6HIlnaR8w==
dependencies:
"@babel/template" "^7.8.3"
"@babel/traverse" "^7.8.4"
"@babel/types" "^7.8.3"
"@babel/highlight@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/highlight/-/highlight-7.8.3.tgz#28f173d04223eaaa59bc1d439a3836e6d1265797"
integrity sha512-PX4y5xQUvy0fnEVHrYOarRPXVWafSjTW9T0Hab8gVIawpl2Sj0ORyrygANq+KjcNlSSTw0YCLSNA8OyZ1I4yEg==
dependencies:
chalk "^2.0.0"
esutils "^2.0.2"
js-tokens "^4.0.0"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/parser@^7.8.6":
version "7.8.6"
resolved "https://registry.yarnpkg.com/@babel/parser/-/parser-7.8.6.tgz#ba5c9910cddb77685a008e3c587af8d27b67962c"
integrity sha512-trGNYSfwq5s0SgM1BMEB8hX3NDmO7EP2wsDGDexiaKMB92BaRpS+qZfpkMqUBhcsOTBwNy9B/jieo4ad/t/z2g==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-proposal-async-generator-functions@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-async-generator-functions/-/plugin-proposal-async-generator-functions-7.8.3.tgz#bad329c670b382589721b27540c7d288601c6e6f"
integrity sha512-NZ9zLv848JsV3hs8ryEh7Uaz/0KsmPLqv0+PdkDJL1cJy0K4kOCFa8zc1E3mp+RHPQcpdfb/6GovEsW4VDrOMw==
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/helper-remap-async-to-generator" "^7.8.3"
"@babel/plugin-syntax-async-generators" "^7.8.0"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-proposal-dynamic-import@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-dynamic-import/-/plugin-proposal-dynamic-import-7.8.3.tgz#38c4fe555744826e97e2ae930b0fb4cc07e66054"
integrity sha512-NyaBbyLFXFLT9FP+zk0kYlUlA8XtCUbehs67F0nnEg7KICgMc2mNkIeu9TYhKzyXMkrapZFwAhXLdnt4IYHy1w==
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/plugin-syntax-dynamic-import" "^7.8.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-proposal-json-strings@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-json-strings/-/plugin-proposal-json-strings-7.8.3.tgz#da5216b238a98b58a1e05d6852104b10f9a70d6b"
integrity sha512-KGhQNZ3TVCQG/MjRbAUwuH+14y9q0tpxs1nWWs3pbSleRdDro9SAMMDyye8HhY1gqZ7/NqIc8SKhya0wRDgP1Q==
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/plugin-syntax-json-strings" "^7.8.0"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-proposal-nullish-coalescing-operator@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-nullish-coalescing-operator/-/plugin-proposal-nullish-coalescing-operator-7.8.3.tgz#e4572253fdeed65cddeecfdab3f928afeb2fd5d2"
integrity sha512-TS9MlfzXpXKt6YYomudb/KU7nQI6/xnapG6in1uZxoxDghuSMZsPb6D2fyUwNYSAp4l1iR7QtFOjkqcRYcUsfw==
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/plugin-syntax-nullish-coalescing-operator" "^7.8.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-proposal-object-rest-spread@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-object-rest-spread/-/plugin-proposal-object-rest-spread-7.8.3.tgz#eb5ae366118ddca67bed583b53d7554cad9951bb"
integrity sha512-8qvuPwU/xxUCt78HocNlv0mXXo0wdh9VT1R04WU8HGOfaOob26pF+9P5/lYjN/q7DHOX1bvX60hnhOvuQUJdbA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/plugin-syntax-object-rest-spread" "^7.8.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-proposal-optional-catch-binding@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-optional-catch-binding/-/plugin-proposal-optional-catch-binding-7.8.3.tgz#9dee96ab1650eed88646ae9734ca167ac4a9c5c9"
integrity sha512-0gkX7J7E+AtAw9fcwlVQj8peP61qhdg/89D5swOkjYbkboA2CVckn3kiyum1DE0wskGb7KJJxBdyEBApDLLVdw==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/plugin-syntax-optional-catch-binding" "^7.8.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-proposal-optional-chaining@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-optional-chaining/-/plugin-proposal-optional-chaining-7.8.3.tgz#ae10b3214cb25f7adb1f3bc87ba42ca10b7e2543"
integrity sha512-QIoIR9abkVn+seDE3OjA08jWcs3eZ9+wJCKSRgo3WdEU2csFYgdScb+8qHB3+WXsGJD55u+5hWCISI7ejXS+kg==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/plugin-syntax-optional-chaining" "^7.8.0"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-proposal-unicode-property-regex@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-unicode-property-regex/-/plugin-proposal-unicode-property-regex-7.8.3.tgz#b646c3adea5f98800c9ab45105ac34d06cd4a47f"
integrity sha512-1/1/rEZv2XGweRwwSkLpY+s60za9OZ1hJs4YDqFHCw0kYWYwL5IFljVY1MYBL+weT1l9pokDO2uhSTLVxzoHkQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/helper-create-regexp-features-plugin" "^7.8.3"
"@babel/helper-plugin-utils" "^7.8.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-syntax-async-generators@^7.8.0":
version "7.8.4"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-async-generators/-/plugin-syntax-async-generators-7.8.4.tgz#a983fb1aeb2ec3f6ed042a210f640e90e786fe0d"
integrity sha512-tycmZxkGfZaxhMRbXlPXuVFpdWlXpir2W4AMhSJgRKzk/eDlIXOhb2LHWoLpDF7TEHylV5zNhykX6KAgHJmTNw==
dependencies:
"@babel/helper-plugin-utils" "^7.8.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-syntax-dynamic-import@^7.8.0":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-dynamic-import/-/plugin-syntax-dynamic-import-7.8.3.tgz#62bf98b2da3cd21d626154fc96ee5b3cb68eacb3"
integrity sha512-5gdGbFon+PszYzqs83S3E5mpi7/y/8M9eC90MRTZfduQOYW76ig6SOSPNe41IG5LoP3FGBn2N0RjVDSQiS94kQ==
dependencies:
"@babel/helper-plugin-utils" "^7.8.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-syntax-json-strings@^7.8.0":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-json-strings/-/plugin-syntax-json-strings-7.8.3.tgz#01ca21b668cd8218c9e640cb6dd88c5412b2c96a"
integrity sha512-lY6kdGpWHvjoe2vk4WrAapEuBR69EMxZl+RoGRhrFGNYVK8mOPAW8VfbT/ZgrFbXlDNiiaxQnAtgVCZ6jv30EA==
dependencies:
"@babel/helper-plugin-utils" "^7.8.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-syntax-nullish-coalescing-operator@^7.8.0":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-nullish-coalescing-operator/-/plugin-syntax-nullish-coalescing-operator-7.8.3.tgz#167ed70368886081f74b5c36c65a88c03b66d1a9"
integrity sha512-aSff4zPII1u2QD7y+F8oDsz19ew4IGEJg9SVW+bqwpwtfFleiQDMdzA/R+UlWDzfnHFCxxleFT0PMIrR36XLNQ==
dependencies:
"@babel/helper-plugin-utils" "^7.8.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-syntax-object-rest-spread@^7.8.0":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-object-rest-spread/-/plugin-syntax-object-rest-spread-7.8.3.tgz#60e225edcbd98a640332a2e72dd3e66f1af55871"
integrity sha512-XoqMijGZb9y3y2XskN+P1wUGiVwWZ5JmoDRwx5+3GmEplNyVM2s2Dg8ILFQm8rWM48orGy5YpI5Bl8U1y7ydlA==
dependencies:
"@babel/helper-plugin-utils" "^7.8.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-syntax-optional-catch-binding@^7.8.0":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-optional-catch-binding/-/plugin-syntax-optional-catch-binding-7.8.3.tgz#6111a265bcfb020eb9efd0fdfd7d26402b9ed6c1"
integrity sha512-6VPD0Pc1lpTqw0aKoeRTMiB+kWhAoT24PA+ksWSBrFtl5SIRVpZlwN3NNPQjehA2E/91FV3RjLWoVTglWcSV3Q==
dependencies:
"@babel/helper-plugin-utils" "^7.8.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-syntax-optional-chaining@^7.8.0":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-optional-chaining/-/plugin-syntax-optional-chaining-7.8.3.tgz#4f69c2ab95167e0180cd5336613f8c5788f7d48a"
integrity sha512-KoK9ErH1MBlCPxV0VANkXW2/dw4vlbGDrFgz8bmUsBGYkFRcbRwMh6cIJubdPrkxRwuGdtCk0v/wPTKbQgBjkg==
dependencies:
"@babel/helper-plugin-utils" "^7.8.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-syntax-top-level-await@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-top-level-await/-/plugin-syntax-top-level-await-7.8.3.tgz#3acdece695e6b13aaf57fc291d1a800950c71391"
integrity sha512-kwj1j9lL/6Wd0hROD3b/OZZ7MSrZLqqn9RAZ5+cYYsflQ9HZBIKCUkr3+uL1MEJ1NePiUbf98jjiMQSv0NMR9g==
dependencies:
"@babel/helper-plugin-utils" "^7.8.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-arrow-functions@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-arrow-functions/-/plugin-transform-arrow-functions-7.8.3.tgz#82776c2ed0cd9e1a49956daeb896024c9473b8b6"
integrity sha512-0MRF+KC8EqH4dbuITCWwPSzsyO3HIWWlm30v8BbbpOrS1B++isGxPnnuq/IZvOX5J2D/p7DQalQm+/2PnlKGxg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/helper-plugin-utils" "^7.8.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-async-to-generator@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-async-to-generator/-/plugin-transform-async-to-generator-7.8.3.tgz#4308fad0d9409d71eafb9b1a6ee35f9d64b64086"
integrity sha512-imt9tFLD9ogt56Dd5CI/6XgpukMwd/fLGSrix2httihVe7LOGVPhyhMh1BU5kDM7iHD08i8uUtmV2sWaBFlHVQ==
dependencies:
"@babel/helper-module-imports" "^7.8.3"
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/helper-remap-async-to-generator" "^7.8.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-block-scoped-functions@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-block-scoped-functions/-/plugin-transform-block-scoped-functions-7.8.3.tgz#437eec5b799b5852072084b3ae5ef66e8349e8a3"
integrity sha512-vo4F2OewqjbB1+yaJ7k2EJFHlTP3jR634Z9Cj9itpqNjuLXvhlVxgnjsHsdRgASR8xYDrx6onw4vW5H6We0Jmg==
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-block-scoping@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-block-scoping/-/plugin-transform-block-scoping-7.8.3.tgz#97d35dab66857a437c166358b91d09050c868f3a"
integrity sha512-pGnYfm7RNRgYRi7bids5bHluENHqJhrV4bCZRwc5GamaWIIs07N4rZECcmJL6ZClwjDz1GbdMZFtPs27hTB06w==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/helper-plugin-utils" "^7.8.3"
lodash "^4.17.13"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-classes@^7.8.6":
version "7.8.6"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-classes/-/plugin-transform-classes-7.8.6.tgz#77534447a477cbe5995ae4aee3e39fbc8090c46d"
integrity sha512-k9r8qRay/R6v5aWZkrEclEhKO6mc1CCQr2dLsVHBmOQiMpN6I2bpjX3vgnldUWeEI1GHVNByULVxZ4BdP4Hmdg==
dependencies:
"@babel/helper-annotate-as-pure" "^7.8.3"
"@babel/helper-define-map" "^7.8.3"
"@babel/helper-function-name" "^7.8.3"
"@babel/helper-optimise-call-expression" "^7.8.3"
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/helper-replace-supers" "^7.8.6"
"@babel/helper-split-export-declaration" "^7.8.3"
globals "^11.1.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-computed-properties@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-computed-properties/-/plugin-transform-computed-properties-7.8.3.tgz#96d0d28b7f7ce4eb5b120bb2e0e943343c86f81b"
integrity sha512-O5hiIpSyOGdrQZRQ2ccwtTVkgUDBBiCuK//4RJ6UfePllUTCENOzKxfh6ulckXKc0DixTFLCfb2HVkNA7aDpzA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/helper-plugin-utils" "^7.8.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-destructuring@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-destructuring/-/plugin-transform-destructuring-7.8.3.tgz#20ddfbd9e4676906b1056ee60af88590cc7aaa0b"
integrity sha512-H4X646nCkiEcHZUZaRkhE2XVsoz0J/1x3VVujnn96pSoGCtKPA99ZZA+va+gK+92Zycd6OBKCD8tDb/731bhgQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/helper-plugin-utils" "^7.8.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-dotall-regex@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-dotall-regex/-/plugin-transform-dotall-regex-7.8.3.tgz#c3c6ec5ee6125c6993c5cbca20dc8621a9ea7a6e"
integrity sha512-kLs1j9Nn4MQoBYdRXH6AeaXMbEJFaFu/v1nQkvib6QzTj8MZI5OQzqmD83/2jEM1z0DLilra5aWO5YpyC0ALIw==
dependencies:
"@babel/helper-create-regexp-features-plugin" "^7.8.3"
"@babel/helper-plugin-utils" "^7.8.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-duplicate-keys@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-duplicate-keys/-/plugin-transform-duplicate-keys-7.8.3.tgz#8d12df309aa537f272899c565ea1768e286e21f1"
integrity sha512-s8dHiBUbcbSgipS4SMFuWGqCvyge5V2ZeAWzR6INTVC3Ltjig/Vw1G2Gztv0vU/hRG9X8IvKvYdoksnUfgXOEQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/helper-plugin-utils" "^7.8.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-exponentiation-operator@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-exponentiation-operator/-/plugin-transform-exponentiation-operator-7.8.3.tgz#581a6d7f56970e06bf51560cd64f5e947b70d7b7"
integrity sha512-zwIpuIymb3ACcInbksHaNcR12S++0MDLKkiqXHl3AzpgdKlFNhog+z/K0+TGW+b0w5pgTq4H6IwV/WhxbGYSjQ==
dependencies:
"@babel/helper-builder-binary-assignment-operator-visitor" "^7.8.3"
"@babel/helper-plugin-utils" "^7.8.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-for-of@^7.8.6":
version "7.8.6"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-for-of/-/plugin-transform-for-of-7.8.6.tgz#a051bd1b402c61af97a27ff51b468321c7c2a085"
integrity sha512-M0pw4/1/KI5WAxPsdcUL/w2LJ7o89YHN3yLkzNjg7Yl15GlVGgzHyCU+FMeAxevHGsLVmUqbirlUIKTafPmzdw==
dependencies:
"@babel/helper-plugin-utils" "^7.8.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-function-name@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-function-name/-/plugin-transform-function-name-7.8.3.tgz#279373cb27322aaad67c2683e776dfc47196ed8b"
integrity sha512-rO/OnDS78Eifbjn5Py9v8y0aR+aSYhDhqAwVfsTl0ERuMZyr05L1aFSCJnbv2mmsLkit/4ReeQ9N2BgLnOcPCQ==
dependencies:
"@babel/helper-function-name" "^7.8.3"
"@babel/helper-plugin-utils" "^7.8.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-literals@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-literals/-/plugin-transform-literals-7.8.3.tgz#aef239823d91994ec7b68e55193525d76dbd5dc1"
integrity sha512-3Tqf8JJ/qB7TeldGl+TT55+uQei9JfYaregDcEAyBZ7akutriFrt6C/wLYIer6OYhleVQvH/ntEhjE/xMmy10A==
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-member-expression-literals@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-member-expression-literals/-/plugin-transform-member-expression-literals-7.8.3.tgz#963fed4b620ac7cbf6029c755424029fa3a40410"
integrity sha512-3Wk2EXhnw+rP+IDkK6BdtPKsUE5IeZ6QOGrPYvw52NwBStw9V1ZVzxgK6fSKSxqUvH9eQPR3tm3cOq79HlsKYA==
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-modules-amd@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-amd/-/plugin-transform-modules-amd-7.8.3.tgz#65606d44616b50225e76f5578f33c568a0b876a5"
integrity sha512-MadJiU3rLKclzT5kBH4yxdry96odTUwuqrZM+GllFI/VhxfPz+k9MshJM+MwhfkCdxxclSbSBbUGciBngR+kEQ==
dependencies:
"@babel/helper-module-transforms" "^7.8.3"
"@babel/helper-plugin-utils" "^7.8.3"
babel-plugin-dynamic-import-node "^2.3.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-modules-commonjs@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-commonjs/-/plugin-transform-modules-commonjs-7.8.3.tgz#df251706ec331bd058a34bdd72613915f82928a5"
integrity sha512-JpdMEfA15HZ/1gNuB9XEDlZM1h/gF/YOH7zaZzQu2xCFRfwc01NXBMHHSTT6hRjlXJJs5x/bfODM3LiCk94Sxg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/helper-module-transforms" "^7.8.3"
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/helper-simple-access" "^7.8.3"
babel-plugin-dynamic-import-node "^2.3.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-modules-systemjs@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-systemjs/-/plugin-transform-modules-systemjs-7.8.3.tgz#d8bbf222c1dbe3661f440f2f00c16e9bb7d0d420"
integrity sha512-8cESMCJjmArMYqa9AO5YuMEkE4ds28tMpZcGZB/jl3n0ZzlsxOAi3mC+SKypTfT8gjMupCnd3YiXCkMjj2jfOg==
dependencies:
"@babel/helper-hoist-variables" "^7.8.3"
"@babel/helper-module-transforms" "^7.8.3"
"@babel/helper-plugin-utils" "^7.8.3"
babel-plugin-dynamic-import-node "^2.3.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-modules-umd@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-umd/-/plugin-transform-modules-umd-7.8.3.tgz#592d578ce06c52f5b98b02f913d653ffe972661a"
integrity sha512-evhTyWhbwbI3/U6dZAnx/ePoV7H6OUG+OjiJFHmhr9FPn0VShjwC2kdxqIuQ/+1P50TMrneGzMeyMTFOjKSnAw==
dependencies:
"@babel/helper-module-transforms" "^7.8.3"
"@babel/helper-plugin-utils" "^7.8.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-named-capturing-groups-regex@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-named-capturing-groups-regex/-/plugin-transform-named-capturing-groups-regex-7.8.3.tgz#a2a72bffa202ac0e2d0506afd0939c5ecbc48c6c"
integrity sha512-f+tF/8UVPU86TrCb06JoPWIdDpTNSGGcAtaD9mLP0aYGA0OS0j7j7DHJR0GTFrUZPUU6loZhbsVZgTh0N+Qdnw==
dependencies:
"@babel/helper-create-regexp-features-plugin" "^7.8.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/plugin-transform-new-target@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-new-target/-/plugin-transform-new-target-7.8.3.tgz#60cc2ae66d85c95ab540eb34babb6434d4c70c43"
integrity sha512-QuSGysibQpyxexRyui2vca+Cmbljo8bcRckgzYV4kRIsHpVeyeC3JDO63pY+xFZ6bWOBn7pfKZTqV4o/ix9sFw==
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/plugin-transform-object-super@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-object-super/-/plugin-transform-object-super-7.8.3.tgz#ebb6a1e7a86ffa96858bd6ac0102d65944261725"
integrity sha512-57FXk+gItG/GejofIyLIgBKTas4+pEU47IXKDBWFTxdPd7F80H8zybyAY7UoblVfBhBGs2EKM+bJUu2+iUYPDQ==
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/helper-replace-supers" "^7.8.3"
"@babel/plugin-transform-parameters@^7.8.4":
version "7.8.4"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-parameters/-/plugin-transform-parameters-7.8.4.tgz#1d5155de0b65db0ccf9971165745d3bb990d77d3"
integrity sha512-IsS3oTxeTsZlE5KqzTbcC2sV0P9pXdec53SU+Yxv7o/6dvGM5AkTotQKhoSffhNgZ/dftsSiOoxy7evCYJXzVA==
dependencies:
"@babel/helper-call-delegate" "^7.8.3"
"@babel/helper-get-function-arity" "^7.8.3"
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/plugin-transform-property-literals@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-property-literals/-/plugin-transform-property-literals-7.8.3.tgz#33194300d8539c1ed28c62ad5087ba3807b98263"
integrity sha512-uGiiXAZMqEoQhRWMK17VospMZh5sXWg+dlh2soffpkAl96KAm+WZuJfa6lcELotSRmooLqg0MWdH6UUq85nmmg==
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/plugin-transform-regenerator@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-regenerator/-/plugin-transform-regenerator-7.8.3.tgz#b31031e8059c07495bf23614c97f3d9698bc6ec8"
integrity sha512-qt/kcur/FxrQrzFR432FGZznkVAjiyFtCOANjkAKwCbt465L6ZCiUQh2oMYGU3Wo8LRFJxNDFwWn106S5wVUNA==
dependencies:
regenerator-transform "^0.14.0"
"@babel/plugin-transform-reserved-words@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-reserved-words/-/plugin-transform-reserved-words-7.8.3.tgz#9a0635ac4e665d29b162837dd3cc50745dfdf1f5"
integrity sha512-mwMxcycN3omKFDjDQUl+8zyMsBfjRFr0Zn/64I41pmjv4NJuqcYlEtezwYtw9TFd9WR1vN5kiM+O0gMZzO6L0A==
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/plugin-transform-shorthand-properties@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-shorthand-properties/-/plugin-transform-shorthand-properties-7.8.3.tgz#28545216e023a832d4d3a1185ed492bcfeac08c8"
integrity sha512-I9DI6Odg0JJwxCHzbzW08ggMdCezoWcuQRz3ptdudgwaHxTjxw5HgdFJmZIkIMlRymL6YiZcped4TTCB0JcC8w==
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/plugin-transform-spread@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-spread/-/plugin-transform-spread-7.8.3.tgz#9c8ffe8170fdfb88b114ecb920b82fb6e95fe5e8"
integrity sha512-CkuTU9mbmAoFOI1tklFWYYbzX5qCIZVXPVy0jpXgGwkplCndQAa58s2jr66fTeQnA64bDox0HL4U56CFYoyC7g==
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/plugin-transform-sticky-regex@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-sticky-regex/-/plugin-transform-sticky-regex-7.8.3.tgz#be7a1290f81dae767475452199e1f76d6175b100"
integrity sha512-9Spq0vGCD5Bb4Z/ZXXSK5wbbLFMG085qd2vhL1JYu1WcQ5bXqZBAYRzU1d+p79GcHs2szYv5pVQCX13QgldaWw==
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/helper-regex" "^7.8.3"
"@babel/plugin-transform-template-literals@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-template-literals/-/plugin-transform-template-literals-7.8.3.tgz#7bfa4732b455ea6a43130adc0ba767ec0e402a80"
integrity sha512-820QBtykIQOLFT8NZOcTRJ1UNuztIELe4p9DCgvj4NK+PwluSJ49we7s9FB1HIGNIYT7wFUJ0ar2QpCDj0escQ==
dependencies:
"@babel/helper-annotate-as-pure" "^7.8.3"
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/plugin-transform-typeof-symbol@^7.8.4":
version "7.8.4"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-typeof-symbol/-/plugin-transform-typeof-symbol-7.8.4.tgz#ede4062315ce0aaf8a657a920858f1a2f35fc412"
integrity sha512-2QKyfjGdvuNfHsb7qnBBlKclbD4CfshH2KvDabiijLMGXPHJXGxtDzwIF7bQP+T0ysw8fYTtxPafgfs/c1Lrqg==
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/plugin-transform-unicode-regex@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-unicode-regex/-/plugin-transform-unicode-regex-7.8.3.tgz#0cef36e3ba73e5c57273effb182f46b91a1ecaad"
integrity sha512-+ufgJjYdmWfSQ+6NS9VGUR2ns8cjJjYbrbi11mZBTaWm+Fui/ncTLFF28Ei1okavY+xkojGr1eJxNsWYeA5aZw==
dependencies:
"@babel/helper-create-regexp-features-plugin" "^7.8.3"
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/preset-env@^7.8.6":
version "7.8.6"
resolved "https://registry.yarnpkg.com/@babel/preset-env/-/preset-env-7.8.6.tgz#2a0773b08589ecba4995fc71b1965e4f531af40b"
integrity sha512-M5u8llV9DIVXBFB/ArIpqJuvXpO+ymxcJ6e8ZAmzeK3sQeBNOD1y+rHvHCGG4TlEmsNpIrdecsHGHT8ZCoOSJg==
dependencies:
"@babel/compat-data" "^7.8.6"
"@babel/helper-compilation-targets" "^7.8.6"
"@babel/helper-module-imports" "^7.8.3"
"@babel/helper-plugin-utils" "^7.8.3"
"@babel/plugin-proposal-async-generator-functions" "^7.8.3"
"@babel/plugin-proposal-dynamic-import" "^7.8.3"
"@babel/plugin-proposal-json-strings" "^7.8.3"
"@babel/plugin-proposal-nullish-coalescing-operator" "^7.8.3"
"@babel/plugin-proposal-object-rest-spread" "^7.8.3"
"@babel/plugin-proposal-optional-catch-binding" "^7.8.3"
"@babel/plugin-proposal-optional-chaining" "^7.8.3"
"@babel/plugin-proposal-unicode-property-regex" "^7.8.3"
"@babel/plugin-syntax-async-generators" "^7.8.0"
"@babel/plugin-syntax-dynamic-import" "^7.8.0"
"@babel/plugin-syntax-json-strings" "^7.8.0"
"@babel/plugin-syntax-nullish-coalescing-operator" "^7.8.0"
"@babel/plugin-syntax-object-rest-spread" "^7.8.0"
"@babel/plugin-syntax-optional-catch-binding" "^7.8.0"
"@babel/plugin-syntax-optional-chaining" "^7.8.0"
"@babel/plugin-syntax-top-level-await" "^7.8.3"
"@babel/plugin-transform-arrow-functions" "^7.8.3"
"@babel/plugin-transform-async-to-generator" "^7.8.3"
"@babel/plugin-transform-block-scoped-functions" "^7.8.3"
"@babel/plugin-transform-block-scoping" "^7.8.3"
"@babel/plugin-transform-classes" "^7.8.6"
"@babel/plugin-transform-computed-properties" "^7.8.3"
"@babel/plugin-transform-destructuring" "^7.8.3"
"@babel/plugin-transform-dotall-regex" "^7.8.3"
"@babel/plugin-transform-duplicate-keys" "^7.8.3"
"@babel/plugin-transform-exponentiation-operator" "^7.8.3"
"@babel/plugin-transform-for-of" "^7.8.6"
"@babel/plugin-transform-function-name" "^7.8.3"
"@babel/plugin-transform-literals" "^7.8.3"
"@babel/plugin-transform-member-expression-literals" "^7.8.3"
"@babel/plugin-transform-modules-amd" "^7.8.3"
"@babel/plugin-transform-modules-commonjs" "^7.8.3"
"@babel/plugin-transform-modules-systemjs" "^7.8.3"
"@babel/plugin-transform-modules-umd" "^7.8.3"
"@babel/plugin-transform-named-capturing-groups-regex" "^7.8.3"
"@babel/plugin-transform-new-target" "^7.8.3"
"@babel/plugin-transform-object-super" "^7.8.3"
"@babel/plugin-transform-parameters" "^7.8.4"
"@babel/plugin-transform-property-literals" "^7.8.3"
"@babel/plugin-transform-regenerator" "^7.8.3"
"@babel/plugin-transform-reserved-words" "^7.8.3"
"@babel/plugin-transform-shorthand-properties" "^7.8.3"
"@babel/plugin-transform-spread" "^7.8.3"
"@babel/plugin-transform-sticky-regex" "^7.8.3"
"@babel/plugin-transform-template-literals" "^7.8.3"
"@babel/plugin-transform-typeof-symbol" "^7.8.4"
"@babel/plugin-transform-unicode-regex" "^7.8.3"
"@babel/types" "^7.8.6"
browserslist "^4.8.5"
core-js-compat "^3.6.2"
invariant "^2.2.2"
levenary "^1.1.1"
semver "^5.5.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/template@^7.8.3", "@babel/template@^7.8.6":
version "7.8.6"
resolved "https://registry.yarnpkg.com/@babel/template/-/template-7.8.6.tgz#86b22af15f828dfb086474f964dcc3e39c43ce2b"
integrity sha512-zbMsPMy/v0PWFZEhQJ66bqjhH+z0JgMoBWuikXybgG3Gkd/3t5oQ1Rw2WQhnSrsOmsKXnZOx15tkC4qON/+JPg==
dependencies:
"@babel/code-frame" "^7.8.3"
"@babel/parser" "^7.8.6"
"@babel/types" "^7.8.6"
"@babel/traverse@^7.8.3", "@babel/traverse@^7.8.4", "@babel/traverse@^7.8.6":
version "7.8.6"
resolved "https://registry.yarnpkg.com/@babel/traverse/-/traverse-7.8.6.tgz#acfe0c64e1cd991b3e32eae813a6eb564954b5ff"
integrity sha512-2B8l0db/DPi8iinITKuo7cbPznLCEk0kCxDoB9/N6gGNg/gxOXiR/IcymAFPiBwk5w6TtQ27w4wpElgp9btR9A==
dependencies:
"@babel/code-frame" "^7.8.3"
"@babel/generator" "^7.8.6"
"@babel/helper-function-name" "^7.8.3"
"@babel/helper-split-export-declaration" "^7.8.3"
"@babel/parser" "^7.8.6"
"@babel/types" "^7.8.6"
debug "^4.1.0"
globals "^11.1.0"
lodash "^4.17.13"
"@babel/types@^7.4", "@babel/types@^7.8.3", "@babel/types@^7.8.6":
version "7.8.6"
resolved "https://registry.yarnpkg.com/@babel/types/-/types-7.8.6.tgz#629ecc33c2557fcde7126e58053127afdb3e6d01"
integrity sha512-wqz7pgWMIrht3gquyEFPVXeXCti72Rm8ep9b5tQKz9Yg9LzJA3HxosF1SB3Kc81KD1A3XBkkVYtJvCKS2Z/QrA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
esutils "^2.0.2"
lodash "^4.17.13"
to-fast-properties "^2.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@types/anymatch@*":
version "1.3.1"
resolved "https://registry.yarnpkg.com/@types/anymatch/-/anymatch-1.3.1.tgz#336badc1beecb9dacc38bea2cf32adf627a8421a"
integrity sha512-/+CRPXpBDpo2RK9C68N3b2cOvO0Cf5B9aPijHsoDQTHivnGSObdOF2BRQOYjojWTDy6nQvMjmqRXIxH55VjxxA==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@types/color-name@^1.1.1":
version "1.1.1"
resolved "https://registry.yarnpkg.com/@types/color-name/-/color-name-1.1.1.tgz#1c1261bbeaa10a8055bbc5d8ab84b7b2afc846a0"
integrity sha512-rr+OQyAjxze7GgWrSaJwydHStIhHq2lvY3BOC2Mj7KnzI7XK0Uw1TOOdI9lDoajEbSWLiYgoo4f1R51erQfhPQ==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@types/events@*":
version "3.0.0"
resolved "https://registry.yarnpkg.com/@types/events/-/events-3.0.0.tgz#2862f3f58a9a7f7c3e78d79f130dd4d71c25c2a7"
integrity sha512-EaObqwIvayI5a8dCzhFrjKzVwKLxjoG9T6Ppd5CEo07LRKfQ8Yokw54r5+Wq7FaBQ+yXRvQAYPrHwya1/UFt9g==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@types/glob@^7.1.1":
version "7.1.1"
resolved "https://registry.yarnpkg.com/@types/glob/-/glob-7.1.1.tgz#aa59a1c6e3fbc421e07ccd31a944c30eba521575"
integrity sha512-1Bh06cbWJUHMC97acuD6UMG29nMt0Aqz1vF3guLfG+kHHJhy3AyohZFFxYk2f7Q1SQIrNwvncxAE0N/9s70F2w==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@types/events" "*"
"@types/minimatch" "*"
"@types/node" "*"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@types/minimatch@*":
version "3.0.3"
resolved "https://registry.yarnpkg.com/@types/minimatch/-/minimatch-3.0.3.tgz#3dca0e3f33b200fc7d1139c0cd96c1268cadfd9d"
integrity sha512-tHq6qdbT9U1IRSGf14CL0pUlULksvY9OZ+5eEgl1N7t+OA3tGvNpxJCzuKQlsNgCVwbAs670L1vcVQi8j9HjnA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@types/node@*":
version "13.7.7"
resolved "https://registry.yarnpkg.com/@types/node/-/node-13.7.7.tgz#1628e6461ba8cc9b53196dfeaeec7b07fa6eea99"
integrity sha512-Uo4chgKbnPNlxQwoFmYIwctkQVkMMmsAoGGU4JKwLuvBefF0pCq4FybNSnfkfRCpC7ZW7kttcC/TrRtAJsvGtg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@types/source-list-map@*":
version "0.1.2"
resolved "https://registry.yarnpkg.com/@types/source-list-map/-/source-list-map-0.1.2.tgz#0078836063ffaf17412349bba364087e0ac02ec9"
integrity sha512-K5K+yml8LTo9bWJI/rECfIPrGgxdpeNbj+d53lwN4QjW1MCwlkhUms+gtdzigTeUyBr09+u8BwOIY3MXvHdcsA==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@types/tapable@*":
version "1.0.5"
resolved "https://registry.yarnpkg.com/@types/tapable/-/tapable-1.0.5.tgz#9adbc12950582aa65ead76bffdf39fe0c27a3c02"
integrity sha512-/gG2M/Imw7cQFp8PGvz/SwocNrmKFjFsm5Pb8HdbHkZ1K8pmuPzOX4VeVoiEecFCVf4CsN1r3/BRvx+6sNqwtQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@types/uglify-js@*":
version "3.0.4"
resolved "https://registry.yarnpkg.com/@types/uglify-js/-/uglify-js-3.0.4.tgz#96beae23df6f561862a830b4288a49e86baac082"
integrity sha512-SudIN9TRJ+v8g5pTG8RRCqfqTMNqgWCKKd3vtynhGzkIIjxaicNAMuY5TRadJ6tzDu3Dotf3ngaMILtmOdmWEQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
source-map "^0.6.1"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@types/webpack-sources@*":
version "0.1.6"
resolved "https://registry.yarnpkg.com/@types/webpack-sources/-/webpack-sources-0.1.6.tgz#3d21dfc2ec0ad0c77758e79362426a9ba7d7cbcb"
integrity sha512-FtAWR7wR5ocJ9+nP137DV81tveD/ZgB1sadnJ/axUGM3BUVfRPx8oQNMtv3JNfTeHx3VP7cXiyfR/jmtEsVHsQ==
dependencies:
"@types/node" "*"
"@types/source-list-map" "*"
source-map "^0.6.1"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@types/webpack@^4.4.31":
version "4.41.7"
resolved "https://registry.yarnpkg.com/@types/webpack/-/webpack-4.41.7.tgz#22be27dbd4362b01c3954ca9b021dbc9328d9511"
integrity sha512-OQG9viYwO0V1NaNV7d0n79V+n6mjOV30CwgFPIfTzwmk8DHbt+C4f2aBGdCYbo3yFyYD6sjXfqqOjwkl1j+ulA==
dependencies:
"@types/anymatch" "*"
"@types/node" "*"
"@types/tapable" "*"
"@types/uglify-js" "*"
"@types/webpack-sources" "*"
source-map "^0.6.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/ast@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/ast/-/ast-1.8.5.tgz#51b1c5fe6576a34953bf4b253df9f0d490d9e359"
integrity sha512-aJMfngIZ65+t71C3y2nBBg5FFG0Okt9m0XEgWZ7Ywgn1oMAT8cNwx00Uv1cQyHtidq0Xn94R4TAywO+LCQ+ZAQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/helper-module-context" "1.8.5"
"@webassemblyjs/helper-wasm-bytecode" "1.8.5"
"@webassemblyjs/wast-parser" "1.8.5"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/floating-point-hex-parser@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/floating-point-hex-parser/-/floating-point-hex-parser-1.8.5.tgz#1ba926a2923613edce496fd5b02e8ce8a5f49721"
integrity sha512-9p+79WHru1oqBh9ewP9zW95E3XAo+90oth7S5Re3eQnECGq59ly1Ri5tsIipKGpiStHsUYmY3zMLqtk3gTcOtQ==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/helper-api-error@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-api-error/-/helper-api-error-1.8.5.tgz#c49dad22f645227c5edb610bdb9697f1aab721f7"
integrity sha512-Za/tnzsvnqdaSPOUXHyKJ2XI7PDX64kWtURyGiJJZKVEdFOsdKUCPTNEVFZq3zJ2R0G5wc2PZ5gvdTRFgm81zA==
"@webassemblyjs/helper-buffer@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-buffer/-/helper-buffer-1.8.5.tgz#fea93e429863dd5e4338555f42292385a653f204"
integrity sha512-Ri2R8nOS0U6G49Q86goFIPNgjyl6+oE1abW1pS84BuhP1Qcr5JqMwRFT3Ah3ADDDYGEgGs1iyb1DGX+kAi/c/Q==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/helper-code-frame@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-code-frame/-/helper-code-frame-1.8.5.tgz#9a740ff48e3faa3022b1dff54423df9aa293c25e"
integrity sha512-VQAadSubZIhNpH46IR3yWO4kZZjMxN1opDrzePLdVKAZ+DFjkGD/rf4v1jap744uPVU6yjL/smZbRIIJTOUnKQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/wast-printer" "1.8.5"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/helper-fsm@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-fsm/-/helper-fsm-1.8.5.tgz#ba0b7d3b3f7e4733da6059c9332275d860702452"
integrity sha512-kRuX/saORcg8se/ft6Q2UbRpZwP4y7YrWsLXPbbmtepKr22i8Z4O3V5QE9DbZK908dh5Xya4Un57SDIKwB9eow==
"@webassemblyjs/helper-module-context@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-module-context/-/helper-module-context-1.8.5.tgz#def4b9927b0101dc8cbbd8d1edb5b7b9c82eb245"
integrity sha512-/O1B236mN7UNEU4t9X7Pj38i4VoU8CcMHyy3l2cV/kIF4U5KoHXDVqcDuOs1ltkac90IM4vZdHc52t1x8Yfs3g==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/ast" "1.8.5"
mamacro "^0.0.3"
"@webassemblyjs/helper-wasm-bytecode@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-wasm-bytecode/-/helper-wasm-bytecode-1.8.5.tgz#537a750eddf5c1e932f3744206551c91c1b93e61"
integrity sha512-Cu4YMYG3Ddl72CbmpjU/wbP6SACcOPVbHN1dI4VJNJVgFwaKf1ppeFJrwydOG3NDHxVGuCfPlLZNyEdIYlQ6QQ==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/helper-wasm-section@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-wasm-section/-/helper-wasm-section-1.8.5.tgz#74ca6a6bcbe19e50a3b6b462847e69503e6bfcbf"
integrity sha512-VV083zwR+VTrIWWtgIUpqfvVdK4ff38loRmrdDBgBT8ADXYsEZ5mPQ4Nde90N3UYatHdYoDIFb7oHzMncI02tA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/ast" "1.8.5"
"@webassemblyjs/helper-buffer" "1.8.5"
"@webassemblyjs/helper-wasm-bytecode" "1.8.5"
"@webassemblyjs/wasm-gen" "1.8.5"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/ieee754@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/ieee754/-/ieee754-1.8.5.tgz#712329dbef240f36bf57bd2f7b8fb9bf4154421e"
integrity sha512-aaCvQYrvKbY/n6wKHb/ylAJr27GglahUO89CcGXMItrOBqRarUMxWLJgxm9PJNuKULwN5n1csT9bYoMeZOGF3g==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@xtuc/ieee754" "^1.2.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/leb128@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/leb128/-/leb128-1.8.5.tgz#044edeb34ea679f3e04cd4fd9824d5e35767ae10"
integrity sha512-plYUuUwleLIziknvlP8VpTgO4kqNaH57Y3JnNa6DLpu/sGcP6hbVdfdX5aHAV716pQBKrfuU26BJK29qY37J7A==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@xtuc/long" "4.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/utf8@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/utf8/-/utf8-1.8.5.tgz#a8bf3b5d8ffe986c7c1e373ccbdc2a0915f0cedc"
integrity sha512-U7zgftmQriw37tfD934UNInokz6yTmn29inT2cAetAsaU9YeVCveWEwhKL1Mg4yS7q//NGdzy79nlXh3bT8Kjw==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/wasm-edit@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/wasm-edit/-/wasm-edit-1.8.5.tgz#962da12aa5acc1c131c81c4232991c82ce56e01a"
integrity sha512-A41EMy8MWw5yvqj7MQzkDjU29K7UJq1VrX2vWLzfpRHt3ISftOXqrtojn7nlPsZ9Ijhp5NwuODuycSvfAO/26Q==
dependencies:
"@webassemblyjs/ast" "1.8.5"
"@webassemblyjs/helper-buffer" "1.8.5"
"@webassemblyjs/helper-wasm-bytecode" "1.8.5"
"@webassemblyjs/helper-wasm-section" "1.8.5"
"@webassemblyjs/wasm-gen" "1.8.5"
"@webassemblyjs/wasm-opt" "1.8.5"
"@webassemblyjs/wasm-parser" "1.8.5"
"@webassemblyjs/wast-printer" "1.8.5"
"@webassemblyjs/wasm-gen@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/wasm-gen/-/wasm-gen-1.8.5.tgz#54840766c2c1002eb64ed1abe720aded714f98bc"
integrity sha512-BCZBT0LURC0CXDzj5FXSc2FPTsxwp3nWcqXQdOZE4U7h7i8FqtFK5Egia6f9raQLpEKT1VL7zr4r3+QX6zArWg==
dependencies:
"@webassemblyjs/ast" "1.8.5"
"@webassemblyjs/helper-wasm-bytecode" "1.8.5"
"@webassemblyjs/ieee754" "1.8.5"
"@webassemblyjs/leb128" "1.8.5"
"@webassemblyjs/utf8" "1.8.5"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/wasm-opt@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/wasm-opt/-/wasm-opt-1.8.5.tgz#b24d9f6ba50394af1349f510afa8ffcb8a63d264"
integrity sha512-HKo2mO/Uh9A6ojzu7cjslGaHaUU14LdLbGEKqTR7PBKwT6LdPtLLh9fPY33rmr5wcOMrsWDbbdCHq4hQUdd37Q==
dependencies:
"@webassemblyjs/ast" "1.8.5"
"@webassemblyjs/helper-buffer" "1.8.5"
"@webassemblyjs/wasm-gen" "1.8.5"
"@webassemblyjs/wasm-parser" "1.8.5"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/wasm-parser@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/wasm-parser/-/wasm-parser-1.8.5.tgz#21576f0ec88b91427357b8536383668ef7c66b8d"
integrity sha512-pi0SYE9T6tfcMkthwcgCpL0cM9nRYr6/6fjgDtL6q/ZqKHdMWvxitRi5JcZ7RI4SNJJYnYNaWy5UUrHQy998lw==
dependencies:
"@webassemblyjs/ast" "1.8.5"
"@webassemblyjs/helper-api-error" "1.8.5"
"@webassemblyjs/helper-wasm-bytecode" "1.8.5"
"@webassemblyjs/ieee754" "1.8.5"
"@webassemblyjs/leb128" "1.8.5"
"@webassemblyjs/utf8" "1.8.5"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/wast-parser@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/wast-parser/-/wast-parser-1.8.5.tgz#e10eecd542d0e7bd394f6827c49f3df6d4eefb8c"
integrity sha512-daXC1FyKWHF1i11obK086QRlsMsY4+tIOKgBqI1lxAnkp9xe9YMcgOxm9kLe+ttjs5aWV2KKE1TWJCN57/Btsg==
dependencies:
"@webassemblyjs/ast" "1.8.5"
"@webassemblyjs/floating-point-hex-parser" "1.8.5"
"@webassemblyjs/helper-api-error" "1.8.5"
"@webassemblyjs/helper-code-frame" "1.8.5"
"@webassemblyjs/helper-fsm" "1.8.5"
"@xtuc/long" "4.2.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@webassemblyjs/wast-printer@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/wast-printer/-/wast-printer-1.8.5.tgz#114bbc481fd10ca0e23b3560fa812748b0bae5bc"
integrity sha512-w0U0pD4EhlnvRyeJzBqaVSJAo9w/ce7/WPogeXLzGkO6hzhr4GnQIZ4W4uUt5b9ooAaXPtnXlj0gzsXEOUNYMg==
dependencies:
"@webassemblyjs/ast" "1.8.5"
"@webassemblyjs/wast-parser" "1.8.5"
"@xtuc/long" "4.2.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@xtuc/ieee754@^1.2.0":
version "1.2.0"
resolved "https://registry.yarnpkg.com/@xtuc/ieee754/-/ieee754-1.2.0.tgz#eef014a3145ae477a1cbc00cd1e552336dceb790"
integrity sha512-DX8nKgqcGwsc0eJSqYt5lwP4DH5FlHnmuWWBRy7X0NcaGR0ZtuyeESgMwTYVEtxmsNGY+qit4QYT/MIYTOTPeA==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@xtuc/long@4.2.2":
version "4.2.2"
resolved "https://registry.yarnpkg.com/@xtuc/long/-/long-4.2.2.tgz#d291c6a4e97989b5c61d9acf396ae4fe133a718d"
integrity sha512-NuHqBY1PB/D8xU6s/thBgOAiAP7HOYDQ32+BFZILJ8ivkUkAHQnWfn6WhL79Owj1qmUnoN/YPhktdIoucipkAQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
accepts@~1.3.4, accepts@~1.3.5, accepts@~1.3.7:
version "1.3.7"
resolved "https://registry.yarnpkg.com/accepts/-/accepts-1.3.7.tgz#531bc726517a3b2b41f850021c6cc15eaab507cd"
integrity sha512-Il80Qs2WjYlJIBNzNkK6KYqlVMTbZLXgHx2oT0pU/fjRHyEp+PEfEPY0R3WCwAGVOtauxh1hOxNgIf5bv7dQpA==
dependencies:
mime-types "~2.1.24"
negotiator "0.6.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
acorn-jsx@^5.1.0:
version "5.2.0"
resolved "https://registry.yarnpkg.com/acorn-jsx/-/acorn-jsx-5.2.0.tgz#4c66069173d6fdd68ed85239fc256226182b2ebe"
integrity sha512-HiUX/+K2YpkpJ+SzBffkM/AQ2YE03S0U1kjTLVpoJdhZMOWy8qvXVN9JdLqv2QsaQ6MPYQIuNmwD8zOiYUofLQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
acorn@^6.2.1:
version "6.4.0"
resolved "https://registry.yarnpkg.com/acorn/-/acorn-6.4.0.tgz#b659d2ffbafa24baf5db1cdbb2c94a983ecd2784"
integrity sha512-gac8OEcQ2Li1dxIEWGZzsp2BitJxwkwcOm0zHAJLcPJaVvm58FRnk6RkuLRpU1EujipU2ZFODv2P9DLMfnV8mw==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
acorn@^7.1.0:
version "7.1.1"
resolved "https://registry.yarnpkg.com/acorn/-/acorn-7.1.1.tgz#e35668de0b402f359de515c5482a1ab9f89a69bf"
integrity sha512-add7dgA5ppRPxCFJoAGfMDi7PIBXq1RtGo7BhbLaxwrXPOmw8gq48Y9ozT01hUKy9byMjlR20EJhu5zlkErEkg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
aggregate-error@^3.0.0:
version "3.0.1"
resolved "https://registry.yarnpkg.com/aggregate-error/-/aggregate-error-3.0.1.tgz#db2fe7246e536f40d9b5442a39e117d7dd6a24e0"
integrity sha512-quoaXsZ9/BLNae5yiNoUz+Nhkwz83GhWwtYFglcjEQB2NDHCIpApbqXxIFnm4Pq/Nvhrsq5sYJFyohrrxnTGAA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
clean-stack "^2.0.0"
indent-string "^4.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ajv-errors@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/ajv-errors/-/ajv-errors-1.0.1.tgz#f35986aceb91afadec4102fbd85014950cefa64d"
integrity sha512-DCRfO/4nQ+89p/RK43i8Ezd41EqdGIU4ld7nGF8OQ14oc/we5rEntLCUa7+jrn3nn83BosfwZA0wb4pon2o8iQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ajv-keywords@^3.1.0, ajv-keywords@^3.4.1:
version "3.4.1"
resolved "https://registry.yarnpkg.com/ajv-keywords/-/ajv-keywords-3.4.1.tgz#ef916e271c64ac12171fd8384eaae6b2345854da"
integrity sha512-RO1ibKvd27e6FEShVFfPALuHI3WjSVNeK5FIsmme/LYRNxjKuNj+Dt7bucLa6NdSv3JcVTyMlm9kGR84z1XpaQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ajv@^6.1.0, ajv@^6.10.0, ajv@^6.10.2:
version "6.12.0"
resolved "https://registry.yarnpkg.com/ajv/-/ajv-6.12.0.tgz#06d60b96d87b8454a5adaba86e7854da629db4b7"
integrity sha512-D6gFiFA0RRLyUbvijN74DWAjXSFxWKaWP7mldxkVhyhAV3+SWA9HEJPHQ2c9soIeTFJqcSdFDGFgdqs1iUU2Hw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05: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"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ansi-colors@^3.0.0:
version "3.2.4"
resolved "https://registry.yarnpkg.com/ansi-colors/-/ansi-colors-3.2.4.tgz#e3a3da4bfbae6c86a9c285625de124a234026fbf"
integrity sha512-hHUXGagefjN2iRrID63xckIvotOXOojhQKWIPUZ4mNUZ9nLZW+7FMNoE1lOkEhNWYsx/7ysGIuJYCiMAA9FnrA==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ansi-escapes@^4.2.1:
version "4.3.1"
resolved "https://registry.yarnpkg.com/ansi-escapes/-/ansi-escapes-4.3.1.tgz#a5c47cc43181f1f38ffd7076837700d395522a61"
integrity sha512-JWF7ocqNrp8u9oqpgV+wH5ftbt+cfvv+PTjOvKLT3AdYly/LmORARfEVT1iyjwN+4MqE5UmVKoAdIBqeoCHgLA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
type-fest "^0.11.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ansi-html@0.0.7:
version "0.0.7"
resolved "https://registry.yarnpkg.com/ansi-html/-/ansi-html-0.0.7.tgz#813584021962a9e9e6fd039f940d12f56ca7859e"
integrity sha1-gTWEAhliqenm/QOflA0S9WynhZ4=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ansi-regex@^2.0.0:
version "2.1.1"
resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-2.1.1.tgz#c3b33ab5ee360d86e0e628f0468ae7ef27d654df"
integrity sha1-w7M6te42DYbg5ijwRorn7yfWVN8=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ansi-regex@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-3.0.0.tgz#ed0317c322064f79466c02966bddb605ab37d998"
integrity sha1-7QMXwyIGT3lGbAKWa922Bas32Zg=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ansi-regex@^4.1.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-4.1.0.tgz#8b9f8f08cf1acb843756a839ca8c7e3168c51997"
integrity sha512-1apePfXM1UOSqw0o9IiFAovVz9M5S1Dg+4TrDwfMewQ6p/rmMueb7tWZjQ1rx4Loy1ArBggoqGpfqqdI4rondg==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ansi-regex@^5.0.0:
version "5.0.0"
resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-5.0.0.tgz#388539f55179bf39339c81af30a654d69f87cb75"
integrity sha512-bY6fj56OUQ0hU1KjFNDQuJFezqKdrAyFdIevADiqrWHwSlbmBNMHp5ak2f40Pm8JTFyM2mqxkG6ngkHO11f/lg==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ansi-styles@^3.2.0, ansi-styles@^3.2.1:
version "3.2.1"
resolved "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-3.2.1.tgz#41fbb20243e50b12be0f04b8dedbf07520ce841d"
integrity sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
color-convert "^1.9.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ansi-styles@^4.1.0:
version "4.2.1"
resolved "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-4.2.1.tgz#90ae75c424d008d2624c5bf29ead3177ebfcf359"
integrity sha512-9VGjrMsG1vePxcSweQsN20KY/c4zN0h9fLjqAbwbPfahM3t+NL+M9HC8xeXG2I8pX5NoamTGNuomEUFI7fcUjA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@types/color-name" "^1.1.1"
color-convert "^2.0.1"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
anymatch@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/anymatch/-/anymatch-2.0.0.tgz#bcb24b4f37934d9aa7ac17b4adaf89e7c76ef2eb"
integrity sha512-5teOsQWABXHHBFP9y3skS5P3d/WfWXpv3FUpy+LorMrNYaT9pI4oLMQX7jzQ2KklNpGpWHzdCXTDT2Y3XGlZBw==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
micromatch "^3.1.4"
normalize-path "^2.1.1"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
aproba@^1.1.1:
version "1.2.0"
resolved "https://registry.yarnpkg.com/aproba/-/aproba-1.2.0.tgz#6802e6264efd18c790a1b0d517f0f2627bf2c94a"
integrity sha512-Y9J6ZjXtoYh8RnXVCMOU/ttDmk1aBjunq9vO0ta5x85WDQiQfUF9sIPBITdbiiIVcBo03Hi3jMxigBtsddlXRw==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
argparse@^1.0.7:
version "1.0.10"
resolved "https://registry.yarnpkg.com/argparse/-/argparse-1.0.10.tgz#bcd6791ea5ae09725e17e5ad988134cd40b3d911"
integrity sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
sprintf-js "~1.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
arr-diff@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/arr-diff/-/arr-diff-4.0.0.tgz#d6461074febfec71e7e15235761a329a5dc7c520"
integrity sha1-1kYQdP6/7HHn4VI1dhoyml3HxSA=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
arr-flatten@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/arr-flatten/-/arr-flatten-1.1.0.tgz#36048bbff4e7b47e136644316c99669ea5ae91f1"
integrity sha512-L3hKV5R/p5o81R7O02IGnwpDmkp6E982XhtbuwSe3O4qOtMMMtodicASA1Cny2U+aCXcNpml+m4dPsvsJ3jatg==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
arr-union@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/arr-union/-/arr-union-3.1.0.tgz#e39b09aea9def866a8f206e288af63919bae39c4"
integrity sha1-45sJrqne+Gao8gbiiK9jkZuuOcQ=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
array-flatten@1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/array-flatten/-/array-flatten-1.1.1.tgz#9a5f699051b1e7073328f2a008968b64ea2955d2"
integrity sha1-ml9pkFGx5wczKPKgCJaLZOopVdI=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
array-flatten@^2.1.0:
version "2.1.2"
resolved "https://registry.yarnpkg.com/array-flatten/-/array-flatten-2.1.2.tgz#24ef80a28c1a893617e2149b0c6d0d788293b099"
integrity sha512-hNfzcOV8W4NdualtqBFPyVO+54DSJuZGY9qT4pRroB6S9e3iiido2ISIC5h9R2sPJ8H3FHCIiEnsv1lPXO3KtQ==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
array-union@^1.0.1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/array-union/-/array-union-1.0.2.tgz#9a34410e4f4e3da23dea375be5be70f24778ec39"
integrity sha1-mjRBDk9OPaI96jdb5b5w8kd47Dk=
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
array-uniq "^1.0.1"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
array-uniq@^1.0.1:
version "1.0.3"
resolved "https://registry.yarnpkg.com/array-uniq/-/array-uniq-1.0.3.tgz#af6ac877a25cc7f74e058894753858dfdb24fdb6"
integrity sha1-r2rId6Jcx/dOBYiUdThY39sk/bY=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
array-unique@^0.3.2:
version "0.3.2"
resolved "https://registry.yarnpkg.com/array-unique/-/array-unique-0.3.2.tgz#a894b75d4bc4f6cd679ef3244a9fd8f46ae2d428"
integrity sha1-qJS3XUvE9s1nnvMkSp/Y9Gri1Cg=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
asn1.js@^4.0.0:
version "4.10.1"
resolved "https://registry.yarnpkg.com/asn1.js/-/asn1.js-4.10.1.tgz#b9c2bf5805f1e64aadeed6df3a2bfafb5a73f5a0"
integrity sha512-p32cOF5q0Zqs9uBiONKYLm6BClCoBCM5O9JfeUSlnQLBTxYdTK+pW+nXflm8UkKd2UYlEbYz5qEi0JuZR9ckSw==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
bn.js "^4.0.0"
inherits "^2.0.1"
minimalistic-assert "^1.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
assert@^1.1.1:
version "1.5.0"
resolved "https://registry.yarnpkg.com/assert/-/assert-1.5.0.tgz#55c109aaf6e0aefdb3dc4b71240c70bf574b18eb"
integrity sha512-EDsgawzwoun2CZkCgtxJbv392v4nbk9XDD06zI+kQYoBM/3RBWLlEyJARDOmhAAosBjWACEkKL6S+lIZtcAubA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
object-assign "^4.1.1"
util "0.10.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
assign-symbols@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/assign-symbols/-/assign-symbols-1.0.0.tgz#59667f41fadd4f20ccbc2bb96b8d4f7f78ec0367"
integrity sha1-WWZ/QfrdTyDMvCu5a41Pf3jsA2c=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ast-types@0.9.6:
version "0.9.6"
resolved "https://registry.yarnpkg.com/ast-types/-/ast-types-0.9.6.tgz#102c9e9e9005d3e7e3829bf0c4fa24ee862ee9b9"
integrity sha1-ECyenpAF0+fjgpvwxPok7oYu6bk=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
astral-regex@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/astral-regex/-/astral-regex-1.0.0.tgz#6c8c3fb827dd43ee3918f27b82782ab7658a6fd9"
integrity sha512-+Ryf6g3BKoRc7jfp7ad8tM4TtMiaWvbF/1/sQcZPkkS7ag3D5nMBCe2UfOTONtAkaG0tO0ij3C5Lwmf1EiyjHg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
async-each@^1.0.1:
version "1.0.3"
resolved "https://registry.yarnpkg.com/async-each/-/async-each-1.0.3.tgz#b727dbf87d7651602f06f4d4ac387f47d91b0cbf"
integrity sha512-z/WhQ5FPySLdvREByI2vZiTWwCnF0moMJ1hK9YQwDTHKh6I7/uSckMetoRGb5UBZPC1z0jlw+n/XCgjeH7y1AQ==
A little more UI refactor, cleanup, eslint more strict (#54) * A little more UI refactor, cleanup, eslint more strict * Split out imports for jQuery components and put them where needed. * No longer do all of it in application module. * Prepares better for code splitting. * Split out video player dialog * Simplifies jquery-ui dependencies for code splitting * Simplifies code * Configure to generate more, but smaller bundles. * Setup some more strict eslint settings * Fix css to import rather than require * Change settings to correctly support tree shaking in production build Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Remove “old” code from TimeFormatter * Accidentally left behind due to overlapping PRs Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-26 01:18:56 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
async-limiter@~1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/async-limiter/-/async-limiter-1.0.1.tgz#dd379e94f0db8310b08291f9d64c3209766617fd"
integrity sha512-csOlWGAcRFJaI6m+F2WKdnMKr4HhdhFVBk0H/QbJFMCr+uO2kwohwXQPxw/9OCxp05r5ghVBFSyioixx3gfkNQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
async@^2.6.2:
version "2.6.3"
resolved "https://registry.yarnpkg.com/async/-/async-2.6.3.tgz#d72625e2344a3656e3a3ad4fa749fa83299d82ff"
integrity sha512-zflvls11DCy+dQWzTW2dzuilv8Z5X/pjfmZOWba6TNIVDm+2UDaJmXSOXlasHKfNBs8oo3M0aT50fDEWfKZjXg==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
lodash "^4.17.14"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
atob@^2.1.2:
version "2.1.2"
resolved "https://registry.yarnpkg.com/atob/-/atob-2.1.2.tgz#6d9517eb9e030d2436666651e86bd9f6f13533c9"
integrity sha512-Wm6ukoaOGJi/73p/cl2GvLjTI5JM1k/O14isD73YML8StrH/7/lRFgmg8nICZgD3bZZvjwCGxtMOD3wWNAu8cg==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
babel-loader@^8.0.6:
version "8.0.6"
resolved "https://registry.yarnpkg.com/babel-loader/-/babel-loader-8.0.6.tgz#e33bdb6f362b03f4bb141a0c21ab87c501b70dfb"
integrity sha512-4BmWKtBOBm13uoUwd08UwjZlaw3O9GWf456R9j+5YykFZ6LUIjIKLc0zEZf+hauxPOJs96C8k6FvYD09vWzhYw==
dependencies:
find-cache-dir "^2.0.0"
loader-utils "^1.0.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
mkdirp "^0.5.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
pify "^4.0.1"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
babel-plugin-dynamic-import-node@^2.3.0:
version "2.3.0"
resolved "https://registry.yarnpkg.com/babel-plugin-dynamic-import-node/-/babel-plugin-dynamic-import-node-2.3.0.tgz#f00f507bdaa3c3e3ff6e7e5e98d90a7acab96f7f"
integrity sha512-o6qFkpeQEBxcqt0XYlWzAVxNCSCZdUgcR8IRlhD/8DylxjjO4foPcvTW0GGKa/cVt3rvxZ7o5ippJ+/0nvLhlQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
object.assign "^4.1.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
babel-plugin-transform-imports@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/babel-plugin-transform-imports/-/babel-plugin-transform-imports-2.0.0.tgz#9e5f49f751a9d34ba8f4bb988c7e48ed2419c6b6"
integrity sha512-65ewumYJ85QiXdcB/jmiU0y0jg6eL6CdnDqQAqQ8JMOKh1E52VPG3NJzbVKWcgovUR5GBH8IWpCXQ7I8Q3wjgw==
dependencies:
"@babel/types" "^7.4"
is-valid-path "^0.1.1"
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
balanced-match@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/balanced-match/-/balanced-match-1.0.0.tgz#89b4d199ab2bee49de164ea02b89ce462d71b767"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-ibTRmasr7kneFk6gK4nORi1xt2c=
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
base64-js@^1.0.2:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.3.1"
resolved "https://registry.yarnpkg.com/base64-js/-/base64-js-1.3.1.tgz#58ece8cb75dd07e71ed08c736abc5fac4dbf8df1"
integrity sha512-mLQ4i2QO1ytvGWFWmcngKO//JXAQueZvwEKtjgQFM4jIK0kU+ytMfplL8j+n5mspOfjHwoAg+9yhb7BwAHm36g==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
base@^0.11.1:
version "0.11.2"
resolved "https://registry.yarnpkg.com/base/-/base-0.11.2.tgz#7bde5ced145b6d551a90db87f83c558b4eb48a8f"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-5T6P4xPgpp0YDFvSWwEZ4NoE3aM4QBQXDzmVbraCkFj8zHM+mba8SyqB5DbZWyR7mYHo6Y7BdQo3MoA4m0TeQg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
cache-base "^1.0.1"
class-utils "^0.3.5"
component-emitter "^1.2.1"
define-property "^1.0.0"
isobject "^3.0.1"
mixin-deep "^1.2.0"
pascalcase "^0.1.1"
batch@0.6.1:
version "0.6.1"
resolved "https://registry.yarnpkg.com/batch/-/batch-0.6.1.tgz#dc34314f4e679318093fc760272525f94bf25c16"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-3DQxT05nkxgJP8dgJyUl+UvyXBY=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
big.js@^3.1.3:
version "3.2.0"
resolved "https://registry.yarnpkg.com/big.js/-/big.js-3.2.0.tgz#a5fc298b81b9e0dca2e458824784b65c52ba588e"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-+hN/Zh2D08Mx65pZ/4g5bsmNiZUuChDiQfTUQ7qJr4/kuopCr88xZsAXv6mBoZEsUI4OuGHlX59qE94K2mMW8Q==
big.js@^5.2.2:
version "5.2.2"
resolved "https://registry.yarnpkg.com/big.js/-/big.js-5.2.2.tgz#65f0af382f578bcdc742bd9c281e9cb2d7768328"
integrity sha512-vyL2OymJxmarO8gxMr0mhChsO9QGwhynfuu4+MHTAW6czfq9humCB7rKpUjDd9YUiDPU4mzpyupFSvOClAwbmQ==
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
binary-extensions@^1.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.13.1"
resolved "https://registry.yarnpkg.com/binary-extensions/-/binary-extensions-1.13.1.tgz#598afe54755b2868a5330d2aff9d4ebb53209b65"
integrity sha512-Un7MIEDdUC5gNpcGDV97op1Ywk748MpHcFTHoYs6qnj1Z3j7I53VG3nwZhKzoBZmbdRNnb6WRdFlwl7tSDuZGw==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
bindings@^1.5.0:
version "1.5.0"
resolved "https://registry.yarnpkg.com/bindings/-/bindings-1.5.0.tgz#10353c9e945334bc0511a6d90b38fbc7c9c504df"
integrity sha512-p2q/t/mhvuOj/UeLlV6566GD/guowlr0hHxClI0W9m7MWYkL1F0hLo+0Aexs9HSPCtR1SXQ0TD3MMKrXZajbiQ==
dependencies:
file-uri-to-path "1.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
bluebird@^3.5.5:
version "3.7.2"
resolved "https://registry.yarnpkg.com/bluebird/-/bluebird-3.7.2.tgz#9f229c15be272454ffa973ace0dbee79a1b0c36f"
integrity sha512-XpNj6GDQzdfW+r2Wnn7xiSAd7TM3jzkxGXBGTtWKuSXv1xUV+azxAm8jdWZN06QTQk+2N2XB9jRDkvbmQmcRtg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
bn.js@^4.0.0, bn.js@^4.1.0, bn.js@^4.1.1, bn.js@^4.4.0:
version "4.11.8"
resolved "https://registry.yarnpkg.com/bn.js/-/bn.js-4.11.8.tgz#2cde09eb5ee341f484746bb0309b3253b1b1442f"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-ItfYfPLkWHUjckQCk8xC+LwxgK8NYcXywGigJgSwOP8Y2iyWT4f2vsZnoOXTTbo+o5yXmIUJ4gn5538SO5S3gA==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
body-parser@1.19.0:
version "1.19.0"
resolved "https://registry.yarnpkg.com/body-parser/-/body-parser-1.19.0.tgz#96b2709e57c9c4e09a6fd66a8fd979844f69f08a"
integrity sha512-dhEPs72UPbDnAQJ9ZKMNTP6ptJaionhP5cBb541nXPlW60Jepo9RV/a4fX4XWW9CuFNK22krhrj1+rgzifNCsw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
bytes "3.1.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
content-type "~1.0.4"
debug "2.6.9"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
depd "~1.1.2"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
http-errors "1.7.2"
iconv-lite "0.4.24"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
on-finished "~2.3.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
qs "6.7.0"
raw-body "2.4.0"
type-is "~1.6.17"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
bonjour@^3.5.0:
version "3.5.0"
resolved "https://registry.yarnpkg.com/bonjour/-/bonjour-3.5.0.tgz#8e890a183d8ee9a2393b3844c691a42bcf7bc9f5"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-jokKGD2O6aI5OzhExpGkK897yfU=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
array-flatten "^2.1.0"
deep-equal "^1.0.1"
dns-equal "^1.0.0"
dns-txt "^2.0.2"
multicast-dns "^6.0.1"
multicast-dns-service-types "^1.1.0"
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
boolbase@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/boolbase/-/boolbase-1.0.0.tgz#68dff5fbe60c51eb37725ea9e3ed310dcc1e776e"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-aN/1++YMUes3cl6p4+0xDcwed24=
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
brace-expansion@^1.1.7:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "1.1.11"
resolved "https://registry.yarnpkg.com/brace-expansion/-/brace-expansion-1.1.11.tgz#3c7fcbf529d87226f3d2f52b966ff5271eb441dd"
integrity sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==
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
dependencies:
balanced-match "^1.0.0"
concat-map "0.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
braces@^2.3.1, braces@^2.3.2:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "2.3.2"
resolved "https://registry.yarnpkg.com/braces/-/braces-2.3.2.tgz#5979fd3f14cd531565e5fa2df1abfff1dfaee729"
integrity sha512-aNdbnj9P8PjdXU4ybaWLK2IF3jc/EoDYbC7AazW6to3TRsfXxscC9UXOB5iDiEQrkyIbWp2SLQda4+QAa7nc3w==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
arr-flatten "^1.1.0"
array-unique "^0.3.2"
extend-shallow "^2.0.1"
fill-range "^4.0.0"
isobject "^3.0.1"
repeat-element "^1.1.2"
snapdragon "^0.8.1"
snapdragon-node "^2.0.1"
split-string "^3.0.2"
to-regex "^3.0.1"
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
brorand@^1.0.1:
version "1.1.0"
resolved "https://registry.yarnpkg.com/brorand/-/brorand-1.1.0.tgz#12c25efe40a45e3c323eb8675a0a0ce57b22371f"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-EsJe/kCkXjwyPrhnWgoM5XsiNx8=
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
browserify-aes@^1.0.0, browserify-aes@^1.0.4:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/browserify-aes/-/browserify-aes-1.2.0.tgz#326734642f403dabc3003209853bb70ad428ef48"
integrity sha512-+7CHXqGuspUn/Sl5aO7Ea0xWGAtETPXNSAjHo48JfLdPWcMng33Xe4znFvQweqc/uzk5zSOI3H52CYnjCfb5hA==
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
dependencies:
buffer-xor "^1.0.3"
cipher-base "^1.0.0"
create-hash "^1.1.0"
evp_bytestokey "^1.0.3"
inherits "^2.0.1"
safe-buffer "^5.0.1"
browserify-cipher@^1.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/browserify-cipher/-/browserify-cipher-1.0.1.tgz#8d6474c1b870bfdabcd3bcfcc1934a10e94f15f0"
integrity sha512-sPhkz0ARKbf4rRQt2hTpAHqn47X3llLkUGn+xEJzLjwY8LRs2p0v7ljvI5EyoRO/mexrNunNECisZs+gw2zz1w==
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
dependencies:
browserify-aes "^1.0.4"
browserify-des "^1.0.0"
evp_bytestokey "^1.0.0"
browserify-des@^1.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/browserify-des/-/browserify-des-1.0.2.tgz#3af4f1f59839403572f1c66204375f7a7f703e9c"
integrity sha512-BioO1xf3hFwz4kc6iBhI3ieDFompMhrMlnDFC4/0/vd5MokpuAc3R+LYbwTA9A5Yc9pq9UYPqffKpW2ObuwX5A==
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
dependencies:
cipher-base "^1.0.1"
des.js "^1.0.0"
inherits "^2.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
safe-buffer "^5.1.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
browserify-rsa@^4.0.0:
version "4.0.1"
resolved "https://registry.yarnpkg.com/browserify-rsa/-/browserify-rsa-4.0.1.tgz#21e0abfaf6f2029cf2fafb133567a701d4135524"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-IeCr+vbyApzy+vsTNWenAdQTVSQ=
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
dependencies:
bn.js "^4.1.0"
randombytes "^2.0.1"
browserify-sign@^4.0.0:
version "4.0.4"
resolved "https://registry.yarnpkg.com/browserify-sign/-/browserify-sign-4.0.4.tgz#aa4eb68e5d7b658baa6bf6a57e630cbd7a93d298"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-qk62jl17ZYuqa/alfmMMvXqT0pg=
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
dependencies:
bn.js "^4.1.1"
browserify-rsa "^4.0.0"
create-hash "^1.1.0"
create-hmac "^1.1.2"
elliptic "^6.0.0"
inherits "^2.0.1"
parse-asn1 "^5.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
browserify-zlib@^0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/browserify-zlib/-/browserify-zlib-0.2.0.tgz#2869459d9aa3be245fe8fe2ca1f46e2e7f54d73f"
integrity sha512-Z942RysHXmJrhqk88FmKBVq/v5tqmSkDz7p54G/MGyjMnCFFnC79XWNbg+Vta8W6Wb2qtSZTSxIGkJrRpCFEiA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
pako "~1.0.5"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
browserslist@^4.8.3, browserslist@^4.8.5:
version "4.9.1"
resolved "https://registry.yarnpkg.com/browserslist/-/browserslist-4.9.1.tgz#01ffb9ca31a1aef7678128fc6a2253316aa7287c"
integrity sha512-Q0DnKq20End3raFulq6Vfp1ecB9fh8yUNV55s8sekaDDeqBaCtWlRHCUdaWyUeSSBJM7IbM6HcsyaeYqgeDhnw==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
caniuse-lite "^1.0.30001030"
electron-to-chromium "^1.3.363"
node-releases "^1.1.50"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
buffer-from@^1.0.0:
version "1.1.1"
resolved "https://registry.yarnpkg.com/buffer-from/-/buffer-from-1.1.1.tgz#32713bc028f75c02fdb710d7c7bcec1f2c6070ef"
integrity sha512-MQcXEUbCKtEo7bhqEs6560Hyd4XaovZlO/k9V3hjVUF/zwW7KBVdSK4gIt/bzwS9MbR5qob+F5jusZsb0YQK2A==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
buffer-indexof@^1.0.0:
version "1.1.1"
resolved "https://registry.yarnpkg.com/buffer-indexof/-/buffer-indexof-1.1.1.tgz#52fabcc6a606d1a00302802648ef68f639da268c"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-4/rOEg86jivtPTeOUUT61jJO1Ya1TrR/OkqCSZDyq84WJh3LuuiphBYJN+fm5xufIk4XAFcEwte/8WzC8If/1g==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
buffer-xor@^1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/buffer-xor/-/buffer-xor-1.0.3.tgz#26e61ed1422fb70dd42e6e36729ed51d855fe8d9"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-JuYe0UIvtw3ULm42cp7VHYVf6Nk=
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
buffer@^4.3.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "4.9.2"
resolved "https://registry.yarnpkg.com/buffer/-/buffer-4.9.2.tgz#230ead344002988644841ab0244af8c44bbe3ef8"
integrity sha512-xq+q3SRMOxGivLhBNaUdC64hDTQwejJ+H0T/NB1XMtTVEwNTrfFF3gAxiyW0Bu/xWEGhjVKgUcMhCrUy2+uCWg==
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
dependencies:
base64-js "^1.0.2"
ieee754 "^1.1.4"
isarray "^1.0.0"
builtin-status-codes@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/builtin-status-codes/-/builtin-status-codes-3.0.0.tgz#85982878e21b98e1c66425e03d0174788f569ee8"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-hZgoeOIbmOHGZCXgPQF0eI9Wnug=
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
bytes@3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/bytes/-/bytes-3.0.0.tgz#d32815404d689699f85a4ea4fa8755dd13a96048"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-0ygVQE1olpn4Wk6k+odV3ROpYEg=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
bytes@3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/bytes/-/bytes-3.1.0.tgz#f6cf7933a360e0588fa9fde85651cdc7f805d1f6"
integrity sha512-zauLjrfCG+xvoyaqLoV8bLVXXNGC4JqlxFCutSDWA6fJrTo2ZuvLYTqZ7aHBLZSMOopbzwv8f+wZcVzfVTI2Dg==
cacache@^12.0.2:
version "12.0.3"
resolved "https://registry.yarnpkg.com/cacache/-/cacache-12.0.3.tgz#be99abba4e1bf5df461cd5a2c1071fc432573390"
integrity sha512-kqdmfXEGFepesTuROHMs3MpFLWrPkSSpRqOw80RCflZXy/khxaArvFrQ7uJxSUduzAufc6G0g1VUCOZXxWavPw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
bluebird "^3.5.5"
chownr "^1.1.1"
figgy-pudding "^3.5.1"
glob "^7.1.4"
graceful-fs "^4.1.15"
infer-owner "^1.0.3"
lru-cache "^5.1.1"
mississippi "^3.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
mkdirp "^0.5.1"
move-concurrently "^1.0.1"
promise-inflight "^1.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
rimraf "^2.6.3"
ssri "^6.0.1"
unique-filename "^1.1.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
y18n "^4.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
cacache@^13.0.1:
version "13.0.1"
resolved "https://registry.yarnpkg.com/cacache/-/cacache-13.0.1.tgz#a8000c21697089082f85287a1aec6e382024a71c"
integrity sha512-5ZvAxd05HDDU+y9BVvcqYu2LLXmPnQ0hW62h32g4xBTgL/MppR4/04NHfj/ycM2y6lmTnbw6HVi+1eN0Psba6w==
dependencies:
chownr "^1.1.2"
figgy-pudding "^3.5.1"
fs-minipass "^2.0.0"
glob "^7.1.4"
graceful-fs "^4.2.2"
infer-owner "^1.0.4"
lru-cache "^5.1.1"
minipass "^3.0.0"
minipass-collect "^1.0.2"
minipass-flush "^1.0.5"
minipass-pipeline "^1.2.2"
mkdirp "^0.5.1"
move-concurrently "^1.0.1"
p-map "^3.0.0"
promise-inflight "^1.0.1"
rimraf "^2.7.1"
ssri "^7.0.0"
unique-filename "^1.1.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
cache-base@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/cache-base/-/cache-base-1.0.1.tgz#0a7f46416831c8b662ee36fe4e7c59d76f666ab2"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-AKcdTnFSWATd5/GCPRxr2ChwIJ85CeyrEyjRHlKxQ56d4XJMGym0uAiKn0xbLOGOl3+yRpOTi484dVCEc5AUzQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
collection-visit "^1.0.0"
component-emitter "^1.2.1"
get-value "^2.0.6"
has-value "^1.0.0"
isobject "^3.0.1"
set-value "^2.0.0"
to-object-path "^0.3.0"
union-value "^1.0.0"
unset-value "^1.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
callsites@^3.0.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/callsites/-/callsites-3.1.0.tgz#b3630abd8943432f54b3f0519238e33cd7df2f73"
integrity sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
camel-case@3.0.x:
version "3.0.0"
resolved "https://registry.yarnpkg.com/camel-case/-/camel-case-3.0.0.tgz#ca3c3688a4e9cf3a4cda777dc4dcbc713249cf73"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-yjw2iKTpzzpM2nd9xNy8cTJJz3M=
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
no-case "^2.2.0"
upper-case "^1.1.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
camelcase@^5.0.0, camelcase@^5.3.1:
version "5.3.1"
resolved "https://registry.yarnpkg.com/camelcase/-/camelcase-5.3.1.tgz#e3c9b31569e106811df242f715725a1f4c494320"
integrity sha512-L28STB170nwWS63UjtlEOE3dldQApaJXZkOI1uMFfzf3rRuPegHaHesyee+YxQ+W6SvRDQV6UrdOdRiR153wJg==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
caniuse-lite@^1.0.30001030:
version "1.0.30001030"
resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30001030.tgz#78076c4c6d67d3e41d6eb9399853fb27fe6e44ee"
integrity sha512-QGK0W4Ft/Ac+zTjEiRJfwDNATvS3fodDczBXrH42784kcfqcDKpEPfN08N0HQjrAp8He/Jw8QiSS9QRn7XAbUw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
chalk@2.4.2, chalk@^2.0.0, chalk@^2.1.0, chalk@^2.4.2:
version "2.4.2"
resolved "https://registry.yarnpkg.com/chalk/-/chalk-2.4.2.tgz#cd42541677a54333cf541a49108c1432b44c9424"
integrity sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==
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
dependencies:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
ansi-styles "^3.2.1"
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
escape-string-regexp "^1.0.5"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
supports-color "^5.3.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
chalk@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/chalk/-/chalk-3.0.0.tgz#3f73c2bf526591f574cc492c51e2456349f844e4"
integrity sha512-4D3B6Wf41KOYRFdszmDqMCGq5VV/uMAB273JILmO+3jAlh8X4qDtdtgCR3fxtbLEMzSx22QdhnDcJvu2u1fVwg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ansi-styles "^4.1.0"
supports-color "^7.1.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
chardet@^0.7.0:
version "0.7.0"
resolved "https://registry.yarnpkg.com/chardet/-/chardet-0.7.0.tgz#90094849f0937f2eedc2425d0d28a9e5f0cbad9e"
integrity sha512-mT8iDcrh03qDGRRmoA2hmBJnxpllMR+0/0qlzjqZES6NdiWDcZkCNAk4rPFZ9Q85r27unkiNNg8ZOiwZXBHwcA==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
chokidar@^2.0.2, chokidar@^2.1.8:
version "2.1.8"
resolved "https://registry.yarnpkg.com/chokidar/-/chokidar-2.1.8.tgz#804b3a7b6a99358c3c5c61e71d8728f041cff917"
integrity sha512-ZmZUazfOzf0Nve7duiCKD23PFSCs4JPoYyccjUFF3aQkQadqBhfzhjkwBH2mNOG9cTBwhamM37EIsIkZw3nRgg==
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
dependencies:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
anymatch "^2.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
async-each "^1.0.1"
braces "^2.3.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
glob-parent "^3.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
inherits "^2.0.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
is-binary-path "^1.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
is-glob "^4.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
normalize-path "^3.0.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
path-is-absolute "^1.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
readdirp "^2.2.1"
upath "^1.1.1"
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
optionalDependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
fsevents "^1.2.7"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
chownr@^1.1.1, chownr@^1.1.2:
version "1.1.4"
resolved "https://registry.yarnpkg.com/chownr/-/chownr-1.1.4.tgz#6fc9d7b42d32a583596337666e7d08084da2cc6b"
integrity sha512-jJ0bqzaylmJtVnNgzTeSOs8DPavpbYgEr/b0YL8/2GO3xJEhInFmhKMUnEJQjZumK7KXGFhUy89PrsJWlakBVg==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
chrome-trace-event@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/chrome-trace-event/-/chrome-trace-event-1.0.2.tgz#234090ee97c7d4ad1a2c4beae27505deffc608a4"
integrity sha512-9e/zx1jw7B4CO+c/RXoCsfg/x1AfUBioy4owYH0bJprEYAx5hRFLRhWBqHAG57D0ZM4H7vxbP7bPe0VwhQRYDQ==
dependencies:
tslib "^1.9.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
cipher-base@^1.0.0, cipher-base@^1.0.1, cipher-base@^1.0.3:
version "1.0.4"
resolved "https://registry.yarnpkg.com/cipher-base/-/cipher-base-1.0.4.tgz#8760e4ecc272f4c363532f926d874aae2c1397de"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-Kkht5ye6ZGmwv40uUDZztayT2ThLQGfnj/T71N/XzeZeo3nf8foyW7zGTsPYkEya3m5f3cAypH+qe7YOrM1U2Q==
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
dependencies:
inherits "^2.0.1"
safe-buffer "^5.0.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
class-utils@^0.3.5:
version "0.3.6"
resolved "https://registry.yarnpkg.com/class-utils/-/class-utils-0.3.6.tgz#f93369ae8b9a7ce02fd41faad0ca83033190c463"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-qOhPa/Fj7s6TY8H8esGu5QNpMMQxz79h+urzrNYN6mn+9BnxlDGf5QZ+XeCDsxSjPqsSR56XOZOJmpeurnLMeg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
arr-union "^3.1.0"
define-property "^0.2.5"
isobject "^3.0.0"
static-extend "^0.1.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
clean-css@4.2.x:
version "4.2.3"
resolved "https://registry.yarnpkg.com/clean-css/-/clean-css-4.2.3.tgz#507b5de7d97b48ee53d84adb0160ff6216380f78"
integrity sha512-VcMWDN54ZN/DS+g58HYL5/n4Zrqe8vHJpGA8KdgUXFU4fuP/aHNw8eld9SyEIyabIMJX/0RaY/fplOo5hYLSFA==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
source-map "~0.6.0"
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
clean-stack@^2.0.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/clean-stack/-/clean-stack-2.2.0.tgz#ee8472dbb129e727b31e8a10a427dee9dfe4008b"
integrity sha512-4diC9HaTE+KRAMWhDhrGOECgWZxoevMc5TlkObMqNSsVU62PYzXZ/SMTjzyGAFF1YusgxGcSWTEXBhp0CPwQ1A==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
clean-webpack-plugin@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/clean-webpack-plugin/-/clean-webpack-plugin-3.0.0.tgz#a99d8ec34c1c628a4541567aa7b457446460c62b"
integrity sha512-MciirUH5r+cYLGCOL5JX/ZLzOZbVr1ot3Fw+KcvbhUb6PM+yycqd9ZhIlcigQ5gl+XhppNmw3bEFuaaMNyLj3A==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@types/webpack" "^4.4.31"
del "^4.1.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
cli-cursor@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/cli-cursor/-/cli-cursor-3.1.0.tgz#264305a7ae490d1d03bf0c9ba7c925d1753af307"
integrity sha512-I/zHAwsKf9FqGoXM4WWRACob9+SNukZTd94DWF57E4toouRulbCxcUh6RKUEOQlYTHJnzkPMySvPNaaSLNfLZw==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
restore-cursor "^3.1.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
cli-width@^2.0.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/cli-width/-/cli-width-2.2.0.tgz#ff19ede8a9a5e579324147b0c11f0fbcbabed639"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-/xnt6Kml5XkyQUewwR8PvLq+1jk=
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
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
cliui@^4.0.0:
version "4.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
resolved "https://registry.yarnpkg.com/cliui/-/cliui-4.1.0.tgz#348422dbe82d800b3022eef4f6ac10bf2e4d1b49"
integrity sha512-4FG+RSG9DL7uEwRUZXZn3SS34DiDPfzP0VOiEwtUWlE+AR2EIg+hSyvrIgUUfhdgR/UkAeW2QHgeP+hWrXs7jQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
string-width "^2.1.1"
strip-ansi "^4.0.0"
wrap-ansi "^2.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
cliui@^5.0.0:
version "5.0.0"
resolved "https://registry.yarnpkg.com/cliui/-/cliui-5.0.0.tgz#deefcfdb2e800784aa34f46fa08e06851c7bbbc5"
integrity sha512-PYeGSEmmHM6zvoef2w8TPzlrnNpXIjTipYK780YswmIP9vjxmd6Y2a3CB2Ks6/AU8NHjZugXvo8w3oWM2qnwXA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
string-width "^3.1.0"
strip-ansi "^5.2.0"
wrap-ansi "^5.1.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
code-point-at@^1.0.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/code-point-at/-/code-point-at-1.1.0.tgz#0d070b4d043a5bea33a2f1a40e2edb3d9a4ccf77"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-DQcLTQQ6W+ozovGkDi7bPZpMz3c=
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
collection-visit@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/collection-visit/-/collection-visit-1.0.0.tgz#4bc0373c164bc3291b4d368c829cf1a80a59dca0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-S8A3PBZLwykbTTaMgpzxqApZ3KA=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
map-visit "^1.0.0"
object-visit "^1.0.0"
color-convert@^1.9.0:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "1.9.3"
resolved "https://registry.yarnpkg.com/color-convert/-/color-convert-1.9.3.tgz#bb71850690e1f136567de629d2d5471deda4c1e8"
integrity sha512-QfAUtd+vFdAtFQcC8CCyYt1fYWxSqAiK2cSD6zDB8N3cpsEBAvRxp9zOGg6G/SHHJYAT88/az/IuDGALsNVbGg==
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
dependencies:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
color-name "1.1.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
color-convert@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/color-convert/-/color-convert-2.0.1.tgz#72d3a68d598c9bdb3af2ad1e84f21d896abd4de3"
integrity sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==
dependencies:
color-name "~1.1.4"
color-name@1.1.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
version "1.1.3"
resolved "https://registry.yarnpkg.com/color-name/-/color-name-1.1.3.tgz#a7d0558bd89c42f795dd42328f740831ca53bc25"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-p9BVi9icQveV3UIyj3QIMcpTvCU=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
color-name@~1.1.4:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "1.1.4"
resolved "https://registry.yarnpkg.com/color-name/-/color-name-1.1.4.tgz#c2a09a87acbde69543de6f63fa3995c826c536a2"
integrity sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
commander@2.17.x:
version "2.17.1"
resolved "https://registry.yarnpkg.com/commander/-/commander-2.17.1.tgz#bd77ab7de6de94205ceacc72f1716d29f20a77bf"
integrity sha512-wPMUt6FnH2yzG95SA6mzjQOEKUU3aLaDEmzs1ti+1E9h+CsrZghRlqEM/EJ4KscsQVG8uNN4uVreUeT8+drlgg==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
commander@^2.20.0:
version "2.20.3"
resolved "https://registry.yarnpkg.com/commander/-/commander-2.20.3.tgz#fd485e84c03eb4881c20722ba48035e8531aeb33"
integrity sha512-GpVkmM8vF2vQUkj2LvZmD35JxeJOLCwJ9cUkugyk2nuhbv3+mJvpLYYt+0+USMxE+oj+ey/lJEnhZw75x/OMcQ==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
commander@~2.19.0:
version "2.19.0"
resolved "https://registry.yarnpkg.com/commander/-/commander-2.19.0.tgz#f6198aa84e5b83c46054b94ddedbfed5ee9ff12a"
integrity sha512-6tvAOO+D6OENvRAh524Dh9jcfKTYDQAqvqezbCW82xj5X0pSrcpxtvRKHLG0yBY6SD7PSDrJaj+0AiOcKVd1Xg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
commondir@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/commondir/-/commondir-1.0.1.tgz#ddd800da0c66127393cca5950ea968a3aaf1253b"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-3dgA2gxmEnOTzKWVDqloo6rxJTs=
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
component-emitter@^1.2.1:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.3.0"
resolved "https://registry.yarnpkg.com/component-emitter/-/component-emitter-1.3.0.tgz#16e4070fba8ae29b679f2215853ee181ab2eabc0"
integrity sha512-Rd3se6QB+sO1TwqZjscQrurpEPIfO0/yYnSin6Q/rD3mOutHvUrCAhJub3r90uNb+SESBuE0QYoB90YdfatsRg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
compressible@~2.0.16:
version "2.0.18"
resolved "https://registry.yarnpkg.com/compressible/-/compressible-2.0.18.tgz#af53cca6b070d4c3c0750fbd77286a6d7cc46fba"
integrity sha512-AF3r7P5dWxL8MxyITRMlORQNaOA2IkAFaTr4k7BUumjPtRpGDTZpl0Pb1XCO6JeDCBdp126Cgs9sMxqSjgYyRg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
mime-db ">= 1.43.0 < 2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
compression-webpack-plugin@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/compression-webpack-plugin/-/compression-webpack-plugin-3.1.0.tgz#9f510172a7b5fae5aad3b670652e8bd7997aeeca"
integrity sha512-iqTHj3rADN4yHwXMBrQa/xrncex/uEQy8QHlaTKxGchT/hC0SdlJlmL/5eRqffmWq2ep0/Romw6Ld39JjTR/ug==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
cacache "^13.0.1"
find-cache-dir "^3.0.0"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
neo-async "^2.5.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
schema-utils "^2.6.1"
serialize-javascript "^2.1.2"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
webpack-sources "^1.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
compression@^1.7.4:
version "1.7.4"
resolved "https://registry.yarnpkg.com/compression/-/compression-1.7.4.tgz#95523eff170ca57c29a0ca41e6fe131f41e5bb8f"
integrity sha512-jaSIDzP9pZVS4ZfQ+TzvtiWhdpFhE2RDHz8QJkpX9SIpLq88VueF5jJw6t+6CUQcAoA6t+x89MLrWAqpfDE8iQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
accepts "~1.3.5"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
bytes "3.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
compressible "~2.0.16"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
debug "2.6.9"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
on-headers "~1.0.2"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
safe-buffer "5.1.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
vary "~1.1.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
concat-map@0.0.1:
version "0.0.1"
resolved "https://registry.yarnpkg.com/concat-map/-/concat-map-0.0.1.tgz#d8a96bd77fd68df7793a73036a3ba0d5405d477b"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-2Klr13/Wjfd5OnMDajug1UBdR3s=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
concat-stream@^1.5.0:
version "1.6.2"
resolved "https://registry.yarnpkg.com/concat-stream/-/concat-stream-1.6.2.tgz#904bdf194cd3122fc675c77fc4ac3d4ff0fd1a34"
integrity sha512-27HBghJxjiZtIk3Ycvn/4kbJk/1uZuJFfuPEns6LaEvpvG1f0hTea8lilrouyo9mVc2GWdcEZ8OLoGmSADlrCw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
buffer-from "^1.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
inherits "^2.0.3"
readable-stream "^2.2.2"
typedarray "^0.0.6"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
connect-history-api-fallback@^1.6.0:
version "1.6.0"
resolved "https://registry.yarnpkg.com/connect-history-api-fallback/-/connect-history-api-fallback-1.6.0.tgz#8b32089359308d111115d81cad3fceab888f97bc"
integrity sha512-e54B99q/OUoH64zYYRf3HBP5z24G38h5D3qXu23JGRoigpX5Ss4r9ZnDk3g0Z8uQC2x2lPaJ+UlWBc1ZWBWdLg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
console-browserify@^1.1.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/console-browserify/-/console-browserify-1.2.0.tgz#67063cef57ceb6cf4993a2ab3a55840ae8c49336"
integrity sha512-ZMkYO/LkF17QvCPqM0gxw8yUzigAOZOSWSHg91FH6orS7vcEj5dVZTidN2fQ14yBSdg97RqhSNwLUXInd52OTA==
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
constants-browserify@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/constants-browserify/-/constants-browserify-1.0.0.tgz#c20b96d8c617748aaf1c16021760cd27fcb8cb75"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-wguW2MYXdIqvHBYCF2DNJ/y4y3U=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
content-disposition@0.5.3:
version "0.5.3"
resolved "https://registry.yarnpkg.com/content-disposition/-/content-disposition-0.5.3.tgz#e130caf7e7279087c5616c2007d0485698984fbd"
integrity sha512-ExO0774ikEObIAEV9kDo50o+79VCUdEB6n6lzKgGwupcVeRlhrj3qGAfwq8G6uBJjkqLrhT0qEYFcWng8z1z0g==
dependencies:
safe-buffer "5.1.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
content-type@~1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/content-type/-/content-type-1.0.4.tgz#e138cc75e040c727b1966fe5e5f8c9aee256fe3b"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-hIP3EEPs8tB9AT1L+NUqtwOAps4mk2Zob89MWXMHjHWg9milF/j4osnnQLXBCBFBk/tvIG/tUc9mOUJiPBhPXA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
convert-source-map@^1.7.0:
version "1.7.0"
resolved "https://registry.yarnpkg.com/convert-source-map/-/convert-source-map-1.7.0.tgz#17a2cb882d7f77d3490585e2ce6c524424a3a442"
integrity sha512-4FJkXzKXEDB1snCFZlLP4gpC3JILicCpGbzG9f9G7tGqGCzETQ2hWPrcinA9oU4wtf2biUaEH5065UnMeR33oA==
dependencies:
safe-buffer "~5.1.1"
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
cookie-signature@1.0.6:
version "1.0.6"
resolved "https://registry.yarnpkg.com/cookie-signature/-/cookie-signature-1.0.6.tgz#e303a882b342cc3ee8ca513a79999734dab3ae2c"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-4wOogrNCzD7oylE6eZmXNNqzriw=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
cookie@0.4.0:
version "0.4.0"
resolved "https://registry.yarnpkg.com/cookie/-/cookie-0.4.0.tgz#beb437e7022b3b6d49019d088665303ebe9c14ba"
integrity sha512-+Hp8fLp57wnUSt0tY0tHEXh4voZRDnoIrZPqlo3DPiI4y9lwg/jqx+1Om94/W6ZaPDOUbnjOt/99w66zk+l1Xg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
copy-concurrently@^1.0.0:
version "1.0.5"
resolved "https://registry.yarnpkg.com/copy-concurrently/-/copy-concurrently-1.0.5.tgz#92297398cae34937fcafd6ec8139c18051f0b5e0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-f2domd9fsVDFtaFcbaRZuYXwtdmnzqbADSwhSWYxYB/Q8zsdUUFMXVRwXGDMWmbEzAn1kdRrtI1T/KTFOL4X2A==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
aproba "^1.1.1"
fs-write-stream-atomic "^1.0.8"
iferr "^0.1.5"
mkdirp "^0.5.1"
rimraf "^2.5.4"
run-queue "^1.0.0"
copy-descriptor@^0.1.0:
version "0.1.1"
resolved "https://registry.yarnpkg.com/copy-descriptor/-/copy-descriptor-0.1.1.tgz#676f6eb3c39997c2ee1ac3a924fd6124748f578d"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-Z29us8OZl8LuGsOpJP1hJHSPV40=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
core-js-compat@^3.6.2:
version "3.6.4"
resolved "https://registry.yarnpkg.com/core-js-compat/-/core-js-compat-3.6.4.tgz#938476569ebb6cda80d339bcf199fae4f16fff17"
integrity sha512-zAa3IZPvsJ0slViBQ2z+vgyyTuhd3MFn1rBQjZSKVEgB0UMYhUkCj9jJUVPgGTGqWvsBVmfnruXgTcNyTlEiSA==
dependencies:
browserslist "^4.8.3"
semver "7.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
core-util-is@~1.0.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
version "1.0.2"
resolved "https://registry.yarnpkg.com/core-util-is/-/core-util-is-1.0.2.tgz#b5fd54220aa2bc5ab57aab7140c940754503c1a7"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-tf1UIgqivFq1eqtxQMlAdUUDwac=
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
create-ecdh@^4.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "4.0.3"
resolved "https://registry.yarnpkg.com/create-ecdh/-/create-ecdh-4.0.3.tgz#c9111b6f33045c4697f144787f9254cdc77c45ff"
integrity sha512-GbEHQPMOswGpKXM9kCWVrremUcBmjteUaQ01T9rkKCPDXfUHX0IoP9LpHYo2NPFampa4e+/pFDc3jQdxrxQLaw==
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
dependencies:
bn.js "^4.1.0"
elliptic "^6.0.0"
create-hash@^1.1.0, create-hash@^1.1.2:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/create-hash/-/create-hash-1.2.0.tgz#889078af11a63756bcfb59bd221996be3a9ef196"
integrity sha512-z00bCGNHDG8mHAkP7CtT1qVu+bFQUPjYq/4Iv3C3kWjTFV10zIjfSoeqXo9Asws8gwSHDGj/hl2u4OGIjapeCg==
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
dependencies:
cipher-base "^1.0.1"
inherits "^2.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
md5.js "^1.3.4"
ripemd160 "^2.0.1"
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
sha.js "^2.4.0"
create-hmac@^1.1.0, create-hmac@^1.1.2, create-hmac@^1.1.4:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.1.7"
resolved "https://registry.yarnpkg.com/create-hmac/-/create-hmac-1.1.7.tgz#69170c78b3ab957147b2b8b04572e47ead2243ff"
integrity sha512-MJG9liiZ+ogc4TzUwuvbER1JRdgvUFSB5+VR/g5h82fGaIRWMWddtKBHi7/sVhfjQZ6SehlyhvQYrcYkaUIpLg==
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
dependencies:
cipher-base "^1.0.3"
create-hash "^1.1.0"
inherits "^2.0.1"
ripemd160 "^2.0.0"
safe-buffer "^5.0.1"
sha.js "^2.4.8"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
cross-spawn@6.0.5, cross-spawn@^6.0.0, cross-spawn@^6.0.5:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
version "6.0.5"
resolved "https://registry.yarnpkg.com/cross-spawn/-/cross-spawn-6.0.5.tgz#4a5ec7c64dfae22c3a14124dbacdee846d80cbc4"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-eTVLrBSt7fjbDygz805pMnstIs2VTBNkRm0qxZd+M7A5XDdxVRWO5MxGBXZhjY4cqLYLdtrGqRf8mBPmzwSpWQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
nice-try "^1.0.4"
path-key "^2.0.1"
semver "^5.5.0"
shebang-command "^1.2.0"
which "^1.2.9"
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
crypto-browserify@^3.11.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "3.12.0"
resolved "https://registry.yarnpkg.com/crypto-browserify/-/crypto-browserify-3.12.0.tgz#396cf9f3137f03e4b8e532c58f698254e00f80ec"
integrity sha512-fz4spIh+znjO2VjL+IdhEpRJ3YN6sMzITSBijk6FK2UvTqruSQW+/cCZTSNsMiZNvUeq0CqurF+dAbyiGOY6Wg==
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
dependencies:
browserify-cipher "^1.0.0"
browserify-sign "^4.0.0"
create-ecdh "^4.0.0"
create-hash "^1.1.0"
create-hmac "^1.1.0"
diffie-hellman "^5.0.0"
inherits "^2.0.1"
pbkdf2 "^3.0.3"
public-encrypt "^4.0.0"
randombytes "^2.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
randomfill "^1.0.3"
css-loader@^3.4.2:
version "3.4.2"
resolved "https://registry.yarnpkg.com/css-loader/-/css-loader-3.4.2.tgz#d3fdb3358b43f233b78501c5ed7b1c6da6133202"
integrity sha512-jYq4zdZT0oS0Iykt+fqnzVLRIeiPWhka+7BqPn+oSIpWJAHak5tmB/WZrJ2a21JhCeFyNnnlroSl8c+MtVndzA==
dependencies:
camelcase "^5.3.1"
cssesc "^3.0.0"
icss-utils "^4.1.1"
loader-utils "^1.2.3"
normalize-path "^3.0.0"
postcss "^7.0.23"
postcss-modules-extract-imports "^2.0.0"
postcss-modules-local-by-default "^3.0.2"
postcss-modules-scope "^2.1.1"
postcss-modules-values "^3.0.0"
postcss-value-parser "^4.0.2"
schema-utils "^2.6.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
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
css-select@^1.1.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/css-select/-/css-select-1.2.0.tgz#2b3a110539c5355f1cd8d314623e870b121ec858"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-KzoRBTnFNV8c2NMUYj6HCxIeyFg=
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
boolbase "~1.0.0"
css-what "2.1"
domutils "1.5.1"
nth-check "~1.0.1"
css-what@2.1:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "2.1.3"
resolved "https://registry.yarnpkg.com/css-what/-/css-what-2.1.3.tgz#a6d7604573365fe74686c3f311c56513d88285f2"
integrity sha512-a+EPoD+uZiNfh+5fxw2nO9QwFa6nJe2Or35fGY6Ipw1R3R4AGz1d1TEZrCegvw2YTmZ0jXirGYlzxxpYSHwpEg==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
cssesc@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/cssesc/-/cssesc-3.0.0.tgz#37741919903b868565e1c09ea747445cd18983ee"
integrity sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
cyclist@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/cyclist/-/cyclist-1.0.1.tgz#596e9698fd0c80e12038c2b82d6eb1b35b6224d9"
integrity sha1-WW6WmP0MgOEgOMK4LW6xs1tiJNk=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
debug@2.6.9, debug@^2.2.0, debug@^2.3.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
version "2.6.9"
resolved "https://registry.yarnpkg.com/debug/-/debug-2.6.9.tgz#5d128515df134ff327e90a4c93f4e077a536341f"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==
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
dependencies:
ms "2.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
debug@^3.0.0, debug@^3.1.1, debug@^3.2.5:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "3.2.6"
resolved "https://registry.yarnpkg.com/debug/-/debug-3.2.6.tgz#e83d17de16d8a7efb7717edbe5fb10135eee629b"
integrity sha512-mel+jf7nrtEl5Pn1Qx46zARXKDpBbvzezse7p7LqINmdoIk8PYP5SySaxEmYv6TZ0JyEKA1hsCId6DIhgITtWQ==
dependencies:
ms "^2.1.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
debug@^4.0.1, debug@^4.1.0, debug@^4.1.1:
version "4.1.1"
resolved "https://registry.yarnpkg.com/debug/-/debug-4.1.1.tgz#3b72260255109c6b589cee050f1d516139664791"
integrity sha512-pYAIzeRo8J6KPEaJ0VWOh5Pzkbw/RetuzehGM7QRRX5he4fPHx2rdKMB256ehJCkX+XRQm16eZLqLNS8RSZXZw==
dependencies:
ms "^2.1.1"
decamelize@^1.2.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
version "1.2.0"
resolved "https://registry.yarnpkg.com/decamelize/-/decamelize-1.2.0.tgz#f6534d15148269b20352e7bee26f501f9a191290"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-9lNNFRSCabIDUue+4m9QH5oZEpA=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
decode-uri-component@^0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/decode-uri-component/-/decode-uri-component-0.2.0.tgz#eb3913333458775cb84cd1a1fae062106bb87545"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-6zkTMzRYd1y4TNGh+uBiEGu4dUU=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
deep-equal@^1.0.1:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.1.1"
resolved "https://registry.yarnpkg.com/deep-equal/-/deep-equal-1.1.1.tgz#b5c98c942ceffaf7cb051e24e1434a25a2e6076a"
integrity sha512-yd9c5AdiqVcR+JjcwUQb9DkhJc8ngNr0MahEBGvDiJw8puWab2yZlh+nkasOnZP+EGTAP6rRp2JzJhJZzvNF8g==
dependencies:
is-arguments "^1.0.4"
is-date-object "^1.0.1"
is-regex "^1.0.4"
object-is "^1.0.1"
object-keys "^1.1.1"
regexp.prototype.flags "^1.2.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
deep-is@~0.1.3:
version "0.1.3"
resolved "https://registry.yarnpkg.com/deep-is/-/deep-is-0.1.3.tgz#b369d6fb5dbc13eecf524f91b070feedc357cf34"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-s2nW+128E+7PUk+RsHD+7cNXzzQ=
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
default-gateway@^4.2.0:
version "4.2.0"
resolved "https://registry.yarnpkg.com/default-gateway/-/default-gateway-4.2.0.tgz#167104c7500c2115f6dd69b0a536bb8ed720552b"
integrity sha512-h6sMrVB1VMWVrW13mSc6ia/DwYYw5MN6+exNu1OaJeFac5aSAvwM7lZ0NVfTABuSkQelr4h5oebg3KB1XPdjgA==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
execa "^1.0.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
ip-regex "^2.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
define-properties@^1.1.2, define-properties@^1.1.3:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "1.1.3"
resolved "https://registry.yarnpkg.com/define-properties/-/define-properties-1.1.3.tgz#cf88da6cbee26fe6db7094f61d870cbd84cee9f1"
integrity sha512-3MqfYKj2lLzdMSf8ZIZE/V+Zuy+BgD6f164e8K2w7dgnpKArBDerGYpM46IYYcjnkdPNMjPk9A6VFB8+3SKlXQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
object-keys "^1.0.12"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
define-property@^0.2.5:
version "0.2.5"
resolved "https://registry.yarnpkg.com/define-property/-/define-property-0.2.5.tgz#c35b1ef918ec3c990f9a5bc57be04aacec5c8116"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-w1se+RjsPJkPmlvFe+BKrOxcgRY=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
is-descriptor "^0.1.0"
define-property@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/define-property/-/define-property-1.0.0.tgz#769ebaaf3f4a63aad3af9e8d304c9bbe79bfb0e6"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-dp66rz9KY6rTr56NMEybvnm/sOY=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
is-descriptor "^1.0.0"
define-property@^2.0.2:
version "2.0.2"
resolved "https://registry.yarnpkg.com/define-property/-/define-property-2.0.2.tgz#d459689e8d654ba77e02a817f8710d702cb16e9d"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-jwK2UV4cnPpbcG7+VRARKTZPUWowwXA8bzH5NP6ud0oeAxyYPuGZUAC7hMugpCdz4BeSZl2Dl9k66CHJ/46ZYQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
is-descriptor "^1.0.2"
isobject "^3.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
del@^4.1.1:
version "4.1.1"
resolved "https://registry.yarnpkg.com/del/-/del-4.1.1.tgz#9e8f117222ea44a31ff3a156c049b99052a9f0b4"
integrity sha512-QwGuEUouP2kVwQenAsOof5Fv8K9t3D8Ca8NxcXKrIpEHjTXK5J2nXLdP+ALI1cgv8wj7KuwBhTwBkOZSJKM5XQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@types/glob" "^7.1.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
globby "^6.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
is-path-cwd "^2.0.0"
is-path-in-cwd "^2.0.0"
p-map "^2.0.0"
pify "^4.0.1"
rimraf "^2.6.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
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
depd@~1.1.2:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
version "1.1.2"
resolved "https://registry.yarnpkg.com/depd/-/depd-1.1.2.tgz#9bcd52e14c097763e749b274c4346ed2e560b5a9"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-m81S4UwJd2PnSbJ0xDRu0uVgtak=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
des.js@^1.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/des.js/-/des.js-1.0.1.tgz#5382142e1bdc53f85d86d53e5f4aa7deb91e0843"
integrity sha512-Q0I4pfFrv2VPd34/vfLrFOoRmlYj3OV50i7fskps1jZWK1kApMWWT9G6RRUeYedLcBDIhnSDaUvJMb3AhUlaEA==
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
dependencies:
inherits "^2.0.1"
minimalistic-assert "^1.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
destroy@~1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/destroy/-/destroy-1.0.4.tgz#978857442c44749e4206613e37946205826abd80"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-l4hXRCxEdJ5CBmE+N5RiBYJqvYA=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
detect-file@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/detect-file/-/detect-file-1.0.0.tgz#f0d66d03672a825cb1b73bdb3fe62310c8e552b7"
integrity sha1-8NZtA2cqglyxtzvbP+YjEMjlUrc=
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
detect-node@^2.0.4:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "2.0.4"
resolved "https://registry.yarnpkg.com/detect-node/-/detect-node-2.0.4.tgz#014ee8f8f669c5c58023da64b8179c083a28c46c"
integrity sha512-ZIzRpLJrOj7jjP2miAtgqIfmzbxa4ZOr5jJc601zklsfEx9oTzmmj2nVpIPRpNlRTIh8lc1kyViIY7BWSGNmKw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
diffie-hellman@^5.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "5.0.3"
resolved "https://registry.yarnpkg.com/diffie-hellman/-/diffie-hellman-5.0.3.tgz#40e8ee98f55a2149607146921c63e1ae5f3d2875"
integrity sha512-kqag/Nl+f3GwyK25fhUMYj81BUOrZ9IuJsjIcDE5icNM9FJHAVm3VcUDxdLPoQtTuUylWm6ZIknYJwwaPxsUzg==
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
dependencies:
bn.js "^4.1.0"
miller-rabin "^4.0.0"
randombytes "^2.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dns-equal@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/dns-equal/-/dns-equal-1.0.0.tgz#b39e7f1da6eb0a75ba9c17324b34753c47e0654d"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-s55/HabrCnW6nBcySzR1PEfgZU0=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dns-packet@^1.3.1:
version "1.3.1"
resolved "https://registry.yarnpkg.com/dns-packet/-/dns-packet-1.3.1.tgz#12aa426981075be500b910eedcd0b47dd7deda5a"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-0UxfQkMhYAUaZI+xrNZOz/as5KgDU0M/fQ9b6SpkyLbk3GEswDi6PADJVaYJradtRVsRIlF1zLyOodbcTCDzUg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
ip "^1.1.0"
safe-buffer "^5.0.1"
dns-txt@^2.0.2:
version "2.0.2"
resolved "https://registry.yarnpkg.com/dns-txt/-/dns-txt-2.0.2.tgz#b91d806f5d27188e4ab3e7d107d881a1cc4642b6"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-uR2Ab10nGI5Ks+fRB9iBocxGQrY=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
buffer-indexof "^1.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
doctrine@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/doctrine/-/doctrine-3.0.0.tgz#addebead72a6574db783639dc87a121773973961"
integrity sha512-yS+Q5i3hBf7GBkd4KG8a7eBNNWNGLTaEwwYWUijIYM7zrlYDM0BFXHjjPWlWZ1Rg7UaddZeIDmi9jF3HmqiQ2w==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
esutils "^2.0.2"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
dom-converter@^0.2:
version "0.2.0"
resolved "https://registry.yarnpkg.com/dom-converter/-/dom-converter-0.2.0.tgz#6721a9daee2e293682955b6afe416771627bb768"
integrity sha512-gd3ypIPfOMr9h5jIKq8E3sHOTCjeirnl0WK5ZdS1AW0Odt0b1PaWaHdJ4Qk4klv+YB9aJBS7mESXjFoDQPu6DA==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
utila "~0.4"
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dom-serializer@0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "0.2.2"
resolved "https://registry.yarnpkg.com/dom-serializer/-/dom-serializer-0.2.2.tgz#1afb81f533717175d478655debc5e332d9f9bb51"
integrity sha512-2/xPb3ORsQ42nHYiSunXkDjPLBaEj/xTwUO4B7XCZQTRk7EBtTOPaygh10YAAh2OI1Qrp6NWfpAhzswj0ydt9g==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
domelementtype "^2.0.1"
entities "^2.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
domain-browser@^1.1.1:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/domain-browser/-/domain-browser-1.2.0.tgz#3d31f50191a6749dd1375a7f522e823d42e54eda"
integrity sha512-jnjyiM6eRyZl2H+W8Q/zLMA481hzi0eszAaBUzIVnmYVDBbnLxVNnfu1HgEBvCbL+71FrxMl3E6lpKH7Ge3OXA==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
domelementtype@1, domelementtype@^1.3.1:
version "1.3.1"
resolved "https://registry.yarnpkg.com/domelementtype/-/domelementtype-1.3.1.tgz#d048c44b37b0d10a7f2a3d5fee3f4333d790481f"
integrity sha512-BSKB+TSpMpFI/HOxCNr1O8aMOTZ8hT3pM3GQ0w/mWRmkhEDSFJkkyzz4XQsBV44BChwGkrDfMyjVD0eA2aFV3w==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
domelementtype@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/domelementtype/-/domelementtype-2.0.1.tgz#1f8bdfe91f5a78063274e803b4bdcedf6e94f94d"
integrity sha512-5HOHUDsYZWV8FGWN0Njbr/Rn7f/eWSQi1v7+HsUVwXgn8nWWlL64zKDkS0n8ZmQ3mlWOMuXOnR+7Nx/5tMO5AQ==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
domhandler@^2.3.0:
version "2.4.2"
resolved "https://registry.yarnpkg.com/domhandler/-/domhandler-2.4.2.tgz#8805097e933d65e85546f726d60f5eb88b44f803"
integrity sha512-JiK04h0Ht5u/80fdLMCEmV4zkNh2BcoMFBmZ/91WtYZ8qVXSKjiw7fXMgFPnHcSZgOo3XdinHvmnDUeMf5R4wA==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
domelementtype "1"
domutils@1.5.1:
version "1.5.1"
resolved "https://registry.yarnpkg.com/domutils/-/domutils-1.5.1.tgz#dcd8488a26f563d61079e48c9f7b7e32373682cf"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-3NhIiib1Y9YQeeSMn3t+Mjc2gs8=
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
dom-serializer "0"
domelementtype "1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
domutils@^1.5.1:
version "1.7.0"
resolved "https://registry.yarnpkg.com/domutils/-/domutils-1.7.0.tgz#56ea341e834e06e6748af7a1cb25da67ea9f8c2a"
integrity sha512-Lgd2XcJ/NjEw+7tFvfKxOzCYKZsdct5lczQ2ZaQY8Djz7pfAD3Gbp8ySJWtreII/vDlMVmxwa6pHmdxIYgttDg==
dependencies:
dom-serializer "0"
domelementtype "1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
duplexify@^3.4.2, duplexify@^3.6.0:
version "3.7.1"
resolved "https://registry.yarnpkg.com/duplexify/-/duplexify-3.7.1.tgz#2a4df5317f6ccfd91f86d6fd25d8d8a103b88309"
integrity sha512-07z8uv2wMyS51kKhD1KsdXJg5WQ6t93RneqRxUHnskXVtlYYkLqM0gqStQZ3pj073g687jPCHrqNfCzawLYh5g==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
end-of-stream "^1.0.0"
inherits "^2.0.1"
readable-stream "^2.0.0"
stream-shift "^1.0.0"
ee-first@1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/ee-first/-/ee-first-1.1.1.tgz#590c61156b0ae2f4f0255732a158b266bc56b21d"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-WQxhFWsK4vTwJVcyoViyZrxWsh0=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
electron-to-chromium@^1.3.363:
version "1.3.364"
resolved "https://registry.yarnpkg.com/electron-to-chromium/-/electron-to-chromium-1.3.364.tgz#524bd0cf9c45ba49c508fd3b731a07efbf310b1c"
integrity sha512-V6hyxQ9jzt6Jy6w8tAv4HHKhIaVS6psG/gmwtQ+2+itdkWMHJLHJ4m1sFep/fWkdKvfJcPXuywfnECRzfNa7gw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
elliptic@^6.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "6.5.2"
resolved "https://registry.yarnpkg.com/elliptic/-/elliptic-6.5.2.tgz#05c5678d7173c049d8ca433552224a495d0e3762"
integrity sha512-f4x70okzZbIQl/NSRLkI/+tteV/9WqL98zx+SQ69KbXxmVrmjwsNUPn/gYJJ0sHvEak24cZgHIPegRePAtA/xw==
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
dependencies:
bn.js "^4.4.0"
brorand "^1.0.1"
hash.js "^1.0.0"
hmac-drbg "^1.0.0"
inherits "^2.0.1"
minimalistic-assert "^1.0.0"
minimalistic-crypto-utils "^1.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
emoji-regex@^7.0.1:
version "7.0.3"
resolved "https://registry.yarnpkg.com/emoji-regex/-/emoji-regex-7.0.3.tgz#933a04052860c85e83c122479c4748a8e4c72156"
integrity sha512-CwBLREIQ7LvYFB0WyRvwhq5N5qPhc6PMjD6bYggFlI5YyDgl+0vxq5VHbMOFqLg7hfWzmu8T5Z1QofhmTIhItA==
emoji-regex@^8.0.0:
version "8.0.0"
resolved "https://registry.yarnpkg.com/emoji-regex/-/emoji-regex-8.0.0.tgz#e818fd69ce5ccfcb404594f842963bf53164cc37"
integrity sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==
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
emojis-list@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/emojis-list/-/emojis-list-2.1.0.tgz#4daa4d9db00f9819880c79fa457ae5b09a1fd389"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-TapNnbAPmBmIDHn6RXrlsJof04k=
emojis-list@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/emojis-list/-/emojis-list-3.0.0.tgz#5570662046ad29e2e916e71aae260abdff4f6a78"
integrity sha512-/kyM18EfinwXZbno9FyUGeFh87KC8HRQBQGildHZbEuRyWFOmv1U10o9BBp8XVZDVNNuQKyIGIu5ZYAAXJ0V2Q==
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
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
encodeurl@~1.0.2:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/encodeurl/-/encodeurl-1.0.2.tgz#ad3ff4c86ec2d029322f5a02c3a9a606c95b3f59"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-rT/0yG7C0CkyL1oCw6mmBslbP1k=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
end-of-stream@^1.0.0, end-of-stream@^1.1.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.4.4"
resolved "https://registry.yarnpkg.com/end-of-stream/-/end-of-stream-1.4.4.tgz#5ae64a5f45057baf3626ec14da0ca5e4b2431eb0"
integrity sha512-+uw1inIHVPQoaVuHzRyXd21icM+cnt4CzD5rW+NC1wjOUSTOs+Te7FOv7AhN7vS9x/oIyhLP5PR1H+phQAHu5Q==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
once "^1.4.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
enhanced-resolve@4.1.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/enhanced-resolve/-/enhanced-resolve-4.1.0.tgz#41c7e0bfdfe74ac1ffe1e57ad6a5c6c9f3742a7f"
integrity sha512-F/7vkyTtyc/llOIn8oWclcB25KdRaiPBpZYDgJHgh/UHtpgT2p2eldQgtQnLtUvfMKPKxbRaQM/hHkvLHt1Vng==
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
dependencies:
graceful-fs "^4.1.2"
memory-fs "^0.4.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
tapable "^1.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
enhanced-resolve@^4.1.0:
version "4.1.1"
resolved "https://registry.yarnpkg.com/enhanced-resolve/-/enhanced-resolve-4.1.1.tgz#2937e2b8066cd0fe7ce0990a98f0d71a35189f66"
integrity sha512-98p2zE+rL7/g/DzMHMTF4zZlCgeVdJ7yr6xzEpJRYwFYrGi9ANdn5DnJURg6RpBkyk60XYDnWIv51VfIhfNGuA==
dependencies:
graceful-fs "^4.1.2"
memory-fs "^0.5.0"
tapable "^1.0.0"
entities@^1.1.1:
version "1.1.2"
resolved "https://registry.yarnpkg.com/entities/-/entities-1.1.2.tgz#bdfa735299664dfafd34529ed4f8522a275fea56"
integrity sha512-f2LZMYl1Fzu7YSBKg+RoROelpOaNrcGmE9AZubeDfrCEia483oW4MI4VyFd5VNHIgQ/7qm1I0wUHK1eJnn2y2w==
entities@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/entities/-/entities-2.0.0.tgz#68d6084cab1b079767540d80e56a39b423e4abf4"
integrity sha512-D9f7V0JSRwIxlRI2mjMqufDrRDnx8p+eEOz7aUM9SuvF8gsBzra0/6tbjl1m8eQHrZlYj6PxqE00hZ1SAIKPLw==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
errno@^0.1.3, errno@~0.1.7:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
version "0.1.7"
resolved "https://registry.yarnpkg.com/errno/-/errno-0.1.7.tgz#4684d71779ad39af177e3f007996f7c67c852618"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-MfrRBDWzIWifgq6tJj60gkAwtLNb6sQPlcFrSOflcP1aFmmruKQ2wRnze/8V6kgyz7H3FF8Npzv78mZ7XLLflg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
prr "~1.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
es-abstract@^1.17.0-next.1:
version "1.17.4"
resolved "https://registry.yarnpkg.com/es-abstract/-/es-abstract-1.17.4.tgz#e3aedf19706b20e7c2594c35fc0d57605a79e184"
integrity sha512-Ae3um/gb8F0mui/jPL+QiqmglkUsaQf7FwBEHYIFkztkneosu9imhqHpBzQ3h1vit8t5iQ74t6PEVvphBZiuiQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
es-to-primitive "^1.2.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
function-bind "^1.1.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
has "^1.0.3"
has-symbols "^1.0.1"
is-callable "^1.1.5"
is-regex "^1.0.5"
object-inspect "^1.7.0"
object-keys "^1.1.1"
object.assign "^4.1.0"
string.prototype.trimleft "^2.1.1"
string.prototype.trimright "^2.1.1"
es-to-primitive@^1.2.1:
version "1.2.1"
resolved "https://registry.yarnpkg.com/es-to-primitive/-/es-to-primitive-1.2.1.tgz#e55cd4c9cdc188bcefb03b366c736323fc5c898a"
integrity sha512-QCOllgZJtaUo9miYBcLChTUaHNjJF3PYs1VidD7AwiEj1kYxKeQTctLAezAOH5ZKRH0g2IgPn6KwB4IT8iRpvA==
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
dependencies:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
is-callable "^1.1.4"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
is-date-object "^1.0.1"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
is-symbol "^1.0.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
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
es6-templates@^0.2.3:
version "0.2.3"
resolved "https://registry.yarnpkg.com/es6-templates/-/es6-templates-0.2.3.tgz#5cb9ac9fb1ded6eb1239342b81d792bbb4078ee4"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-XLmsn7He1usSOTQrgdeSu7QHjuQ=
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
recast "~0.11.12"
through "~2.3.6"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
escape-html@~1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/escape-html/-/escape-html-1.0.3.tgz#0258eae4d3d0c0974de1c169188ef0051d1d1988"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-Aljq5NPQwJdN4cFpGI7wBR0dGYg=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
escape-string-regexp@^1.0.5:
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
version "1.0.5"
resolved "https://registry.yarnpkg.com/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz#1b61c0562190a8dff6ae3bb2cf0200ca130b86d4"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-G2HAViGQqN/2rjuyzwIAyhMLhtQ=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
eslint-config-google@^0.14.0:
version "0.14.0"
resolved "https://registry.yarnpkg.com/eslint-config-google/-/eslint-config-google-0.14.0.tgz#4f5f8759ba6e11b424294a219dbfa18c508bcc1a"
integrity sha512-WsbX4WbjuMvTdeVL6+J3rK1RGhCTqjsFjX7UMSMgZiyxxaNLkoJENbrGExzERFeoTpGw3F3FypTiWAP9ZXzkEw==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
eslint-scope@^4.0.3:
version "4.0.3"
resolved "https://registry.yarnpkg.com/eslint-scope/-/eslint-scope-4.0.3.tgz#ca03833310f6889a3264781aa82e63eb9cfe7848"
integrity sha512-p7VutNr1O/QrxysMo3E45FjYDTeXBy0iTltPFNSqKAIfjDSXC+4dj+qfyuD8bfAXrW/y6lW3O76VaYNPKfpKrg==
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
dependencies:
esrecurse "^4.1.0"
estraverse "^4.1.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
eslint-scope@^5.0.0:
version "5.0.0"
resolved "https://registry.yarnpkg.com/eslint-scope/-/eslint-scope-5.0.0.tgz#e87c8887c73e8d1ec84f1ca591645c358bfc8fb9"
integrity sha512-oYrhJW7S0bxAFDvWqzvMPRm6pcgcnWc4QnofCAqRTRfQC0JcwenzGglTtsLyIuuWFfkqDG9vz67cnttSd53djw==
dependencies:
esrecurse "^4.1.0"
estraverse "^4.1.1"
eslint-utils@^1.4.3:
version "1.4.3"
resolved "https://registry.yarnpkg.com/eslint-utils/-/eslint-utils-1.4.3.tgz#74fec7c54d0776b6f67e0251040b5806564e981f"
integrity sha512-fbBN5W2xdY45KulGXmLHZ3c3FHfVYmKg0IrAKGOkT/464PQsx2UeIzfz1RmEci+KLm1bBaAzZAh8+/E+XAeZ8Q==
dependencies:
eslint-visitor-keys "^1.1.0"
eslint-visitor-keys@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/eslint-visitor-keys/-/eslint-visitor-keys-1.1.0.tgz#e2a82cea84ff246ad6fb57f9bde5b46621459ec2"
integrity sha512-8y9YjtM1JBJU/A9Kc+SbaOV4y29sSWckBwMHa+FGtVj5gN/sbnKDf6xJUl+8g7FAij9LVaP8C24DUiH/f/2Z9A==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
eslint@^6.8.0:
version "6.8.0"
resolved "https://registry.yarnpkg.com/eslint/-/eslint-6.8.0.tgz#62262d6729739f9275723824302fb227c8c93ffb"
integrity sha512-K+Iayyo2LtyYhDSYwz5D5QdWw0hCacNzyq1Y821Xna2xSJj7cijoLLYmLxTQgcgZ9mC61nryMy9S7GRbYpI5Ig==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/code-frame" "^7.0.0"
ajv "^6.10.0"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
chalk "^2.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
cross-spawn "^6.0.5"
debug "^4.0.1"
doctrine "^3.0.0"
eslint-scope "^5.0.0"
eslint-utils "^1.4.3"
eslint-visitor-keys "^1.1.0"
espree "^6.1.2"
esquery "^1.0.1"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
esutils "^2.0.2"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
file-entry-cache "^5.0.1"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
functional-red-black-tree "^1.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
glob-parent "^5.0.0"
globals "^12.1.0"
ignore "^4.0.6"
import-fresh "^3.0.0"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
imurmurhash "^0.1.4"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
inquirer "^7.0.0"
is-glob "^4.0.0"
js-yaml "^3.13.1"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
json-stable-stringify-without-jsonify "^1.0.1"
levn "^0.3.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
lodash "^4.17.14"
minimatch "^3.0.4"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
mkdirp "^0.5.1"
natural-compare "^1.4.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
optionator "^0.8.3"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
progress "^2.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
regexpp "^2.0.1"
semver "^6.1.2"
strip-ansi "^5.2.0"
strip-json-comments "^3.0.1"
table "^5.2.3"
text-table "^0.2.0"
v8-compile-cache "^2.0.3"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
espree@^6.1.2:
version "6.1.2"
resolved "https://registry.yarnpkg.com/espree/-/espree-6.1.2.tgz#6c272650932b4f91c3714e5e7b5f5e2ecf47262d"
integrity sha512-2iUPuuPP+yW1PZaMSDM9eyVf8D5P0Hi8h83YtZ5bPc/zHYjII5khoixIUTMO794NOY8F/ThF1Bo8ncZILarUTA==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
acorn "^7.1.0"
acorn-jsx "^5.1.0"
eslint-visitor-keys "^1.1.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
esprima@^4.0.0:
version "4.0.1"
resolved "https://registry.yarnpkg.com/esprima/-/esprima-4.0.1.tgz#13b04cdb3e6c5d19df91ab6987a8695619b0aa71"
integrity sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
esprima@~3.1.0:
version "3.1.3"
resolved "https://registry.yarnpkg.com/esprima/-/esprima-3.1.3.tgz#fdca51cee6133895e3c88d535ce49dbff62a4633"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-/cpRzuYTOJXjyI1TXOSdv/YqRjM=
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
esquery@^1.0.1:
version "1.1.0"
resolved "https://registry.yarnpkg.com/esquery/-/esquery-1.1.0.tgz#c5c0b66f383e7656404f86b31334d72524eddb48"
integrity sha512-MxYW9xKmROWF672KqjO75sszsA8Mxhw06YFeS5VHlB98KDHbOSurm3ArsjO60Eaf3QmGMCP1yn+0JQkNLo/97Q==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
estraverse "^4.0.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
esrecurse@^4.1.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "4.2.1"
resolved "https://registry.yarnpkg.com/esrecurse/-/esrecurse-4.2.1.tgz#007a3b9fdbc2b3bb87e4879ea19c92fdbd3942cf"
integrity sha512-64RBB++fIOAXPw3P9cy89qfMlvZEXZkqqJkjqqXIvzP5ezRZjW+lPWjw35UX/3EhUPFYbg5ER4JYgDw4007/DQ==
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
dependencies:
estraverse "^4.1.0"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
estraverse@^4.0.0, estraverse@^4.1.0, estraverse@^4.1.1:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "4.3.0"
resolved "https://registry.yarnpkg.com/estraverse/-/estraverse-4.3.0.tgz#398ad3f3c5a24948be7725e83d11a7de28cdbd1d"
integrity sha512-39nnKffWz8xN1BU/2c79n9nB9HDzo0niYUqx6xyqUnyoAnQyyWpOTdZEeiCch8BBu515t4wp9ZmgVfVhn9EBpw==
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
esutils@^2.0.2:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "2.0.3"
resolved "https://registry.yarnpkg.com/esutils/-/esutils-2.0.3.tgz#74d2eb4de0b8da1293711910d50775b9b710ef64"
integrity sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
etag@~1.8.1:
version "1.8.1"
resolved "https://registry.yarnpkg.com/etag/-/etag-1.8.1.tgz#41ae2eeb65efa62268aebfea83ac7d79299b0887"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-Qa4u62XvpiJorr/qg6x9eSmbCIc=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
eventemitter3@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/eventemitter3/-/eventemitter3-4.0.0.tgz#d65176163887ee59f386d64c82610b696a4a74eb"
integrity sha512-qerSRB0p+UDEssxTtm6EDKcE7W4OaoisfIMl4CngyEhjpYglocpNg6UEqCvemdGhosAsg4sO2dXJOdyBifPGCg==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
events@^3.0.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/events/-/events-3.1.0.tgz#84279af1b34cb75aa88bf5ff291f6d0bd9b31a59"
integrity sha512-Rv+u8MLHNOdMjTAFeT3nCjHn2aGlx435FP/sDHNaRhDEMwyI/aB22Kj2qIN8R0cw3z28psEQLYwxVKLsKrMgWg==
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
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
eventsource@^1.0.7:
version "1.0.7"
resolved "https://registry.yarnpkg.com/eventsource/-/eventsource-1.0.7.tgz#8fbc72c93fcd34088090bc0a4e64f4b5cee6d8d0"
integrity sha512-4Ln17+vVT0k8aWq+t/bF5arcS3EpT9gYtW66EPacdj/mAFevznsnyoHLPy2BA8gbIQeIHoPsvwmfBftfcG//BQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
original "^1.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
evp_bytestokey@^1.0.0, evp_bytestokey@^1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/evp_bytestokey/-/evp_bytestokey-1.0.3.tgz#7fcbdb198dc71959432efe13842684e0525acb02"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-/f2Go4TognH/KvCISP7OUsHn85hT9nUkxxA9BEWxFn+Oj9o8ZNLm/40hdlgSLyuOimsrTKLUMEorQexp/aPQeA==
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
dependencies:
md5.js "^1.3.4"
safe-buffer "^5.1.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
execa@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/execa/-/execa-1.0.0.tgz#c6236a5bb4df6d6f15e88e7f017798216749ddd8"
integrity sha512-adbxcyWV46qiHyvSp50TKt05tB4tK3HcmF7/nxfAdhnox83seTDbwnaqKO4sXRy7roHAIFqJP/Rw/AuEbX61LA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
cross-spawn "^6.0.0"
get-stream "^4.0.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
is-stream "^1.1.0"
npm-run-path "^2.0.0"
p-finally "^1.0.0"
signal-exit "^3.0.0"
strip-eof "^1.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
expand-brackets@^2.1.4:
version "2.1.4"
resolved "https://registry.yarnpkg.com/expand-brackets/-/expand-brackets-2.1.4.tgz#b77735e315ce30f6b6eff0f83b04151a22449622"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-t3c14xXOMPa27/D4OwQVGiJEliI=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
debug "^2.3.3"
define-property "^0.2.5"
extend-shallow "^2.0.1"
posix-character-classes "^0.1.0"
regex-not "^1.0.0"
snapdragon "^0.8.1"
to-regex "^3.0.1"
expand-tilde@^2.0.0, expand-tilde@^2.0.2:
version "2.0.2"
resolved "https://registry.yarnpkg.com/expand-tilde/-/expand-tilde-2.0.2.tgz#97e801aa052df02454de46b02bf621642cdc8502"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-l+gBqgUt8CRU3kawK/YhZCzchQI=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
homedir-polyfill "^1.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
express@^4.17.1:
version "4.17.1"
resolved "https://registry.yarnpkg.com/express/-/express-4.17.1.tgz#4491fc38605cf51f8629d39c2b5d026f98a4c134"
integrity sha512-mHJ9O79RqluphRrcw2X/GTh3k9tVv8YcoyY4Kkh4WDMUYKRZUq0h1o0w2rrrxBqM7VoeUVqgb27xlEMXTnYt4g==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
accepts "~1.3.7"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
array-flatten "1.1.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
body-parser "1.19.0"
content-disposition "0.5.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
content-type "~1.0.4"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
cookie "0.4.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
cookie-signature "1.0.6"
debug "2.6.9"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
depd "~1.1.2"
encodeurl "~1.0.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
escape-html "~1.0.3"
etag "~1.8.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
finalhandler "~1.1.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
fresh "0.5.2"
merge-descriptors "1.0.1"
methods "~1.1.2"
on-finished "~2.3.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
parseurl "~1.3.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
path-to-regexp "0.1.7"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
proxy-addr "~2.0.5"
qs "6.7.0"
range-parser "~1.2.1"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
safe-buffer "5.1.2"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
send "0.17.1"
serve-static "1.14.1"
setprototypeof "1.1.1"
statuses "~1.5.0"
type-is "~1.6.18"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
utils-merge "1.0.1"
vary "~1.1.2"
extend-shallow@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/extend-shallow/-/extend-shallow-2.0.1.tgz#51af7d614ad9a9f610ea1bafbb989d6b1c56890f"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-Ua99YUrZqfYQ6huvu5idaxxWiQ8=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
is-extendable "^0.1.0"
extend-shallow@^3.0.0, extend-shallow@^3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/extend-shallow/-/extend-shallow-3.0.2.tgz#26a71aaf073b39fb2127172746131c2704028db8"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-Jqcarwc7OfshJxcnRhMcJwQCjbg=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
assign-symbols "^1.0.0"
is-extendable "^1.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
external-editor@^3.0.3:
version "3.1.0"
resolved "https://registry.yarnpkg.com/external-editor/-/external-editor-3.1.0.tgz#cb03f740befae03ea4d283caed2741a83f335495"
integrity sha512-hMQ4CX1p1izmuLYyZqLMO/qGNw10wSv9QDCPfzXfyFrOaCSSoRfqE1Kf1s5an66J5JZC62NewG+mK49jOCtQew==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
chardet "^0.7.0"
iconv-lite "^0.4.24"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
tmp "^0.0.33"
extglob@^2.0.4:
version "2.0.4"
resolved "https://registry.yarnpkg.com/extglob/-/extglob-2.0.4.tgz#ad00fe4dc612a9232e8718711dc5cb5ab0285543"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-Nmb6QXkELsuBr24CJSkilo6UHHgbekK5UiZgfE6UHD3Eb27YC6oD+bhcT+tJ6cl8dmsgdQxnWlcry8ksBIBLpw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
array-unique "^0.3.2"
define-property "^1.0.0"
expand-brackets "^2.1.4"
extend-shallow "^2.0.1"
fragment-cache "^0.2.1"
regex-not "^1.0.0"
snapdragon "^0.8.1"
to-regex "^3.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
fast-deep-equal@^3.1.1:
version "3.1.1"
resolved "https://registry.yarnpkg.com/fast-deep-equal/-/fast-deep-equal-3.1.1.tgz#545145077c501491e33b15ec408c294376e94ae4"
integrity sha512-8UEa58QDLauDNfpbrX55Q9jrGHThw2ZMdOky5Gl1CDtVeJDPVrG4Jxx1N8jw2gkWaff5UUuX1KJd+9zGe2B+ZA==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
fast-json-stable-stringify@^2.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "2.1.0"
resolved "https://registry.yarnpkg.com/fast-json-stable-stringify/-/fast-json-stable-stringify-2.1.0.tgz#874bf69c6f404c2b5d99c481341399fd55892633"
integrity sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
fast-levenshtein@~2.0.6:
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
version "2.0.6"
resolved "https://registry.yarnpkg.com/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz#3d8a5c66883a16a30ca8643e851f19baa7797917"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-PYpcZog6FqMMqGQ+hR8Zuqd5eRc=
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04: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
fastparse@^1.1.1:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.1.2"
resolved "https://registry.yarnpkg.com/fastparse/-/fastparse-1.1.2.tgz#91728c5a5942eced8531283c79441ee4122c35a9"
integrity sha512-483XLLxTVIwWK3QTrMGRqUfUpoOs/0hbQrl2oz4J0pAcm3A3bu84wxTFqGqkJzewCLdME38xJLJAxBABfQT8sQ==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
faye-websocket@^0.10.0:
version "0.10.0"
resolved "https://registry.yarnpkg.com/faye-websocket/-/faye-websocket-0.10.0.tgz#4e492f8d04dfb6f89003507f6edbf2d501e7c6f4"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-TkkvjQTftviQA1B/btvy1QHnxvQ=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
websocket-driver ">=0.5.1"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
faye-websocket@~0.11.1:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "0.11.3"
resolved "https://registry.yarnpkg.com/faye-websocket/-/faye-websocket-0.11.3.tgz#5c0e9a8968e8912c286639fde977a8b209f2508e"
integrity sha512-D2y4bovYpzziGgbHYtGCMjlJM36vAl/y+xUyn1C+FVx8szd1E+86KwVw6XvYSzOP8iMpm1X0I4xJD+QtUb36OA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
websocket-driver ">=0.5.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
figgy-pudding@^3.5.1:
version "3.5.1"
resolved "https://registry.yarnpkg.com/figgy-pudding/-/figgy-pudding-3.5.1.tgz#862470112901c727a0e495a80744bd5baa1d6790"
integrity sha512-vNKxJHTEKNThjfrdJwHc7brvM6eVevuO5nTj6ez8ZQ1qbXTvGthucRF7S4vf2cr71QVnT70V34v0S1DyQsti0w==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
figures@^3.0.0:
version "3.2.0"
resolved "https://registry.yarnpkg.com/figures/-/figures-3.2.0.tgz#625c18bd293c604dc4a8ddb2febf0c88341746af"
integrity sha512-yaduQFRKLXYOGgEn6AZau90j3ggSOyiqXU0F9JZfeXYhNa+Jk4X+s45A2zg5jns87GAFa34BBm2kXw4XpNcbdg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
escape-string-regexp "^1.0.5"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
file-entry-cache@^5.0.1:
version "5.0.1"
resolved "https://registry.yarnpkg.com/file-entry-cache/-/file-entry-cache-5.0.1.tgz#ca0f6efa6dd3d561333fb14515065c2fafdf439c"
integrity sha512-bCg29ictuBaKUwwArK4ouCaqDgLZcysCFLmM/Yn/FDoqndh/9vNuQfXRDvTuXKLxfD/JtZQGKFT8MGcJBK644g==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
flat-cache "^2.0.1"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
file-loader@^5.1.0:
version "5.1.0"
resolved "https://registry.yarnpkg.com/file-loader/-/file-loader-5.1.0.tgz#cb56c070efc0e40666424309bd0d9e45ac6f2bb8"
integrity sha512-u/VkLGskw3Ue59nyOwUwXI/6nuBCo7KBkniB/l7ICwr/7cPNGsL1WCXUp3GB0qgOOKU1TiP49bv4DZF/LJqprg==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
loader-utils "^1.4.0"
schema-utils "^2.5.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
file-uri-to-path@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/file-uri-to-path/-/file-uri-to-path-1.0.0.tgz#553a7b8446ff6f684359c445f1e37a05dacc33dd"
integrity sha512-0Zt+s3L7Vf1biwWZ29aARiVYLx7iMGnEUl9x33fbB/j3jR81u/O2LbqK+Bm1CDSNDKVtJ/YjwY7TUd5SkeLQLw==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
fill-range@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/fill-range/-/fill-range-4.0.0.tgz#d544811d428f98eb06a63dc402d2403c328c38f7"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-1USBHUKPmOsGpj3EAtJAPDKMOPc=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
extend-shallow "^2.0.1"
is-number "^3.0.0"
repeat-string "^1.6.1"
to-regex-range "^2.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
finalhandler@~1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/finalhandler/-/finalhandler-1.1.2.tgz#b7e7d000ffd11938d0fdb053506f6ebabe9f587d"
integrity sha512-aAWcW57uxVNrQZqFXjITpW3sIUQmHGG3qSb9mUah9MgMC4NeWhNOlNjXEYq3HjRAvL6arUviZGGJsBg6z0zsWA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
debug "2.6.9"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
encodeurl "~1.0.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
escape-html "~1.0.3"
on-finished "~2.3.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
parseurl "~1.3.3"
statuses "~1.5.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
unpipe "~1.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
find-cache-dir@^2.0.0, find-cache-dir@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/find-cache-dir/-/find-cache-dir-2.1.0.tgz#8d0f94cd13fe43c6c7c261a0d86115ca918c05f7"
integrity sha512-Tq6PixE0w/VMFfCgbONnkiQIVol/JJL7nRMi20fqzA4NRs9AfeqMGeRdPi3wIhYkxjeBaWh2rxwapn5Tu3IqOQ==
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
dependencies:
commondir "^1.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
make-dir "^2.0.0"
pkg-dir "^3.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
find-cache-dir@^3.0.0:
version "3.3.0"
resolved "https://registry.yarnpkg.com/find-cache-dir/-/find-cache-dir-3.3.0.tgz#4d74ed1fe9ef1731467ca24378e8f8f5c8b6ed11"
integrity sha512-PtXtQb7IrD8O+h6Cq1dbpJH5NzD8+9keN1zZ0YlpDzl1PwXEJEBj6u1Xa92t1Hwluoozd9TNKul5Hi2iqpsWwg==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
commondir "^1.0.1"
make-dir "^3.0.2"
pkg-dir "^4.1.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
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
find-up@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/find-up/-/find-up-3.0.0.tgz#49169f1d7993430646da61ecc5ae355c21c97b73"
integrity sha512-1yD6RmLI1XBfxugvORwlck6f75tYL+iR0jqwsOrOxMZyGYqUuDhJ0l4AXdO1iX/FTs9cBAMEk1gWSEx1kSbylg==
dependencies:
locate-path "^3.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
find-up@^4.0.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/find-up/-/find-up-4.1.0.tgz#97afe7d6cdc0bc5928584b7c8d7b16e8a9aa5d19"
integrity sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
locate-path "^5.0.0"
path-exists "^4.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
findup-sync@3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/findup-sync/-/findup-sync-3.0.0.tgz#17b108f9ee512dfb7a5c7f3c8b27ea9e1a9c08d1"
integrity sha512-YbffarhcicEhOrm4CtrwdKBdCuz576RLdhJDsIfvNtxUuhdRet1qZcsMjqbePtAseKdAnDyM/IyXbu7PRPRLYg==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
detect-file "^1.0.0"
is-glob "^4.0.0"
micromatch "^3.0.4"
resolve-dir "^1.0.1"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
flat-cache@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/flat-cache/-/flat-cache-2.0.1.tgz#5d296d6f04bda44a4630a301413bdbc2ec085ec0"
integrity sha512-LoQe6yDuUMDzQAEH8sgmh4Md6oZnc/7PjtwjNFSzveXqSHt6ka9fPBuso7IGf9Rz4uqnSnWiFH2B/zj24a5ReA==
dependencies:
flatted "^2.0.0"
rimraf "2.6.3"
write "1.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
flatted@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/flatted/-/flatted-2.0.1.tgz#69e57caa8f0eacbc281d2e2cb458d46fdb449e08"
integrity sha512-a1hQMktqW9Nmqr5aktAux3JMNqaucxGcjtjWnZLHX7yyPCmlSV3M54nGYbqT8K+0GhF3NBgmJCc3ma+WOgX8Jg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
flush-write-stream@^1.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.1.1"
resolved "https://registry.yarnpkg.com/flush-write-stream/-/flush-write-stream-1.1.1.tgz#8dd7d873a1babc207d94ead0c2e0e44276ebf2e8"
integrity sha512-3Z4XhFZ3992uIq0XOqb9AreonueSYphE6oYbpt5+3u06JWklbsPkNv3ZKkP9Bz/r+1MWCaMoSQ28P85+1Yc77w==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
inherits "^2.0.3"
readable-stream "^2.3.6"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
follow-redirects@^1.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.10.0"
resolved "https://registry.yarnpkg.com/follow-redirects/-/follow-redirects-1.10.0.tgz#01f5263aee921c6a54fb91667f08f4155ce169eb"
integrity sha512-4eyLK6s6lH32nOvLLwlIOnr9zrL8Sm+OvW4pVTJNoXeGzYIkHVf+pADQi+OJ0E67hiuSLezPVPyBcIZO50TmmQ==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
debug "^3.0.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
for-in@^1.0.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
version "1.0.2"
resolved "https://registry.yarnpkg.com/for-in/-/for-in-1.0.2.tgz#81068d295a8142ec0ac726c6e2200c30fb6d5e80"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-gQaNKVqBQuwKxybG4iAMMPttXoA=
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
forwarded@~0.1.2:
version "0.1.2"
resolved "https://registry.yarnpkg.com/forwarded/-/forwarded-0.1.2.tgz#98c23dab1175657b8c0573e8ceccd91b0ff18c84"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-mMI9qxF1ZXuMBXPozszZGw/xjIQ=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
fragment-cache@^0.2.1:
version "0.2.1"
resolved "https://registry.yarnpkg.com/fragment-cache/-/fragment-cache-0.2.1.tgz#4290fad27f13e89be7f33799c6bc5a0abfff0d19"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-QpD60n8T6Jvn8zeZxrxaCr//DRk=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
map-cache "^0.2.2"
fresh@0.5.2:
version "0.5.2"
resolved "https://registry.yarnpkg.com/fresh/-/fresh-0.5.2.tgz#3d8cadd90d976569fa835ab1f8e4b23a105605a7"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-PYyt2Q2XZWn6g1qx+OSyOhBWBac=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
from2@^2.1.0:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
version "2.3.0"
resolved "https://registry.yarnpkg.com/from2/-/from2-2.3.0.tgz#8bfb5502bde4a4d36cfdeea007fcca21d7e382af"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-i/tVAr3kpNNs/e6gB/zKIdfjgq8=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
inherits "^2.0.1"
readable-stream "^2.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
fs-minipass@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/fs-minipass/-/fs-minipass-2.1.0.tgz#7f5036fdbf12c63c169190cbe4199c852271f9fb"
integrity sha512-V/JgOLFCS+R6Vcq0slCuaeWEdNC3ouDlJMNIsacH2VtALiu9mV4LPrHc5cDl8k5aw6J8jwgWWpiTo5RYhmIzvg==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
minipass "^3.0.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
fs-write-stream-atomic@^1.0.8:
version "1.0.10"
resolved "https://registry.yarnpkg.com/fs-write-stream-atomic/-/fs-write-stream-atomic-1.0.10.tgz#b47df53493ef911df75731e70a9ded0189db40c9"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-tH31NJPvkR33VzHnCp3tAYnbQMk=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
graceful-fs "^4.1.2"
iferr "^0.1.5"
imurmurhash "^0.1.4"
readable-stream "1 || 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
fs.realpath@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/fs.realpath/-/fs.realpath-1.0.0.tgz#1504ad2523158caa40db4a2787cb01411994ea4f"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-FQStJSMVjKpA20onh8sBQRmU6k8=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
fsevents@^1.2.7:
version "1.2.11"
resolved "https://registry.yarnpkg.com/fsevents/-/fsevents-1.2.11.tgz#67bf57f4758f02ede88fb2a1712fef4d15358be3"
integrity sha512-+ux3lx6peh0BpvY0JebGyZoiR4D+oYzdPZMKJwkZ+sFkNJzpL7tXc/wehS49gUAxg3tmMHPHZkA8JU2rhhgDHw==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
bindings "^1.5.0"
nan "^2.12.1"
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
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
function-bind@^1.1.1:
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
version "1.1.1"
resolved "https://registry.yarnpkg.com/function-bind/-/function-bind-1.1.1.tgz#a56899d3ea3c9bab874bb9773b7c5ede92f4895d"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-yIovAzMX49sF8Yl58fSCWJ5svSLuaibPxXQJFLmBObTuCr0Mf1KiPopGM9NiFjiYBCbfaa2Fh6breQ6ANVTI0A==
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
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
functional-red-black-tree@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/functional-red-black-tree/-/functional-red-black-tree-1.0.1.tgz#1b0ab3bd553b2a0d6399d29c0e3ea0b252078327"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-GwqzvVU7Kg1jmdKcDj6gslIHgyc=
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
gensync@^1.0.0-beta.1:
version "1.0.0-beta.1"
resolved "https://registry.yarnpkg.com/gensync/-/gensync-1.0.0-beta.1.tgz#58f4361ff987e5ff6e1e7a210827aa371eaac269"
integrity sha512-r8EC6NO1sngH/zdD9fiRDLdcgnbayXah+mLgManTaIZJqEC1MZstmnox8KpnI2/fxQwrp5OpCOYWLp4rBl4Jcg==
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
get-caller-file@^1.0.1:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "1.0.3"
resolved "https://registry.yarnpkg.com/get-caller-file/-/get-caller-file-1.0.3.tgz#f978fa4c90d1dfe7ff2d6beda2a515e713bdcf4a"
integrity sha512-3t6rVToeoZfYSGd8YoLFR2DJkiQrIiUrGcjvFX2mDw3bn6k2OtwHN0TNCLbBO+w8qTvimhDkv+LSscbJY1vE6w==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
get-caller-file@^2.0.1:
version "2.0.5"
resolved "https://registry.yarnpkg.com/get-caller-file/-/get-caller-file-2.0.5.tgz#4f94412a82db32f36e3b0b9741f8a97feb031f7e"
integrity sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==
get-stream@^4.0.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/get-stream/-/get-stream-4.1.0.tgz#c1b255575f3dc21d59bfc79cd3d2b46b1c3a54b5"
integrity sha512-GMat4EJ5161kIy2HevLlr4luNjBgvmj413KaQA7jt4V8B4RDsfpHk7WQ9GVqfYyyx8OS/L66Kox+rJRNklLK7w==
dependencies:
pump "^3.0.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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
get-value@^2.0.3, get-value@^2.0.6:
version "2.0.6"
resolved "https://registry.yarnpkg.com/get-value/-/get-value-2.0.6.tgz#dc15ca1c672387ca76bd37ac0a395ba2042a2c28"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-3BXKHGcjh8p2vTesCjlbogQqLCg=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
glob-parent@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/glob-parent/-/glob-parent-3.1.0.tgz#9e6af6299d8d3bd2bd40430832bd113df906c5ae"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-nmr2KZ2NO9K9QEMIMr0RPfkGxa4=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
is-glob "^3.1.0"
path-dirname "^1.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
glob-parent@^5.0.0:
version "5.1.0"
resolved "https://registry.yarnpkg.com/glob-parent/-/glob-parent-5.1.0.tgz#5f4c1d1e748d30cd73ad2944b3577a81b081e8c2"
integrity sha512-qjtRgnIVmOfnKUE3NJAQEdk+lKrxfw8t5ke7SXtfMTHcjsBfOfWXCQfdb30zfDoZQ2IRSIiidmjtbHZPZ++Ihw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
is-glob "^4.0.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
glob@^7.0.3, glob@^7.1.3, glob@^7.1.4:
version "7.1.6"
resolved "https://registry.yarnpkg.com/glob/-/glob-7.1.6.tgz#141f33b81a7c2492e125594307480c46679278a6"
integrity sha512-LwaxwyZ72Lk7vZINtNNrywX0ZuLyStrdDtabefZKAY5ZGJhVtgdznluResxNmPitE0SAO+O26sWTHeKSI2wMBA==
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
dependencies:
fs.realpath "^1.0.0"
inflight "^1.0.4"
inherits "2"
minimatch "^3.0.4"
once "^1.3.0"
path-is-absolute "^1.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
global-modules@2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/global-modules/-/global-modules-2.0.0.tgz#997605ad2345f27f51539bea26574421215c7780"
integrity sha512-NGbfmJBp9x8IxyJSd1P+otYK8vonoJactOogrVfFRIAEY1ukil8RSKDz2Yo7wh1oihl51l/r6W4epkeKJHqL8A==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
global-prefix "^3.0.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
global-modules@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/global-modules/-/global-modules-1.0.0.tgz#6d770f0eb523ac78164d72b5e71a8877265cc3ea"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-sKzpEkf11GpOFuw0Zzjzmt4B4UZwjOcG757PPvrfhxcLFbq0wpsgpOqxpxtxFiCG4DtG93M6XRVbF2oGdev7bg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
global-prefix "^1.0.1"
is-windows "^1.0.1"
resolve-dir "^1.0.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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
global-prefix@^1.0.1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/global-prefix/-/global-prefix-1.0.2.tgz#dbf743c6c14992593c655568cb66ed32c0122ebe"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-2/dDxsFJklk8ZVVoy2btMsASLr4=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
expand-tilde "^2.0.2"
homedir-polyfill "^1.0.1"
ini "^1.3.4"
is-windows "^1.0.1"
which "^1.2.14"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
global-prefix@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/global-prefix/-/global-prefix-3.0.0.tgz#fc85f73064df69f50421f47f883fe5b913ba9b97"
integrity sha512-awConJSVCHVGND6x3tmMaKcQvwXLhjdkmomy2W+Goaui8YPgYgXJZewhg3fWC+DlfqqQuWg8AwqjGTD2nAPVWg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ini "^1.3.5"
kind-of "^6.0.2"
which "^1.3.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
globals@^11.1.0:
version "11.12.0"
resolved "https://registry.yarnpkg.com/globals/-/globals-11.12.0.tgz#ab8795338868a0babd8525758018c2a7eb95c42e"
integrity sha512-WOBp/EEGUiIsJSp7wcv/y6MO+lV9UoncWqxuFfm8eBwzWNgyfBd6Gz+IeKQ9jCmyhoH99g15M3T+QaVHFjizVA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
globals@^12.1.0:
version "12.3.0"
resolved "https://registry.yarnpkg.com/globals/-/globals-12.3.0.tgz#1e564ee5c4dded2ab098b0f88f24702a3c56be13"
integrity sha512-wAfjdLgFsPZsklLJvOBUBmzYE8/CwhEqSBEMRXA3qxIiNtyqvjYurAtIfDh6chlEPUfmTY3MnZh5Hfh4q0UlIw==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
type-fest "^0.8.1"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
globby@^6.1.0:
version "6.1.0"
resolved "https://registry.yarnpkg.com/globby/-/globby-6.1.0.tgz#f5a6d70e8395e21c858fb0489d64df02424d506c"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-9abXDoOV4hyFj7BInWTfAkJNUGw=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
array-union "^1.0.1"
glob "^7.0.3"
object-assign "^4.0.1"
pify "^2.0.0"
pinkie-promise "^2.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
graceful-fs@^4.1.11, graceful-fs@^4.1.15, graceful-fs@^4.1.2, graceful-fs@^4.2.2:
version "4.2.3"
resolved "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-4.2.3.tgz#4a12ff1b60376ef09862c2093edd908328be8423"
integrity sha512-a30VEBm4PEdx1dRB7MFK7BejejvCvBronbLjht+sHuGYj8PHs7M/5Z+rt5lw551vZ7yfTCj4Vuyy3mSJytDWRQ==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
handle-thing@^2.0.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
version "2.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
resolved "https://registry.yarnpkg.com/handle-thing/-/handle-thing-2.0.0.tgz#0e039695ff50c93fc288557d696f3c1dc6776754"
integrity sha512-d4sze1JNC454Wdo2fkuyzCr6aHcbL6PGGuFAz0Li/NcOm1tCHGnWDRmJP85dh9IhQErTc2svWFEX5xHIOo//kQ==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
has-flag@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/has-flag/-/has-flag-3.0.0.tgz#b5d454dc2199ae225699f3467e5a07f3b955bafd"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-tdRU3CGZriJWmfNGfloH87lVuv0=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
has-flag@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/has-flag/-/has-flag-4.0.0.tgz#944771fd9c81c81265c4d6941860da06bb59479b"
integrity sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
has-symbols@^1.0.0, has-symbols@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/has-symbols/-/has-symbols-1.0.1.tgz#9f5214758a44196c406d9bd76cebf81ec2dd31e8"
integrity sha512-PLcsoqu++dmEIZB+6totNFKq/7Do+Z0u4oT0zKOJNl3lYK6vGwwu2hjHs+68OEZbTjiUE9bgOABXbP/GvrS0Kg==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
has-value@^0.3.1:
version "0.3.1"
resolved "https://registry.yarnpkg.com/has-value/-/has-value-0.3.1.tgz#7b1f58bada62ca827ec0a2078025654845995e1f"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-ex9YutpiyoJ+wKIHgCVlSEWZXh8=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
get-value "^2.0.3"
has-values "^0.1.4"
isobject "^2.0.0"
has-value@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/has-value/-/has-value-1.0.0.tgz#18b281da585b1c5c51def24c930ed29a0be6b177"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-GLKB2lhbHFxR3vJMkw7SmgvmsXc=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
get-value "^2.0.6"
has-values "^1.0.0"
isobject "^3.0.0"
has-values@^0.1.4:
version "0.1.4"
resolved "https://registry.yarnpkg.com/has-values/-/has-values-0.1.4.tgz#6d61de95d91dfca9b9a02089ad384bff8f62b771"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-bWHeldkd/Km5oCCJrThL/49it3E=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
has-values@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/has-values/-/has-values-1.0.0.tgz#95b0b63fec2146619a6fe57fe75628d5a39efe4f"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-lbC2P+whRmGab+V/51Yo1aOe/k8=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
is-number "^3.0.0"
kind-of "^4.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
has@^1.0.3:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "1.0.3"
resolved "https://registry.yarnpkg.com/has/-/has-1.0.3.tgz#722d7cbfc1f6aa8241f16dd814e011e1f41e8796"
integrity sha512-f2dvO0VU6Oej7RkWJGrehjbzMAjFp5/VKPp5tTpWIV4JHHZK1/BxbFRtf/siA2SWTe09caDmVtYYzWEIbBS4zw==
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
dependencies:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
function-bind "^1.1.1"
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
hash-base@^3.0.0:
version "3.0.4"
resolved "https://registry.yarnpkg.com/hash-base/-/hash-base-3.0.4.tgz#5fc8686847ecd73499403319a6b0a3f3f6ae4918"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-X8hoaEfs1zSZQDMZprCj8/auSRg=
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
dependencies:
inherits "^2.0.1"
safe-buffer "^5.0.1"
hash.js@^1.0.0, hash.js@^1.0.3:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.1.7"
resolved "https://registry.yarnpkg.com/hash.js/-/hash.js-1.1.7.tgz#0babca538e8d4ee4a0f8988d68866537a003cf42"
integrity sha512-taOaskGt4z4SOANNseOviYDvjEJinIkRgmp7LbKP2YTTmVxWBl87s/uzK9r+44BclBSp2X7K1hqeNfz9JbBeXA==
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
dependencies:
inherits "^2.0.3"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
minimalistic-assert "^1.0.1"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
he@1.2.x:
version "1.2.0"
resolved "https://registry.yarnpkg.com/he/-/he-1.2.0.tgz#84ae65fa7eafb165fddb61566ae14baf05664f0f"
integrity sha512-F/1DnUGPopORZi0ni+CvrCgHQ5FyEAHRLSApuYWMmrbSwoN2Mn/7k+Gl38gJnR7yyDZk6WLXwiGod1JOWNDKGw==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -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
hmac-drbg@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/hmac-drbg/-/hmac-drbg-1.0.1.tgz#d2745701025a6c775a6c545793ed502fc0c649a1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-0nRXAQJabHdabFRXk+1QL8DGSaE=
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
dependencies:
hash.js "^1.0.3"
minimalistic-assert "^1.0.0"
minimalistic-crypto-utils "^1.0.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
homedir-polyfill@^1.0.1:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.0.3"
resolved "https://registry.yarnpkg.com/homedir-polyfill/-/homedir-polyfill-1.0.3.tgz#743298cef4e5af3e194161fbadcc2151d3a058e8"
integrity sha512-eSmmWE5bZTK2Nou4g0AI3zZ9rswp7GRKoKXS1BLUkvPviOqs4YTN1djQIqrXy9k5gEtdLPy86JjRwsNM9tnDcA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
parse-passwd "^1.0.0"
hpack.js@^2.1.6:
version "2.1.6"
resolved "https://registry.yarnpkg.com/hpack.js/-/hpack.js-2.1.6.tgz#87774c0949e513f42e84575b3c45681fade2a0b2"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-h3dMCUnlE/QuhFdbPEVoH63ioLI=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
inherits "^2.0.1"
obuf "^1.0.0"
readable-stream "^2.0.1"
wbuf "^1.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
html-entities@^1.2.1:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
version "1.2.1"
resolved "https://registry.yarnpkg.com/html-entities/-/html-entities-1.2.1.tgz#0df29351f0721163515dfb9e5543e5f6eed5162f"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-DfKTUfByEWNRXfueVUPl9u7VFi8=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
html-loader@^0.5.5:
version "0.5.5"
resolved "https://registry.yarnpkg.com/html-loader/-/html-loader-0.5.5.tgz#6356dbeb0c49756d8ebd5ca327f16ff06ab5faea"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-7hIW7YinOYUpo//kSYcPB6dCKoceKLmOwjEMmhIobHuWGDVl0Nwe4l68mdG/Ru0wcUxQjVMEoZpkalZ/SE7zog==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
es6-templates "^0.2.3"
fastparse "^1.1.1"
html-minifier "^3.5.8"
loader-utils "^1.1.0"
object-assign "^4.1.1"
html-minifier@^3.2.3, html-minifier@^3.5.8:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "3.5.21"
resolved "https://registry.yarnpkg.com/html-minifier/-/html-minifier-3.5.21.tgz#d0040e054730e354db008463593194015212d20c"
integrity sha512-LKUKwuJDhxNa3uf/LPR/KVjm/l3rBqtYeCOAekvG8F1vItxMUpueGd94i/asDDr8/1u7InxzFA5EeGjhhG5mMA==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
camel-case "3.0.x"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
clean-css "4.2.x"
commander "2.17.x"
he "1.2.x"
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
param-case "2.1.x"
relateurl "0.2.x"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
uglify-js "3.4.x"
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
html-webpack-plugin@^3.2.0:
version "3.2.0"
resolved "https://registry.yarnpkg.com/html-webpack-plugin/-/html-webpack-plugin-3.2.0.tgz#b01abbd723acaaa7b37b6af4492ebda03d9dd37b"
integrity sha1-sBq71yOsqqeze2r0SS69oD2d03s=
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
html-minifier "^3.2.3"
loader-utils "^0.2.16"
lodash "^4.17.3"
pretty-error "^2.0.2"
tapable "^1.0.0"
toposort "^1.0.0"
util.promisify "1.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
htmlparser2@^3.3.0:
version "3.10.1"
resolved "https://registry.yarnpkg.com/htmlparser2/-/htmlparser2-3.10.1.tgz#bd679dc3f59897b6a34bb10749c855bb53a9392f"
integrity sha512-IgieNijUMbkDovyoKObU1DUhm1iwNYE/fuifEoEHfd1oZKZDaONBSkal7Y01shxsM49R4XaMdGez3WnF9UfiCQ==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
domelementtype "^1.3.1"
domhandler "^2.3.0"
domutils "^1.5.1"
entities "^1.1.1"
inherits "^2.0.1"
readable-stream "^3.1.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
http-deceiver@^1.2.7:
version "1.2.7"
resolved "https://registry.yarnpkg.com/http-deceiver/-/http-deceiver-1.2.7.tgz#fa7168944ab9a519d337cb0bec7284dc3e723d87"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-+nFolEq5pRnTN8sL7HKE3D5yPYc=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
http-errors@1.7.2:
version "1.7.2"
resolved "https://registry.yarnpkg.com/http-errors/-/http-errors-1.7.2.tgz#4f5029cf13239f31036e5b2e55292bcfbcc85c8f"
integrity sha512-uUQBt3H/cSIVfch6i1EuPNy/YsRSOUBXTVfZ+yR7Zjez3qjBz6i9+i4zjNaoqcoFVI4lQJ5plg63TvGfRSDCRg==
dependencies:
depd "~1.1.2"
inherits "2.0.3"
setprototypeof "1.1.1"
statuses ">= 1.5.0 < 2"
toidentifier "1.0.0"
http-errors@~1.6.2:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "1.6.3"
resolved "https://registry.yarnpkg.com/http-errors/-/http-errors-1.6.3.tgz#8b55680bb4be283a0b5bf4ea2e38580be1d9320d"
integrity sha1-i1VoC7S+KDoLW/TqLjhYC+HZMg0=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
depd "~1.1.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
inherits "2.0.3"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
setprototypeof "1.1.0"
statuses ">= 1.4.0 < 2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
http-errors@~1.7.2:
version "1.7.3"
resolved "https://registry.yarnpkg.com/http-errors/-/http-errors-1.7.3.tgz#6c619e4f9c60308c38519498c14fbb10aacebb06"
integrity sha512-ZTTX0MWrsQ2ZAhA1cejAwDLycFsd7I7nVtnkT3Ol0aqodaKW+0CTZDQ1uBv5whptCnc8e8HeRRJxRs0kmm/Qfw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
depd "~1.1.2"
inherits "2.0.4"
setprototypeof "1.1.1"
statuses ">= 1.5.0 < 2"
toidentifier "1.0.0"
"http-parser-js@>=0.4.0 <0.4.11":
version "0.4.10"
resolved "https://registry.yarnpkg.com/http-parser-js/-/http-parser-js-0.4.10.tgz#92c9c1374c35085f75db359ec56cc257cbb93fa4"
integrity sha1-ksnBN0w1CF912zWexWzCV8u5P6Q=
http-proxy-middleware@0.19.1:
version "0.19.1"
resolved "https://registry.yarnpkg.com/http-proxy-middleware/-/http-proxy-middleware-0.19.1.tgz#183c7dc4aa1479150306498c210cdaf96080a43a"
integrity sha512-yHYTgWMQO8VvwNS22eLLloAkvungsKdKTLO8AJlftYIKNfJr3GK3zK0ZCfzDDGUBttdGc8xFy1mCitvNKQtC3Q==
dependencies:
http-proxy "^1.17.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
is-glob "^4.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
lodash "^4.17.11"
micromatch "^3.1.10"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
http-proxy@^1.17.0:
version "1.18.0"
resolved "https://registry.yarnpkg.com/http-proxy/-/http-proxy-1.18.0.tgz#dbe55f63e75a347db7f3d99974f2692a314a6a3a"
integrity sha512-84I2iJM/n1d4Hdgc6y2+qY5mDaz2PUVjlg9znE9byl+q0uC3DeByqBGReQu5tpLK0TAqTIXScRUV+dg7+bUPpQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
eventemitter3 "^4.0.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
follow-redirects "^1.0.0"
requires-port "^1.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
https-browserify@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/https-browserify/-/https-browserify-1.0.0.tgz#ec06c10e0a34c0f2faf199f7fd7fc78fffd03c73"
integrity sha1-7AbBDgo0wPL68Zn3/X/Hj//QPHM=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
iconv-lite@0.4.24, iconv-lite@^0.4.24:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "0.4.24"
resolved "https://registry.yarnpkg.com/iconv-lite/-/iconv-lite-0.4.24.tgz#2022b4b25fbddc21d2f524974a474aafe733908b"
integrity sha512-v3MXnZAcvnywkTUEZomIActle7RXXeedOR31wwl7VlyoXO4Qi9arvSenNQWne1TcRwhCL1HwLI21bEqdpj8/rA==
dependencies:
safer-buffer ">= 2.1.2 < 3"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
icss-utils@^4.0.0, icss-utils@^4.1.1:
version "4.1.1"
resolved "https://registry.yarnpkg.com/icss-utils/-/icss-utils-4.1.1.tgz#21170b53789ee27447c2f47dd683081403f9a467"
integrity sha512-4aFq7wvWyMHKgxsH8QQtGpvbASCf+eM3wPRLI6R+MgAnTCZ6STYsRvttLvRWK0Nfif5piF394St3HeJDaljGPA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
postcss "^7.0.14"
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
ieee754@^1.1.4:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.1.13"
resolved "https://registry.yarnpkg.com/ieee754/-/ieee754-1.1.13.tgz#ec168558e95aa181fd87d37f55c32bbcb6708b84"
integrity sha512-4vf7I2LYV/HaWerSo3XmlMkp5eZ83i+/CDluXi/IGTs/O1sejBNhTtnxzmRZfvOUqj7lZjqHkeTvpgSFDlWZTg==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
iferr@^0.1.5:
version "0.1.5"
resolved "https://registry.yarnpkg.com/iferr/-/iferr-0.1.5.tgz#c60eed69e6d8fdb6b3104a1fcbca1c192dc5b501"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-xg7taebY/bazEEofy8ocGS3FtQE=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ignore@^4.0.6:
version "4.0.6"
resolved "https://registry.yarnpkg.com/ignore/-/ignore-4.0.6.tgz#750e3db5862087b4737ebac8207ffd1ef27b25fc"
integrity sha512-cyFDKrqc/YdcWFniJhzI42+AzS+gNwmUzOSFcRCQYwySuBBBy/KjuxWLZ/FHEH6Moq1NizMOBWyTcv8O4OZIMg==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
import-fresh@^3.0.0:
version "3.2.1"
resolved "https://registry.yarnpkg.com/import-fresh/-/import-fresh-3.2.1.tgz#633ff618506e793af5ac91bf48b72677e15cbe66"
integrity sha512-6e1q1cnWP2RXD9/keSkxHScg508CdXqXWgWBaETNhyuBFz+kUZlKboh+ISK+bU++DmbHimVBrOz/zzPe0sZ3sQ==
dependencies:
parent-module "^1.0.0"
resolve-from "^4.0.0"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
import-local@2.0.0, import-local@^2.0.0:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "2.0.0"
resolved "https://registry.yarnpkg.com/import-local/-/import-local-2.0.0.tgz#55070be38a5993cf18ef6db7e961f5bee5c5a09d"
integrity sha512-b6s04m3O+s3CGSbqDIyP4R6aAwAeYlVq9+WUWep6iHa8ETRf9yei1U48C5MmfJmV9AiLYYBKPMq/W+/WRpQmCQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
pkg-dir "^3.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
resolve-cwd "^2.0.0"
imurmurhash@^0.1.4:
version "0.1.4"
resolved "https://registry.yarnpkg.com/imurmurhash/-/imurmurhash-0.1.4.tgz#9218b9b2b928a238b13dc4fb6b6d576f231453ea"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-khi5srkoojixPcT7a21XbyMUU+o=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
indent-string@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/indent-string/-/indent-string-4.0.0.tgz#624f8f4497d619b2d9768531d58f4122854d7251"
integrity sha512-EdDDZu4A2OyIK7Lr/2zG+w5jmbuk1DVBnEwREQvBzspBJkCEbRa8GxU1lghYcaGJCnRWibjDXlq779X1/y5xwg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
indexes-of@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/indexes-of/-/indexes-of-1.0.1.tgz#f30f716c8e2bd346c7b67d3df3915566a7c05607"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-8w9xbI4r00bHtn0985FVZqfAVgc=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
infer-owner@^1.0.3, infer-owner@^1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/infer-owner/-/infer-owner-1.0.4.tgz#c4cefcaa8e51051c2a40ba2ce8a3d27295af9467"
integrity sha512-IClj+Xz94+d7irH5qRyfJonOdfTzuDaifE6ZPWfx0N0+/ATZCbuTPq2prFl526urkQd90WyUKIh1DfBQ2hMz9A==
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
inflight@^1.0.4:
version "1.0.6"
resolved "https://registry.yarnpkg.com/inflight/-/inflight-1.0.6.tgz#49bd6331d7d02d0c09bc910a1075ba8165b56df9"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-Sb1jMdfQLQwJvJEKEHW6gWW1bfk=
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
dependencies:
once "^1.3.0"
wrappy "1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
inherits@2, inherits@2.0.4, inherits@^2.0.1, inherits@^2.0.3, inherits@~2.0.1, inherits@~2.0.3:
version "2.0.4"
resolved "https://registry.yarnpkg.com/inherits/-/inherits-2.0.4.tgz#0fa2c64f932917c3433a0ded55363aae37416b7c"
integrity sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==
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
inherits@2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/inherits/-/inherits-2.0.1.tgz#b17d08d326b4423e568eff719f91b0b1cbdf69f1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-sX0I0ya0Qj5Wjv9xn5GwscvfafE=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
inherits@2.0.3:
version "2.0.3"
resolved "https://registry.yarnpkg.com/inherits/-/inherits-2.0.3.tgz#633c2c83e3da42a502f52466022480f4208261de"
integrity sha1-Yzwsg+PaQqUC9SRmAiSA9CCCYd4=
ini@^1.3.4, ini@^1.3.5:
version "1.3.5"
resolved "https://registry.yarnpkg.com/ini/-/ini-1.3.5.tgz#eee25f56db1c9ec6085e0c22778083f596abf927"
integrity sha512-RZY5huIKCMRWDUqZlEi72f/lmXKMvuszcMBduliQ3nnWbx9X/ZBQO7DijMEYS9EhHBb2qacRUMtC7svLwe0lcw==
inquirer@^7.0.0:
version "7.0.5"
resolved "https://registry.yarnpkg.com/inquirer/-/inquirer-7.0.5.tgz#fb95b238ba19966c1a1f55db53c3f0ce5c9e4275"
integrity sha512-6Z5cP+LAO0rzNE7xWjWtT84jxKa5ScLEGLgegPXeO3dGeU8lNe5Ii7SlXH6KVtLGlDuaEhsvsFjrjWjw8j5lFg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ansi-escapes "^4.2.1"
chalk "^3.0.0"
cli-cursor "^3.1.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
cli-width "^2.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
external-editor "^3.0.3"
figures "^3.0.0"
lodash "^4.17.15"
mute-stream "0.0.8"
run-async "^2.4.0"
rxjs "^6.5.3"
string-width "^4.1.0"
strip-ansi "^6.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
through "^2.3.6"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
internal-ip@^4.3.0:
version "4.3.0"
resolved "https://registry.yarnpkg.com/internal-ip/-/internal-ip-4.3.0.tgz#845452baad9d2ca3b69c635a137acb9a0dad0907"
integrity sha512-S1zBo1D6zcsyuC6PMmY5+55YMILQ9av8lotMx447Bq6SAgo/sDK6y6uUKmuYhW7eacnIhFfsPmCNYdDzsnnDCg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
default-gateway "^4.2.0"
ipaddr.js "^1.9.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
interpret@1.2.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/interpret/-/interpret-1.2.0.tgz#d5061a6224be58e8083985f5014d844359576296"
integrity sha512-mT34yGKMNceBQUoVn7iCDKDntA7SC6gycMAWzGx1z/CMCTV7b2AAtXlo3nRyHZ1FelRkQbQjprHSYGwzLtkVbw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
invariant@^2.2.2, invariant@^2.2.4:
version "2.2.4"
resolved "https://registry.yarnpkg.com/invariant/-/invariant-2.2.4.tgz#610f3c92c9359ce1db616e538008d23ff35158e6"
integrity sha512-phJfQVBuaJM5raOpJjSfkiD6BpbCE4Ns//LaXl6wGYtUBY83nWS6Rf9tXm2e8VaK60JEjYldbPif/A2B1C2gNA==
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
dependencies:
loose-envify "^1.0.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
invert-kv@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/invert-kv/-/invert-kv-2.0.0.tgz#7393f5afa59ec9ff5f67a27620d11c226e3eec02"
integrity sha512-wPVv/y/QQ/Uiirj/vh3oP+1Ww+AWehmi1g5fFWGPF6IpCBCDVrhgHRMvrLfdYcwDh3QJbGXDW4JAuzxElLSqKA==
ip-regex@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/ip-regex/-/ip-regex-2.1.0.tgz#fa78bf5d2e6913c911ce9f819ee5146bb6d844e9"
integrity sha1-+ni/XS5pE8kRzp+BnuUUa7bYROk=
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
ip@^1.1.0, ip@^1.1.5:
version "1.1.5"
resolved "https://registry.yarnpkg.com/ip/-/ip-1.1.5.tgz#bdded70114290828c0a039e72ef25f5aaec4354a"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-vd7XARQpCCjAoDnnLvJfWq7ENUo=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ipaddr.js@1.9.1, ipaddr.js@^1.9.0:
version "1.9.1"
resolved "https://registry.yarnpkg.com/ipaddr.js/-/ipaddr.js-1.9.1.tgz#bff38543eeb8984825079ff3a2a8e6cbd46781b3"
integrity sha512-0KI/607xoxSToH7GjN1FfSbLoU0+btTicjsQSWQlh/hZykN8KpmMf7uYwPW3R+akZ6R/w18ZlXSHBYXiYUPO3g==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
is-absolute-url@^3.0.3:
version "3.0.3"
resolved "https://registry.yarnpkg.com/is-absolute-url/-/is-absolute-url-3.0.3.tgz#96c6a22b6a23929b11ea0afb1836c36ad4a5d698"
integrity sha512-opmNIX7uFnS96NtPmhWQgQx6/NYFgsUXYMllcfzwWKUMwfo8kku1TvE6hkNcH+Q1ts5cMVrsY7j0bxXQDciu9Q==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
is-accessor-descriptor@^0.1.6:
version "0.1.6"
resolved "https://registry.yarnpkg.com/is-accessor-descriptor/-/is-accessor-descriptor-0.1.6.tgz#a9e12cb3ae8d876727eeef3843f8a0897b5c98d6"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-qeEss66Nh2cn7u84Q/igiXtcmNY=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
kind-of "^3.0.2"
is-accessor-descriptor@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-accessor-descriptor/-/is-accessor-descriptor-1.0.0.tgz#169c2f6d3df1f992618072365c9b0ea1f6878656"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-m5hnHTkcVsPfqx3AKlyttIPb7J+XykHvJP2B9bZDjlhLIoEq4XoK64Vg7boZlVWYK6LUY94dYPEE7Lh0ZkZKcQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
kind-of "^6.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
is-arguments@^1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/is-arguments/-/is-arguments-1.0.4.tgz#3faf966c7cba0ff437fb31f6250082fcf0448cf3"
integrity sha512-xPh0Rmt8NE65sNzvyUmWgI1tz3mKq74lGA0mL8LYZcoIzKOzDh6HmrYm3d18k60nHerC8A9Km8kYu87zfSFnLA==
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
is-binary-path@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/is-binary-path/-/is-binary-path-1.0.1.tgz#75f16642b480f187a711c814161fd3a4a7655898"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-dfFmQrSA8YenEcgUFh/TpKdlWJg=
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
dependencies:
binary-extensions "^1.0.0"
is-buffer@^1.1.5:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "1.1.6"
resolved "https://registry.yarnpkg.com/is-buffer/-/is-buffer-1.1.6.tgz#efaa2ea9daa0d7ab2ea13a97b2b8ad51fefbe8be"
integrity sha512-NcdALwpXkTm5Zvvbk7owOUSvVvBKDgKP5/ewfXEznmQFfs4ZRmanOeKBTjRVjka3QFoN6XJ+9F3USqfHqTaU5w==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
is-callable@^1.1.4, is-callable@^1.1.5:
version "1.1.5"
resolved "https://registry.yarnpkg.com/is-callable/-/is-callable-1.1.5.tgz#f7e46b596890456db74e7f6e976cb3273d06faab"
integrity sha512-ESKv5sMCJB2jnHTWZ3O5itG+O128Hsus4K4Qh1h2/cgn2vbgnLSVqfV46AeJA9D5EeeLa9w81KUXMtn34zhX+Q==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
is-data-descriptor@^0.1.4:
version "0.1.4"
resolved "https://registry.yarnpkg.com/is-data-descriptor/-/is-data-descriptor-0.1.4.tgz#0b5ee648388e2c860282e793f1856fec3f301b56"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-C17mSDiOLIYCgueT8YVv7D8wG1Y=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
kind-of "^3.0.2"
is-data-descriptor@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-data-descriptor/-/is-data-descriptor-1.0.0.tgz#d84876321d0e7add03990406abbbbd36ba9268c7"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-jbRXy1FmtAoCjQkVmIVYwuuqDFUbaOeDjmed1tOGPrsMhtJA4rD9tkgA0F1qJ3gRFRXcHYVkdeaP50Q5rE/jLQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
kind-of "^6.0.0"
is-date-object@^1.0.1:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/is-date-object/-/is-date-object-1.0.2.tgz#bda736f2cd8fd06d32844e7743bfa7494c3bfd7e"
integrity sha512-USlDT524woQ08aoZFzh3/Z6ch9Y/EWXEHQ/AaRN0SkKq4t2Jw2R2339tSXmwuVoY7LLlBCbOIlx2myP/L5zk0g==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
is-descriptor@^0.1.0:
version "0.1.6"
resolved "https://registry.yarnpkg.com/is-descriptor/-/is-descriptor-0.1.6.tgz#366d8240dde487ca51823b1ab9f07a10a78251ca"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-avDYr0SB3DwO9zsMov0gKCESFYqCnE4hq/4z3TdUlukEy5t9C0YRq7HLrsN52NAcqXKaepeCD0n+B0arnVG3Hg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
is-accessor-descriptor "^0.1.6"
is-data-descriptor "^0.1.4"
kind-of "^5.0.0"
is-descriptor@^1.0.0, is-descriptor@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/is-descriptor/-/is-descriptor-1.0.2.tgz#3b159746a66604b04f8c81524ba365c5f14d86ec"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-2eis5WqQGV7peooDyLmNEPUrps9+SXX5c9pL3xEB+4e9HnGuDa7mB7kHxHw4CbqS9k1T2hOH3miL8n8WtiYVtg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
is-accessor-descriptor "^1.0.0"
is-data-descriptor "^1.0.0"
kind-of "^6.0.2"
is-extendable@^0.1.0, is-extendable@^0.1.1:
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
version "0.1.1"
resolved "https://registry.yarnpkg.com/is-extendable/-/is-extendable-0.1.1.tgz#62b110e289a471418e3ec36a617d472e301dfc89"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-YrEQ4omkcUGOPsNqYX1HLjAd/Ik=
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
is-extendable@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/is-extendable/-/is-extendable-1.0.1.tgz#a7470f9e426733d81bd81e1155264e3a3507cab4"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-arnXMxT1hhoKo9k1LZdmlNyJdDDfy2v0fXjFlmok4+i8ul/6WlbVge9bhM74OpNPQPMGUToDtz+KXa1PneJxOA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
is-plain-object "^2.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
is-extglob@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-extglob/-/is-extglob-1.0.0.tgz#ac468177c4943405a092fc8f29760c6ffc6206c0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-rEaBd8SUNAWgkvyPKXYMb/xiBsA=
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
is-extglob@^2.1.0, is-extglob@^2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/is-extglob/-/is-extglob-2.1.1.tgz#a88c02535791f02ed37c76a1b9ea9773c833f8c2"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-qIwCU1eR8C7TfHahueqXc8gz+MI=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
is-fullwidth-code-point@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-fullwidth-code-point/-/is-fullwidth-code-point-1.0.0.tgz#ef9e31386f031a7f0d643af82fde50c457ef00cb"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-754xOG8DGn8NZDr4L95QxFfvAMs=
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
dependencies:
number-is-nan "^1.0.0"
is-fullwidth-code-point@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/is-fullwidth-code-point/-/is-fullwidth-code-point-2.0.0.tgz#a3b30a5c4f199183167aaab93beefae3ddfb654f"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-o7MKXE8ZkYMWeqq5O+764937ZU8=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
is-fullwidth-code-point@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz#f116f8064fe90b3f7844a38997c0b75051269f1d"
integrity sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==
is-glob@^2.0.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
version "2.0.1"
resolved "https://registry.yarnpkg.com/is-glob/-/is-glob-2.0.1.tgz#d096f926a3ded5600f3fdfd91198cb0888c2d863"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-0Jb5JqPe1WAPP9/ZEZjLCIjC2GM=
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
dependencies:
is-extglob "^1.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
is-glob@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/is-glob/-/is-glob-3.1.0.tgz#7ba5ae24217804ac70707b96922567486cc3e84a"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-e6WuJCF4BKxwcHuWkiVnSGzD6Eo=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
is-extglob "^2.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
is-glob@^4.0.0, is-glob@^4.0.1:
version "4.0.1"
resolved "https://registry.yarnpkg.com/is-glob/-/is-glob-4.0.1.tgz#7567dbe9f2f5e2467bc77ab83c4a29482407a5dc"
integrity sha512-5G0tKtBTFImOqDnLB2hG6Bp2qcKEFduo4tZu9MT/H6NQv/ghhy30o55ufafxJ/LdH79LLs2Kfrn85TLKyA7BUg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
is-extglob "^2.1.1"
A little more UI refactor, cleanup, eslint more strict (#54) * A little more UI refactor, cleanup, eslint more strict * Split out imports for jQuery components and put them where needed. * No longer do all of it in application module. * Prepares better for code splitting. * Split out video player dialog * Simplifies jquery-ui dependencies for code splitting * Simplifies code * Configure to generate more, but smaller bundles. * Setup some more strict eslint settings * Fix css to import rather than require * Change settings to correctly support tree shaking in production build Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Remove “old” code from TimeFormatter * Accidentally left behind due to overlapping PRs Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-26 01:18:56 -04:00
is-invalid-path@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/is-invalid-path/-/is-invalid-path-0.1.0.tgz#307a855b3cf1a938b44ea70d2c61106053714f34"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-MHqFWzzxqTi0TqcNLGEQYFNxTzQ=
A little more UI refactor, cleanup, eslint more strict (#54) * A little more UI refactor, cleanup, eslint more strict * Split out imports for jQuery components and put them where needed. * No longer do all of it in application module. * Prepares better for code splitting. * Split out video player dialog * Simplifies jquery-ui dependencies for code splitting * Simplifies code * Configure to generate more, but smaller bundles. * Setup some more strict eslint settings * Fix css to import rather than require * Change settings to correctly support tree shaking in production build Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Remove “old” code from TimeFormatter * Accidentally left behind due to overlapping PRs Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-26 01:18:56 -04:00
dependencies:
is-glob "^2.0.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
is-number@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/is-number/-/is-number-3.0.0.tgz#24fd6201a4782cf50561c810276afc7d12d71195"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-JP1iAaR4LPUFYcgQJ2r8fRLXEZU=
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
dependencies:
kind-of "^3.0.2"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
is-path-cwd@^2.0.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/is-path-cwd/-/is-path-cwd-2.2.0.tgz#67d43b82664a7b5191fd9119127eb300048a9fdb"
integrity sha512-w942bTcih8fdJPJmQHFzkS76NEP8Kzzvmw92cXsazb8intwLqPibPPdXf4ANdKV3rYMuuQYGIWtvz9JilB3NFQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
is-path-in-cwd@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/is-path-in-cwd/-/is-path-in-cwd-2.1.0.tgz#bfe2dca26c69f397265a4009963602935a053acb"
integrity sha512-rNocXHgipO+rvnP6dk3zI20RpOtrAM/kzbB258Uw5BWr3TpXi861yzjo16Dn4hUox07iw5AyeMLHWsujkjzvRQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
is-path-inside "^2.1.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
is-path-inside@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/is-path-inside/-/is-path-inside-2.1.0.tgz#7c9810587d659a40d27bcdb4d5616eab059494b2"
integrity sha512-wiyhTzfDWsvwAW53OBWF5zuvaOGlZ6PwYxAbPVDhpm+gM09xKQGjBq/8uYN12aDvMxnAnq3dxTyoSoRNmg5YFg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
path-is-inside "^1.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
is-plain-object@^2.0.3, is-plain-object@^2.0.4:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
version "2.0.4"
resolved "https://registry.yarnpkg.com/is-plain-object/-/is-plain-object-2.0.4.tgz#2c163b3fafb1b606d9d17928f05c2a1c38e07677"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-h5PpgXkWitc38BBMYawTYMWJHFZJVnBquFE57xFpjB8pJFiF6gZ+bU+WyI/yqXiFR5mdLsgYNaPe8uao6Uv9Og==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
isobject "^3.0.1"
is-promise@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/is-promise/-/is-promise-2.1.0.tgz#79a2a9ece7f096e80f36d2b2f3bc16c1ff4bf3fa"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-eaKp7OfwlugPNtKy87wWwf9L8/o=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
is-regex@^1.0.4, is-regex@^1.0.5:
version "1.0.5"
resolved "https://registry.yarnpkg.com/is-regex/-/is-regex-1.0.5.tgz#39d589a358bf18967f726967120b8fc1aed74eae"
integrity sha512-vlKW17SNq44owv5AQR3Cq0bQPEb8+kF3UKZ2fiZNOWtztYE5i0CzCZxFDwO58qAOWtxdBRVO/V5Qin1wjCqFYQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
has "^1.0.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
is-stream@^1.1.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
version "1.1.0"
resolved "https://registry.yarnpkg.com/is-stream/-/is-stream-1.1.0.tgz#12d4a3dd4e68e0b79ceb8dbc84173ae80d91ca44"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-EtSj3U5o4Lec6428hBc66A2RykQ=
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
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
is-symbol@^1.0.2:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.0.3"
resolved "https://registry.yarnpkg.com/is-symbol/-/is-symbol-1.0.3.tgz#38e1014b9e6329be0de9d24a414fd7441ec61937"
integrity sha512-OwijhaRSgqvhm/0ZdAcXNZt9lYdKFpcRDT5ULUuYXPoT794UNOdU+gpT6Rzo7b4V2HUl/op6GqY894AZwv9faQ==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
has-symbols "^1.0.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
A little more UI refactor, cleanup, eslint more strict (#54) * A little more UI refactor, cleanup, eslint more strict * Split out imports for jQuery components and put them where needed. * No longer do all of it in application module. * Prepares better for code splitting. * Split out video player dialog * Simplifies jquery-ui dependencies for code splitting * Simplifies code * Configure to generate more, but smaller bundles. * Setup some more strict eslint settings * Fix css to import rather than require * Change settings to correctly support tree shaking in production build Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Remove “old” code from TimeFormatter * Accidentally left behind due to overlapping PRs Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-26 01:18:56 -04:00
is-valid-path@^0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/is-valid-path/-/is-valid-path-0.1.1.tgz#110f9ff74c37f663e1ec7915eb451f2db93ac9df"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-EQ+f90w39mPh7HkV60UfLbk6yd8=
A little more UI refactor, cleanup, eslint more strict (#54) * A little more UI refactor, cleanup, eslint more strict * Split out imports for jQuery components and put them where needed. * No longer do all of it in application module. * Prepares better for code splitting. * Split out video player dialog * Simplifies jquery-ui dependencies for code splitting * Simplifies code * Configure to generate more, but smaller bundles. * Setup some more strict eslint settings * Fix css to import rather than require * Change settings to correctly support tree shaking in production build Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Remove “old” code from TimeFormatter * Accidentally left behind due to overlapping PRs Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-26 01:18:56 -04:00
dependencies:
is-invalid-path "^0.1.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
is-windows@^1.0.1, is-windows@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/is-windows/-/is-windows-1.0.2.tgz#d1850eb9791ecd18e6182ce12a30f396634bb19d"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-eXK1UInq2bPmjyX6e3VHIzMLobc4J94i4AWn+Hpq3OU5KkrRC96OAcR3PRJ/pGu6m8TRnBHP9dkXQVsT/COVIA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
is-wsl@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/is-wsl/-/is-wsl-1.1.0.tgz#1f16e4aa22b04d1336b66188a66af3c600c3a66d"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-HxbkqiKwTRM2tmGIpmrzxgDDpm0=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
isarray@1.0.0, isarray@^1.0.0, isarray@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/isarray/-/isarray-1.0.0.tgz#bb935d48582cba168c06834957a54a3e07124f11"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=
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
isexe@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/isexe/-/isexe-2.0.0.tgz#e8fbf374dc556ff8947a10dcb0572d633f2cfa10"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-6PvzdNxVb/iUehDcsFctYz8s+hA=
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
isobject@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/isobject/-/isobject-2.1.0.tgz#f065561096a3f1da2ef46272f815c840d87e0c89"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-8GVWEJaj8dou9GJy+BXIQNh+DIk=
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
dependencies:
isarray "1.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
isobject@^3.0.0, isobject@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/isobject/-/isobject-3.0.1.tgz#4e431e92b11a9731636aa1f9c8d1ccbcfdab78df"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-TkMekrEalzFjaqH5yNHMvP2reN8=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
jquery-ui@^1.12.1:
version "1.12.1"
resolved "https://registry.yarnpkg.com/jquery-ui/-/jquery-ui-1.12.1.tgz#bcb4045c8dd0539c134bc1488cdd3e768a7a9e51"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-vLQEXI3QU5wTS8FIjN0+dop6nlE=
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
jquery@^3.2.1:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "3.4.1"
resolved "https://registry.yarnpkg.com/jquery/-/jquery-3.4.1.tgz#714f1f8d9dde4bdfa55764ba37ef214630d80ef2"
integrity sha512-36+AdBzCL+y6qjw5Tx7HgzeGCzC81MDDgaUP8ld2zhx58HdqXGoBd+tHdrBMiyjGQs0Hxs/MLZTu/eHNJJuWPw==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"js-tokens@^3.0.0 || ^4.0.0", js-tokens@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/js-tokens/-/js-tokens-4.0.0.tgz#19203fb59991df98e3a287050d4647cdeaf32499"
integrity sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
js-yaml@^3.13.1:
version "3.13.1"
resolved "https://registry.yarnpkg.com/js-yaml/-/js-yaml-3.13.1.tgz#aff151b30bfdfa8e49e05da22e7415e9dfa37847"
integrity sha512-YfbcO7jXDdyj0DGxYVSlSeQNHbD7XPWvrVWeVUujrQEoZzWJIRrCPoyk6kL6IAjAG2IolMK4T0hNUe0HOUs5Jw==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
argparse "^1.0.7"
esprima "^4.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
jsesc@^2.5.1:
version "2.5.2"
resolved "https://registry.yarnpkg.com/jsesc/-/jsesc-2.5.2.tgz#80564d2e483dacf6e8ef209650a67df3f0c283a4"
integrity sha512-OYu7XEzjkCQ3C5Ps3QIZsQfNpqoJyZZA99wd9aWd05NCtC5pWOkShK2mkL6HXQR6/Cy2lbNdPlZBpuQHXE63gA==
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
jsesc@~0.5.0:
version "0.5.0"
resolved "https://registry.yarnpkg.com/jsesc/-/jsesc-0.5.0.tgz#e7dee66e35d6fc16f710fe91d5cf69f70f08911d"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-597mbjXW/Bb3EP6R1c9p9w8IkR0=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
json-parse-better-errors@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/json-parse-better-errors/-/json-parse-better-errors-1.0.2.tgz#bb867cfb3450e69107c131d1c514bab3dc8bcaa9"
integrity sha512-mrqyZKfX5EhL7hvqcV6WG1yYjnjeuYDzDhhcAAUrq8Po85NBQBJP+ZDUT75qZQ98IkUoBqdkExkukOU7Ts2wrw==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
json-schema-traverse@^0.4.1:
version "0.4.1"
resolved "https://registry.yarnpkg.com/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz#69f6a87d9513ab8bb8fe63bdb0979c448e684660"
integrity sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==
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
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
json-stable-stringify-without-jsonify@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/json-stable-stringify-without-jsonify/-/json-stable-stringify-without-jsonify-1.0.1.tgz#9db7b59496ad3f3cfef30a75142d2d930ad72651"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-nbe1lJatPzz+8wp1FC0tkwrXJlE=
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
json3@^3.3.2:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "3.3.3"
resolved "https://registry.yarnpkg.com/json3/-/json3-3.3.3.tgz#7fc10e375fc5ae42c4705a5cc0aa6f62be305b81"
integrity sha512-c7/8mbUsKigAbLkD5B010BK4D9LZm7A1pNItkEwiUZRpIN66exu/e7YQWysGun+TRKaJp8MhemM+VkfWv42aCA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
json5@^0.5.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
version "0.5.1"
resolved "https://registry.yarnpkg.com/json5/-/json5-0.5.1.tgz#1eade7acc012034ad84e2396767ead9fa5495821"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-Hq3nrMASA0rYTiOWdn6tn6VJWCE=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
json5@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/json5/-/json5-1.0.1.tgz#779fb0018604fa854eacbf6252180d83543e3dbe"
integrity sha512-aKS4WQjPenRxiQsC93MNfjx+nbF4PAdYzmd/1JIj8HYzqfbu86beTuNgXDzPknWk0n0uARlyewZo4s++ES36Ow==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
minimist "^1.2.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
json5@^2.1.0:
version "2.1.1"
resolved "https://registry.yarnpkg.com/json5/-/json5-2.1.1.tgz#81b6cb04e9ba496f1c7005d07b4368a2638f90b6"
integrity sha512-l+3HXD0GEI3huGq1njuqtzYK8OYJyXMkOLtQ53pjWh89tvWS2h6l+1zMkYWqlb57+SiQodKZyvMEFb2X+KrFhQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
minimist "^1.2.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
killable@^1.0.1:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/killable/-/killable-1.0.1.tgz#4c8ce441187a061c7474fb87ca08e2a638194892"
integrity sha512-LzqtLKlUwirEUyl/nicirVmNiPvYs7l5n8wOPP7fyJVpUPkvCnW/vuiXGpylGUlnPDnB7311rARzAt3Mhswpjg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
kind-of@^3.0.2, kind-of@^3.0.3, kind-of@^3.2.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
version "3.2.2"
resolved "https://registry.yarnpkg.com/kind-of/-/kind-of-3.2.2.tgz#31ea21a734bab9bbb0f32466d893aea51e4a3c64"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=
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
dependencies:
is-buffer "^1.1.5"
kind-of@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/kind-of/-/kind-of-4.0.0.tgz#20813df3d712928b207378691a45066fae72dd57"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-IIE989cSkosgc3hpGkUGb65y3Vc=
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
dependencies:
is-buffer "^1.1.5"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
kind-of@^5.0.0:
version "5.1.0"
resolved "https://registry.yarnpkg.com/kind-of/-/kind-of-5.1.0.tgz#729c91e2d857b7a419a1f9aa65685c4c33f5845d"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-NGEErnH6F2vUuXDh+OlbcKW7/wOcfdRHaZ7VWtqCztfHri/++YKmP51OdWeGPuqCOba6kk2OTe5d02VmTB80Pw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
kind-of@^6.0.0, kind-of@^6.0.2:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "6.0.3"
resolved "https://registry.yarnpkg.com/kind-of/-/kind-of-6.0.3.tgz#07c05034a6c349fa06e24fa35aa76db4580ce4dd"
integrity sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==
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
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
lcid@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/lcid/-/lcid-2.0.0.tgz#6ef5d2df60e52f82eb228a4c373e8d1f397253cf"
integrity sha512-avPEb8P8EGnwXKClwsNUgryVjllcRqtMYa49NTsbQagYuT1DcXnl1915oxWjoyGrXR6zH/Y0Zc96xWsPcoDKeA==
dependencies:
invert-kv "^2.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
leven@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/leven/-/leven-3.1.0.tgz#77891de834064cccba82ae7842bb6b14a13ed7f2"
integrity sha512-qsda+H8jTaUaN/x5vzW2rzc+8Rw4TAQ/4KjB46IwK5VH+IlVeeeje/EoZRpiXvIqjFgK84QffqPztGI3VBLG1A==
levenary@^1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/levenary/-/levenary-1.1.1.tgz#842a9ee98d2075aa7faeedbe32679e9205f46f77"
integrity sha512-mkAdOIt79FD6irqjYSs4rdbnlT5vRonMEvBVPVb3XmevfS8kgRXwfes0dhPdEtzTWD/1eNE/Bm/G1iRt6DcnQQ==
dependencies:
leven "^3.1.0"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
levn@^0.3.0, levn@~0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/levn/-/levn-0.3.0.tgz#3b09924edf9f083c0490fdd4c0bc4421e04764ee"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-OwmSTt+fCDwEkP3UwLxEIeBHZO4=
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
prelude-ls "~1.1.2"
type-check "~0.3.2"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
loader-runner@^2.4.0:
version "2.4.0"
resolved "https://registry.yarnpkg.com/loader-runner/-/loader-runner-2.4.0.tgz#ed47066bfe534d7e84c4c7b9998c2a75607d9357"
integrity sha512-Jsmr89RcXGIwivFY21FcRrisYZfvLMTWx5kOLc+JTxtpBOG6xML0vzbc6SEQG2FO9/4Fc3wW4LVcB5DmGflaRw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
loader-utils@1.2.3:
version "1.2.3"
resolved "https://registry.yarnpkg.com/loader-utils/-/loader-utils-1.2.3.tgz#1ff5dc6911c9f0a062531a4c04b609406108c2c7"
integrity sha512-fkpz8ejdnEMG3s37wGL07iSBDg99O9D5yflE9RGNH3hRdx9SOwYfnGYdZOUIZitN8E+E2vkq3MUMYMvPYl5ZZA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
big.js "^5.2.2"
emojis-list "^2.0.0"
json5 "^1.0.1"
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
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
loader-utils@^0.2.16:
version "0.2.17"
resolved "https://registry.yarnpkg.com/loader-utils/-/loader-utils-0.2.17.tgz#f86e6374d43205a6e6c60e9196f17c0299bfb348"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-+G5jdNQyBabmxg6RlvF8Apm/s0g=
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
big.js "^3.1.3"
emojis-list "^2.0.0"
json5 "^0.5.0"
object-assign "^4.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
loader-utils@^1.0.2, loader-utils@^1.1.0, loader-utils@^1.2.3, loader-utils@^1.4.0:
version "1.4.0"
resolved "https://registry.yarnpkg.com/loader-utils/-/loader-utils-1.4.0.tgz#c579b5e34cb34b1a74edc6c1fb36bfa371d5a613"
integrity sha512-qH0WSMBtn/oHuwjy/NucEgbx5dbxxnxup9s4PVXJUDHZBQY+s0NWA9rJf53RBnQZxfch7euUui7hpoAPvALZdA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
big.js "^5.2.2"
emojis-list "^3.0.0"
json5 "^1.0.1"
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
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
locate-path@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/locate-path/-/locate-path-3.0.0.tgz#dbec3b3ab759758071b58fe59fc41871af21400e"
integrity sha512-7AO748wWnIhNqAuaty2ZWHkQHRSNfPVIsPIfwEOWO22AmaoVrWavlOcMR5nzTLNYvp36X220/maaRsrec1G65A==
dependencies:
p-locate "^3.0.0"
path-exists "^3.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
locate-path@^5.0.0:
version "5.0.0"
resolved "https://registry.yarnpkg.com/locate-path/-/locate-path-5.0.0.tgz#1afba396afd676a6d42504d0a67a3a7eb9f62aa0"
integrity sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
p-locate "^4.1.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
lodash@^4.17.11, lodash@^4.17.13, lodash@^4.17.14, lodash@^4.17.15, lodash@^4.17.3:
version "4.17.15"
resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.15.tgz#b447f6670a0455bbfeedd11392eff330ea097548"
integrity sha512-8xOcRHvCjnocdS5cpwXQXVzmmh5e5+saE2QGoeQmbKmRS6J3VQppPOIt0MnmE+4xlZoumy0GPG0D0MVIQbNA1A==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
loglevel@^1.6.6:
version "1.6.7"
resolved "https://registry.yarnpkg.com/loglevel/-/loglevel-1.6.7.tgz#b3e034233188c68b889f5b862415306f565e2c56"
integrity sha512-cY2eLFrQSAfVPhCgH1s7JI73tMbg9YC3v3+ZHVW67sBS7UxWzNEk/ZBbSfLykBWHp33dqqtOv82gjhKEi81T/A==
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
loose-envify@^1.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.4.0"
resolved "https://registry.yarnpkg.com/loose-envify/-/loose-envify-1.4.0.tgz#71ee51fa7be4caec1a63839f7e682d8132d30caf"
integrity sha512-lyuxPGr/Wfhrlem2CL/UcnUc1zcqKAImBDzukY7Y5F/yQiNdko6+fRLevlw1HgMySw7f611UIY408EtxRSoK3Q==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
js-tokens "^3.0.0 || ^4.0.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
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
lower-case@^1.1.1:
version "1.1.4"
resolved "https://registry.yarnpkg.com/lower-case/-/lower-case-1.1.4.tgz#9a2cabd1b9e8e0ae993a4bf7d5875c39c42e8eac"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-miyr0bno4K6ZOkv31YdcOcQujqw=
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
lru-cache@^5.1.1:
version "5.1.1"
resolved "https://registry.yarnpkg.com/lru-cache/-/lru-cache-5.1.1.tgz#1da27e6710271947695daf6848e847f01d84b920"
integrity sha512-KpNARQA3Iwv+jTA0utUVVbrh+Jlrr1Fv0e56GGzAFOXN7dk/FviaDW8LHmK52DlcH4WP2n6gI8vN1aesBFgo9w==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
yallist "^3.0.2"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
make-dir@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/make-dir/-/make-dir-2.1.0.tgz#5f0310e18b8be898cc07009295a30ae41e91e6f5"
integrity sha512-LS9X+dc8KLxXCb8dni79fLIIUA5VyZoyjSMCwTluaXA0o27cCK0bhXkpgw+sTXVpPy/lSO57ilRixqk0vDmtRA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
pify "^4.0.1"
semver "^5.6.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
make-dir@^3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/make-dir/-/make-dir-3.0.2.tgz#04a1acbf22221e1d6ef43559f43e05a90dbb4392"
integrity sha512-rYKABKutXa6vXTXhoV18cBE7PaewPXHe/Bdq4v+ZLMhxbWApkFFplT0LcbMW+6BbjnQXzZ/sAvSE/JdguApG5w==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
semver "^6.0.0"
mamacro@^0.0.3:
version "0.0.3"
resolved "https://registry.yarnpkg.com/mamacro/-/mamacro-0.0.3.tgz#ad2c9576197c9f1abf308d0787865bd975a3f3e4"
integrity sha512-qMEwh+UujcQ+kbz3T6V+wAmO2U8veoq2w+3wY8MquqwVA3jChfwY+Tk52GZKDfACEPjuZ7r2oJLejwpt8jtwTA==
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
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
map-age-cleaner@^0.1.1:
version "0.1.3"
resolved "https://registry.yarnpkg.com/map-age-cleaner/-/map-age-cleaner-0.1.3.tgz#7d583a7306434c055fe474b0f45078e6e1b4b92a"
integrity sha512-bJzx6nMoP6PDLPBFmg7+xRKeFZvFboMrGlxmNj9ClvX53KrmvM5bXFXEWjbz4cz1AFn+jWJ9z/DJSz7hrs0w3w==
dependencies:
p-defer "^1.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
map-cache@^0.2.2:
version "0.2.2"
resolved "https://registry.yarnpkg.com/map-cache/-/map-cache-0.2.2.tgz#c32abd0bd6525d9b051645bb4f26ac5dc98a0dbf"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-wyq9C9ZSXZsFFkW7TyasXcmKDb8=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
map-visit@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/map-visit/-/map-visit-1.0.0.tgz#ecdca8f13144e660f1b5bd41f12f3479d98dfb8f"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-7Nyo8TFE5mDxtb1B8S80edmN+48=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
object-visit "^1.0.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
md5.js@^1.3.4:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.3.5"
resolved "https://registry.yarnpkg.com/md5.js/-/md5.js-1.3.5.tgz#b5d07b8e3216e3e27cd728d72f70d1e6a342005f"
integrity sha512-xitP+WxNPcTTOgnTJcrhM0xvdPepipPSf3I8EIpGKeFLjt3PlJLIDG3u8EX53ZIubkb+5U2+3rELYpEhHhzdkg==
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
dependencies:
hash-base "^3.0.0"
inherits "^2.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
safe-buffer "^5.1.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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
media-typer@0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/media-typer/-/media-typer-0.3.0.tgz#8710d7af0aa626f8fffa1ce00168545263255748"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-hxDXrwqmJvj/+hzgAWhUUmMlV0g=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
mem@^4.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "4.3.0"
resolved "https://registry.yarnpkg.com/mem/-/mem-4.3.0.tgz#461af497bc4ae09608cdb2e60eefb69bff744178"
integrity sha512-qX2bG48pTqYRVmDB37rn/6PT7LcR8T7oAX3bf99u1Tt1nzxYfxkgqDwUwolPlXweM0XzBOBFzSx4kfp7KP1s/w==
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
dependencies:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
map-age-cleaner "^0.1.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
mimic-fn "^2.0.0"
p-is-promise "^2.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
memory-fs@^0.4.0, memory-fs@^0.4.1:
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
version "0.4.1"
resolved "https://registry.yarnpkg.com/memory-fs/-/memory-fs-0.4.1.tgz#3a9a20b8462523e447cfbc7e8bb80ed667bfc552"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-OpoguEYlI+RHz7x+i7gO1me/xVI=
dependencies:
errno "^0.1.3"
readable-stream "^2.0.1"
memory-fs@^0.5.0:
version "0.5.0"
resolved "https://registry.yarnpkg.com/memory-fs/-/memory-fs-0.5.0.tgz#324c01288b88652966d161db77838720845a8e3c"
integrity sha512-jA0rdU5KoQMC0e6ppoNRtpp6vjFq6+NY7r8hywnC7V+1Xj/MtHwGIbB1QaK/dunyjWteJzmkpd7ooeWg10T7GA==
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
dependencies:
errno "^0.1.3"
readable-stream "^2.0.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
merge-descriptors@1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/merge-descriptors/-/merge-descriptors-1.0.1.tgz#b00aaa556dd8b44568150ec9d1b953f3f90cbb61"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-sAqqVW3YtEVoFQ7J0blT8/kMu2E=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
methods@~1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/methods/-/methods-1.1.2.tgz#5529a4d67654134edcc5266656835b0f851afcee"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-VSmk1nZUE07cxSZmVoNbD4Ua/O4=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
micromatch@^3.0.4, micromatch@^3.1.10, micromatch@^3.1.4:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "3.1.10"
resolved "https://registry.yarnpkg.com/micromatch/-/micromatch-3.1.10.tgz#70859bc95c9840952f359a068a3fc49f9ecfac23"
integrity sha512-MWikgl9n9M3w+bpsY3He8L+w9eF9338xRl8IAO5viDizwSzziFEyUzo2xrrloB64ADbTf8uA8vRqqttDTOmccg==
dependencies:
arr-diff "^4.0.0"
array-unique "^0.3.2"
braces "^2.3.1"
define-property "^2.0.2"
extend-shallow "^3.0.2"
extglob "^2.0.4"
fragment-cache "^0.2.1"
kind-of "^6.0.2"
nanomatch "^1.2.9"
object.pick "^1.3.0"
regex-not "^1.0.0"
snapdragon "^0.8.1"
to-regex "^3.0.2"
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
miller-rabin@^4.0.0:
version "4.0.1"
resolved "https://registry.yarnpkg.com/miller-rabin/-/miller-rabin-4.0.1.tgz#f080351c865b0dc562a8462966daa53543c78a4d"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-115fLhvZVqWwHPbClyntxEVfVDfl9DLLTuJvq3g2O/Oxi8AiNouAHvDSzHS0viUJc+V5vm3eq91Xwqn9dp4jRA==
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
dependencies:
bn.js "^4.0.0"
brorand "^1.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
mime-db@1.43.0, "mime-db@>= 1.43.0 < 2":
version "1.43.0"
resolved "https://registry.yarnpkg.com/mime-db/-/mime-db-1.43.0.tgz#0a12e0502650e473d735535050e7c8f4eb4fae58"
integrity sha512-+5dsGEEovYbT8UY9yD7eE4XTc4UwJ1jBYlgaQQF38ENsKR3wj/8q8RFZrF9WIZpB2V1ArTVFUva8sAul1NzRzQ==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
mime-types@~2.1.17, mime-types@~2.1.24:
version "2.1.26"
resolved "https://registry.yarnpkg.com/mime-types/-/mime-types-2.1.26.tgz#9c921fc09b7e149a65dfdc0da4d20997200b0a06"
integrity sha512-01paPWYgLrkqAyrlDorC1uDwl2p3qZT7yl806vW7DvDoxwXi46jsjFbg+WdwotBIk6/MbEhO/dh5aZ5sNj/dWQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
mime-db "1.43.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
mime@1.6.0:
version "1.6.0"
resolved "https://registry.yarnpkg.com/mime/-/mime-1.6.0.tgz#32cd9e5c64553bd58d19a568af452acff04981b1"
integrity sha512-x0Vn8spI+wuJ1O6S7gnbaQg8Pxh4NNHb7KSINmEWKiPE4RKOplvijn+NkmYmmRgP68mc70j2EbeTFRsrswaQeg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
mime@^2.4.4:
version "2.4.4"
resolved "https://registry.yarnpkg.com/mime/-/mime-2.4.4.tgz#bd7b91135fc6b01cde3e9bae33d659b63d8857e5"
integrity sha512-LRxmNwziLPT828z+4YkNzloCFC2YM4wrB99k+AV5ZbEyfGNWfG8SO1FUXLmLDBSo89NrJZ4DIWeLjy1CHGhMGA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
mimic-fn@^2.0.0, mimic-fn@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/mimic-fn/-/mimic-fn-2.1.0.tgz#7ed2c2ccccaf84d3ffcb7a69b57711fc2083401b"
integrity sha512-OqbOk5oEQeAZ8WXWydlu9HJjz9WVdEIvamMCcXmuqUYjTknH/sqsWvhQ3vgwKFRR1HpjvNBKQ37nbJgYzGqGcg==
minimalistic-assert@^1.0.0, minimalistic-assert@^1.0.1:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/minimalistic-assert/-/minimalistic-assert-1.0.1.tgz#2e194de044626d4a10e7f7fbc00ce73e83e4d5c7"
integrity sha512-UtJcAD4yEaGtjPezWuO9wC4nwUnVH/8/Im3yEHQP4b67cXlD/Qr9hdITCU1xDbSEXg2XKNaP8jsReV7vQd00/A==
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
minimalistic-crypto-utils@^1.0.0, minimalistic-crypto-utils@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/minimalistic-crypto-utils/-/minimalistic-crypto-utils-1.0.1.tgz#f6c00c1c0b082246e5c4d99dfb8c7c083b2b582a"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-9sAMHAsIIkblxNmd+4x8CDsrWCo=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
minimatch@^3.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
version "3.0.4"
resolved "https://registry.yarnpkg.com/minimatch/-/minimatch-3.0.4.tgz#5166e286457f03306064be5497e8dbb0c3d32083"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-yJHVQEhyqPLUTgt9B83PXu6W3rx4MvvHvSUvToogpwoGDOUQ+yDrR0HRot+yOCdCO7u4hX3pWft6kWBBcqh0UA==
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
dependencies:
brace-expansion "^1.1.7"
minimist@0.0.8:
version "0.0.8"
resolved "https://registry.yarnpkg.com/minimist/-/minimist-0.0.8.tgz#857fcabfc3397d2625b8228262e86aa7a011b05d"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-hX/Kv8M5fSYluCKCYuhqp6ARsF0=
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
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
minimist@^1.2.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
version "1.2.0"
resolved "https://registry.yarnpkg.com/minimist/-/minimist-1.2.0.tgz#a35008b20f41383eec1fb914f4cd5df79a264284"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-o1AIsg9BOD7sH7kU9M1d95omQoQ=
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
minipass-collect@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/minipass-collect/-/minipass-collect-1.0.2.tgz#22b813bf745dc6edba2576b940022ad6edc8c617"
integrity sha512-6T6lH0H8OG9kITm/Jm6tdooIbogG9e0tLgpY6mphXSm/A9u8Nq1ryBG+Qspiub9LjWlBPsPS3tWQ/Botq4FdxA==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
minipass "^3.0.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
minipass-flush@^1.0.5:
version "1.0.5"
resolved "https://registry.yarnpkg.com/minipass-flush/-/minipass-flush-1.0.5.tgz#82e7135d7e89a50ffe64610a787953c4c4cbb373"
integrity sha512-JmQSYYpPUqX5Jyn1mXaRwOda1uQ8HP5KAT/oDSLCzt1BYRhQU0/hDtsB1ufZfEEzMZ9aAVmsBw8+FWsIXlClWw==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
minipass "^3.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
minipass-pipeline@^1.2.2:
version "1.2.2"
resolved "https://registry.yarnpkg.com/minipass-pipeline/-/minipass-pipeline-1.2.2.tgz#3dcb6bb4a546e32969c7ad710f2c79a86abba93a"
integrity sha512-3JS5A2DKhD2g0Gg8x3yamO0pj7YeKGwVlDS90pF++kxptwx/F+B//roxf9SqYil5tQo65bijy+dAuAFZmYOouA==
dependencies:
minipass "^3.0.0"
minipass@^3.0.0, minipass@^3.1.1:
version "3.1.1"
resolved "https://registry.yarnpkg.com/minipass/-/minipass-3.1.1.tgz#7607ce778472a185ad6d89082aa2070f79cedcd5"
integrity sha512-UFqVihv6PQgwj8/yTGvl9kPz7xIAY+R5z6XYjRInD3Gk3qx6QGSD6zEcpeG4Dy/lQnv1J6zv8ejV90hyYIKf3w==
dependencies:
yallist "^4.0.0"
mississippi@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/mississippi/-/mississippi-3.0.0.tgz#ea0a3291f97e0b5e8776b363d5f0a12d94c67022"
integrity sha512-x471SsVjUtBRtcvd4BzKE9kFC+/2TeWgKCgw0bZcw1b9l2X3QX5vCWgF+KaZaYm87Ss//rHnWryupDrgLvmSkA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
concat-stream "^1.5.0"
duplexify "^3.4.2"
end-of-stream "^1.1.0"
flush-write-stream "^1.0.0"
from2 "^2.1.0"
parallel-transform "^1.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
pump "^3.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
pumpify "^1.3.3"
stream-each "^1.1.0"
through2 "^2.0.0"
mixin-deep@^1.2.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.3.2"
resolved "https://registry.yarnpkg.com/mixin-deep/-/mixin-deep-1.3.2.tgz#1120b43dc359a785dce65b55b82e257ccf479566"
integrity sha512-WRoDn//mXBiJ1H40rqa3vH0toePwSsGb45iInWlTySa+Uu4k3tYUSxa2v1KqAiLtvlrSzaExqS1gtk96A9zvEA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
for-in "^1.0.2"
is-extendable "^1.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
mkdirp@^0.5.1:
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
version "0.5.1"
resolved "https://registry.yarnpkg.com/mkdirp/-/mkdirp-0.5.1.tgz#30057438eac6cf7f8c4767f38648d6697d75c903"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-MAV0OOrGz3+MR2fzhkjWaX11yQM=
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
dependencies:
minimist "0.0.8"
moment-timezone@^0.5.13:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "0.5.28"
resolved "https://registry.yarnpkg.com/moment-timezone/-/moment-timezone-0.5.28.tgz#f093d789d091ed7b055d82aa81a82467f72e4338"
integrity sha512-TDJkZvAyKIVWg5EtVqRzU97w0Rb0YVbfpqyjgu6GwXCAohVRqwZjf4fOzDE6p1Ch98Sro/8hQQi65WDXW5STPw==
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
dependencies:
moment ">= 2.9.0"
"moment@>= 2.9.0":
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "2.24.0"
resolved "https://registry.yarnpkg.com/moment/-/moment-2.24.0.tgz#0d055d53f5052aa653c9f6eb68bb5d12bf5c2b5b"
integrity sha512-bV7f+6l2QigeBBZSM/6yTNq4P2fNpSWj/0e7jQcy87A8e7o2nAfP/34/2ky5Vw4B9S446EtIhodAzkFCcR4dQg==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
move-concurrently@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/move-concurrently/-/move-concurrently-1.0.1.tgz#be2c005fda32e0b29af1f05d7c4b33214c701f92"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-viwAX9oy4LKa8fBdfEszIUxwH5I=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
aproba "^1.1.1"
copy-concurrently "^1.0.0"
fs-write-stream-atomic "^1.0.8"
mkdirp "^0.5.1"
rimraf "^2.5.4"
run-queue "^1.0.3"
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
ms@2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/ms/-/ms-2.0.0.tgz#5608aeadfc00be6c2901df5f9861788de0d597c8"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-VgiurfwAvmwpAd9fmGF4jeDVl8g=
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ms@2.1.1:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "2.1.1"
resolved "https://registry.yarnpkg.com/ms/-/ms-2.1.1.tgz#30a5864eb3ebb0a66f2ebe6d727af06a09d86e0a"
integrity sha512-tgp+dl5cGk28utYktBsrFqA7HKgrhgPsg6Z/EfhWI4gl1Hwq8B/GmY/0oXZ6nF8hDVesS/FpnYaD/kOWhYQvyg==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ms@^2.1.1:
version "2.1.2"
resolved "https://registry.yarnpkg.com/ms/-/ms-2.1.2.tgz#d09d1f357b443f493382a8eb3ccd183872ae6009"
integrity sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
multicast-dns-service-types@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/multicast-dns-service-types/-/multicast-dns-service-types-1.1.0.tgz#899f11d9686e5e05cb91b35d5f0e63b773cfc901"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-iZ8R2WhuXgXLkbNdXw5jt3PPyQE=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
multicast-dns@^6.0.1:
version "6.2.3"
resolved "https://registry.yarnpkg.com/multicast-dns/-/multicast-dns-6.2.3.tgz#a0ec7bd9055c4282f790c3c82f4e28db3b31b229"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-ji6J5enbMyGRHIAkAOu3WdV8nggqviKCEKtXcOqfphZZtQrmHKycfynJ2V7eVPUA4NhJ6V7Wf4TmGbTwKE9B6g==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
dns-packet "^1.3.1"
thunky "^1.0.2"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
mute-stream@0.0.8:
version "0.0.8"
resolved "https://registry.yarnpkg.com/mute-stream/-/mute-stream-0.0.8.tgz#1630c42b2251ff81e2a283de96a5497ea92e5e0d"
integrity sha512-nnbWWOkoWyUsTjKrhgD0dcz22mdkSnpYqbEjIm2nhwhuxlSkpywJmBo8h0ZqJdkp73mb90SssHkN4rsRaBAfAA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
nan@^2.12.1:
version "2.14.0"
resolved "https://registry.yarnpkg.com/nan/-/nan-2.14.0.tgz#7818f722027b2459a86f0295d434d1fc2336c52c"
integrity sha512-INOFj37C7k3AfaNTtX8RhsTw7qRy7eLET14cROi9+5HAVbbHuIWUHEauBv5qT4Av2tWasiTY1Jw6puUNqRJXQg==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
nanomatch@^1.2.9:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "1.2.13"
resolved "https://registry.yarnpkg.com/nanomatch/-/nanomatch-1.2.13.tgz#b87a8aa4fc0de8fe6be88895b38983ff265bd119"
integrity sha512-fpoe2T0RbHwBTBUOftAfBPaDEi06ufaUai0mE6Yn1kacc3SnTErfb/h+X94VXzI64rKFHYImXSvdwGGCmwOqCA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
arr-diff "^4.0.0"
array-unique "^0.3.2"
define-property "^2.0.2"
extend-shallow "^3.0.2"
fragment-cache "^0.2.1"
is-windows "^1.0.2"
kind-of "^6.0.2"
object.pick "^1.3.0"
regex-not "^1.0.0"
snapdragon "^0.8.1"
to-regex "^3.0.1"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
natural-compare@^1.4.0:
version "1.4.0"
resolved "https://registry.yarnpkg.com/natural-compare/-/natural-compare-1.4.0.tgz#4abebfeed7541f2c27acfb29bdbbd15c8d5ba4f7"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-Sr6/7tdUHywnrPspvbvRXI1bpPc=
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
negotiator@0.6.2:
version "0.6.2"
resolved "https://registry.yarnpkg.com/negotiator/-/negotiator-0.6.2.tgz#feacf7ccf525a77ae9634436a64883ffeca346fb"
integrity sha512-hZXc7K2e+PgeI1eDBe/10Ard4ekbfrrqG8Ep+8Jmf4JID2bNg7NvCPOZN+kfF574pFQI7mum2AUqDidoKqcTOw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
neo-async@^2.5.0, neo-async@^2.6.1:
version "2.6.1"
resolved "https://registry.yarnpkg.com/neo-async/-/neo-async-2.6.1.tgz#ac27ada66167fa8849a6addd837f6b189ad2081c"
integrity sha512-iyam8fBuCUpWeKPGpaNMetEocMt364qkCsfL9JuhjXX6dRnguRVOfk2GZaDpPjcOKiiXCPINZC1GczQ7iTq3Zw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
nice-try@^1.0.4:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.0.5"
resolved "https://registry.yarnpkg.com/nice-try/-/nice-try-1.0.5.tgz#a3378a7696ce7d223e88fc9b764bd7ef1089e366"
integrity sha512-1nh45deeb5olNY7eX82BkPO7SSxR5SSYJiPTrTdFUVYwAl8CKMA5N9PjTYkHiRjisVcxcQ1HXdLhx2qxxJzLNQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
no-case@^2.2.0:
version "2.3.2"
resolved "https://registry.yarnpkg.com/no-case/-/no-case-2.3.2.tgz#60b813396be39b3f1288a4c1ed5d1e7d28b464ac"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-rmTZ9kz+f3rCvK2TD1Ue/oZlns7OGoIWP4fc3llxxRXlOkHKoWPPWJOfFYpITabSow43QJbRIoHQXtt10VldyQ==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
lower-case "^1.1.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
node-forge@0.9.0:
version "0.9.0"
resolved "https://registry.yarnpkg.com/node-forge/-/node-forge-0.9.0.tgz#d624050edbb44874adca12bb9a52ec63cb782579"
integrity sha512-7ASaDa3pD+lJ3WvXFsxekJQelBKRpne+GOVbLbtHYdd7pFspyeuJHnWfLplGf3SwKGbfs/aYl5V/JCIaHVUKKQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
node-libs-browser@^2.2.1:
version "2.2.1"
resolved "https://registry.yarnpkg.com/node-libs-browser/-/node-libs-browser-2.2.1.tgz#b64f513d18338625f90346d27b0d235e631f6425"
integrity sha512-h/zcD8H9kaDZ9ALUWwlBUDo6TKF8a7qBSCSEGfjTVIYeqsioSKaAX+BN7NgiMGp6iSIXZ3PxgCu8KS3b71YK5Q==
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
dependencies:
assert "^1.1.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
browserify-zlib "^0.2.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
buffer "^4.3.0"
console-browserify "^1.1.0"
constants-browserify "^1.0.0"
crypto-browserify "^3.11.0"
domain-browser "^1.1.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
events "^3.0.0"
https-browserify "^1.0.0"
os-browserify "^0.3.0"
path-browserify "0.0.1"
process "^0.11.10"
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
punycode "^1.2.4"
querystring-es3 "^0.2.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
readable-stream "^2.3.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
stream-browserify "^2.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
stream-http "^2.7.2"
string_decoder "^1.0.0"
timers-browserify "^2.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
tty-browserify "0.0.0"
url "^0.11.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
util "^0.11.0"
vm-browserify "^1.0.1"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
node-releases@^1.1.50:
version "1.1.50"
resolved "https://registry.yarnpkg.com/node-releases/-/node-releases-1.1.50.tgz#803c40d2c45db172d0410e4efec83aa8c6ad0592"
integrity sha512-lgAmPv9eYZ0bGwUYAKlr8MG6K4CvWliWqnkcT2P8mMAgVrH3lqfBPorFlxiG1pHQnqmavJZ9vbMXUTNyMLbrgQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
semver "^6.3.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
normalize-path@^2.1.1:
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
version "2.1.1"
resolved "https://registry.yarnpkg.com/normalize-path/-/normalize-path-2.1.1.tgz#1ab28b556e198363a8c1a6f7e6fa20137fe6aed9"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-GrKLVW4Zg2Oowab35vogE3/mrtk=
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
dependencies:
remove-trailing-separator "^1.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
normalize-path@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/normalize-path/-/normalize-path-3.0.0.tgz#0dcd69ff23a1c9b11fd0978316644a0388216a65"
integrity sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -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
npm-run-path@^2.0.0:
version "2.0.2"
resolved "https://registry.yarnpkg.com/npm-run-path/-/npm-run-path-2.0.2.tgz#35a9232dfa35d7067b4cb2ddf2357b1871536c5f"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-NakjLfo11wZ7TLLd8jV7GHFTbF8=
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
dependencies:
path-key "^2.0.0"
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
nth-check@~1.0.1:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/nth-check/-/nth-check-1.0.2.tgz#b2bd295c37e3dd58a3bf0700376663ba4d9cf05c"
integrity sha512-WeBOdju8SnzPN5vTUJYxYUxLeXpCaVP5i5e0LF8fg7WORF2Wd7wFX/pk0tYZk7s8T+J7VLy0Da6J1+wCT0AtHg==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
boolbase "~1.0.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
number-is-nan@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/number-is-nan/-/number-is-nan-1.0.1.tgz#097b602b53422a522c1afb8790318336941a011d"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-CXtgK1NCKlIsGvuHkDGDNpQaAR0=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
object-assign@^4.0.1, object-assign@^4.1.1:
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
version "4.1.1"
resolved "https://registry.yarnpkg.com/object-assign/-/object-assign-4.1.1.tgz#2109adc7965887cfc05cbbd442cac8bfbb360863"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-IQmtx5ZYh8/AXLvUQsrIv7s2CGM=
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
object-copy@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/object-copy/-/object-copy-0.1.0.tgz#7e7d858b781bd7c991a41ba975ed3812754e998c"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-fn2Fi3gb18mRpBupde04EnVOmYw=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
copy-descriptor "^0.1.0"
define-property "^0.2.5"
kind-of "^3.0.3"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
object-inspect@^1.7.0:
version "1.7.0"
resolved "https://registry.yarnpkg.com/object-inspect/-/object-inspect-1.7.0.tgz#f4f6bd181ad77f006b5ece60bd0b6f398ff74a67"
integrity sha512-a7pEHdh1xKIAgTySUGgLMx/xwDZskN1Ud6egYYN3EdRW4ZMPNEDUTF+hwy2LUC+Bl+SyLXANnwz/jyh/qutKUw==
object-is@^1.0.1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/object-is/-/object-is-1.0.2.tgz#6b80eb84fe451498f65007982f035a5b445edec4"
integrity sha512-Epah+btZd5wrrfjkJZq1AOB9O6OxUQto45hzFd7lXGrpHPGE0W1k+426yrZV+k6NJOzLNNW/nVsmZdIWsAqoOQ==
object-keys@^1.0.11, object-keys@^1.0.12, object-keys@^1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/object-keys/-/object-keys-1.1.1.tgz#1c47f272df277f3b1daf061677d9c82e2322c60e"
integrity sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
object-visit@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/object-visit/-/object-visit-1.0.1.tgz#f79c4493af0c5377b59fe39d395e41042dd045bb"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-95xEk68MU3e1n+OdOV5BBC3QRbs=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
isobject "^3.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
object.assign@^4.1.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/object.assign/-/object.assign-4.1.0.tgz#968bf1100d7956bb3ca086f006f846b3bc4008da"
integrity sha512-exHJeq6kBKj58mqGyTQ9DFvrZC/eR6OwxzoM9YRoGBqrXYonaFyGiFMuc9VZrXf7DarreEwMpurG3dd+CNyW5w==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
define-properties "^1.1.2"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
function-bind "^1.1.1"
has-symbols "^1.0.0"
object-keys "^1.0.11"
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
object.getownpropertydescriptors@^2.0.3:
version "2.1.0"
resolved "https://registry.yarnpkg.com/object.getownpropertydescriptors/-/object.getownpropertydescriptors-2.1.0.tgz#369bf1f9592d8ab89d712dced5cb81c7c5352649"
integrity sha512-Z53Oah9A3TdLoblT7VKJaTDdXdT+lQO+cNpKVnya5JDe9uLvzu1YyY1yFDFrcxrlRgWrEFH0jJtD/IbuwjcEVg==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
define-properties "^1.1.3"
es-abstract "^1.17.0-next.1"
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
object.pick@^1.3.0:
version "1.3.0"
resolved "https://registry.yarnpkg.com/object.pick/-/object.pick-1.3.0.tgz#87a10ac4c1694bd2e1cbf53591a66141fb5dd747"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-h6EKxMFpS9Lhy/U1kaZhQftd10c=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
isobject "^3.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
obuf@^1.0.0, obuf@^1.1.2:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "1.1.2"
resolved "https://registry.yarnpkg.com/obuf/-/obuf-1.1.2.tgz#09bea3343d41859ebd446292d11c9d4db619084e"
integrity sha512-PX1wu0AmAdPqOL1mWhqmlOd8kOIZQwGZw6rh7uby9fTc5lhaOWFLX3I6R1hrF9k3zUY40e6igsLGkDXK92LJNg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
on-finished@~2.3.0:
version "2.3.0"
resolved "https://registry.yarnpkg.com/on-finished/-/on-finished-2.3.0.tgz#20f1336481b083cd75337992a16971aa2d906947"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-IPEzZIGwg811M3mSoWlxqi2QaUc=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
ee-first "1.1.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
on-headers@~1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/on-headers/-/on-headers-1.0.2.tgz#772b0ae6aaa525c399e489adfad90c403eb3c28f"
integrity sha512-pZAE+FJLoyITytdqK0U5s+FIpjN0JP3OzFi/u8Rx+EV5/W+JTWGXG8xFzevE7AjBfDqHv/8vL8qQsIhHnqRkrA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
once@^1.3.0, once@^1.3.1, once@^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
version "1.4.0"
resolved "https://registry.yarnpkg.com/once/-/once-1.4.0.tgz#583b1aa775961d4b113ac17d9c50baef9dd76bd1"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-WDsap3WWHUsROsF9nFC6753Xa9E=
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
dependencies:
wrappy "1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
onetime@^5.1.0:
version "5.1.0"
resolved "https://registry.yarnpkg.com/onetime/-/onetime-5.1.0.tgz#fff0f3c91617fe62bb50189636e99ac8a6df7be5"
integrity sha512-5NcSkPHhwTVFIQN+TUqXoS5+dlElHXdpAWu9I0HP20YOtIi+aZ0Ct82jdlILDxjLEAWwvm+qj1m6aEtsDVmm6Q==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
mimic-fn "^2.1.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
opn@^5.5.0:
version "5.5.0"
resolved "https://registry.yarnpkg.com/opn/-/opn-5.5.0.tgz#fc7164fab56d235904c51c3b27da6758ca3b9bfc"
integrity sha512-PqHpggC9bLV0VeWcdKhkpxY+3JTzetLSqTCWL/z/tFIbI6G8JCjondXklT1JinczLz2Xib62sSp0T/gKT4KksA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
is-wsl "^1.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
optionator@^0.8.3:
version "0.8.3"
resolved "https://registry.yarnpkg.com/optionator/-/optionator-0.8.3.tgz#84fa1d036fe9d3c7e21d99884b601167ec8fb495"
integrity sha512-+IW9pACdk3XWmmTXG8m3upGUJst5XRGzxMRjXzAuJ1XnIFNvfhjjIuYkDvysnPQ7qzqVzLt78BCruntqRhWQbA==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
deep-is "~0.1.3"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
fast-levenshtein "~2.0.6"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
levn "~0.3.0"
prelude-ls "~1.1.2"
type-check "~0.3.2"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
word-wrap "~1.2.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
original@^1.0.0:
version "1.0.2"
resolved "https://registry.yarnpkg.com/original/-/original-1.0.2.tgz#e442a61cffe1c5fd20a65f3261c26663b303f25f"
integrity sha512-hyBVl6iqqUOJ8FqRe+l/gS8H+kKYjrEndd5Pm1MfBtsEKA038HkkdbAl/72EAXGyonD/PFsvmVG+EvcIpliMBg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
url-parse "^1.4.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
os-browserify@^0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/os-browserify/-/os-browserify-0.3.0.tgz#854373c7f5c2315914fc9bfc6bd8238fdda1ec27"
integrity sha1-hUNzx/XCMVkU/Jv8a9gjj92h7Cc=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
os-locale@^3.0.0, os-locale@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/os-locale/-/os-locale-3.1.0.tgz#a802a6ee17f24c10483ab9935719cef4ed16bf1a"
integrity sha512-Z8l3R4wYWM40/52Z+S265okfFj8Kt2cC2MKY+xNi3kFs+XGI7WXu/I309QQQYbRW4ijiZ+yxs9pqEhJh0DqW3Q==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
execa "^1.0.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
lcid "^2.0.0"
mem "^4.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
os-tmpdir@~1.0.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
version "1.0.2"
resolved "https://registry.yarnpkg.com/os-tmpdir/-/os-tmpdir-1.0.2.tgz#bbe67406c79aa85c5cfec766fe5734555dfa1274"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-u+Z0BseaqFxc/sdm/lc0VV36EnQ=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
p-defer@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/p-defer/-/p-defer-1.0.0.tgz#9f6eb182f6c9aa8cd743004a7d4f96b196b0fb0c"
integrity sha1-n26xgvbJqozXQwBKfU+WsZaw+ww=
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
p-finally@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/p-finally/-/p-finally-1.0.0.tgz#3fbcfb15b899a44123b34b6dcc18b724336a2cae"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-P7z7FbiZpEEjs0ttzBi3JDNqLK4=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
p-is-promise@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/p-is-promise/-/p-is-promise-2.1.0.tgz#918cebaea248a62cf7ffab8e3bca8c5f882fc42e"
integrity sha512-Y3W0wlRPK8ZMRbNq97l4M5otioeA5lm1z7bkNkxCka8HSPjR0xRWmpCmc9utiaLP9Jb1eD8BgeIxTW4AIF45Pg==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
p-limit@^2.0.0, p-limit@^2.2.0:
version "2.2.2"
resolved "https://registry.yarnpkg.com/p-limit/-/p-limit-2.2.2.tgz#61279b67721f5287aa1c13a9a7fbbc48c9291b1e"
integrity sha512-WGR+xHecKTr7EbUEhyLSh5Dube9JtdiG78ufaeLxTgpudf/20KqyMioIUZJAezlTIi6evxuoUs9YXc11cU+yzQ==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
dependencies:
p-try "^2.0.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
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
p-locate@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/p-locate/-/p-locate-3.0.0.tgz#322d69a05c0264b25997d9f40cd8a891ab0064a4"
integrity sha512-x+12w/To+4GFfgJhBEpiDcLozRJGegY+Ei7/z0tSLkMmxGZNybVMSfWj9aJn8Z5Fc7dBUNJOOVgPv2H7IwulSQ==
dependencies:
p-limit "^2.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
p-locate@^4.1.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/p-locate/-/p-locate-4.1.0.tgz#a3428bb7088b3a60292f66919278b7c297ad4f07"
integrity sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A==
dependencies:
p-limit "^2.2.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
p-map@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/p-map/-/p-map-2.1.0.tgz#310928feef9c9ecc65b68b17693018a665cea175"
integrity sha512-y3b8Kpd8OAN444hxfBbFfj1FY/RjtTd8tzYwhUqNYXx0fXx2iX4maP4Qr6qhIKbQXI02wTLAda4fYUbDagTUFw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
p-map@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/p-map/-/p-map-3.0.0.tgz#d704d9af8a2ba684e2600d9a215983d4141a979d"
integrity sha512-d3qXVTF/s+W+CdJ5A29wywV2n8CQQYahlgz2bFiA+4eVNJbHJodPZ+/gXwPGh0bOqA+j8S+6+ckmvLGPk1QpxQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
aggregate-error "^3.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
p-retry@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/p-retry/-/p-retry-3.0.1.tgz#316b4c8893e2c8dc1cfa891f406c4b422bebf328"
integrity sha512-XE6G4+YTTkT2a0UWb2kjZe8xNwf8bIbnqpc/IS/idOBVhyves0mK5OJgeocjx7q5pvX/6m23xuzVPYT1uGM73w==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
retry "^0.12.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
p-try@^2.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "2.2.0"
resolved "https://registry.yarnpkg.com/p-try/-/p-try-2.2.0.tgz#cb2868540e313d61de58fafbe35ce9004d5540e6"
integrity sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
pako@~1.0.5:
version "1.0.11"
resolved "https://registry.yarnpkg.com/pako/-/pako-1.0.11.tgz#6c9599d340d54dfd3946380252a35705a6b992bf"
integrity sha512-4hLB8Py4zZce5s4yd9XzopqwVv/yGNhV1Bl8NTmCq1763HeK2+EwVTv+leGeL13Dnh2wfbqowVPXCIO0z4taYw==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
parallel-transform@^1.1.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/parallel-transform/-/parallel-transform-1.2.0.tgz#9049ca37d6cb2182c3b1d2c720be94d14a5814fc"
integrity sha512-P2vSmIu38uIlvdcU7fDkyrxj33gTUy/ABO5ZUbGowxNCopBq/OoD42bP4UmMrJoPyk4Uqf0mu3mtWBhHCZD8yg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
cyclist "^1.0.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
inherits "^2.0.3"
readable-stream "^2.1.5"
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
param-case@2.1.x:
version "2.1.1"
resolved "https://registry.yarnpkg.com/param-case/-/param-case-2.1.1.tgz#df94fd8cf6531ecf75e6bef9a0858fbc72be2247"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-35T9jPZTHs915r75oIWPvHK+Ikc=
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
no-case "^2.2.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
parent-module@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/parent-module/-/parent-module-1.0.1.tgz#691d2709e78c79fae3a156622452d00762caaaa2"
integrity sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==
dependencies:
callsites "^3.0.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
parse-asn1@^5.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "5.1.5"
resolved "https://registry.yarnpkg.com/parse-asn1/-/parse-asn1-5.1.5.tgz#003271343da58dc94cace494faef3d2147ecea0e"
integrity sha512-jkMYn1dcJqF6d5CpU689bq7w/b5ALS9ROVSpQDPrZsqqesUJii9qutvoT5ltGedNXMO2e16YUWIghG9KxaViTQ==
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
dependencies:
asn1.js "^4.0.0"
browserify-aes "^1.0.0"
create-hash "^1.1.0"
evp_bytestokey "^1.0.0"
pbkdf2 "^3.0.3"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
safe-buffer "^5.1.1"
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
parse-passwd@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/parse-passwd/-/parse-passwd-1.0.0.tgz#6d5b934a456993b23d37f40a382d6f1666a8e5c6"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-bVuTSkVpk7I9N/QKOC1vFmao5cY=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
parseurl@~1.3.2, parseurl@~1.3.3:
version "1.3.3"
resolved "https://registry.yarnpkg.com/parseurl/-/parseurl-1.3.3.tgz#9da19e7bee8d12dff0513ed5b76957793bc2e8d4"
integrity sha512-CiyeOxFT/JZyN5m0z9PfXw4SCBJ6Sygz1Dpl0wqjlhDEGGBP1GnsUVEL0p63hoG1fcj3fHynXi9NYO4nWOL+qQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
pascalcase@^0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/pascalcase/-/pascalcase-0.1.1.tgz#b363e55e8006ca6fe21784d2db22bd15d7917f14"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-s2PlXoAGym/iF4TS2yK9FdeRfxQ=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
path-browserify@0.0.1:
version "0.0.1"
resolved "https://registry.yarnpkg.com/path-browserify/-/path-browserify-0.0.1.tgz#e6c4ddd7ed3aa27c68a20cc4e50e1a4ee83bbc4a"
integrity sha512-BapA40NHICOS+USX9SN4tyhq+A2RrN/Ws5F0Z5aMHDp98Fl86lX8Oti8B7uN93L4Ifv4fHOEA+pQw87gmMO/lQ==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
path-dirname@^1.0.0:
version "1.0.2"
resolved "https://registry.yarnpkg.com/path-dirname/-/path-dirname-1.0.2.tgz#cc33d24d525e099a5388c0336c6e32b9160609e0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-zDPSTVJeCZpTiMAzbG4yuRYGCeA=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
path-exists@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/path-exists/-/path-exists-3.0.0.tgz#ce0ebeaa5f78cb18925ea7d810d7b59b010fd515"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-zg6+ql94yxiSXqfYENe1mwEP1RU=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
path-exists@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/path-exists/-/path-exists-4.0.0.tgz#513bdbe2d3b95d7762e8c1137efa195c6c61b5b3"
integrity sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==
path-is-absolute@^1.0.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
version "1.0.1"
resolved "https://registry.yarnpkg.com/path-is-absolute/-/path-is-absolute-1.0.1.tgz#174b9268735534ffbc7ace6bf53a5a9e1b5c5f5f"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-F0uSaHNVNP+8es5r9TpanhtcX18=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
path-is-inside@^1.0.2:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/path-is-inside/-/path-is-inside-1.0.2.tgz#365417dede44430d1c11af61027facf074bdfc53"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-NlQX3t5EQw0cEa9hAn+s8HS9/FM=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
path-key@^2.0.0, path-key@^2.0.1:
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
version "2.0.1"
resolved "https://registry.yarnpkg.com/path-key/-/path-key-2.0.1.tgz#411cadb574c5a140d3a4b1910d40d80cc9f40b40"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-QRyttXTFoUDTpLGRDUDYDMn0C0A=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
path-parse@^1.0.6:
version "1.0.6"
resolved "https://registry.yarnpkg.com/path-parse/-/path-parse-1.0.6.tgz#d62dbb5679405d72c4737ec58600e9ddcf06d24c"
integrity sha512-GSmOT2EbHrINBf9SR7CDELwlJ8AENk3Qn7OikK4nFYAu3Ote2+JYNVvkpAEQm3/TLNEJFD/xZJjzyxg3KBWOzw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
path-to-regexp@0.1.7:
version "0.1.7"
resolved "https://registry.yarnpkg.com/path-to-regexp/-/path-to-regexp-0.1.7.tgz#df604178005f522f15eb4490e7247a1bfaa67f8c"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-32BBeABfUi8V60SQ5yR6G/qmf4w=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
pbkdf2@^3.0.3:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "3.0.17"
resolved "https://registry.yarnpkg.com/pbkdf2/-/pbkdf2-3.0.17.tgz#976c206530617b14ebb32114239f7b09336e93a6"
integrity sha512-U/il5MsrZp7mGg3mSQfn742na2T+1/vHDCG5/iTI3X9MKUuYUZVLQhyRsg06mCgDBTd57TxzgZt7P+fYfjRLtA==
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
dependencies:
create-hash "^1.1.2"
create-hmac "^1.1.4"
ripemd160 "^2.0.1"
safe-buffer "^5.0.1"
sha.js "^2.4.8"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
pify@^2.0.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
version "2.3.0"
resolved "https://registry.yarnpkg.com/pify/-/pify-2.3.0.tgz#ed141a6ac043a849ea588498e7dca8b15330e90c"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-7RQaasBDqEnqWISY59yosVMw6Qw=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
pify@^4.0.1:
version "4.0.1"
resolved "https://registry.yarnpkg.com/pify/-/pify-4.0.1.tgz#4b2cd25c50d598735c50292224fd8c6df41e3231"
integrity sha512-uB80kBFb/tfd68bVleG9T5GGsGPjJrLAUpR5PZIrhBnIaRTQRjqdJSsIKkOP6OAIFbj7GOrcudc5pNjZ+geV2g==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
pinkie-promise@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/pinkie-promise/-/pinkie-promise-2.0.1.tgz#2135d6dfa7a358c069ac9b178776288228450ffa"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-ITXW36ejWMBprJsXh3YogihFD/o=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
pinkie "^2.0.0"
pinkie@^2.0.0:
version "2.0.4"
resolved "https://registry.yarnpkg.com/pinkie/-/pinkie-2.0.4.tgz#72556b80cfa0d48a974e80e77248e80ed4f7f870"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-clVrgM+g1IqXToDnckjoDtT3+HA=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
pkg-dir@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/pkg-dir/-/pkg-dir-3.0.0.tgz#2749020f239ed990881b1f71210d51eb6523bea3"
integrity sha512-/E57AYkoeQ25qkxMj5PBOVgF8Kiu/h7cYS30Z5+R7WaiCCBfLq58ZI/dSeaEKb9WVJV5n/03QwrN3IeWIFllvw==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
find-up "^3.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
pkg-dir@^4.1.0:
version "4.2.0"
resolved "https://registry.yarnpkg.com/pkg-dir/-/pkg-dir-4.2.0.tgz#f099133df7ede422e81d1d8448270eeb3e4261f3"
integrity sha512-HRDzbaKjC+AOWVXxAU/x54COGeIv9eb+6CkDSQoNTt4XyWoIJvuPsXizxu/Fr23EiekbtZwmh1IcIG/l/a10GQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
find-up "^4.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
portfinder@^1.0.25:
version "1.0.25"
resolved "https://registry.yarnpkg.com/portfinder/-/portfinder-1.0.25.tgz#254fd337ffba869f4b9d37edc298059cb4d35eca"
integrity sha512-6ElJnHBbxVA1XSLgBp7G1FiCkQdlqGzuF7DswL5tcea+E8UpuvPU7beVAjjRwCioTS9ZluNbu+ZyRvgTsmqEBg==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
async "^2.6.2"
debug "^3.1.1"
mkdirp "^0.5.1"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
posix-character-classes@^0.1.0:
version "0.1.1"
resolved "https://registry.yarnpkg.com/posix-character-classes/-/posix-character-classes-0.1.1.tgz#01eac0fe3b5af71a2a6c02feabb8c1fef7e00eab"
integrity sha1-AerA/jta9xoqbAL+q7jB/vfgDqs=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
postcss-modules-extract-imports@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/postcss-modules-extract-imports/-/postcss-modules-extract-imports-2.0.0.tgz#818719a1ae1da325f9832446b01136eeb493cd7e"
integrity sha512-LaYLDNS4SG8Q5WAWqIJgdHPJrDDr/Lv775rMBFUbgjTz6j34lUznACHcdRWroPvXANP2Vj7yNK57vp9eFqzLWQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
postcss "^7.0.5"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
postcss-modules-local-by-default@^3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/postcss-modules-local-by-default/-/postcss-modules-local-by-default-3.0.2.tgz#e8a6561be914aaf3c052876377524ca90dbb7915"
integrity sha512-jM/V8eqM4oJ/22j0gx4jrp63GSvDH6v86OqyTHHUvk4/k1vceipZsaymiZ5PvocqZOl5SFHiFJqjs3la0wnfIQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
icss-utils "^4.1.1"
postcss "^7.0.16"
postcss-selector-parser "^6.0.2"
postcss-value-parser "^4.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
postcss-modules-scope@^2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/postcss-modules-scope/-/postcss-modules-scope-2.1.1.tgz#33d4fc946602eb5e9355c4165d68a10727689dba"
integrity sha512-OXRUPecnHCg8b9xWvldG/jUpRIGPNRka0r4D4j0ESUU2/5IOnpsjfPPmDprM3Ih8CgZ8FXjWqaniK5v4rWt3oQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
postcss "^7.0.6"
postcss-selector-parser "^6.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
postcss-modules-values@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/postcss-modules-values/-/postcss-modules-values-3.0.0.tgz#5b5000d6ebae29b4255301b4a3a54574423e7f10"
integrity sha512-1//E5jCBrZ9DmRX+zCtmQtRSV6PV42Ix7Bzj9GbwJceduuf7IqP8MgeTXuRDHOWj2m0VzZD5+roFWDuU8RQjcg==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
icss-utils "^4.0.0"
postcss "^7.0.6"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
postcss-selector-parser@^6.0.0, postcss-selector-parser@^6.0.2:
version "6.0.2"
resolved "https://registry.yarnpkg.com/postcss-selector-parser/-/postcss-selector-parser-6.0.2.tgz#934cf799d016c83411859e09dcecade01286ec5c"
integrity sha512-36P2QR59jDTOAiIkqEprfJDsoNrvwFei3eCqKd1Y0tUsBimsq39BLp7RD+JWny3WgB1zGhJX8XVePwm9k4wdBg==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
cssesc "^3.0.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
indexes-of "^1.0.1"
uniq "^1.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
postcss-value-parser@^4.0.0, postcss-value-parser@^4.0.2:
version "4.0.3"
resolved "https://registry.yarnpkg.com/postcss-value-parser/-/postcss-value-parser-4.0.3.tgz#651ff4593aa9eda8d5d0d66593a2417aeaeb325d"
integrity sha512-N7h4pG+Nnu5BEIzyeaaIYWs0LI5XC40OrRh5L60z0QjFsqGWcHcbkBvpe1WYpcIS9yQ8sOi/vIPt1ejQCrMVrg==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
postcss@^7.0.14, postcss@^7.0.16, postcss@^7.0.23, postcss@^7.0.5, postcss@^7.0.6:
version "7.0.27"
resolved "https://registry.yarnpkg.com/postcss/-/postcss-7.0.27.tgz#cc67cdc6b0daa375105b7c424a85567345fc54d9"
integrity sha512-WuQETPMcW9Uf1/22HWUWP9lgsIC+KEHg2kozMflKjbeUtw9ujvFX6QmIfozaErDkmLWS9WEnEdEe6Uo9/BNTdQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
chalk "^2.4.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
source-map "^0.6.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
supports-color "^6.1.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
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
prelude-ls@~1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/prelude-ls/-/prelude-ls-1.1.2.tgz#21932a549f5e52ffd9a827f570e04be62a97da54"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-IZMqVJ9eUv/ZqCf1cOBL5iqX2lQ=
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
prettier@1.19.1:
version "1.19.1"
resolved "https://registry.yarnpkg.com/prettier/-/prettier-1.19.1.tgz#f7d7f5ff8a9cd872a7be4ca142095956a60797cb"
integrity sha512-s7PoyDv/II1ObgQunCbB9PdLmUcBZcnWOcxDh7O0N/UwDEsHyqkW+Qh28jW+mVuCdx7gLB0BotYI1Y6uI9iyew==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
pretty-error@^2.0.2:
version "2.1.1"
resolved "https://registry.yarnpkg.com/pretty-error/-/pretty-error-2.1.1.tgz#5f4f87c8f91e5ae3f3ba87ab4cf5e03b1a17f1a3"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-X0+HyPkeWuPzuoerTPXgOxoX8aM=
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
renderkid "^2.0.1"
utila "~0.4"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
private@^0.1.6, private@~0.1.5:
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
version "0.1.8"
resolved "https://registry.yarnpkg.com/private/-/private-0.1.8.tgz#2381edb3689f7a53d653190060fcf822d2f368ff"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-VvivMrbvd2nKkiG38qjULzlc+4Vx4wm/whI9pQD35YrARNnhxeiRktSOhSukRLFNlzg6Br/cJPet5J/u19r/mg==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
process-nextick-args@~2.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "2.0.1"
resolved "https://registry.yarnpkg.com/process-nextick-args/-/process-nextick-args-2.0.1.tgz#7820d9b16120cc55ca9ae7792680ae7dba6d7fe2"
integrity sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
process@^0.11.10:
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
version "0.11.10"
resolved "https://registry.yarnpkg.com/process/-/process-0.11.10.tgz#7332300e840161bda3e69a1d1d91a7d4bc16f182"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-czIwDoQBYb2j5podHZGn1LwW8YI=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
progress@^2.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "2.0.3"
resolved "https://registry.yarnpkg.com/progress/-/progress-2.0.3.tgz#7e8cf8d8f5b8f239c1bc68beb4eb78567d572ef8"
integrity sha512-7PiHtLll5LdnKIMw100I+8xJXR5gW2QwWYkT6iJva0bXitZKa/XMrSbdmg3r2Xnaidz9Qumd0VPaMrZlF9V9sA==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
promise-inflight@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/promise-inflight/-/promise-inflight-1.0.1.tgz#98472870bf228132fcbdd868129bad12c3c029e3"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-mEcocL8igTL8vdhoEputEsPAKeM=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
proxy-addr@~2.0.5:
version "2.0.6"
resolved "https://registry.yarnpkg.com/proxy-addr/-/proxy-addr-2.0.6.tgz#fdc2336505447d3f2f2c638ed272caf614bbb2bf"
integrity sha512-dh/frvCBVmSsDYzw6n926jv974gddhkFPfiN8hPOi30Wax25QZyZEGveluCgliBnqmuM+UJmBErbAUFIoDbjOw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
forwarded "~0.1.2"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ipaddr.js "1.9.1"
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
prr@~1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/prr/-/prr-1.0.1.tgz#d3fc114ba06995a45ec6893f484ceb1d78f5f476"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-0/wRS6BplaRexok/SEzrHXj19HY=
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
public-encrypt@^4.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "4.0.3"
resolved "https://registry.yarnpkg.com/public-encrypt/-/public-encrypt-4.0.3.tgz#4fcc9d77a07e48ba7527e7cbe0de33d0701331e0"
integrity sha512-zVpa8oKZSz5bTMTFClc1fQOnyyEzpl5ozpi1B5YcvBrdohMjH2rfsBtyXcuNuwjsDIXmBYlF2N5FlJYhR29t8Q==
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
dependencies:
bn.js "^4.1.0"
browserify-rsa "^4.0.0"
create-hash "^1.1.0"
parse-asn1 "^5.0.0"
randombytes "^2.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
safe-buffer "^5.1.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
pump@^2.0.0:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
version "2.0.1"
resolved "https://registry.yarnpkg.com/pump/-/pump-2.0.1.tgz#12399add6e4cf7526d973cbc8b5ce2e2908b3909"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-ruPMNRkN3MHP1cWJc9OWr+T/xDP0jhXYCLfJcBuX54hhfIBnaQmAUMfDcG4DM5UMWByBbJY69QSphm3jtDKIkA==
dependencies:
end-of-stream "^1.1.0"
once "^1.3.1"
pump@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/pump/-/pump-3.0.0.tgz#b4a2116815bde2f4e1ea602354e8c75565107a64"
integrity sha512-LwZy+p3SFs1Pytd/jYct4wpv49HiYCqd9Rlc5ZVdk0V+8Yzv6jR5Blk3TRmPL1ft69TxP0IMZGJ+WPFU2BFhww==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
end-of-stream "^1.1.0"
once "^1.3.1"
pumpify@^1.3.3:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.5.1"
resolved "https://registry.yarnpkg.com/pumpify/-/pumpify-1.5.1.tgz#36513be246ab27570b1a374a5ce278bfd74370ce"
integrity sha512-oClZI37HvuUJJxSKKrC17bZ9Cu0ZYhEAGPsPUy9KlMUmv9dKX2o77RUmq7f3XjIxbwyGwYzbzQ1L2Ks8sIradQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
duplexify "^3.6.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
inherits "^2.0.3"
pump "^2.0.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
punycode@1.3.2:
version "1.3.2"
resolved "https://registry.yarnpkg.com/punycode/-/punycode-1.3.2.tgz#9653a036fb7c1ee42342f2325cceefea3926c48d"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-llOgNvt8HuQjQvIyXM7v6jkmxI0=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
punycode@^1.2.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
version "1.4.1"
resolved "https://registry.yarnpkg.com/punycode/-/punycode-1.4.1.tgz#c0d5a63b2718800ad8e1eb0fa5269c84dd41845e"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-wNWmOycYgArY4esPpSachN1BhF4=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
punycode@^2.1.0:
version "2.1.1"
resolved "https://registry.yarnpkg.com/punycode/-/punycode-2.1.1.tgz#b58b010ac40c22c5657616c8d2c2c02c7bf479ec"
integrity sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
qs@6.7.0:
version "6.7.0"
resolved "https://registry.yarnpkg.com/qs/-/qs-6.7.0.tgz#41dc1a015e3d581f1621776be31afb2876a9b1bc"
integrity sha512-VCdBRNFTX1fyE7Nb6FYoURo/SPe62QCaAyzJvUjwRaIsc+NePBEniHlvxFmmX56+HZphIGtV0XeCirBtpDrTyQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
querystring-es3@^0.2.0:
version "0.2.1"
resolved "https://registry.yarnpkg.com/querystring-es3/-/querystring-es3-0.2.1.tgz#9ec61f79049875707d69414596fd907a4d711e73"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-nsYfeQSYdXB9aUFFlv2Qek1xHnM=
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
querystring@0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/querystring/-/querystring-0.2.0.tgz#b209849203bb25df820da756e747005878521620"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-sgmEkgO7Jd+CDadW50cAWHhSFiA=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
querystringify@^2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/querystringify/-/querystringify-2.1.1.tgz#60e5a5fd64a7f8bfa4d2ab2ed6fdf4c85bad154e"
integrity sha512-w7fLxIRCRT7U8Qu53jQnJyPkYZIaR4n5151KMfcJlO/A9397Wxb1amJvROTK6TOnp7PfoAmg/qXiNHI+08jRfA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
randombytes@^2.0.0, randombytes@^2.0.1, randombytes@^2.0.5:
version "2.1.0"
resolved "https://registry.yarnpkg.com/randombytes/-/randombytes-2.1.0.tgz#df6f84372f0270dc65cdf6291349ab7a473d4f2a"
integrity sha512-vYl3iOX+4CKUWuxGi9Ukhie6fsqXqS9FE2Zaic4tNFD2N2QQaXOMFbuKK4QmDHC0JO6B1Zp41J0LpT0oR68amQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
safe-buffer "^5.1.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
randomfill@^1.0.3:
version "1.0.4"
resolved "https://registry.yarnpkg.com/randomfill/-/randomfill-1.0.4.tgz#c92196fc86ab42be983f1bf31778224931d61458"
integrity sha512-87lcbR8+MhcWcUiQ+9e+Rwx8MyR2P7qnt15ynUlbm3TU/fjbgz4GsvfSUDTemtCCtVCqb4ZcEFlyPNTh9bBTLw==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
randombytes "^2.0.5"
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
safe-buffer "^5.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
range-parser@^1.2.1, range-parser@~1.2.1:
version "1.2.1"
resolved "https://registry.yarnpkg.com/range-parser/-/range-parser-1.2.1.tgz#3cf37023d199e1c24d1a55b84800c2f3e6468031"
integrity sha512-Hrgsx+orqoygnmhFbKaHE6c296J+HTAQXoxEF6gNupROmmGJRoyzfG3ccAveqCBrwr/2yxQ5BVd/GTl5agOwSg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
raw-body@2.4.0:
version "2.4.0"
resolved "https://registry.yarnpkg.com/raw-body/-/raw-body-2.4.0.tgz#a1ce6fb9c9bc356ca52e89256ab59059e13d0332"
integrity sha512-4Oz8DUIwdvoa5qMJelxipzi/iJIi40O5cGV1wNYp5hvZP8ZN0T+jiNkL0QepXs+EsQ9XJ8ipEDoiH70ySUJP3Q==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
bytes "3.1.0"
http-errors "1.7.2"
iconv-lite "0.4.24"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
unpipe "1.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"readable-stream@1 || 2", readable-stream@^2.0.0, readable-stream@^2.0.1, readable-stream@^2.0.2, readable-stream@^2.1.5, readable-stream@^2.2.2, readable-stream@^2.3.3, readable-stream@^2.3.6, readable-stream@~2.3.6:
version "2.3.7"
resolved "https://registry.yarnpkg.com/readable-stream/-/readable-stream-2.3.7.tgz#1eca1cf711aef814c04f62252a36a62f6cb23b57"
integrity sha512-Ebho8K4jIbHAxnuxi7o42OrZgF/ZTNcsZj6nRKyUmkhLFq8CHItp/fy6hQZuZmP/n3yZ9VBUbp4zz/mX8hmYPw==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
dependencies:
core-util-is "~1.0.0"
inherits "~2.0.3"
isarray "~1.0.0"
process-nextick-args "~2.0.0"
safe-buffer "~5.1.1"
string_decoder "~1.1.1"
util-deprecate "~1.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
readable-stream@^3.0.6, readable-stream@^3.1.1:
version "3.6.0"
resolved "https://registry.yarnpkg.com/readable-stream/-/readable-stream-3.6.0.tgz#337bbda3adc0706bd3e024426a286d4b4b2c9198"
integrity sha512-BViHy7LKeTz4oNnkcLJ+lVSL6vpiFeX6/d3oSH8zCW7UxP2onchk+vTGB143xuFjHS3deTgkKoXXymXqymiIdA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
inherits "^2.0.3"
string_decoder "^1.1.1"
util-deprecate "^1.0.1"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
readdirp@^2.2.1:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "2.2.1"
resolved "https://registry.yarnpkg.com/readdirp/-/readdirp-2.2.1.tgz#0e87622a3325aa33e892285caf8b4e846529a525"
integrity sha512-1JU/8q+VgFZyxwrJ+SVIOsh+KywWGpds3NTqikiKpDMZWScmAYyKIgqkO+ARvNWJfXeXR1zxz7aHF4u4CyH6vQ==
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
dependencies:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
graceful-fs "^4.1.11"
micromatch "^3.1.10"
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
readable-stream "^2.0.2"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
recast@~0.11.12:
version "0.11.23"
resolved "https://registry.yarnpkg.com/recast/-/recast-0.11.23.tgz#451fd3004ab1e4df9b4e4b66376b2a21912462d3"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-RR/TAEqx5N+bTktmN2sqIZEkYtM=
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
ast-types "0.9.6"
esprima "~3.1.0"
private "~0.1.5"
source-map "~0.5.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
regenerate-unicode-properties@^8.1.0:
version "8.1.0"
resolved "https://registry.yarnpkg.com/regenerate-unicode-properties/-/regenerate-unicode-properties-8.1.0.tgz#ef51e0f0ea4ad424b77bf7cb41f3e015c70a3f0e"
integrity sha512-LGZzkgtLY79GeXLm8Dp0BVLdQlWICzBnJz/ipWUgo59qBaZ+BHtq51P2q1uVZlppMuUAT37SDk39qUbjTWB7bA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
regenerate "^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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
regenerate@^1.4.0:
version "1.4.0"
resolved "https://registry.yarnpkg.com/regenerate/-/regenerate-1.4.0.tgz#4a856ec4b56e4077c557589cae85e7a4c8869a11"
integrity sha512-1G6jJVDWrt0rK99kBjvEtziZNCICAuvIPkSiUFIQxVP06RCVpq3dmDo2oi6ABpYaDYaTRr67BEhL8r1wgEZZKg==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
regenerator-transform@^0.14.0:
version "0.14.1"
resolved "https://registry.yarnpkg.com/regenerator-transform/-/regenerator-transform-0.14.1.tgz#3b2fce4e1ab7732c08f665dfdb314749c7ddd2fb"
integrity sha512-flVuee02C3FKRISbxhXl9mGzdbWUVHubl1SMaknjxkFB1/iqpJhArQUvRxOOPEc/9tAiX0BaQ28FJH10E4isSQ==
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
dependencies:
private "^0.1.6"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
regex-not@^1.0.0, regex-not@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/regex-not/-/regex-not-1.0.2.tgz#1f4ece27e00b0b65e0247a6810e6a85d83a5752c"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-J6SDjUgDxQj5NusnOtdFxDwN/+HWykR8GELwctJ7mdqhcyy1xEc4SRFHUXvxTp661YaVKAjfRLZ9cCqS6tn32A==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
extend-shallow "^3.0.2"
safe-regex "^1.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
regexp.prototype.flags@^1.2.0:
version "1.3.0"
resolved "https://registry.yarnpkg.com/regexp.prototype.flags/-/regexp.prototype.flags-1.3.0.tgz#7aba89b3c13a64509dabcf3ca8d9fbb9bdf5cb75"
integrity sha512-2+Q0C5g951OlYlJz6yu5/M33IcsESLlLfsyIaLJaG4FA2r4yP8MvVMJUUP/fVBkSpbbbZlS5gynbEWLipiiXiQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
define-properties "^1.1.3"
es-abstract "^1.17.0-next.1"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
regexpp@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/regexpp/-/regexpp-2.0.1.tgz#8d19d31cf632482b589049f8281f93dbcba4d07f"
integrity sha512-lv0M6+TkDVniA3aD1Eg0DVpfU/booSu7Eev3TDO/mZKHBfVjgCGTV4t4buppESEYDtkArYFOxTJWv6S5C+iaNw==
regexpu-core@^4.6.0:
version "4.6.0"
resolved "https://registry.yarnpkg.com/regexpu-core/-/regexpu-core-4.6.0.tgz#2037c18b327cfce8a6fea2a4ec441f2432afb8b6"
integrity sha512-YlVaefl8P5BnFYOITTNzDvan1ulLOiXJzCNZxduTIosN17b87h3bvG9yHMoHaRuo88H4mQ06Aodj5VtYGGGiTg==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
regenerate "^1.4.0"
regenerate-unicode-properties "^8.1.0"
regjsgen "^0.5.0"
regjsparser "^0.6.0"
unicode-match-property-ecmascript "^1.0.4"
unicode-match-property-value-ecmascript "^1.1.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
regjsgen@^0.5.0:
version "0.5.1"
resolved "https://registry.yarnpkg.com/regjsgen/-/regjsgen-0.5.1.tgz#48f0bf1a5ea205196929c0d9798b42d1ed98443c"
integrity sha512-5qxzGZjDs9w4tzT3TPhCJqWdCc3RLYwy9J2NB0nm5Lz+S273lvWcpjaTGHsT1dc6Hhfq41uSEOw8wBmxrKOuyg==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
regjsparser@^0.6.0:
version "0.6.3"
resolved "https://registry.yarnpkg.com/regjsparser/-/regjsparser-0.6.3.tgz#74192c5805d35e9f5ebe3c1fb5b40d40a8a38460"
integrity sha512-8uZvYbnfAtEm9Ab8NTb3hdLwL4g/LQzEYP7Xs27T96abJCCE2d6r3cPZPQEsLKy0vRSGVNG+/zVGtLr86HQduA==
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
dependencies:
jsesc "~0.5.0"
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
relateurl@0.2.x:
version "0.2.7"
resolved "https://registry.yarnpkg.com/relateurl/-/relateurl-0.2.7.tgz#54dbf377e51440aca90a4cd274600d3ff2d888a9"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-VNvzd+UUQKypCkzSdGANP/LYiKk=
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -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
remove-trailing-separator@^1.0.1:
version "1.1.0"
resolved "https://registry.yarnpkg.com/remove-trailing-separator/-/remove-trailing-separator-1.1.0.tgz#c24bce2a283adad5bc3f58e0d48249b92379d8ef"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-wkvOKig62tW8P1jg1IJJuSN52O8=
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
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
renderkid@^2.0.1:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "2.0.3"
resolved "https://registry.yarnpkg.com/renderkid/-/renderkid-2.0.3.tgz#380179c2ff5ae1365c522bf2fcfcff01c5b74149"
integrity sha512-z8CLQp7EZBPCwCnncgf9C4XAi3WR0dv+uWu/PjIyhhAb5d6IJ/QZqlHFprHeKT+59//V6BNUsLbvN8+2LarxGA==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
css-select "^1.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
dom-converter "^0.2"
htmlparser2 "^3.3.0"
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
strip-ansi "^3.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
utila "^0.4.0"
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -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
repeat-element@^1.1.2:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "1.1.3"
resolved "https://registry.yarnpkg.com/repeat-element/-/repeat-element-1.1.3.tgz#782e0d825c0c5a3bb39731f84efee6b742e6b1ce"
integrity sha512-ahGq0ZnV5m5XtZLMb+vP76kcAM5nkLqk0lpqAuojSKGgQtn4eRi4ZZGm2olo2zKFH+sMsWaqOCW1dqAnOru72g==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
repeat-string@^1.6.1:
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
version "1.6.1"
resolved "https://registry.yarnpkg.com/repeat-string/-/repeat-string-1.6.1.tgz#8dcae470e1c88abc2d600fff4a776286da75e637"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-jcrkcOHIirwtYA//Sndihtp15jc=
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
require-directory@^2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/require-directory/-/require-directory-2.1.1.tgz#8c64ad5fd30dab1c976e2344ffe7f792a6a6df42"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-jGStX9MNqxyXbiNE/+f3kqam30I=
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
require-main-filename@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/require-main-filename/-/require-main-filename-1.0.1.tgz#97f717b69d48784f5f526a6c5aa8ffdda055a4d1"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-l/cXtp1IeE9fUmpsWqj/3aBVpNE=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
require-main-filename@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/require-main-filename/-/require-main-filename-2.0.0.tgz#d0b329ecc7cc0f61649f62215be69af54aa8989b"
integrity sha512-NKN5kMDylKuldxYLSUfrbo5Tuzh4hd+2E8NPPX02mZtn1VuREQToYe/ZdlJy+J3uCpfaiGF05e7B8W0iXbQHmg==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
requires-port@^1.0.0:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
version "1.0.0"
resolved "https://registry.yarnpkg.com/requires-port/-/requires-port-1.0.0.tgz#925d2601d39ac485e091cf0da5c6e694dc3dcaff"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-kl0mAdOaxIXgkc8NpcbmlNw9yv8=
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
resolve-cwd@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/resolve-cwd/-/resolve-cwd-2.0.0.tgz#00a9f7387556e27038eae232caa372a6a59b665a"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-AKn3OHVW4nA46uIyyqNypqWbZlo=
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
dependencies:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
resolve-from "^3.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
resolve-dir@^1.0.0, resolve-dir@^1.0.1:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/resolve-dir/-/resolve-dir-1.0.1.tgz#79a40644c362be82f26effe739c9bb5382046f43"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-eaQGRMNivoLybv/nOcm7U4IEb0M=
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
dependencies:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
expand-tilde "^2.0.0"
global-modules "^1.0.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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
resolve-from@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/resolve-from/-/resolve-from-3.0.0.tgz#b22c7af7d9d6881bc8b6e653335eebcb0a188748"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-six699nWiBvItuZTM17rywoYh0g=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
resolve-from@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/resolve-from/-/resolve-from-4.0.0.tgz#4abcd852ad32dd7baabfe9b40e00a36db5f392e6"
integrity sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
resolve-url@^0.2.1:
version "0.2.1"
resolved "https://registry.yarnpkg.com/resolve-url/-/resolve-url-0.2.1.tgz#2c637fe77c893afd2a663fe21aa9080068e2052a"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-LGN/53yJOv0qZj/iGqkIAGjiBSo=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
resolve@^1.3.2:
version "1.15.1"
resolved "https://registry.yarnpkg.com/resolve/-/resolve-1.15.1.tgz#27bdcdeffeaf2d6244b95bb0f9f4b4653451f3e8"
integrity sha512-84oo6ZTtoTUpjgNEr5SJyzQhzL72gaRodsSfyxC/AXRvwu0Yse9H8eF9IpGo7b8YetZhlI6v7ZQ6bKBFV/6S7w==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
path-parse "^1.0.6"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
restore-cursor@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/restore-cursor/-/restore-cursor-3.1.0.tgz#39f67c54b3a7a58cea5236d95cf0034239631f7e"
integrity sha512-l+sSefzHpj5qimhFSE5a8nufZYAM3sBSVMAPtYkmC+4EH2anSGaEMXSD0izRQbu9nfyQ9y5JrVmp7E8oZrUjvA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
onetime "^5.1.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
signal-exit "^3.0.2"
ret@~0.1.10:
version "0.1.15"
resolved "https://registry.yarnpkg.com/ret/-/ret-0.1.15.tgz#b8a4825d5bdb1fc3f6f53c2bc33f81388681c7bc"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-TTlYpa+OL+vMMNG24xSlQGEJ3B/RzEfUlLct7b5G/ytav+wPrplCpVMFuwzXbkecJrb6IYo1iFb0S9v37754mg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
retry@^0.12.0:
version "0.12.0"
resolved "https://registry.yarnpkg.com/retry/-/retry-0.12.0.tgz#1b42a6266a21f07421d1b0b54b7dc167b01c013b"
integrity sha1-G0KmJmoh8HQh0bC1S33BZ7AcATs=
rimraf@2.6.3:
version "2.6.3"
resolved "https://registry.yarnpkg.com/rimraf/-/rimraf-2.6.3.tgz#b2d104fe0d8fb27cf9e0a1cda8262dd3833c6cab"
integrity sha512-mwqeW5XsA2qAejG46gYdENaxXjx9onRNCfn7L0duuP4hCuTIi/QO7PDK07KJfp1d+izWPrzEJDcSqBa0OZQriA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
glob "^7.1.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
rimraf@^2.5.4, rimraf@^2.6.3, rimraf@^2.7.1:
version "2.7.1"
resolved "https://registry.yarnpkg.com/rimraf/-/rimraf-2.7.1.tgz#35797f13a7fdadc566142c29d4f07ccad483e3ec"
integrity sha512-uWjbaKIK3T1OSVptzX7Nl6PvQ3qAGtKEtVRjRuazjfL3Bx5eI409VZSqgND+4UNnmzLVdPj9FqFJNPqBZFve4w==
dependencies:
glob "^7.1.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
ripemd160@^2.0.0, ripemd160@^2.0.1:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "2.0.2"
resolved "https://registry.yarnpkg.com/ripemd160/-/ripemd160-2.0.2.tgz#a1c1a6f624751577ba5d07914cbc92850585890c"
integrity sha512-ii4iagi25WusVoiC4B4lq7pbXfAp3D9v5CwfkY33vffw2+pkDjY1D8GaN7spsxvCSx8dkPqOZCEZyfxcmJG2IA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
hash-base "^3.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
inherits "^2.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
run-async@^2.4.0:
version "2.4.0"
resolved "https://registry.yarnpkg.com/run-async/-/run-async-2.4.0.tgz#e59054a5b86876cfae07f431d18cbaddc594f1e8"
integrity sha512-xJTbh/d7Lm7SBhc1tNvTpeCHaEzoyxPrqNlvSdMfBTYwaY++UJFyXUOxAtsRUXjlqOfj8luNaR9vjCh4KeV+pg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
is-promise "^2.1.0"
run-queue@^1.0.0, run-queue@^1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/run-queue/-/run-queue-1.0.3.tgz#e848396f057d223f24386924618e25694161ec47"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-6Eg5bwV9Ij8kOGkkYY4laUFh7Ec=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
aproba "^1.1.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
rxjs@^6.5.3:
version "6.5.4"
resolved "https://registry.yarnpkg.com/rxjs/-/rxjs-6.5.4.tgz#e0777fe0d184cec7872df147f303572d414e211c"
integrity sha512-naMQXcgEo3csAEGvw/NydRA0fuS2nDZJiw1YUWFKU7aPPAPGZEsD4Iimit96qwCieH6y614MCLYwdkrWx7z/7Q==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
tslib "^1.9.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
safe-buffer@5.1.2, safe-buffer@~5.1.0, safe-buffer@~5.1.1:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "5.1.2"
resolved "https://registry.yarnpkg.com/safe-buffer/-/safe-buffer-5.1.2.tgz#991ec69d296e0313747d59bdfd2b745c35f8828d"
integrity sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
safe-buffer@>=5.1.0, safe-buffer@^5.0.1, safe-buffer@^5.1.0, safe-buffer@^5.1.1, safe-buffer@^5.1.2, safe-buffer@~5.2.0:
version "5.2.0"
resolved "https://registry.yarnpkg.com/safe-buffer/-/safe-buffer-5.2.0.tgz#b74daec49b1148f88c64b68d49b1e815c1f2f519"
integrity sha512-fZEwUGbVl7kouZs1jCdMLdt95hdIv0ZeHg6L7qPeciMZhZ+/gdesW4wgTARkrFWEpspjEATAzUGPG8N2jJiwbg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
safe-regex@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/safe-regex/-/safe-regex-1.1.0.tgz#40a3669f3b077d1e943d44629e157dd48023bf2e"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-QKNmnzsHfR6UPURinhV91IAjvy4=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
ret "~0.1.10"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"safer-buffer@>= 2.1.2 < 3":
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "2.1.2"
resolved "https://registry.yarnpkg.com/safer-buffer/-/safer-buffer-2.1.2.tgz#44fa161b0187b9549dd84bb91802f9bd8385cd6a"
integrity sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==
schema-utils@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/schema-utils/-/schema-utils-1.0.0.tgz#0b79a93204d7b600d4b2850d1f66c2a34951c770"
integrity sha512-i27Mic4KovM/lnGsy8whRCHhc7VicJajAjTrYg11K9zfZXnYIt4k5F+kZkwjnrhKzLic/HLU4j11mjsz2G/75g==
dependencies:
ajv "^6.1.0"
ajv-errors "^1.0.0"
ajv-keywords "^3.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
schema-utils@^2.5.0, schema-utils@^2.6.0, schema-utils@^2.6.1, schema-utils@^2.6.4:
version "2.6.4"
resolved "https://registry.yarnpkg.com/schema-utils/-/schema-utils-2.6.4.tgz#a27efbf6e4e78689d91872ee3ccfa57d7bdd0f53"
integrity sha512-VNjcaUxVnEeun6B2fiiUDjXXBtD4ZSH7pdbfIu1pOFwgptDPLMo/z9jr4sUfsjFVPqDCEin/F7IYlq7/E6yDbQ==
dependencies:
ajv "^6.10.2"
ajv-keywords "^3.4.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
select-hose@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/select-hose/-/select-hose-2.0.0.tgz#625d8658f865af43ec962bfc376a37359a4994ca"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-Yl2GWPhlr0Psliv8N2o3NZpJlMo=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
selfsigned@^1.10.7:
version "1.10.7"
resolved "https://registry.yarnpkg.com/selfsigned/-/selfsigned-1.10.7.tgz#da5819fd049d5574f28e88a9bcc6dbc6e6f3906b"
integrity sha512-8M3wBCzeWIJnQfl43IKwOmC4H/RAp50S8DF60znzjW5GVqTcSe2vWclt7hmYVPkKPlHWOu5EaWOMZ2Y6W8ZXTA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
node-forge "0.9.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
semver@7.0.0:
version "7.0.0"
resolved "https://registry.yarnpkg.com/semver/-/semver-7.0.0.tgz#5f3ca35761e47e05b206c6daff2cf814f0316b8e"
integrity sha512-+GB6zVA9LWh6zovYQLALHwv5rb2PHGlJi3lfiqIHxR0uuwCgefcOJc59v9fv1w8GbStwxuuqqAjI9NMAOOgq1A==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
semver@^5.4.1, semver@^5.5.0, semver@^5.6.0:
version "5.7.1"
resolved "https://registry.yarnpkg.com/semver/-/semver-5.7.1.tgz#a954f931aeba508d307bbf069eff0c01c96116f7"
integrity sha512-sauaDf/PZdVgrLTNYHRtpXa1iRiKcaebiKQ1BJdpQlWH2lCvexQdX55snPFyK7QzpudqbCI0qXFfOasHdyNDGQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
semver@^6.0.0, semver@^6.1.2, semver@^6.3.0:
version "6.3.0"
resolved "https://registry.yarnpkg.com/semver/-/semver-6.3.0.tgz#ee0a64c8af5e8ceea67687b133761e1becbd1d3d"
integrity sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==
send@0.17.1:
version "0.17.1"
resolved "https://registry.yarnpkg.com/send/-/send-0.17.1.tgz#c1d8b059f7900f7466dd4938bdc44e11ddb376c8"
integrity sha512-BsVKsiGcQMFwT8UxypobUKyv7irCNRHk1T0G680vk88yf6LBByGcZJOTJCrTP2xVN6yI+XjPJcNuE3V4fT9sAg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
debug "2.6.9"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
depd "~1.1.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
destroy "~1.0.4"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
encodeurl "~1.0.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
escape-html "~1.0.3"
etag "~1.8.1"
fresh "0.5.2"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
http-errors "~1.7.2"
mime "1.6.0"
ms "2.1.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
on-finished "~2.3.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
range-parser "~1.2.1"
statuses "~1.5.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
serialize-javascript@^2.1.2:
version "2.1.2"
resolved "https://registry.yarnpkg.com/serialize-javascript/-/serialize-javascript-2.1.2.tgz#ecec53b0e0317bdc95ef76ab7074b7384785fa61"
integrity sha512-rs9OggEUF0V4jUSecXazOYsLfu7OGK2qIn3c7IPBiffz32XniEp/TX9Xmc9LQfK2nQ2QKHvZ2oygKUGU0lG4jQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
serve-index@^1.9.1:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
version "1.9.1"
resolved "https://registry.yarnpkg.com/serve-index/-/serve-index-1.9.1.tgz#d3768d69b1e7d82e5ce050fff5b453bea12a9239"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-03aNabHn2C5c4FD/9bRTvqEqkjk=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05: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"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
serve-static@1.14.1:
version "1.14.1"
resolved "https://registry.yarnpkg.com/serve-static/-/serve-static-1.14.1.tgz#666e636dc4f010f7ef29970a88a674320898b2f9"
integrity sha512-JMrvUwE54emCYWlTI+hGrGv5I8dEwmco/00EvkzIIsR7MqrHonbD9pO2MOfFnpFntl7ecpZs+3mW+XbQZu9QCg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
encodeurl "~1.0.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
escape-html "~1.0.3"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
parseurl "~1.3.3"
send "0.17.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
set-blocking@^2.0.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
version "2.0.0"
resolved "https://registry.yarnpkg.com/set-blocking/-/set-blocking-2.0.0.tgz#045f9782d011ae9a6803ddd382b24392b3d890f7"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-BF+XgtARrppoA93TgrJDkrPYkPc=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
set-value@^2.0.0, set-value@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/set-value/-/set-value-2.0.1.tgz#a18d40530e6f07de4228c7defe4227af8cad005b"
integrity sha512-JxHc1weCN68wRY0fhCoXpyK55m/XPHafOmK4UWD7m2CI14GMcFypt4w/0+NV5f/ZMby2F6S2wwA7fgynh9gWSw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
extend-shallow "^2.0.1"
is-extendable "^0.1.1"
is-plain-object "^2.0.3"
split-string "^3.0.1"
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
setimmediate@^1.0.4:
version "1.0.5"
resolved "https://registry.yarnpkg.com/setimmediate/-/setimmediate-1.0.5.tgz#290cbb232e306942d7d7ea9b83732ab7856f8285"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-KQy7Iy4waULX1+qbg3Mqt4VvgoU=
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
setprototypeof@1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/setprototypeof/-/setprototypeof-1.1.0.tgz#d0bd85536887b6fe7c0d818cb962d9d91c54e656"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-BvE/TwpZX4FXExxOxZyRGQQv651MSwmWKZGqvmPcRIjDqWub67kTKuIMx43cZZrS/cBBzwBcNDWoFxt2XEFIpQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
setprototypeof@1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/setprototypeof/-/setprototypeof-1.1.1.tgz#7e95acb24aa92f5885e0abef5ba131330d4ae683"
integrity sha512-JvdAWfbXeIGaZ9cILp38HntZSFSo3mWg6xGcJJsd+d4aRMOqauag1C63dJfDw7OaMYwEbHMOxEZ1lqVRYP2OAw==
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
sha.js@^2.4.0, sha.js@^2.4.8:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "2.4.11"
resolved "https://registry.yarnpkg.com/sha.js/-/sha.js-2.4.11.tgz#37a5cf0b81ecbc6943de109ba2960d1b26584ae7"
integrity sha512-QMEp5B7cftE7APOjk5Y6xgrbWu+WkLVQwk8JNjZ8nKRciZaByEW6MubieAiToS7+dwvrjGhH8jRXz3MVd0AYqQ==
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
dependencies:
inherits "^2.0.1"
safe-buffer "^5.0.1"
shebang-command@^1.2.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/shebang-command/-/shebang-command-1.2.0.tgz#44aac65b695b03398968c39f363fee5deafdf1ea"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-RKrGW2lbAzmJaMOfNj/uXer98eo=
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
dependencies:
shebang-regex "^1.0.0"
shebang-regex@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/shebang-regex/-/shebang-regex-1.0.0.tgz#da42f49740c0b42db2ca9728571cb190c98efea3"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-2kL0l0DAtC2yypcoVxyxkMmO/qM=
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
signal-exit@^3.0.0, signal-exit@^3.0.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
version "3.0.2"
resolved "https://registry.yarnpkg.com/signal-exit/-/signal-exit-3.0.2.tgz#b5fdc08f1287ea1178628e415e25132b73646c6d"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-tf3AjxKH6hF4Yo5BXiUTK3NkbG0=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
slice-ansi@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/slice-ansi/-/slice-ansi-2.1.0.tgz#cacd7693461a637a5788d92a7dd4fba068e81636"
integrity sha512-Qu+VC3EwYLldKa1fCxuuvULvSJOKEgk9pi8dZeCVK7TqBfUNTH4sFkk4joj8afVSfAYgJoSOetjx9QWOJ5mYoQ==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ansi-styles "^3.2.0"
astral-regex "^1.0.0"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
is-fullwidth-code-point "^2.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
snapdragon-node@^2.0.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/snapdragon-node/-/snapdragon-node-2.1.1.tgz#6c175f86ff14bdb0724563e8f3c1b021a286853b"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-O27l4xaMYt/RSQ5TR3vpWCAB5Kb/czIcqUFOM/C4fYcLnbZUc1PkjTAMjof2pBWaSTwOUd6qUHcFGVGj7aIwnw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
define-property "^1.0.0"
isobject "^3.0.0"
snapdragon-util "^3.0.1"
snapdragon-util@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/snapdragon-util/-/snapdragon-util-3.0.1.tgz#f956479486f2acd79700693f6f7b805e45ab56e2"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-mbKkMdQKsjX4BAL4bRYTj21edOf8cN7XHdYUJEe+Zn99hVEYcMvKPct1IqNe7+AZPirn8BCDOQBHQZknqmKlZQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
kind-of "^3.2.0"
snapdragon@^0.8.1:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "0.8.2"
resolved "https://registry.yarnpkg.com/snapdragon/-/snapdragon-0.8.2.tgz#64922e7c565b0e14204ba1aa7d6964278d25182d"
integrity sha512-FtyOnWN/wCHTVXOMwvSv26d+ko5vWlIDD6zoUJ7LW8vh+ZBC8QdljveRP+crNrtBwioEUWy/4dMtbBjA4ioNlg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
base "^0.11.1"
debug "^2.2.0"
define-property "^0.2.5"
extend-shallow "^2.0.1"
map-cache "^0.2.2"
source-map "^0.5.6"
source-map-resolve "^0.5.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
use "^3.1.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
sockjs-client@1.4.0:
version "1.4.0"
resolved "https://registry.yarnpkg.com/sockjs-client/-/sockjs-client-1.4.0.tgz#c9f2568e19c8fd8173b4997ea3420e0bb306c7d5"
integrity sha512-5zaLyO8/nri5cua0VtOrFXBPK1jbL4+1cebT/mmKA1E1ZXOvJrII75bPu0l0k843G/+iAbhEqzyKr0w/eCCj7g==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
debug "^3.2.5"
eventsource "^1.0.7"
faye-websocket "~0.11.1"
inherits "^2.0.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
json3 "^3.3.2"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
url-parse "^1.4.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
sockjs@0.3.19:
version "0.3.19"
resolved "https://registry.yarnpkg.com/sockjs/-/sockjs-0.3.19.tgz#d976bbe800af7bd20ae08598d582393508993c0d"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-V48klKZl8T6MzatbLlzzRNhMepEys9Y4oGFpypBFFn1gLI/QQ9HtLLyWJNbPlwGLelOVOEijUbTTJeLLI59jLw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
faye-websocket "^0.10.0"
uuid "^3.0.1"
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
source-list-map@^2.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "2.0.1"
resolved "https://registry.yarnpkg.com/source-list-map/-/source-list-map-2.0.1.tgz#3993bd873bfc48479cca9ea3a547835c7c154b34"
integrity sha512-qnQ7gVMxGNxsiL4lEuJwe/To8UnK7fAnmbGEEH8RpLouuKbeEm0lhbQVFIrNSuB+G7tVrAlVsZgETT5nljf+Iw==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
source-map-resolve@^0.5.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "0.5.3"
resolved "https://registry.yarnpkg.com/source-map-resolve/-/source-map-resolve-0.5.3.tgz#190866bece7553e1f8f267a2ee82c606b5509a1a"
integrity sha512-Htz+RnsXWk5+P2slx5Jh3Q66vhQj1Cllm0zvnaY98+NFx+Dv2CF/f5O/t8x+KaNdrdIAsruNzoh/KpialbqAnw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
atob "^2.1.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
decode-uri-component "^0.2.0"
resolve-url "^0.2.1"
source-map-url "^0.4.0"
urix "^0.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
source-map-support@~0.5.12:
version "0.5.16"
resolved "https://registry.yarnpkg.com/source-map-support/-/source-map-support-0.5.16.tgz#0ae069e7fe3ba7538c64c98515e35339eac5a042"
integrity sha512-efyLRJDr68D9hBBNIPWFjhpFzURh+KJykQwvMyW5UiZzYwoF6l4YMMDIJJEyFWxWCqfyxLzz6tSfUFR+kXXsVQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
buffer-from "^1.0.0"
source-map "^0.6.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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
source-map-url@^0.4.0:
version "0.4.0"
resolved "https://registry.yarnpkg.com/source-map-url/-/source-map-url-0.4.0.tgz#3e935d7ddd73631b97659956d55128e87b5084a3"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-PpNdfd1zYxuXZZlW1VEo6HtQhKM=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
source-map@^0.5.0, source-map@^0.5.6, source-map@~0.5.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
version "0.5.7"
resolved "https://registry.yarnpkg.com/source-map/-/source-map-0.5.7.tgz#8a039d2d1021d22d1ea14c80d8ea468ba2ef3fcc"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-igOdLRAh0i0eoUyA2OpGi6LvP8w=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
source-map@^0.6.0, source-map@^0.6.1, source-map@~0.6.0, source-map@~0.6.1:
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
version "0.6.1"
resolved "https://registry.yarnpkg.com/source-map/-/source-map-0.6.1.tgz#74722af32e9614e9c287a8d0bbde48b5e2f1a263"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
spdy-transport@^3.0.0:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "3.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
resolved "https://registry.yarnpkg.com/spdy-transport/-/spdy-transport-3.0.0.tgz#00d4863a6400ad75df93361a1608605e5dcdcf31"
integrity sha512-hsLVFE5SjA6TCisWeJXFKniGGOpBgMLmerfO2aCyCU5s7nJ/rpAepqmFifv/GCbSbueEeAJJnmSQ2rKC/g8Fcw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
debug "^4.1.0"
detect-node "^2.0.4"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
hpack.js "^2.1.6"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
obuf "^1.1.2"
readable-stream "^3.0.6"
wbuf "^1.7.3"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
spdy@^4.0.1:
version "4.0.1"
resolved "https://registry.yarnpkg.com/spdy/-/spdy-4.0.1.tgz#6f12ed1c5db7ea4f24ebb8b89ba58c87c08257f2"
integrity sha512-HeZS3PBdMA+sZSu0qwpCxl3DeALD5ASx8pAX0jZdKXSpPWbQ6SYGnlg3BBmYLx5LtiZrmkAZfErCm2oECBcioA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
debug "^4.1.0"
handle-thing "^2.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
http-deceiver "^1.2.7"
select-hose "^2.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
spdy-transport "^3.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
split-string@^3.0.1, split-string@^3.0.2:
version "3.1.0"
resolved "https://registry.yarnpkg.com/split-string/-/split-string-3.1.0.tgz#7cb09dda3a86585705c64b39a6466038682e8fe2"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-NzNVhJDYpwceVVii8/Hu6DKfD2G+NrQHlS/V/qgv763EYudVwEcMQNxd2lh+0VrUByXN/oJkl5grOhYWvQUYiw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
extend-shallow "^3.0.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
sprintf-js@~1.0.2:
version "1.0.3"
resolved "https://registry.yarnpkg.com/sprintf-js/-/sprintf-js-1.0.3.tgz#04e6926f662895354f3dd015203633b857297e2c"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-BOaSb2YolTVPPdAVIDYzuFcpfiw=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ssri@^6.0.1:
version "6.0.1"
resolved "https://registry.yarnpkg.com/ssri/-/ssri-6.0.1.tgz#2a3c41b28dd45b62b63676ecb74001265ae9edd8"
integrity sha512-3Wge10hNcT1Kur4PDFwEieXSCMCJs/7WvSACcrMYrNp+b8kDL1/0wJch5Ni2WrtwEa2IO8OsVfeKIciKCDx/QA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
figgy-pudding "^3.5.1"
ssri@^7.0.0:
version "7.1.0"
resolved "https://registry.yarnpkg.com/ssri/-/ssri-7.1.0.tgz#92c241bf6de82365b5c7fb4bd76e975522e1294d"
integrity sha512-77/WrDZUWocK0mvA5NTRQyveUf+wsrIc6vyrxpS8tVvYBcX215QbafrJR3KtkpskIzoFLqqNuuYQvxaMjXJ/0g==
dependencies:
figgy-pudding "^3.5.1"
minipass "^3.1.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
static-extend@^0.1.1:
version "0.1.2"
resolved "https://registry.yarnpkg.com/static-extend/-/static-extend-0.1.2.tgz#60809c39cbff55337226fd5e0b520f341f1fb5c6"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-YICcOcv/VTNyJv1eC1IPNB8ftcY=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
define-property "^0.2.5"
object-copy "^0.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"statuses@>= 1.4.0 < 2", "statuses@>= 1.5.0 < 2", statuses@~1.5.0:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "1.5.0"
resolved "https://registry.yarnpkg.com/statuses/-/statuses-1.5.0.tgz#161c7dac177659fd9811f43771fa99381478628c"
integrity sha1-Fhx9rBd2Wf2YEfQ3cfqZOBR4Yow=
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
stream-browserify@^2.0.1:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "2.0.2"
resolved "https://registry.yarnpkg.com/stream-browserify/-/stream-browserify-2.0.2.tgz#87521d38a44aa7ee91ce1cd2a47df0cb49dd660b"
integrity sha512-nX6hmklHs/gr2FuxYDltq8fJA1GDlxKQCz8O/IM4atRqBH8OORmBNgfvW5gG10GT/qQ9u0CzIvr2X5Pkt6ntqg==
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
dependencies:
inherits "~2.0.1"
readable-stream "^2.0.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
stream-each@^1.1.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.2.3"
resolved "https://registry.yarnpkg.com/stream-each/-/stream-each-1.2.3.tgz#ebe27a0c389b04fbcc233642952e10731afa9bae"
integrity sha512-vlMC2f8I2u/bZGqkdfLQW/13Zihpej/7PmSiMQsbYddxuTsJp8vRe2x2FvVExZg7FaOds43ROAuFJwPR4MTZLw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
end-of-stream "^1.1.0"
stream-shift "^1.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
stream-http@^2.7.2:
version "2.8.3"
resolved "https://registry.yarnpkg.com/stream-http/-/stream-http-2.8.3.tgz#b2d242469288a5a27ec4fe8933acf623de6514fc"
integrity sha512-+TSkfINHDo4J+ZobQLWiMouQYB+UVYFttRA94FpEzzJ7ZdqcL4uUUQ7WkdkI4DSozGmgBUE/a47L+38PenXhUw==
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
dependencies:
builtin-status-codes "^3.0.0"
inherits "^2.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
readable-stream "^2.3.6"
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
to-arraybuffer "^1.0.0"
xtend "^4.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
stream-shift@^1.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/stream-shift/-/stream-shift-1.0.1.tgz#d7088281559ab2778424279b0877da3c392d5a3d"
integrity sha512-AiisoFqQ0vbGcZgQPY1cdP2I76glaVA/RauYR4G4thNFgkTqr90yXTo4LYX60Jl+sIlPNHHdGSwo01AvbKUSVQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
string-width@^1.0.1:
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
version "1.0.2"
resolved "https://registry.yarnpkg.com/string-width/-/string-width-1.0.2.tgz#118bdf5b8cdc51a2a7e70d211e07e2b0b9b107d3"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-EYvfW4zcUaKn5w0hHgfisLmxB9M=
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
dependencies:
code-point-at "^1.0.0"
is-fullwidth-code-point "^1.0.0"
strip-ansi "^3.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
string-width@^2.0.0, string-width@^2.1.1:
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
version "2.1.1"
resolved "https://registry.yarnpkg.com/string-width/-/string-width-2.1.1.tgz#ab93f27a8dc13d28cac815c462143a6d9012ae9e"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-nOqH59deCq9SRHlxq1Aw85Jnt4w6KvLKqWVik6oA9ZklXLNIOlqg4F2yrT1MVaTjAqvVwdfeZ7w7aCvJD7ugkw==
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
dependencies:
is-fullwidth-code-point "^2.0.0"
strip-ansi "^4.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
string-width@^3.0.0, string-width@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/string-width/-/string-width-3.1.0.tgz#22767be21b62af1081574306f69ac51b62203961"
integrity sha512-vafcv6KjVZKSgz06oM/H6GDBrAtz8vdhQakGjFIvNrHA6y3HCF1CInLy+QLq8dTJPQ1b+KDUqDFctkdRW44e1w==
dependencies:
emoji-regex "^7.0.1"
is-fullwidth-code-point "^2.0.0"
strip-ansi "^5.1.0"
string-width@^4.1.0:
version "4.2.0"
resolved "https://registry.yarnpkg.com/string-width/-/string-width-4.2.0.tgz#952182c46cc7b2c313d1596e623992bd163b72b5"
integrity sha512-zUz5JD+tgqtuDjMhwIg5uFVV3dtqZ9yQJlZVfq4I01/K5Paj5UHj7VyrQOJvzawSVlKpObApbfD0Ed6yJc+1eg==
dependencies:
emoji-regex "^8.0.0"
is-fullwidth-code-point "^3.0.0"
strip-ansi "^6.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
string.prototype.trimleft@^2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/string.prototype.trimleft/-/string.prototype.trimleft-2.1.1.tgz#9bdb8ac6abd6d602b17a4ed321870d2f8dcefc74"
integrity sha512-iu2AGd3PuP5Rp7x2kEZCrB2Nf41ehzh+goo8TV7z8/XDBbsvc6HQIlUl9RjkZ4oyrW1XM5UwlGl1oVEaDjg6Ag==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
define-properties "^1.1.3"
function-bind "^1.1.1"
string.prototype.trimright@^2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/string.prototype.trimright/-/string.prototype.trimright-2.1.1.tgz#440314b15996c866ce8a0341894d45186200c5d9"
integrity sha512-qFvWL3/+QIgZXVmJBfpHmxLB7xsUXz6HsUmP8+5dRaC3Q7oKUv9Vo6aMCRZC1smrtyECFsIT30PqBJ1gTjAs+g==
dependencies:
define-properties "^1.1.3"
function-bind "^1.1.1"
string_decoder@^1.0.0, string_decoder@^1.1.1:
version "1.3.0"
resolved "https://registry.yarnpkg.com/string_decoder/-/string_decoder-1.3.0.tgz#42f114594a46cf1a8e30b0a84f56c78c3edac21e"
integrity sha512-hkRX8U1WjJFd8LsDJ2yQ/wWWxaopEsABU1XfkM8A+j0+85JAGppt16cr1Whg6KIbb4okU6Mql6BOj+uup/wKeA==
dependencies:
safe-buffer "~5.2.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
string_decoder@~1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/string_decoder/-/string_decoder-1.1.1.tgz#9cf1611ba62685d7030ae9e4ba34149c3af03fc8"
integrity sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==
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
dependencies:
safe-buffer "~5.1.0"
strip-ansi@^3.0.0, strip-ansi@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-3.0.1.tgz#6a385fb8853d952d5ff05d0e8aaf94278dc63dcf"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-ajhfuIU9lS1f8F0Oiq+UJ43GPc8=
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
dependencies:
ansi-regex "^2.0.0"
strip-ansi@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-4.0.0.tgz#a8479022eb1ac368a871389b635262c505ee368f"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-qEeQIusaw2iocTibY1JixQXuNo8=
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
dependencies:
ansi-regex "^3.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
strip-ansi@^5.0.0, strip-ansi@^5.1.0, strip-ansi@^5.2.0:
version "5.2.0"
resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-5.2.0.tgz#8c9a536feb6afc962bdfa5b104a5091c1ad9c0ae"
integrity sha512-DuRs1gKbBqsMKIZlrffwlug8MHkcnpjs5VPmL1PAh+mA30U0DTotfDZ0d2UUsXpPmPmMMJ6W773MaA3J+lbiWA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ansi-regex "^4.1.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
strip-ansi@^6.0.0:
version "6.0.0"
resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-6.0.0.tgz#0b1571dd7669ccd4f3e06e14ef1eed26225ae532"
integrity sha512-AuvKTrTfQNYNIctbR1K/YGTR1756GycPsg7b9bdV9Duqur4gv6aKqHXah67Z8ImS7WEz5QVcOtlfW2rZEugt6w==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ansi-regex "^5.0.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
strip-eof@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/strip-eof/-/strip-eof-1.0.0.tgz#bb43ff5598a6eb05d89b59fcd129c983313606bf"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-u0P/VZim6wXYm1n80SnJgzE2Br8=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
strip-json-comments@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/strip-json-comments/-/strip-json-comments-3.0.1.tgz#85713975a91fb87bf1b305cca77395e40d2a64a7"
integrity sha512-VTyMAUfdm047mwKl+u79WIdrZxtFtn+nBxHeb844XBQ9uMNTuTHdx2hc5RiAJYqwTj3wc/xe5HLSdJSkJ+WfZw==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
style-loader@^1.1.3:
version "1.1.3"
resolved "https://registry.yarnpkg.com/style-loader/-/style-loader-1.1.3.tgz#9e826e69c683c4d9bf9db924f85e9abb30d5e200"
integrity sha512-rlkH7X/22yuwFYK357fMN/BxYOorfnfq0eD7+vqlemSK4wEcejFF1dg4zxP0euBW8NrYx2WZzZ8PPFevr7D+Kw==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
loader-utils "^1.2.3"
schema-utils "^2.6.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
supports-color@6.1.0, supports-color@^6.1.0:
version "6.1.0"
resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-6.1.0.tgz#0764abc69c63d5ac842dd4867e8d025e880df8f3"
integrity sha512-qe1jfm1Mg7Nq/NSh6XE24gPXROEVsWHxC1LIx//XNlD9iw7YZQGjZNjYN7xGaEG6iKdA8EtNFW6R0gjnVXp+wQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
has-flag "^3.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
supports-color@^5.3.0:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "5.5.0"
resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-5.5.0.tgz#e2e69a44ac8772f78a1ec0b35b689df6530efc8f"
integrity sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow==
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
dependencies:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
has-flag "^3.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
supports-color@^7.1.0:
version "7.1.0"
resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-7.1.0.tgz#68e32591df73e25ad1c4b49108a2ec507962bfd1"
integrity sha512-oRSIpR8pxT1Wr2FquTNnGet79b3BWljqOuoW/h4oBhxJ/HUbX5nX6JSruTkvXDCFMwDPvsaTTbvMLKZWSy0R5g==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
has-flag "^4.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
table@^5.2.3:
version "5.4.6"
resolved "https://registry.yarnpkg.com/table/-/table-5.4.6.tgz#1292d19500ce3f86053b05f0e8e7e4a3bb21079e"
integrity sha512-wmEc8m4fjnob4gt5riFRtTu/6+4rSe12TpAELNSqHMfF3IqnA+CH37USM6/YR3qRZv7e56kAEAtd6nKZaxe0Ug==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ajv "^6.10.2"
lodash "^4.17.14"
slice-ansi "^2.1.0"
string-width "^3.0.0"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
tapable@^1.0.0, tapable@^1.1.3:
version "1.1.3"
resolved "https://registry.yarnpkg.com/tapable/-/tapable-1.1.3.tgz#a1fccc06b58db61fd7a45da2da44f5f3a3e67ba2"
integrity sha512-4WK/bYZmj8xLr+HUCODHGF1ZFzsYffasLUgEiMBY4fgtltdO6B4WJtlSbPaDTLpYTcGVwM2qLnFTICEcNxs3kA==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
terser-webpack-plugin@^1.4.3:
version "1.4.3"
resolved "https://registry.yarnpkg.com/terser-webpack-plugin/-/terser-webpack-plugin-1.4.3.tgz#5ecaf2dbdc5fb99745fd06791f46fc9ddb1c9a7c"
integrity sha512-QMxecFz/gHQwteWwSo5nTc6UaICqN1bMedC5sMtUc7y3Ha3Q8y6ZO0iCR8pq4RJC8Hjf0FEPEHZqcMB/+DFCrA==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
cacache "^12.0.2"
find-cache-dir "^2.1.0"
is-wsl "^1.1.0"
schema-utils "^1.0.0"
serialize-javascript "^2.1.2"
source-map "^0.6.1"
terser "^4.1.2"
webpack-sources "^1.4.0"
worker-farm "^1.7.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
terser@^4.1.2:
version "4.6.4"
resolved "https://registry.yarnpkg.com/terser/-/terser-4.6.4.tgz#40a0b37afbe5b57e494536815efa68326840fc00"
integrity sha512-5fqgBPLgVHZ/fVvqRhhUp9YUiGXhFJ9ZkrZWD9vQtFBR4QIGTnbsb+/kKqSqfgp3WnBwGWAFnedGTtmX1YTn0w==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
commander "^2.20.0"
source-map "~0.6.1"
source-map-support "~0.5.12"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
text-table@^0.2.0:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
version "0.2.0"
resolved "https://registry.yarnpkg.com/text-table/-/text-table-0.2.0.tgz#7f5ee823ae805207c00af2df4a84ec3fcfa570b4"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-f17oI66AUgfACvLfSoTsP8+lcLQ=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
through2@^2.0.0:
version "2.0.5"
resolved "https://registry.yarnpkg.com/through2/-/through2-2.0.5.tgz#01c1e39eb31d07cb7d03a96a70823260b23132cd"
integrity sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
readable-stream "~2.3.6"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
xtend "~4.0.1"
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
through@^2.3.6, through@~2.3.6:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
version "2.3.8"
resolved "https://registry.yarnpkg.com/through/-/through-2.3.8.tgz#0dd4c9ffaabc357960b1b724115d7e0e86a2e1f5"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-DdTJ/6q8NXlgsbckEV1+Doai4fU=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
thunky@^1.0.2:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.1.0"
resolved "https://registry.yarnpkg.com/thunky/-/thunky-1.1.0.tgz#5abaf714a9405db0504732bbccd2cedd9ef9537d"
integrity sha512-eHY7nBftgThBqOyHGVN+l8gF0BucP09fMo0oO/Lb0w1OF80dJv+lDVpXG60WMQvkcxAkNybKsrEIE3ZtKGmPrA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
timers-browserify@^2.0.4:
version "2.0.11"
resolved "https://registry.yarnpkg.com/timers-browserify/-/timers-browserify-2.0.11.tgz#800b1f3eee272e5bc53ee465a04d0e804c31211f"
integrity sha512-60aV6sgJ5YEbzUdn9c8kYGIqOubPoUdqQCul3SBAsRCZ40s6Y5cMcrW4dt3/k/EsbLVJNl9n6Vz3fTc+k2GeKQ==
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
dependencies:
setimmediate "^1.0.4"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
tmp@^0.0.33:
version "0.0.33"
resolved "https://registry.yarnpkg.com/tmp/-/tmp-0.0.33.tgz#6d34335889768d21b2bcda0aa277ced3b1bfadf9"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-jRCJlojKnZ3addtTOjdIqoRuPEKBvNXcGYqzO6zWZX8KfKEpnGY5jfggJQ3EjKuu8D4bJRr0y+cYJFmYbImXGw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
os-tmpdir "~1.0.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
to-arraybuffer@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/to-arraybuffer/-/to-arraybuffer-1.0.1.tgz#7d229b1fcc637e466ca081180836a7aabff83f43"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-fSKbH8xjfkZsoIEYCDanqr/4P0M=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
to-fast-properties@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/to-fast-properties/-/to-fast-properties-2.0.0.tgz#dc5e698cbd079265bc73e0377681a4e4e83f616e"
integrity sha1-3F5pjL0HkmW8c+A3doGk5Og/YW4=
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
to-object-path@^0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/to-object-path/-/to-object-path-0.3.0.tgz#297588b7b0e7e0ac08e04e672f85c1f4999e17af"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-KXWIt7Dn4KwI4E5nL4XB9JmeF68=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
kind-of "^3.0.2"
to-regex-range@^2.1.0:
version "2.1.1"
resolved "https://registry.yarnpkg.com/to-regex-range/-/to-regex-range-2.1.1.tgz#7c80c17b9dfebe599e27367e0d4dd5590141db38"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-fIDBe53+vlmeJzZ+DU3VWQFB2zg=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
is-number "^3.0.0"
repeat-string "^1.6.1"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
to-regex@^3.0.1, to-regex@^3.0.2:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
version "3.0.2"
resolved "https://registry.yarnpkg.com/to-regex/-/to-regex-3.0.2.tgz#13cfdd9b336552f30b51f33a8ae1b42a7a7599ce"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-FWtleNAtZ/Ki2qtqej2CXTOayOH9bHDQF+Q48VpWyDXjbYxA4Yz8iDB31zXOBUlOHHKidDbqGVrTUvQMPmBGBw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
define-property "^2.0.2"
extend-shallow "^3.0.2"
regex-not "^1.0.2"
safe-regex "^1.1.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
toidentifier@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/toidentifier/-/toidentifier-1.0.0.tgz#7e1be3470f1e77948bc43d94a3c8f4d7752ba553"
integrity sha512-yaOH/Pk/VEhBWWTlhI+qXxDFXlejDGcQipMlyxda9nthulaxLZUNcUqFxokp0vcYnvteJln5FNQDRrxj3YcbVw==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
toposort@^1.0.0:
version "1.0.7"
resolved "https://registry.yarnpkg.com/toposort/-/toposort-1.0.7.tgz#2e68442d9f64ec720b8cc89e6443ac6caa950029"
integrity sha1-LmhELZ9k7HILjMieZEOsbKqVACk=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
tslib@^1.9.0:
version "1.11.1"
resolved "https://registry.yarnpkg.com/tslib/-/tslib-1.11.1.tgz#eb15d128827fbee2841549e171f45ed338ac7e35"
integrity sha512-aZW88SY8kQbU7gpV19lN24LtXh/yD4ZZg6qieAJDDg+YBsJcSmLGK9QpnUjAKVG/xefmvJGd1WUmfpT/g6AJGA==
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
tty-browserify@0.0.0:
version "0.0.0"
resolved "https://registry.yarnpkg.com/tty-browserify/-/tty-browserify-0.0.0.tgz#a157ba402da24e9bf957f9aa69d524eed42901a6"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-oVe6QC2iTpv5V/mqadUk7tQpAaY=
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
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
type-check@~0.3.2:
version "0.3.2"
resolved "https://registry.yarnpkg.com/type-check/-/type-check-0.3.2.tgz#5884cab512cf1d355e3fb784f30804b2b520db72"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-WITKtRLPHTVeP7eE8wgEsrUg23I=
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
prelude-ls "~1.1.2"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
type-fest@^0.11.0:
version "0.11.0"
resolved "https://registry.yarnpkg.com/type-fest/-/type-fest-0.11.0.tgz#97abf0872310fed88a5c466b25681576145e33f1"
integrity sha512-OdjXJxnCN1AvyLSzeKIgXTXxV+99ZuXl3Hpo9XpJAv9MBcHrrJOQ5kV7ypXOuQie+AmWG25hLbiKdwYTifzcfQ==
type-fest@^0.8.1:
version "0.8.1"
resolved "https://registry.yarnpkg.com/type-fest/-/type-fest-0.8.1.tgz#09e249ebde851d3b1e48d27c105444667f17b83d"
integrity sha512-4dbzIzqvjtgiM5rw1k5rEHtBANKmdudhGyBEajN01fEyhaAIhsoKNy6y7+IN93IfpFtwY9iqi7kD+xwKhQsNJA==
type-is@~1.6.17, type-is@~1.6.18:
version "1.6.18"
resolved "https://registry.yarnpkg.com/type-is/-/type-is-1.6.18.tgz#4e552cd05df09467dcbc4ef739de89f2cf37c131"
integrity sha512-TkRKr9sUTxEH8MdfuCSP7VizJyzRNMjj2J2do2Jr3Kym598JVdEksuzPQCnlFPW4ky9Q+iA+ma9BGm06XQBy8g==
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
dependencies:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
media-typer "0.3.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
mime-types "~2.1.24"
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
typedarray@^0.0.6:
version "0.0.6"
resolved "https://registry.yarnpkg.com/typedarray/-/typedarray-0.0.6.tgz#867ac74e3864187b1d3d47d996a78ec5c8830777"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-hnrHTjhkGHsdPUfZlqeOxciDB3c=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
uglify-js@3.4.x:
version "3.4.10"
resolved "https://registry.yarnpkg.com/uglify-js/-/uglify-js-3.4.10.tgz#9ad9563d8eb3acdfb8d38597d2af1d815f6a755f"
integrity sha512-Y2VsbPVs0FIshJztycsO2SfPk7/KAF/T72qzv9u5EpQ4kB2hQoHlhNQTsNyy6ul7lQtqJN/AoWeS23OzEiEFxw==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
commander "~2.19.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
source-map "~0.6.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
unicode-canonical-property-names-ecmascript@^1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/unicode-canonical-property-names-ecmascript/-/unicode-canonical-property-names-ecmascript-1.0.4.tgz#2619800c4c825800efdd8343af7dd9933cbe2818"
integrity sha512-jDrNnXWHd4oHiTZnx/ZG7gtUTVp+gCcTTKr8L0HjlwphROEW3+Him+IpvC+xcJEFegapiMZyZe02CyuOnRmbnQ==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
unicode-match-property-ecmascript@^1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/unicode-match-property-ecmascript/-/unicode-match-property-ecmascript-1.0.4.tgz#8ed2a32569961bce9227d09cd3ffbb8fed5f020c"
integrity sha512-L4Qoh15vTfntsn4P1zqnHulG0LdXgjSO035fEpdtp6YxXhMT51Q6vgM5lYdG/5X3MjS+k/Y9Xw4SFCY9IkR0rg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
unicode-canonical-property-names-ecmascript "^1.0.4"
unicode-property-aliases-ecmascript "^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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
unicode-match-property-value-ecmascript@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/unicode-match-property-value-ecmascript/-/unicode-match-property-value-ecmascript-1.1.0.tgz#5b4b426e08d13a80365e0d657ac7a6c1ec46a277"
integrity sha512-hDTHvaBk3RmFzvSl0UVrUmC3PuW9wKVnpoUDYH0JDkSIovzw+J5viQmeYHxVSBptubnr7PbH2e0fnpDRQnQl5g==
unicode-property-aliases-ecmascript@^1.0.4:
version "1.0.5"
resolved "https://registry.yarnpkg.com/unicode-property-aliases-ecmascript/-/unicode-property-aliases-ecmascript-1.0.5.tgz#a9cc6cc7ce63a0a3023fc99e341b94431d405a57"
integrity sha512-L5RAqCfXqAwR3RriF8pM0lU0w4Ryf/GgzONwi6KnL1taJQa7x1TCxdJnILX59WIGOwR57IVxn7Nej0fz1Ny6fw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
union-value@^1.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/union-value/-/union-value-1.0.1.tgz#0b6fe7b835aecda61c6ea4d4f02c14221e109847"
integrity sha512-tJfXmxMeWYnczCVs7XAEvIV7ieppALdyepWMkHkwciRpZraG/xwT+s2JN8+pr1+8jCRf80FFzvr+MpQeeoF4Xg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
arr-union "^3.1.0"
get-value "^2.0.6"
is-extendable "^0.1.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
set-value "^2.0.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
uniq@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/uniq/-/uniq-1.0.1.tgz#b31c5ae8254844a3a8281541ce2b04b865a734ff"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-sxxa6CVIRKOoKBVBzisEuGWnNP8=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
unique-filename@^1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/unique-filename/-/unique-filename-1.1.1.tgz#1d69769369ada0583103a1e6ae87681b56573230"
integrity sha512-Vmp0jIp2ln35UTXuryvjzkjGdRyf9b2lTXuSYUiPmzRcl3FDtYqAwOnTJkAngD9SWhnoJzDbTKwaOrZ+STtxNQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
unique-slug "^2.0.0"
unique-slug@^2.0.0:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "2.0.2"
resolved "https://registry.yarnpkg.com/unique-slug/-/unique-slug-2.0.2.tgz#baabce91083fc64e945b0f3ad613e264f7cd4e6c"
integrity sha512-zoWr9ObaxALD3DOPfjPSqxt4fnZiWblxHIgeWqW8x7UqDzEtHEQLzji2cuJYQFCU6KmoJikOYAZlrTHHebjx2w==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
imurmurhash "^0.1.4"
unpipe@1.0.0, unpipe@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/unpipe/-/unpipe-1.0.0.tgz#b2bf4ee8514aae6165b4817829d21b2ef49904ec"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-sr9O6FFKrmFltIF4KdIbLvSZBOw=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
unset-value@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/unset-value/-/unset-value-1.0.0.tgz#8376873f7d2335179ffb1e6fc3a8ed0dfc8ab559"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-g3aHP30jNRef+x5vw6jtDfyKtVk=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
has-value "^0.3.1"
isobject "^3.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
upath@^1.1.1:
version "1.2.0"
resolved "https://registry.yarnpkg.com/upath/-/upath-1.2.0.tgz#8f66dbcd55a883acdae4408af8b035a5044c1894"
integrity sha512-aZwGpamFO61g3OlfT7OQCHqhGnW43ieH9WZeP7QxN/G/jS4jfqUkZxoryvJgVPEcrl5NL/ggHsSmLMHuH64Lhg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
upper-case@^1.1.1:
version "1.1.3"
resolved "https://registry.yarnpkg.com/upper-case/-/upper-case-1.1.3.tgz#f6b4501c2ec4cdd26ba78be7222961de77621598"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-9rRQHC7EzdJrp4vnIilh3ndiFZg=
uri-js@^4.2.2:
version "4.2.2"
resolved "https://registry.yarnpkg.com/uri-js/-/uri-js-4.2.2.tgz#94c540e1ff772956e2299507c010aea6c8838eb0"
integrity sha512-KY9Frmirql91X2Qgjry0Wd4Y+YTdrdZheS8TFwvkbLWf/G5KNJDCh6pKL5OZctEW4+0Baa5idK2ZQuELRwPznQ==
dependencies:
punycode "^2.1.0"
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
urix@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/urix/-/urix-0.1.0.tgz#da937f7a62e21fec1fd18d49b35c2935067a6c72"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-2pN/emLiH+wf0Y1Js1wpNQZ6bHI=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
url-parse@^1.4.3:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "1.4.7"
resolved "https://registry.yarnpkg.com/url-parse/-/url-parse-1.4.7.tgz#a8a83535e8c00a316e403a5db4ac1b9b853ae278"
integrity sha512-d3uaVyzDB9tQoSXFvuSUNFibTd9zxd2bkVrDRvF5TmvWWQwqE4lgYJ5m+x1DbecWkw+LK4RNl2CU1hHuOKPVlg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
querystringify "^2.1.1"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
requires-port "^1.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -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
url@^0.11.0:
version "0.11.0"
resolved "https://registry.yarnpkg.com/url/-/url-0.11.0.tgz#3838e97cfc60521eb73c525a8e55bfdd9e2e28f1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-ODjpfPxgUh63PFJajlW/3Z4uKPE=
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
dependencies:
punycode "1.3.2"
querystring "0.2.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
use@^3.1.0:
version "3.1.1"
resolved "https://registry.yarnpkg.com/use/-/use-3.1.1.tgz#d50c8cac79a19fbc20f2911f56eb973f4e10070f"
integrity sha512-cwESVXlO3url9YWlFW/TA9cshCEhtu7IKJ/p5soJ/gGpj7vbvFrAY/eIioQ6Dw23KjZhYgiIo8HOs1nQ2vr/oQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
util-deprecate@^1.0.1, util-deprecate@~1.0.1:
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
version "1.0.2"
resolved "https://registry.yarnpkg.com/util-deprecate/-/util-deprecate-1.0.2.tgz#450d4dc9fa70de732762fbd2d4a28981419a0ccf"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-RQ1Nyfpw3nMnYvvS1KKJgUGaDM8=
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
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
util.promisify@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/util.promisify/-/util.promisify-1.0.0.tgz#440f7165a459c9a16dc145eb8e72f35687097030"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-i+6qA2MPhvoKLuxnJNpXAGhg7HphQOSUq2LKMZD0m15EiskXUkMvKdF4Uui0WYeCUGea+o2cw/ZuwehtfsrNkA==
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
dependencies:
define-properties "^1.1.2"
object.getownpropertydescriptors "^2.0.3"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
util@0.10.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
version "0.10.3"
resolved "https://registry.yarnpkg.com/util/-/util-0.10.3.tgz#7afb1afe50805246489e3db7fe0ed379336ac0f9"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-evsa/lCAUkZInj23/g7TeTNqwPk=
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
dependencies:
inherits "2.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
util@^0.11.0:
version "0.11.1"
resolved "https://registry.yarnpkg.com/util/-/util-0.11.1.tgz#3236733720ec64bb27f6e26f421aaa2e1b588d61"
integrity sha512-HShAsny+zS2TZfaXxD9tYj4HQGlBezXZMZuM/S5PKLLoZkShZiGk9o5CzukI1LVHZvjdvZ2Sj1aW/Ndn2NB/HQ==
dependencies:
inherits "2.0.3"
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
utila@^0.4.0, utila@~0.4:
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
version "0.4.0"
resolved "https://registry.yarnpkg.com/utila/-/utila-0.4.0.tgz#8a16a05d445657a3aea5eecc5b12a4fa5379772c"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha1-ihagXURWV6Oupe7MWxKk+lN5dyw=
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
utils-merge@1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/utils-merge/-/utils-merge-1.0.1.tgz#9f95710f50a267947b2ccc124741c1028427e713"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-n5VxD1CiZ5R7LMwSR0HBAoQn5xM=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
uuid@^3.0.1, uuid@^3.3.2:
version "3.4.0"
resolved "https://registry.yarnpkg.com/uuid/-/uuid-3.4.0.tgz#b23e4358afa8a202fe7a100af1f5f883f02007ee"
integrity sha512-HjSDRw6gZE5JMggctHBcjVak08+KEVhSIiDzFnT9S9aegmp85S/bReBVTb4QTFaRNptJ9kuYaNhnbNEOkbKb/A==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
v8-compile-cache@2.0.3:
version "2.0.3"
resolved "https://registry.yarnpkg.com/v8-compile-cache/-/v8-compile-cache-2.0.3.tgz#00f7494d2ae2b688cfe2899df6ed2c54bef91dbe"
integrity sha512-CNmdbwQMBjwr9Gsmohvm0pbL954tJrNzf6gWL3K+QMQf00PF7ERGrEiLgjuU3mKreLC2MeGhUsNV9ybTbLgd3w==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
v8-compile-cache@^2.0.3:
version "2.1.0"
resolved "https://registry.yarnpkg.com/v8-compile-cache/-/v8-compile-cache-2.1.0.tgz#e14de37b31a6d194f5690d67efc4e7f6fc6ab30e"
integrity sha512-usZBT3PW+LOjM25wbqIlZwPeJV+3OSz3M1k1Ws8snlW39dZyYL9lOGC5FgPVHfk0jKmjiDV8Z0mIbVQPiwFs7g==
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
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
vary@~1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/vary/-/vary-1.1.2.tgz#2299f02c6ded30d4a5961b0b9f74524a18f634fc"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-IpnwLG3tMNSllhsLn3RSShj2NPw=
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
vm-browserify@^1.0.1:
version "1.1.2"
resolved "https://registry.yarnpkg.com/vm-browserify/-/vm-browserify-1.1.2.tgz#78641c488b8e6ca91a75f511e7a3b32a86e5dda0"
integrity sha512-2ham8XPWTONajOR0ohOKOHXkm3+gaBmGut3SRuu75xLd/RRaY6vqgh8NBYYk7+RW3u5AtzPQZG8F10LHkl0lAQ==
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
watchpack@^1.6.0:
version "1.6.0"
resolved "https://registry.yarnpkg.com/watchpack/-/watchpack-1.6.0.tgz#4bc12c2ebe8aa277a71f1d3f14d685c7b446cd00"
integrity sha512-i6dHe3EyLjMmDlU1/bGQpEw25XSjkJULPuAVKCbNRefQVq48yXKUpwg538F7AZTf9kyr57zj++pQFltUa5H7yA==
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
dependencies:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
chokidar "^2.0.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
graceful-fs "^4.1.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
neo-async "^2.5.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
wbuf@^1.1.0, wbuf@^1.7.3:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "1.7.3"
resolved "https://registry.yarnpkg.com/wbuf/-/wbuf-1.7.3.tgz#c1d8d149316d3ea852848895cb6a0bfe887b87df"
integrity sha512-O84QOnr0icsbFGLS0O3bI5FswxzRr8/gHwWkDlQFskhSPryQXvrTMxjxGP4+iWYoauLoBvfDpkrOauZ+0iZpDA==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
minimalistic-assert "^1.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
webpack-cli@^3.3.11:
version "3.3.11"
resolved "https://registry.yarnpkg.com/webpack-cli/-/webpack-cli-3.3.11.tgz#3bf21889bf597b5d82c38f215135a411edfdc631"
integrity sha512-dXlfuml7xvAFwYUPsrtQAA9e4DOe58gnzSxhgrO/ZM/gyXTBowrsYeubyN4mqGhYdpXMFNyQ6emjJS9M7OBd4g==
dependencies:
chalk "2.4.2"
cross-spawn "6.0.5"
enhanced-resolve "4.1.0"
findup-sync "3.0.0"
global-modules "2.0.0"
import-local "2.0.0"
interpret "1.2.0"
loader-utils "1.2.3"
supports-color "6.1.0"
v8-compile-cache "2.0.3"
yargs "13.2.4"
webpack-dev-middleware@^3.7.2:
version "3.7.2"
resolved "https://registry.yarnpkg.com/webpack-dev-middleware/-/webpack-dev-middleware-3.7.2.tgz#0019c3db716e3fa5cecbf64f2ab88a74bab331f3"
integrity sha512-1xC42LxbYoqLNAhV6YzTYacicgMZQTqRd27Sim9wn5hJrX3I5nxYy1SxSd4+gjUFsz1dQFj+yEe6zEVmSkeJjw==
dependencies:
memory-fs "^0.4.1"
mime "^2.4.4"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
mkdirp "^0.5.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
range-parser "^1.2.1"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
webpack-log "^2.0.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
webpack-dev-server@^3.10.3:
version "3.10.3"
resolved "https://registry.yarnpkg.com/webpack-dev-server/-/webpack-dev-server-3.10.3.tgz#f35945036813e57ef582c2420ef7b470e14d3af0"
integrity sha512-e4nWev8YzEVNdOMcNzNeCN947sWJNd43E5XvsJzbAL08kGc2frm1tQ32hTJslRS+H65LCb/AaUCYU7fjHCpDeQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
ansi-html "0.0.7"
bonjour "^3.5.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
chokidar "^2.1.8"
compression "^1.7.4"
connect-history-api-fallback "^1.6.0"
debug "^4.1.1"
del "^4.1.1"
express "^4.17.1"
html-entities "^1.2.1"
http-proxy-middleware "0.19.1"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
import-local "^2.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
internal-ip "^4.3.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
ip "^1.1.5"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
is-absolute-url "^3.0.3"
killable "^1.0.1"
loglevel "^1.6.6"
opn "^5.5.0"
p-retry "^3.0.1"
portfinder "^1.0.25"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
schema-utils "^1.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
selfsigned "^1.10.7"
semver "^6.3.0"
serve-index "^1.9.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
sockjs "0.3.19"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
sockjs-client "1.4.0"
spdy "^4.0.1"
strip-ansi "^3.0.1"
supports-color "^6.1.0"
url "^0.11.0"
webpack-dev-middleware "^3.7.2"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
webpack-log "^2.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ws "^6.2.1"
yargs "12.0.5"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
webpack-log@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/webpack-log/-/webpack-log-2.0.0.tgz#5b7928e0637593f119d32f6227c1e0ac31e1b47f"
integrity sha512-cX8G2vR/85UYG59FgkoMamwHUIkSSlV3bBMRsbxVXVUk2j6NleCKjQ/WE9eYg9WY4w25O9w8wKP4rzNZFmUcUg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
ansi-colors "^3.0.0"
uuid "^3.3.2"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
webpack-merge@^4.2.2:
version "4.2.2"
resolved "https://registry.yarnpkg.com/webpack-merge/-/webpack-merge-4.2.2.tgz#a27c52ea783d1398afd2087f547d7b9d2f43634d"
integrity sha512-TUE1UGoTX2Cd42j3krGYqObZbOD+xF7u28WB7tfUordytSjbWTIjK/8V0amkBfTYN4/pB/GIDlJZZ657BGG19g==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
lodash "^4.17.15"
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
webpack-sources@^1.0.1, webpack-sources@^1.4.0, webpack-sources@^1.4.1:
version "1.4.3"
resolved "https://registry.yarnpkg.com/webpack-sources/-/webpack-sources-1.4.3.tgz#eedd8ec0b928fbf1cbfe994e22d2d890f330a933"
integrity sha512-lgTS3Xhv1lCOKo7SA5TjKXMjpSM4sBjNV5+q2bqesbSPs5FjGmU6jjtBSkX9b4qW87vDIsCIlUPOEhbZrMdjeQ==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
source-list-map "^2.0.0"
source-map "~0.6.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
webpack@^4.41.6:
version "4.41.6"
resolved "https://registry.yarnpkg.com/webpack/-/webpack-4.41.6.tgz#12f2f804bf6542ef166755050d4afbc8f66ba7e1"
integrity sha512-yxXfV0Zv9WMGRD+QexkZzmGIh54bsvEs+9aRWxnN8erLWEOehAKUTeNBoUbA6HPEZPlRo7KDi2ZcNveoZgK9MA==
dependencies:
"@webassemblyjs/ast" "1.8.5"
"@webassemblyjs/helper-module-context" "1.8.5"
"@webassemblyjs/wasm-edit" "1.8.5"
"@webassemblyjs/wasm-parser" "1.8.5"
acorn "^6.2.1"
ajv "^6.10.2"
ajv-keywords "^3.4.1"
chrome-trace-event "^1.0.2"
enhanced-resolve "^4.1.0"
eslint-scope "^4.0.3"
json-parse-better-errors "^1.0.2"
loader-runner "^2.4.0"
loader-utils "^1.2.3"
memory-fs "^0.4.1"
micromatch "^3.1.10"
mkdirp "^0.5.1"
neo-async "^2.6.1"
node-libs-browser "^2.2.1"
schema-utils "^1.0.0"
tapable "^1.1.3"
terser-webpack-plugin "^1.4.3"
watchpack "^1.6.0"
webpack-sources "^1.4.1"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
websocket-driver@>=0.5.1:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
version "0.7.3"
resolved "https://registry.yarnpkg.com/websocket-driver/-/websocket-driver-0.7.3.tgz#a2d4e0d4f4f116f1e6297eba58b05d430100e9f9"
integrity sha512-bpxWlvbbB459Mlipc5GBzzZwhoZgGEZLuqPaR0INBGnPAY1vdBX6hPnoFXiw+3yWxDuHyQjO2oXTMyS8A5haFg==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
http-parser-js ">=0.4.0 <0.4.11"
safe-buffer ">=5.1.0"
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
websocket-extensions ">=0.1.1"
websocket-extensions@>=0.1.1:
version "0.1.3"
resolved "https://registry.yarnpkg.com/websocket-extensions/-/websocket-extensions-0.1.3.tgz#5d2ff22977003ec687a4b87073dfbbac146ccf29"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha512-nqHUnMXmBzT0w570r2JpJxfiSD1IzoI+HGVdd3aZ0yNi3ngvQ4jv1dtHt5VGxfI2yj5yqImPhOK4vmIh2xMbGg==
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
which-module@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/which-module/-/which-module-2.0.0.tgz#d9ef07dce77b9902b8a3a8fa4b31c3e3f7e6e87a"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-2e8H3Od7mQK4o6j6SzHD4/fm6Ho=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
which@^1.2.14, which@^1.2.9, which@^1.3.1:
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
version "1.3.1"
resolved "https://registry.yarnpkg.com/which/-/which-1.3.1.tgz#a45043d54f5805316da8d62f9f50918d3da70b0a"
integrity sha512-HxJdYWq1MTIQbJ3nw0cqssHoTNU267KlrDuGZ1WYlxDStUtKUhOaJmh112/TZmHxxUfuJqPXSOm7tDyas0OSIQ==
dependencies:
isexe "^2.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
word-wrap@~1.2.3:
version "1.2.3"
resolved "https://registry.yarnpkg.com/word-wrap/-/word-wrap-1.2.3.tgz#610636f6b1f703891bd34771ccb17fb93b47079c"
integrity sha512-Hz/mrNwitNRh/HUAtM/VT/5VH+ygD6DV7mYKZAtHOrbs8U7lvPS6xf7EJKMF0uW1KJCl0H701g3ZGus+muE5vQ==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
worker-farm@^1.7.0:
version "1.7.0"
resolved "https://registry.yarnpkg.com/worker-farm/-/worker-farm-1.7.0.tgz#26a94c5391bbca926152002f69b84a4bf772e5a8"
integrity sha512-rvw3QTZc8lAxyVrqcSGVm5yP/IJ2UcB3U0graE3LCFoZ0Yn2x4EoVSqJKdB/T5M+FLcRPjz4TDacRf3OCfNUzw==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
dependencies:
errno "~0.1.7"
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
wrap-ansi@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/wrap-ansi/-/wrap-ansi-2.1.0.tgz#d8fc3d284dd05794fe84973caecdd1cf824fdd85"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-2Pw9KE3QV5T+hJc8rs3Rz4JP3YU=
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
dependencies:
string-width "^1.0.1"
strip-ansi "^3.0.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
wrap-ansi@^5.1.0:
version "5.1.0"
resolved "https://registry.yarnpkg.com/wrap-ansi/-/wrap-ansi-5.1.0.tgz#1fd1f67235d5b6d0fee781056001bfb694c03b09"
integrity sha512-QC1/iN/2/RPVJ5jYK8BGttj5z83LmSKmvbvrXPNCLZSEb32KKVDJDl/MOt2N01qU2H/FkzEa9PKto1BqDjtd7Q==
dependencies:
ansi-styles "^3.2.0"
string-width "^3.0.0"
strip-ansi "^5.0.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
wrappy@1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/wrappy/-/wrappy-1.0.2.tgz#b5243d8f3ec1aa35f1364605bc0d1036e30ab69f"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
integrity sha1-tSQ9jz7BqjXxNkYFvA0QNuMKtp8=
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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
write@1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/write/-/write-1.0.3.tgz#0800e14523b923a387e415123c865616aae0f5c3"
integrity sha512-/lg70HAjtkUgWPVZhZcm+T4hkL8Zbtp1nFNOn3lRrxnlv50SRBv7cR7RqR+GMsd3hUXy9hWBo4CHTbFTcOYwig==
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
dependencies:
mkdirp "^0.5.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
ws@^6.2.1:
version "6.2.1"
resolved "https://registry.yarnpkg.com/ws/-/ws-6.2.1.tgz#442fdf0a47ed64f59b6a5d8ff130f4748ed524fb"
integrity sha512-GIyAXC2cB7LjvpgMt9EKS2ldqr0MTrORaleiOno6TweZ6r3TKtoFQWay/2PceJ3RuBasOHzXNn5Lrw1X0bEjqA==
dependencies:
async-limiter "~1.0.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
xtend@^4.0.0, xtend@~4.0.1:
version "4.0.2"
resolved "https://registry.yarnpkg.com/xtend/-/xtend-4.0.2.tgz#bb72779f5fa465186b1f438f674fa347fdb5db54"
integrity sha512-LKYU1iAXJXUgAXn9URjiu+MWhyUXHsvfp7mcuYm9dSUKK0/CjtrUwFAxD82/mCWbtLsGjFIad0wIsod4zrTAEQ==
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
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
"y18n@^3.2.1 || ^4.0.0", y18n@^4.0.0:
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
version "4.0.0"
resolved "https://registry.yarnpkg.com/y18n/-/y18n-4.0.0.tgz#95ef94f85ecc81d007c264e190a120f0a3c8566b"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
integrity sha512-r9S/ZyXu/Xu9q1tYlpsLIsa3EeLXXk0VwlxqTcFRfg9EhMW+17kbt9G0NrgCmhGb5vT2hyhJZLfDGx+7+5Uj/w==
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
yallist@^3.0.2:
version "3.1.1"
resolved "https://registry.yarnpkg.com/yallist/-/yallist-3.1.1.tgz#dbb7daf9bfd8bac9ab45ebf602b8cbad0d5d08fd"
integrity sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
yallist@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/yallist/-/yallist-4.0.0.tgz#9bb92790d9c0effec63be73519e11a35019a3a72"
integrity sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
yargs-parser@^11.1.1:
version "11.1.1"
resolved "https://registry.yarnpkg.com/yargs-parser/-/yargs-parser-11.1.1.tgz#879a0865973bca9f6bab5cbdf3b1c67ec7d3bcf4"
integrity sha512-C6kB/WJDiaxONLJQnF8ccx9SEeoTTLek8RVbaOIsrAUS8VrBEXfmeSnCZxygc+XC2sNMBIwOOnfcxiynjHsVSQ==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
camelcase "^5.0.0"
decamelize "^1.2.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
yargs-parser@^13.1.0:
version "13.1.1"
resolved "https://registry.yarnpkg.com/yargs-parser/-/yargs-parser-13.1.1.tgz#d26058532aa06d365fe091f6a1fc06b2f7e5eca0"
integrity sha512-oVAVsHz6uFrg3XQheFII8ESO2ssAf9luWuAd6Wexsu4F3OtIW0o8IribPXYrD4WC24LWtPrJlGy87y5udK+dxQ==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
camelcase "^5.0.0"
decamelize "^1.2.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
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
yargs@12.0.5:
version "12.0.5"
resolved "https://registry.yarnpkg.com/yargs/-/yargs-12.0.5.tgz#05f5997b609647b64f66b81e3b4b10a368e7ad13"
integrity sha512-Lhz8TLaYnxq/2ObqHDql8dX8CJi97oHxrjUcYtzKbbykPtVW9WB+poxI+NM2UIzsMgNCZTIf0AQwsjK5yMAqZw==
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
dependencies:
cliui "^4.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
decamelize "^1.2.0"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
find-up "^3.0.0"
get-caller-file "^1.0.1"
os-locale "^3.0.0"
require-directory "^2.1.1"
require-main-filename "^1.0.1"
set-blocking "^2.0.0"
string-width "^2.0.0"
which-module "^2.0.0"
y18n "^3.2.1 || ^4.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
yargs-parser "^11.1.1"
upgrade some JS deps to work with node 11 Fixes #62 * added travis config for latest node as well as 8. * ran "yarn upgrade -P webpack-dev-server", which caused the upath dependency to be upgraded. I arrived at this by inspecting yarn.lock for the things depending on upack, along with some trial and error. ("yarn upgrade -P chokidar" was less successful.)
2018-11-20 13:59:00 -05:00
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
yargs@13.2.4:
version "13.2.4"
resolved "https://registry.yarnpkg.com/yargs/-/yargs-13.2.4.tgz#0b562b794016eb9651b98bd37acf364aa5d6dc83"
integrity sha512-HG/DWAJa1PAnHT9JAhNa8AbAv3FPaiLzioSjCcmuXXhP8MlpHO5vwls4g4j6n30Z74GVQj8Xa62dWVx1QCGklg==
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
dependencies:
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
cliui "^5.0.0"
find-up "^3.0.0"
get-caller-file "^2.0.1"
os-locale "^3.1.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
require-directory "^2.1.1"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
require-main-filename "^2.0.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
set-blocking "^2.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
string-width "^3.0.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
which-module "^2.0.0"
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
y18n "^4.0.0"
yargs-parser "^13.1.0"