8e6893d550
Bumps [ip](https://github.com/indutny/node-ip) from 1.1.5 to 1.1.9. <details> <summary>Commits</summary> <ul> <li><a href="1ecbf2fd8c"><code>1ecbf2f</code></a> 1.1.9</li> <li><a href="6a3ada9b47"><code>6a3ada9</code></a> lib: fixed CVE-2023-42282 and added unit test</li> <li><a href="5dc3b2f3f4"><code>5dc3b2f</code></a> 1.1.8</li> <li><a href="8e6f28b23a"><code>8e6f28b</code></a> lib: even better node 6 support</li> <li><a href="088c9e5664"><code>088c9e5</code></a> 1.1.7</li> <li><a href="1a4ca35ddc"><code>1a4ca35</code></a> lib: add back support for Node.js 6</li> <li><a href="af82ef42ad"><code>af82ef4</code></a> 1.1.6</li> <li><a href="dba19f6c0c"><code>dba19f6</code></a> package: exclude test folder from publishing</li> <li><a href="7cd7f30991"><code>7cd7f30</code></a> ci: use github workflows</li> <li><a href="4de50aec87"><code>4de50ae</code></a> lib: node 18 support</li> <li>See full diff in <a href="https://github.com/indutny/node-ip/compare/v1.1.5...v1.1.9">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/dcs-liberation/dcs_liberation/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
DCS Liberation Client
This is a React app for the front-end of DCS Liberation. It is a work in progress that just barely implements the map. This is not useful for players yet.
For development, set the following environment variables when launching DCS Liberation (the Qt UI):
-
CORS_ALLOW_DEBUG_SERVER=trueThis will allow the front-end to make requests to the server, as long as the front-end is running on http://localhost:3000.
Then, run npm start to start the development server. Launch the Qt UI with
--new-map --dev to connect the webview to the development server, or navigate
to http://localhost:3000 in your browser.
Regenerating the API stubs
The backend uses FastAPI which exposes /openapi.json. This is consumed by
@rtk-query/codegen-openapi to automatically generate the API stubs in
src/api/liberationApi.ts.
If you make a change to the API surface the typescript API will need to be regenerated. To do this, first launch Liberation (to start the backend) and run
npm run regenerate-api
See https://redux-toolkit.js.org/rtk-query/usage/code-generation for more information.
Available Scripts
In the project directory, you can run:
npm start
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
npm test
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
npm run build
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
npm run eject
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
Learn More
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.