Fix ES2015 built-in type errors in consumers by adding lib reference directive to published declarations

[Copilot]

Consumers using "lib": ["ES5", "DOM"] (or omitting lib entirely) get TypeScript errors like Cannot find name 'Symbol' / Cannot find name 'Iterator' because the package's published .d.ts file references ES2015 built-ins without declaring that dependency to TypeScript.

Root Cause

The bundled declaration file (lib/dist/types/ts-utils.d.ts) exposes ES2015 types such as Symbol, Iterator<T>, Iterable<T>, IterableIterator<T>, and Promise<T> in its public API surface. Without a /// <reference lib="es2015" /> directive in the published file, consumers must manually add "lib": ["ES2015"] to their own tsconfig.json — otherwise TypeScript cannot resolve these types.

Changes

• lib/src/index.ts and lib/src/polyfills.ts — adds /// <reference lib="es2015" /> to the source entry points so TypeScript includes the directive in generated .d.ts files and validates against ES2015 types at build time
• lib/scripts/setTsReferences.js — new post-processing script that prepends /// <reference lib="es2015" /> to the api-extractor bundled output (lib/dist/types/ts-utils.d.ts); this is required because api-extractor strips /// <reference lib="..." /> directives from its rollup
• package.json — updates the dtsgen script to api-extractor run --local --verbose && node lib/scripts/setTsReferences.js so the post-processing runs automatically as part of every build
• lib/tsconfig.base.json — adds "lib": ["ES2015", "DOM"]; propagates to both the ES5 and ES6 build configs via extends
• lib/test/tsconfig.test.json, lib/test/tsconfig.test.karma.json, lib/test/tsconfig.worker.karma.json — add "lib": ["ES2015", "DOM"]
• lib/test/tsconfig.test.esnext.json — adds "lib": ["ESNext", "DOM"]
• CHANGELOG.md — adds bug fix entry for v0.13.0

The net effect is that consumers who import from @nevware21/ts-utils automatically get the ES2015 type definitions included by TypeScript — no change to their own tsconfig.json is required.

DOM is included alongside ES2015 in all tsconfig files because the public API exports types like Window, Document, Navigator, and History (from helpers/environment.ts), which require the DOM lib to resolve.

This does not change the JavaScript runtime target or emit.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.46%. Comparing base (da838a4) to head (287c358).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #558   +/-   ##
=======================================
  Coverage   99.46%   99.46%           
=======================================
  Files         145      145           
  Lines        4271     4271           
  Branches      938      938           
=======================================
  Hits         4248     4248           
  Misses         23       23           

Files with missing lines	Coverage Δ
lib/src/polyfills.ts	94.11% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

This PR makes the required TypeScript standard library typings explicit across the library build and test tsconfig files by declaring ES2015 (and ESNext for ESNext tests) alongside DOM, preventing missing built-in type errors during compilation.

Changes:

• Add "lib": ["ES2015", "DOM"] to the shared lib/tsconfig.base.json so it propagates to the library build configs via extends.
• Add "lib": ["ES2015", "DOM"] to the ES5-oriented test tsconfigs (Node + Karma runner configs).
• Add "lib": ["ESNext", "DOM"] to the ESNext test tsconfig.

Reviewed changes

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

Show a summary per file

File	Description
lib/tsconfig.base.json	Declares ES2015 + DOM libs for the base compiler config used by library builds.
lib/test/tsconfig.worker.karma.json	Declares ES2015 + DOM libs for worker Karma test compilation.
lib/test/tsconfig.test.karma.json	Declares ES2015 + DOM libs for browser Karma test compilation.
lib/test/tsconfig.test.json	Declares ES2015 + DOM libs for Node/common test compilation via ts-mocha.
lib/test/tsconfig.test.esnext.json	Declares ESNext + DOM libs for ESNext test compilation.

[nev21]

@copilot This is only addressing the local test resources and not the actual reported issue.
Also update the change list / log

[Copilot]

@copilot This is only addressing the local test resources and not the actual reported issue.
Also update the change list / log

Addressed in commit 337e0e8. The actual fix is a /// <reference lib="es2015" /> directive added to the published bundled declaration file (lib/dist/types/ts-utils.d.ts). When consumers import from the package, TypeScript automatically includes ES2015 type definitions — so they no longer need to add "lib": ["ES2015"] to their own tsconfig.

The implementation:

• Added /// <reference lib="es2015" /> to lib/src/index.ts and lib/src/polyfills.ts for build-time validation
• Created lib/scripts/setTsReferences.js as a post-processing step, since api-extractor strips reference lib directives from its bundled rollup output
• Updated the dtsgen npm script to run the post-processor after api-extractor
• Updated CHANGELOG.md with the bug fix entry

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• www.googleapis.com
  • Triggering command: /usr/local/bin/node node install.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• api-extractor.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)
• www.googleapis.com
  • Triggering command: /usr/local/bin/node node install.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[nevware21-bot]

Approved by nevware21-bot

[Copilot]

Pull request overview

Copilot reviewed 10 out of 10 changed files in this pull request and generated 1 comment.