@seedtactics/insight-client 16.7.2 → 16.8.1

package/docs/server-config.md

@@ -2,55 +2,46 @@
 title: FMS Insight Server Configuration
 nav: FMS Insight Server > Configuration
 description: >-
-  The FMS Insight server runs on the cell controller and is configured by
-  a config.ini file.
+  The FMS Insight server runs on the cell controller and is configured by a config.ini file.
 ---
 
 # FMS Insight Server Configuration
 
-The FMS Insight server is configured via a file
-`SeedTactics\FMSInsight\config.ini` located in the Windows Common AppData
-folder. On a default Windows install, this has a full path of
-`c:\ProgramData\SeedTactics\FMSInsight\config.ini`. The config file itself
-describes the settings in detail, but they fall into three groups: server
-settings such as network ports and SSL, FMS settings such as automatic serial
-assignment, and finally cell controller specific settings.
-
-The first time FMS Insight starts, if the `config.ini` file does not exist,
-FMS Insight will create a default config file. FMS Insight should run fine
-with the default settings, so typically when first getting started no config
-file settings need to be changed. Any changes to settings in `config.ini`
-require the FMS Insight server to be restarted before they take effect.
-
-The `config.ini` file is an [INI file](https://en.wikipedia.org/wiki/INI_file).
-The default config file contains a large number of comments describing each option.
-Comments describing each option are prefixed by a hash (`#`) and the options themselves
-are prefixed by a semicolon (`;`). To edit an option, remove the leading semicolon (`;`)
-and then edit the option value. Remember to restart the FMS Insight server. If any configuration
-errors are present, FMS Insight will generate an error message with details into the
-[event log](server-errors).
+The FMS Insight server is configured via a file `SeedTactics\FMSInsight\config.ini` located in the
+Windows Common AppData folder. On a default Windows install, this has a full path of
+`c:\ProgramData\SeedTactics\FMSInsight\config.ini`. The config file itself describes the settings in
+detail, but they fall into three groups: server settings such as network ports and SSL, FMS settings
+such as automatic serial assignment, and finally cell controller specific settings.
+
+The first time FMS Insight starts, if the `config.ini` file does not exist, FMS Insight will create
+a default config file. FMS Insight should run fine with the default settings, so typically when
+first getting started no config file settings need to be changed. Any changes to settings in
+`config.ini` require the FMS Insight server to be restarted before they take effect.
+
+The `config.ini` file is an [INI file](https://en.wikipedia.org/wiki/INI_file). The default config
+file contains a large number of comments describing each option. Comments describing each option are
+prefixed by a hash (`#`) and the options themselves are prefixed by a semicolon (`;`). To edit an
+option, remove the leading semicolon (`;`) and then edit the option value. Remember to restart the
+FMS Insight server. If any configuration errors are present, FMS Insight will generate an error
+message with details into the [event log](server-errors).
 
 ## Databases
 
-FMS Insight uses [SQLite](https://www.sqlite.org/) to store data about the cell.
-The primary data stored is a log of the activity of all parts, pallets, machines, jobs,
-schedules, inspections, serial numbers, orders, and other data. In addition, FMS Insight
-stores a small amount of temporary data to assist with monitoring.
-
-The SQLite databases are by default stored locally in the Windows Common
-AppData folder which on a default Windows install is
-`c:\ProgramData\SeedTactics\FMSInsight`. This path can be changed in the
-`config.ini` file if needed, but we suggest that the databases are kept on
-the local drive for performance and data integrity (SQLite works best on a
-local drive). The SQLite databases are not large, typically under 100
-megabytes, so disk space is not a problem.
-
-Every time FMS Insight starts, it checks for the existence of the SQLite
-databases and if they are missing it creates them. For this reason, the
-databases can be deleted without impacting the operation of the cell (as long
-as FMS Insight is restarted). Also, since the databases just store a log of
-past activity and all complex logic is outside FMS Insight, if the databases
-are deleted (and recreated) the cell will continue to operate just fine in
-the future (minus the historical data). Thus it is not necessary to backup
-the databases (but of course you can if you want to preserve historical
-data).
+FMS Insight uses [SQLite](https://www.sqlite.org/) to store data about the cell. The primary data
+stored is a log of the activity of all parts, pallets, machines, jobs, schedules, inspections,
+serial numbers, orders, and other data. In addition, FMS Insight stores a small amount of temporary
+data to assist with monitoring.
+
+The SQLite databases are by default stored locally in the Windows Common AppData folder which on a
+default Windows install is `c:\ProgramData\SeedTactics\FMSInsight`. This path can be changed in the
+`config.ini` file if needed, but we suggest that the databases are kept on the local drive for
+performance and data integrity (SQLite works best on a local drive). The SQLite databases are not
+large, typically under 100 megabytes, so disk space is not a problem.
+
+Every time FMS Insight starts, it checks for the existence of the SQLite databases and if they are
+missing it creates them. For this reason, the databases can be deleted without impacting the
+operation of the cell (as long as FMS Insight is restarted). Also, since the databases just store a
+log of past activity and all complex logic is outside FMS Insight, if the databases are deleted (and
+recreated) the cell will continue to operate just fine in the future (minus the historical data).
+Thus it is not necessary to backup the databases (but of course you can if you want to preserve
+historical data).

package/docs/server-errors.md

@@ -2,8 +2,8 @@
 title: FMS Insight Errors
 nav: FMS Insight Server > Errors
 description: >-
-  The FMS Insight server runs on the cell controller and logs errors and warnings
-  into the Windows Event Viewer.
+  The FMS Insight server runs on the cell controller and logs errors and warnings into the Windows
+  Event Viewer.
 ---
 
 # FMS Insight Error Logging
@@ -11,34 +11,33 @@ description: >-
 When the FMS Insight server encounters an error, it reports the error back over the network to the
 software that requested the operation (such as the Insight client web page). The FMS Insight server
 also logs the error with more details into the Windows Event Log. Thus, when the Insight web page or
-any other software reports an error you can check the Windows Event Log on the cell controller
-for more information.
+any other software reports an error you can check the Windows Event Log on the cell controller for
+more information.
 
 ## Windows Event Viewer
 
-The location of the viewer is different in different versions of Windows;
-on Windows 10 and 11, open the start menu and search for "Event Viewer" and on Windows 7 open the "Control Panel",
-navigate to "Administrative Tools", and then open the "Event Viewer". To view the events in the event viewer,
-navigate to "Windows Logs" and then "Application" in the tree on the left (see the screenshot below).
+The location of the viewer is different in different versions of Windows; on Windows 10 and 11, open
+the start menu and search for "Event Viewer" and on Windows 7 open the "Control Panel", navigate to
+"Administrative Tools", and then open the "Event Viewer". To view the events in the event viewer,
+navigate to "Windows Logs" and then "Application" in the tree on the left (see the screenshot
+below).
 
 ![Screenshot of Windows 10 Event Viewer](screenshots/insight-event-viewer.jpg)
 
-The windows event viewer shows events from all applications. FMS Insight generates events "FMS Insight"
-as the event source, which allows you to create a custom view to filter only the events from FMS Insight.
-To do so, go to the action menu, click "Create Custom View", and fill in "FMS Insight" as the event source
-(see the screenshot below).
+The windows event viewer shows events from all applications. FMS Insight generates events "FMS
+Insight" as the event source, which allows you to create a custom view to filter only the events
+from FMS Insight. To do so, go to the action menu, click "Create Custom View", and fill in "FMS
+Insight" as the event source (see the screenshot below).
 
 ![Screenshot of creating a custom event view](screenshots/insight-event-custom-view.jpg)
 
 ## Debug Log
 
-To assist with debugging, FMS Insight has the ability to output a trace of
-activity with events for almost all actions that FMS Insight takes. The debug
-trace is disabled by default because it generates a lot of data. To enable
-it, edit the [config file](server-config) and change the setting
-"EnableDebugLog" to true. The FMS Insight server must be restarted before the
-config setting takes effect. The debug trace log will be generated into the
-global AppData folder, which defaults to `c:\ProgramData\SeedTactics\FMSInsight`.
-The debug trace files are named `fmsinsight-debug.txt`, there will be one file
-per day, and the file is JSON formatted. Remember to disable the trace log after
-a day or two because it generates a lot of data.
+To assist with debugging, FMS Insight has the ability to output a trace of activity with events for
+almost all actions that FMS Insight takes. The debug trace is disabled by default because it
+generates a lot of data. To enable it, edit the [config file](server-config) and change the setting
+"EnableDebugLog" to true. The FMS Insight server must be restarted before the config setting takes
+effect. The debug trace log will be generated into the global AppData folder, which defaults to
+`c:\ProgramData\SeedTactics\FMSInsight`. The debug trace files are named `fmsinsight-debug.txt`,
+there will be one file per day, and the file is JSON formatted. Remember to disable the trace log
+after a day or two because it generates a lot of data.

package/package.json

@@ -1,11 +1,15 @@
 {
   "name": "@seedtactics/insight-client",
-  "version": "16.7.2",
+  "version": "16.8.1",
   "license": "BSD-3-Clause",
-  "type": "module",
   "repository": {
     "url": "https://github.com/SeedTactics/fms-insight"
   },
+  "files": [
+    "dist",
+    "docs"
+  ],
+  "type": "module",
   "exports": {
     "./cell-status/*": "./dist/cell-status/*.js",
     "./components/*": "./dist/components/*.js",
@@ -17,20 +21,16 @@
     "./network/*": "./dist/network/*.js",
     "./util/*": "./dist/util/*.js"
   },
-  "files": [
-    "dist",
-    "docs"
-  ],
   "dependencies": {
     "@dnd-kit/core": "^6.3.1",
     "@dnd-kit/sortable": "^10.0.0",
     "@emotion/react": "^11.14.0",
     "@emotion/styled": "^11.14.1",
     "@fontsource/roboto": "^5.2.10",
-    "@mui/icons-material": "^9.0.1",
-    "@mui/material": "^9.0.1",
-    "@react-spring/rafz": "^10.1.0",
-    "@react-spring/web": "^10.1.0",
+    "@mui/icons-material": "^9.1.1",
+    "@mui/material": "^9.1.2",
+    "@react-spring/rafz": "^10.1.2",
+    "@react-spring/web": "^10.1.2",
     "@seedtactics/immutable-collections": "^1.1.1",
     "@yudiel/react-qr-scanner": "^2.6.0",
     "copy-to-clipboard": "^4.0.2",
@@ -38,16 +38,16 @@
     "d3-sankey": "^0.12.3",
     "d3-scale": "^4.0.2",
     "d3-shape": "^3.2.0",
-    "date-fns": "^4.3.0",
+    "date-fns": "^4.4.0",
     "highlight.js": "^11.11.1",
     "jdenticon": "^3.3.0",
-    "jotai": "^2.20.0",
+    "jotai": "^2.20.1",
     "jotai-family": "^1.0.2",
     "jsbarcode": "^3.12.3",
     "oidc-client-ts": "^3.5.0",
-    "react": "^19.2.6",
+    "react": "^19.2.7",
     "react-calendar": "^6.0.1",
-    "react-dom": "^19.2.6",
+    "react-dom": "^19.2.7",
     "react-error-boundary": "^6.1.2",
     "react-resize-detector": "^12.3.0",
     "react-timeago": "^8.3.0",
@@ -55,28 +55,29 @@
     "urlpattern-polyfill": "^10.1.0"
   },
   "devDependencies": {
-    "@faker-js/faker": "^10.4.0",
+    "@faker-js/faker": "^10.5.0",
     "@types/d3-interpolate-path": "^2.0.3",
     "@types/d3-sankey": "^0.12.5",
     "@types/d3-scale": "^4.0.9",
     "@types/d3-shape": "^3.1.8",
-    "@types/node": "^25.9.1",
-    "@types/react": "^19.2.15",
+    "@types/node": "^26.0.1",
+    "@types/react": "^19.2.17",
     "@types/react-dom": "^19.2.3",
-    "@vitejs/plugin-react": "^6.0.2",
-    "@vitest/browser-playwright": "^4.1.7",
+    "@vitejs/plugin-react": "^6.0.3",
+    "@vitest/browser-playwright": "^4.1.9",
     "jsdom": "^29.1.1",
     "nswag": "^14.7.1",
-    "oxlint": "^1.66.0",
+    "oxfmt": "^0.56.0",
+    "oxlint": "^1.71.0",
     "oxlint-tsgolint": "^0.23.0",
-    "prettier": "^3.8.3",
     "typescript": "^6.0.3",
-    "vite": "^8.0.14",
-    "vitest": "^4.1.7",
+    "vite": "^8.1.0",
+    "vitest": "^4.1.9",
     "vitest-browser-react": "^2.2.0"
   },
   "scripts": {
-    "check": "tsc --noEmit --skipLibCheck && oxlint --type-aware",
+    "type-check": "tsc --noEmit --skipLibCheck",
+    "lint": "oxlint --type-aware",
     "build": "tsc --noEmit --skipLibCheck && vite build",
     "build:package": "tsc --project tsconfig.publish.json && cp -Tr ../../docs ./docs",
     "start": "vite",