[n-lark]

Description

Sets up TypeScript so new files can be written in it. It's optional so existing JavaScript keeps working as-is and isn't type checked, so JS-only PRs aren't affected.

• ui/tsconfig.json (replaces jsconfig.json) and nodes/tsconfig.json
• npm run typecheck, which also runs as part of npm run lint
• ESLint support for .ts files and <script lang="ts">
• TypeScript pinned to ~6.0, since TS 7 doesn't work with vue-tsc yet
• A short TypeScript section in the contributor docs

TypeScript under nodes/ needs a compile step, which comes with the first file that uses it (the data store, #2239).

Test plan

• lint, typecheck, test and build pass
• Type and lint errors are caught in .ts files and lang="ts" blocks
• Dashboard and Node-RED editor load in a live Node-RED with no console errors

Related Issue(s)

Resolves #2329.

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated
  • Upgrade instructions
  • Configuration details
  • Concepts
• Changes flowforge.yml?
  • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
  • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production
• Link to Changelog Entry PR, or note why one is not needed.

Labels

• Includes a DB migration? -> add the area:migration label

[andypalmi]

Pulled the branch and ran it locally.

Verified

1. typecheck passes and lint:js has 0 errors.
2. Deliberately bad .ts, lang="ts" and nodes/*.ts files are caught by vue-tsc, tsc and ESLint.
3. typescript, tsc and vue-tsc all resolve to 6.0.3, so the ~6.0 pin holds.
4. Removing ui/jsconfig.json loses nothing: its @/* alias is unused and not defined in vite.config.js.

Questions

5. The description says docs "(en/de)" but the German translation was removed in dab994ef. Could it be updated?
6. Could the docs say TypeScript isn't supported in /nodes yet, since there's no compile step?
7. Is limiting the *.ts ESLint override to no-unused-vars intentional?
8. @types/node is ^22 while CI runs Node 24. Is that deliberate?

[n-lark]

Hey @andypalmi thanks for looking.

1. Already updated, description no longer mentions de.
2. Added a line to the contributor docs. It goes away when the data store PR adds the build step.
3. Intentional, and .ts gets the same checks as JS. no-unused-vars is swapped for the TS version, and tsc covers no-undef and no-redeclare since typecheck runs in lint. All other rules still apply.
4. Deliberate. ^22 is what Vite's peer range already had locked, so the lockfile doesn't change. Types should stay behind CI, since nodes/ still has to run on older Node.