xTr1m/RpgRoller
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove legacy TypeScript frontend and npm pipeline

Browse Source
This commit is contained in:
Frank Tovar
2026-02-25 12:31:39 +01:00
parent 35c60c4ea2
commit 0f44cc466b
31 changed files with 20 additions and 2526 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
FAQ.md
View File

@@ -1,15 +1,9 @@
# FAQ
## Why does this starter use custom frontend lint/format scripts instead of heavy npm dependencies?
## Does this project still require npm/frontend TypeScript tooling?
The kickoff scaffold is intentionally lightweight and keeps only strictly relevant tooling:
- API client generation from the OpenAPI contract
- TypeScript compilation for frontend source files
- basic frontend contract checks
- deterministic formatting checks used by `scripts/ci-local.ps1`
This keeps the first commit small while preserving CI discipline. Additional tooling can be introduced when the frontend stack is finalized.
No. The legacy TypeScript frontend pipeline was removed after the Blazor rewrite.
`scripts/ci-local.ps1` is now a .NET-only flow (restore, build, tests, coverage checks).
## Is frontend JavaScript handwritten?
@@ -21,7 +15,7 @@ There is still small handwritten JavaScript in `RpgRoller/wwwroot/js/rpgroller-a
- SSE connection/reconnect handling
- per-tab session storage helpers used by the Blazor UI
The TypeScript frontend folders remain in the repo for tooling and generated API client contract checks used by CI.
There is no TypeScript runtime frontend in the current codebase.
## Where is backend state stored locally?