@seedtactics/insight-client 16.4.0

package/docs/operator-procedures.md

@@ -0,0 +1,106 @@
+---
+title: Load/Unload Procedures
+nav: Procedures > Operator Load/Unload
+description: >-
+  Implement continuous improvement of a flexible machining system by reviewing
+  targeted metrics which expose cell efficiency and cost per piece.
+---
+
+# Load/Unload Procedures
+
+FMS Insight provides [targeted pages](client-station-monitor) for operators on the factory floor:
+a page for each load station which shows the material to load or unload, a page for each inspection stand
+showing details about the material to be inspected, a page for the wash station, and finally a page
+for in-process material queue management. These pages use the [whiteboard metaphor](material-tracking)
+for material tracking. We suggest that each station has a dedicated display or tablet with the relevant page
+bookmarked or made the homepage; these pages are designed to work on a touchscreen. In addition, each station
+should have an attached barcode scanner.
+
+FMS Insight's load station page will display what the cell controller
+is expecting to happen at the load station. Specifically, the page will display the material
+to load, the material to unload, and the material to transfer between faces (if the pallet has
+multiple faces). If the operator performs all the tasks as specified, the operator presses
+the load button to signal to the cell controller that the load is complete. FMS Insight monitors
+the cell controller and will update the page.
+
+![Screenshot of Load Station screen](screenshots/insight-load-station.png)
+
+If queues are used for managing material, the load station screen also can show the queues on the
+right hand side. The specific material that is marked as loaded is the first material in the queue
+which matches the job and route details. The material in the queue can be re-ordered by dragging,
+which allows the operator to control which serial is loaded onto the pallet. Note that because
+the cell controller has already assigned a job to the pallet at the load station, the material
+at the front of the queue will not always be the material that is loaded; the first material which
+matches the job is loaded.
+
+## Introducing Raw Material
+
+The jobs control how raw material is introduced. If no raw
+material queue is set on the job, the cell controller will assume that raw material is
+always available and bring a pallet to be loaded as soon as it is empty. FMS Insight is watching
+the cell controller and will create new material once the load is complete.
+
+Alternatively, the job can be configured with an input queue on the first process. In this case,
+the contents of the queue control when the cell controller will bring a pallet to the load
+station to be loaded. The Queues webpage shows the contents of the queue and allows the operator
+to scan or enter new material into the queue. The page also shows a table of scheduled jobs and
+shows the quantity of parts that still must be loaded.
+
+![Screenshot of queues page](screenshots/insight-queues-jobs-table.png)
+
+The operator should physically bring the casting/raw material to the cell and place it in
+a designated area nearby the load station. Once the material has arrived, the operator
+can click a button on the queues webpage (or scan a barcode) to add the material to the queue.
+FMS Insight supports a variety of techniques controlled by [config settings](server-config):
+adding raw material assigned to a specific job, adding raw material with or without a serial,
+or bulk adding a large quantity of material.
+
+Each physical location on the shop floor which holds material should correspond to a queue
+in FMS Insight. In addition, each queue should have a dedicated display or tablet mounted
+on the shop floor right next to the queue. This display should have the queues page
+bookmarked or set as the homepage and only show the queues page. This allows the operators
+and supervisors to quickly check at a glance that the material on the shop floor matches
+the material FMS Insight records as in the queue.
+
+## Quarantine Material
+
+FMS Insight optionally supports the ability to [quarantine material](material-quarantine).
+Quarantined material is material that is temporarily removed from the cell for re-machining,
+more detailed inspection, or some other rework. Material can be quarantined on the queues
+page by opening the material dialog and clicking a button. This moves the material to
+the quarantine queue where it is visible on the supervisor's material page.
+
+Once the material is ready to be re-introduced into the cell, the operator should bring it
+back to the shop floor. Once the material has arrived, the operator can click a button on
+the queues webpage (or scan the barcode) to add the material into the queue. Once it is
+back in the queue, the cell controller will activate a pallet to load the material.
+
+## Recovering From Misload
+
+The load station page displays the load, unload, or reclamp steps that the cell
+controller is expecting the operator to preform. When the operator presses the ready button,
+both the cell controller and FMS Insight (which is watching the cell controller) assumes
+that these instructions took place. FMS Insight will take the material from the input queue
+and record it as loaded onto the pallet. The cell controller will begin moving the pallet
+to the machine.
+
+If for whatever reason the load instructions can not be followed, ideally the operator should
+edit the cell controller **before** the load is completed. FMS Insight will adjust itself
+based on whatever the cell controller expects to happen and only at the time that the load
+is completed is anything finalized and recorded.
+
+If the load button is pressed, the first step is to adjust the status in the cell controller
+to match what actually happened. FMS Insight is watching the cell controller and when
+the pallet status is adjusted, FMS Insight will move any material that was thought to
+be loaded on the pallet to the quarantine queue. That material can then be re-introduced
+back into the queue so that the queue in FMS Insight matches the material on the shop floor.
+In addition, FMS Insight allows the ability to invalidate the inadvertent load events that
+were created.
+
+Finally, in certain situations depending on the specific configuration of the jobs and queues,
+FMS Insight supports a serial swap. FMS Insight assumes the material that is loaded is the
+first material in the queue which matches the job the cell controller expects.
+If the serial actually loaded is different but the job and details match, the supervisor can
+swap the two serials on the supervisor's material page. This is a data-only change and no
+change is made to the cell controller. If a swap cannot be performed, the material must be
+quarantined and invalidated as described above.

package/docs/part-instructions.md

@@ -0,0 +1,63 @@
+---
+title: Operator Instructions
+nav: FMS Insight Server > Instructions
+description: >-
+  The FMS Insight server can be configured to display arbitrary load, unload, wash
+  and inspection instructions to the operator.
+---
+
+# FMS Insight Operator Instructions
+
+FMS Insight can display load, wash, and inspection instructions to the operator.
+The instructions are documents (typically PDF files) stored on the FMS Insight server,
+and when the user clicks a button in the client the instructions are shown in a new
+browser tab.
+
+### Configuration
+
+The instruction files are kept on the FMS Insight server in a single directory. The
+directory is configured via a [configuration option](server-config) `InstructionFilePath`
+within the `FMS` section. Once configured, this directory should be filled with files
+that can be displayed in a browser (PDF is a good choice). When the user requests an
+instruction file, the FMS Insight server will search the filename of all files inside this
+directory
+
+### Instruction Types
+
+There are four instruction types: load, unload, wash, and inspections. Each instruction type will
+search for a different file depending on the page on the
+[station monitor screen](client-station-monitor) and the currently selected part. To create
+instruction files for all possibilities, you should create files as follows:
+
+- For each part, create a file with the partname and `load` in the filename. Inside this
+  file, add pictures and text to explain how to load and optionally unload the part from the pallet.
+  For example, for a part named `ABC123`, you could create a file `ABC123-load.pdf` which contains
+  the instructions. When the user is on the Load Station page in FMS Insight, FMS Insight
+  will search for a file with the partname and `load` in the filename, find `ABC123-load.pdf`,
+  and display it to the user.
+
+- For each part, optionally create a file with the partname and `unload` in the filename. If no
+  file exists with the partname and `unload` in the filename, FMS Insight will fall back to searching
+  for a file with the partname and `load` in the filename. Thus you could just create a single file
+  (e.g. `ABC123-load.pdf`) which contains both the load and unload instructions, or you could create
+  two separate files (e.g. `ABC123-load.pdf` and `ABC123-unload.pdf`).
+
+- For each part, create a file with the partname and `wash` in the filename. Inside this
+  file, add pictures and text to explain how to wash and perhaps other tasks at the wash station.
+  For example, for a part named `ABC123`, you could create a file `ABC123-wash.pdf`.
+  Similar to before, when the user is on the Wash page in FMS Insight, this instruction file
+  will be displayed.
+
+- For each part and each inspection type, create a file with the partname and the inspection type
+  in the filename. For example, for a part named `ABC123` and inspection types `CMM` and `3DScan`,
+  you should create two files: `ABC123-CMM.pdf` and `ABC123-3DScan.pdf`. Each file should contain
+  pictures and text to explain how to perform the inspection on this part. When the user is on
+  the Inspection page, FMS Insight will find the file based on the currently selected part and
+  inspection type.
+
+### Opening the instructions
+
+To open the instructions, click on any material card in the [station monitor page](client-station-monitor). When clicked, a dialog will appear with details about the
+material. On the bottom of the dialog, there is a button "Instructions". When clicked,
+FMS Insight will search for a file matching the current partname and page (load, wash, or inspection) as described above. The instruction file will then be displayed in a new tab. When subsequent instructions are requested, the tab will be re-used. Thus the tab does not need to be
+manually closed after each operation.

package/docs/security.md

@@ -0,0 +1,131 @@
+---
+title: FMS Insight Security
+nav: FMS Insight Server > Security
+description: >-
+  The FMS Insight server runs on the cell controller and uses TLS and OpenID
+  Connect.
+---
+
+# FMS Insight Security
+
+FMS Insight implements a JSON+REST-based HTTP server and runs on the cell
+controller. By default, FMS Insight listens on port 5000 with no TLS and no
+authentication; any computer which can connect to the port can view data and
+download jobs.
+
+To implement security, we recommend one of two possible variants.
+
+- FMS Insight can be configured to require TLS and require OpenID connect authentication for
+  single-sign-on. This requires the cell controller computer (running FMS Insight) to be directly connected
+  to the existing factory network, but a firewall can be used to only allow access on the specific
+  port running FMS Insight.
+- A cell-local private network containing the machines, cell-controller, and FMS Insight is created.
+  A reverse HTTP proxy connects the cell-local private network to the factory network.
+
+## FMS Insight HTTPS, Authentication, and Firewall
+
+In this design, FMS Insight is configured to require TLS/HTTPS and implements
+authentication using OpenID Connect. We have tested with AzureAD, Okta, and
+Keycloak, but any OpenID/OAuth2 compliant identity provider should work. An
+external firewall is placed between the cell-controller and the factory
+network and is configured to only allow traffic on the FMS Insight port.
+
+To enable HTTPS, a server certificate must be created and stored in a pfx file. This
+should be signed by the enterprise domain, but could also be a self-signed certificate.
+Once created, within the FMS Insight [config.ini](server-config) file, enable the
+`TLSCertFile` setting with the path to the certificate.
+
+Within your identity provider, create an application for FMS Insight and create a client.
+The client must require implicit grant flow with no client secret. The Redirect URI for the client
+must be set to the common name from the TLS certificate with a root path.
+Finally, most identity providers allow the administrator to restrict an
+application to a set of users (e.g. Azure Active Directory allows assigning specific users
+or groups to the application).
+
+Once the client has been created, there are four settings in the [config.ini](server-config).
+
+- `OpenIDConnectAuthority`: This setting is the path to the well-known configuration document for the identity provider.
+  For example, for AzureAD, this is `https://login.microsoftonline.com/{tenant}/v2.0` where `{tenant}` is your tenant GUID.
+- `OpenIDConnectClientID`: This should be the ClientID for the implicit grant flow client. This ClientID is passed
+  to the FMS Insight webpage which then performs the implicit flow grant to obtain a token.
+- `AuthAuthority`: This must be identical to the `OpenIDConnectAuthority`.
+- `AuthTokenAudiences`: This is a list of audiences which the server uses to validate the identity tokens. In almost all
+  cases, the audience matches the ClientID. Multiple audiences are separated by semi-colons.
+
+## Cell-Local Private Network With Proxy
+
+In this design, a cell-local private network is created with a proxy computer to the factory network.
+The design is based on a networking DMZ-setup.
+
+- The machines and cell controller are placed on a private network. This network has no DNS,
+  no DHCP, and no route or access to any other network. IP Addresses are statically assigned.
+
+- The cell controller computer runs FMS Insight with no TLS, listening on port 5000.
+
+- The factory provides a computer with two network cards. One network card connects
+  to the cell-local private network and is statically assigned an IP address.
+  The second network card connects to the existing factory network. This computer can join the domain,
+  enable Windows Updates, and use all the typical configuration of the Factory's IT.
+  This computer should deny ALL network traffic to be routed between the cell-local network and the
+  factory network. All communication is proxied (a networking DMZ setup). The factory provides this
+  computer, allowing you to use your preferred supplier and configuration.
+
+- The proxy computer runs a reverse-HTTP-proxy. This can be Nginx, IIS, or something else. We
+  also provide the source code for a small C# reverse-proxy server built using ASP.NET Core and Kestrel
+  (~250 lines of code) which you can use if you wish it. The reverse-proxy implements TLS and requires connections over HTTPS.
+
+- Either the reverse-proxy or FMS Insight itself is configured to require OpenID Connect/OAuth2 Authentication.
+  This allows single-sign-on and only authenticated users will then be able to view data and create jobs.
+  FMS Insight has been tested with AzureAD, Okta, and Keycloak, but any OpenID Connect compliant
+  identity provider should work.
+
+- Software running on the factory network connects and authenticates with the reverse-proxy, which
+  passes the requests along to FMS Insight running on the cell controller.
+
+#### Reverse-Proxy Implemented Authentication
+
+One option for authentication is for the reverse-proxy to require authentication. The reverse-proxy
+should require OpenID Connect authentication for all routes starting with `/api` except for `/api/v1/fms/fms-information`.
+Our small C# reverse-proxy implements OpenID Connect authentication and has been tested with AzureAD, Okta,
+and Keycloak. Alternatively, Nginx+ or IIS can be configured to require authentication.
+
+In this scenario, two settings are needed in FMS Insight's [config.ini](server-config):
+
+- `OpenIDConnectAuthority`: This setting is the path to the well-known configuration document for the identity provider.
+  For example, for AzureAD, this is `https://login.microsoftonline.com/{tenant}/v2.0` where `{tenant}` is your tenant GUID.
+- `OpenIDConnectClientID`: This is the ClientID for an implicit grant flow client. This ClientID is passed
+  to the FMS Insight webpage which then performs the implicit flow grant to authenticate the user and obtain a token.
+
+These settings are just returned to clients in the `/api/v1/fms/fms-information` route, FMS Insight itself does not
+check the request for a proper JWT token.
+
+Next, the reverse-proxy is configured with TLS certificates and authentication. For our small C# reverse-proxy,
+this is done in the appsettings.json file.
+
+#### FMS Insight Implemented Authentication
+
+If the reverse-proxy does not implement authentication, FMS Insight itself can verify the tokens. The main challenge
+is that the FMS Insight server requires access to the OpenID Connect Authority well-known configuration document
+to be able to obtain the signing keys. For example, in AzureAD, the well-known document
+is `https://login.microsoftonline.com/{tenant}/v2.0/.well-known/openid-configuration` where tenant is your tenant GUID.
+This document is required to be accessible by the FMS Insight server to obtain the rotating signing keys of the
+identity provider. Since FMS Insight is running on the cell-controller on the cell-local private network and the proxy
+computer denies all routed traffic, FMS Insight has no direct access to the well-known configuration document.
+
+Thus, the reverse-proxy must also proxy the well-known configuration document. That is, the reverse-proxy is
+configured to first proxy all connections from the factory network to FMS Insight. In addition, the reverse-proxy
+is then also configured to proxy the request from FMS Insight to the OpenID Connect configuration document to
+the real identity provider.
+
+The configuration in FMS Insight's [config.ini](server-config) are as follows:
+
+- `OpenIDConnectAuthority`: The real identity-provided authority URL.
+  For example, for AzureAD, this is `https://login.microsoftonline.com/{tenant}/v2.0` where `{tenant}` is your tenant GUID.
+- `OpenIDConnectClientID`: This is the ClientID for an implicit grant flow client. This ClientID is passed
+  to the FMS Insight webpage which then performs the implicit flow grant to authenticate the user and obtain a token.
+- `AuthAuthority`: The path to the reverse-proxy to obtain the OpenID configuration. For example, it could be
+  `http://{reverse-proxy-ip-address}/openid-authority`. The reverse-proxy should then be configured to proxy all
+  paths starting with `/openid-authority/*` to the real identity provider.
+- `AuthTokenAudiences`: This is a list of audiences which the server uses to validate the identity tokens. In almost all
+  cases, the audience matches the ClientID. Multiple audiences are separated by semi-colons. Thus this setting should
+  be all the ClientIDs created separated by semi-colons.

package/docs/server-config.md

@@ -0,0 +1,56 @@
+---
+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.
+---
+
+# 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).
+
+## 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).

package/docs/server-errors.md

@@ -0,0 +1,44 @@
+---
+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.
+---
+
+# FMS Insight Error Logging
+
+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.
+
+## 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).
+
+![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).
+
+![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.

package/package.json

@@ -0,0 +1,90 @@
+{
+  "name": "@seedtactics/insight-client",
+  "version": "16.4.0",
+  "license": "BSD-3-Clause",
+  "type": "module",
+  "main": "./src/index.ts",
+  "repository": {
+    "url": "https://github.com/seedtactics/fms-insight.git"
+  },
+  "exports": {
+    "./cell-status/*": "./dist/cell-status/*.js",
+    "./components/*": "./dist/components/*.js",
+    "./components/analysis/*": "./dist/components/analysis/*.js",
+    "./components/operations/*": "./dist/components/operations/*.js",
+    "./components/quality/*": "./dist/components/quality/*.js",
+    "./components/station-monitor/*": "./dist/components/station-monitor/*.js",
+    "./data/*": "./dist/data/*.js",
+    "./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.9",
+    "@mui/icons-material": "^7.3.6",
+    "@mui/material": "^7.3.6",
+    "@react-spring/rafz": "^10.0.3",
+    "@react-spring/web": "^10.0.3",
+    "@seedtactics/immutable-collections": "^1.0.2",
+    "@yudiel/react-qr-scanner": "^2.5.0",
+    "copy-to-clipboard": "^3.3.3",
+    "d3-interpolate-path": "^2.3.0",
+    "d3-sankey": "^0.12.3",
+    "d3-scale": "^4.0.2",
+    "d3-shape": "^3.2.0",
+    "date-fns": "^4.1.0",
+    "highlight.js": "^11.11.1",
+    "jdenticon": "^3.3.0",
+    "jotai": "^2.16.0",
+    "jotai-family": "^1.0.1",
+    "jsbarcode": "^3.12.1",
+    "oidc-client-ts": "^3.4.1",
+    "react": "^19.2.3",
+    "react-calendar": "^6.0.0",
+    "react-dom": "^19.2.3",
+    "react-error-boundary": "^6.0.0",
+    "react-resize-detector": "^12.3.0",
+    "react-timeago": "^8.3.0",
+    "react-to-print": "^3.2.0",
+    "urlpattern-polyfill": "^10.1.0"
+  },
+  "devDependencies": {
+    "@eslint/js": "^9.39.2",
+    "@faker-js/faker": "^10.1.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.7",
+    "@types/node": "^25.0.3",
+    "@types/react": "^19.2.7",
+    "@types/react-dom": "^19.2.3",
+    "@vitejs/plugin-react": "^5.1.2",
+    "eslint": "^9.39.2",
+    "eslint-config-prettier": "^10.1.8",
+    "eslint-plugin-react": "^7.37.5",
+    "eslint-plugin-react-hooks": "^7.0.1",
+    "eslint-plugin-react-refresh": "^0.4.26",
+    "jsdom": "^27.3.0",
+    "nswag": "^14.6.3",
+    "prettier": "^3.7.4",
+    "typescript": "^5.9.3",
+    "typescript-eslint": "^8.50.0",
+    "vite": "^7.3.0",
+    "vitest": "^4.0.16"
+  },
+  "scripts": {
+    "build": "tsc --noEmit --skipLibCheck && vite build",
+    "build:package": "tsc --project tsconfig.publish.json && cp -Tr ../../docs ./docs",
+    "start": "vite",
+    "test": "vitest run",
+    "test:watch": "vitest watch",
+    "nswag": "./node_modules/nswag/bin/nswag.js aspnetcore2openapi /project:../../server/debug-mock /output:../../server/fms-insight-api.json && ./node_modules/nswag/bin/nswag.js openapi2tsclient /UseAbortSignal:true /input:../../server/fms-insight-api.json /output:src/network/api.ts"
+  }
+}