Skip to content

Update project to ES2025, expand npm package exports, enhance TypeDoc coverage#1748

Merged
pethers merged 2 commits intomainfrom
copilot/update-to-es2025-config-and-docs
Mar 31, 2026
Merged

Update project to ES2025, expand npm package exports, enhance TypeDoc coverage#1748
pethers merged 2 commits intomainfrom
copilot/update-to-es2025-config-and-docs

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Mar 31, 2026

Migrate all config from ES2024 → ES2025, add missing module exports to the npm package, and extend TypeDoc to cover the full public API with comprehensive ISMS/security doc references.

ES2025 migration

  • All 5 tsconfig files: target and libES2025
  • ESLint: ecmaVersion2025
  • Vite build/esbuild targets → esnext (esbuild doesn't support literal "es2025" yet)

npm package expansion

  • New barrel exports: src/hooks/index.ts (19 hooks), src/data/index.ts (4 data modules)
  • Added ./hooks and ./data subpath exports to package.json
  • Hooks/data exposed as namespaced-only exports (Data, Hooks) from root due to naming collisions (DamageType, SafeAreaInsets, getTechniqueById)
  • files array expanded with 8 architecture/security docs (ARCHITECTURE.md, SECURITY_ARCHITECTURE.md, THREAT_MODEL.md, etc.)
// Consumers can now import directly
import { useDebounce, useThrottle } from "blacktrigram/hooks";
import { techniques } from "blacktrigram/data";

// Or via namespace from root
import { Hooks, Data } from "blacktrigram";

TypeDoc enhancement

  • Entry points: 29 → 40 (added hooks, data, trigram techniques, combat sub-modules, training HUD, controls, philosophy, Three.js optimization)
  • Sidebar links: 15 → 24 (added Future Threat/Data/Workflows, Controls, Financial Security, BCP Plan, End-of-Life, Workflows, Roadmap)

Module resolution (no change needed)

Project already uses "module": "ESNext" + "moduleResolution": "bundler" — correct for Vite + Node 25. No Node16 references exist in config.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 31, 2026

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA 7d5475e.
Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

Scanned Files

None

@github-actions
Copy link
Copy Markdown
Contributor

📸 Automated UI Screenshots

📋 Screenshots Captured (8)

# Screenshot
1 01-splash-screen.png - 01 splash screen.png
2 02-intro-screen-menu.png - 02 intro screen menu.png
3 03-intro-screen-archetype-selector.png - 03 intro screen archetype selector.png
4 04-controls-screen.png - 04 controls screen.png
5 05-philosophy-screen.png - 05 philosophy screen.png
6 06-training-screen.png - 06 training screen.png
7 07-combat-screen-practice.png - 07 combat screen practice.png
8 08-combat-screen-versus.png - 08 combat screen versus.png

📦 Download Screenshots

📥 Download all screenshots from workflow artifacts

Screenshots are preserved as workflow artifacts for 30 days.


🤖 Generated by Playwright automation

…typedoc documentation

- Update all TypeScript configs (tsconfig.json, tsconfig.app.json, tsconfig.lib.json,
  tsconfig.node.json, cypress/tsconfig.json) from ES2024 to ES2025
- Update ESLint ecmaVersion from 2024 to 2025
- Update Vite build targets to esnext (esbuild doesn't support es2025 literal yet)
- Create src/hooks/index.ts barrel export for all 19 custom hooks
- Create src/data/index.ts barrel export for game data modules
- Add hooks and data to package.json exports map and src/index.ts
- Expand package.json files array to include architecture/security docs
- Extend typedoc.json with 40 entry points (was 29), including hooks, data,
  trigram techniques, combat helpers/effects/HUD, training HUD, controls,
  philosophy, and optimization modules
- Extend typedoc sidebar links with ISMS docs (Future Threat Model, Future
  Data Model, Future Workflows, Controls, Financial Security, BCP Plan,
  End-of-Life Strategy, Workflows, Roadmap)

Agent-Logs-Url: https://github.com/Hack23/blacktrigram/sessions/d1c0f5bb-29a4-4d22-8e7a-20c358efa011

Co-authored-by: pethers <1726836+pethers@users.noreply.github.com>
@github-actions github-actions bot added dependencies Dependency updates infrastructure CI/CD and build infrastructure config Configuration changes testing Testing improvements needs-tests Needs test coverage e2e End-to-end testing labels Mar 31, 2026
Copilot AI changed the title [WIP] Update project to ES2025 for all config and documentation Update project to ES2025, expand npm package exports, enhance TypeDoc coverage Mar 31, 2026
Copilot AI requested a review from pethers March 31, 2026 23:28
@pethers pethers marked this pull request as ready for review March 31, 2026 23:29
@pethers pethers requested a review from Copilot March 31, 2026 23:30
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates build/tooling targets and published API surface to align the project with ES2025-era config while expanding the library’s consumable entry points and generated API documentation.

Changes:

  • Migrates TypeScript configs to target/lib: ES2025 and updates ESLint/Vite/esbuild targets to esnext where required.
  • Expands npm package exports with new ./hooks and ./data subpath entry points, plus root-level Data/Hooks namespaces.
  • Extends TypeDoc entry points and sidebar links to cover additional public modules and security/architecture references.

Reviewed changes

Copilot reviewed 12 out of 14 changed files in this pull request and generated no comments.

Show a summary per file
File Description
vite.lib.config.ts Library build target updated to esnext for esbuild compatibility.
vite.config.ts App build + esbuild targets updated to esnext.
typedoc.json Adds hooks/data and more module entry points; expands sidebar documentation links.
tsconfig.node.json Bumps Node/tooling TS target/lib to ES2025.
tsconfig.lib.json Bumps library TS target/lib to ES2025.
tsconfig.json Bumps base TS target/lib to ES2025.
tsconfig.app.json Bumps app TS target/lib to ES2025.
src/index.ts Adds namespaced Data and Hooks exports from the root entry point.
src/hooks/index.ts New hooks barrel file to support blacktrigram/hooks entry point + TypeDoc grouping.
src/data/index.ts New data barrel file to support blacktrigram/data entry point + TypeDoc grouping.
package.json Adds ./hooks and ./data to exports; expands published files list with key docs.
eslint.config.js Updates ecmaVersion to 2025.
cypress/tsconfig.json Bumps Cypress TS target/lib to ES2025.
.gitignore Adds an additional build/ ignore entry (currently redundant).

@github-actions
Copy link
Copy Markdown
Contributor

📸 Automated UI Screenshots

📋 Screenshots Captured (8)

# Screenshot
1 01-splash-screen.png - 01 splash screen.png
2 02-intro-screen-menu.png - 02 intro screen menu.png
3 03-intro-screen-archetype-selector.png - 03 intro screen archetype selector.png
4 04-controls-screen.png - 04 controls screen.png
5 05-philosophy-screen.png - 05 philosophy screen.png
6 06-training-screen.png - 06 training screen.png
7 07-combat-screen-practice.png - 07 combat screen practice.png
8 08-combat-screen-versus.png - 08 combat screen versus.png

📦 Download Screenshots

📥 Download all screenshots from workflow artifacts

Screenshots are preserved as workflow artifacts for 30 days.


🤖 Generated by Playwright automation

@pethers pethers merged commit 2c8f044 into main Mar 31, 2026
20 checks passed
@pethers pethers deleted the copilot/update-to-es2025-config-and-docs branch March 31, 2026 23:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

config Configuration changes dependencies Dependency updates e2e End-to-end testing infrastructure CI/CD and build infrastructure needs-tests Needs test coverage testing Testing improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants