Conversation
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Snapshot WarningsEnsure 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 FilesNone |
Contributor
📸 Automated UI Screenshots📋 Screenshots Captured (8)
📦 Download Screenshots📥 Download all screenshots from workflow artifacts
🤖 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>
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
Contributor
There was a problem hiding this comment.
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: ES2025and updates ESLint/Vite/esbuild targets toesnextwhere required. - Expands npm package exports with new
./hooksand./datasubpath entry points, plus root-levelData/Hooksnamespaces. - 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). |
Contributor
📸 Automated UI Screenshots📋 Screenshots Captured (8)
📦 Download Screenshots📥 Download all screenshots from workflow artifacts
🤖 Generated by Playwright automation |
pethers
approved these changes
Mar 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
targetandlib→ES2025ecmaVersion→2025esnext(esbuild doesn't support literal"es2025"yet)npm package expansion
src/hooks/index.ts(19 hooks),src/data/index.ts(4 data modules)./hooksand./datasubpath exports topackage.jsonData,Hooks) from root due to naming collisions (DamageType,SafeAreaInsets,getTechniqueById)filesarray expanded with 8 architecture/security docs (ARCHITECTURE.md, SECURITY_ARCHITECTURE.md, THREAT_MODEL.md, etc.)TypeDoc enhancement
Module resolution (no change needed)
Project already uses
"module": "ESNext"+"moduleResolution": "bundler"— correct for Vite + Node 25. NoNode16references exist in config.