Fix TypeScript 6 checker config

[cursor]

Asana Task/Github Issue: PR #2602

Description

Restores the repository's intended TypeScript checker assumptions under TypeScript 6 by explicitly setting strict: false, preserving pre-6.0 automatic @types discovery, and suppressing the moduleResolution: node deprecation until the resolver can be migrated. Also updates a test setup delete to avoid the newer DOM lib's non-optional navigation property typing.

Testing Steps

• npm run tsc
• npm run tsc-strict-core
• npm run docs-preview

Checklist

Please tick all that apply:

• I have tested this change locally
• I have tested this change locally in all supported browsers
• This change will be visible to users
• I have added automated tests that cover this change
• I have ensured the change is gated by config
• This change was covered by a ship review
• This change was covered by a tech design
• Any dependent config has been merged

  

---

Note

Medium Risk
Upgrades TypeScript/TypeDoc and adjusts tsconfig.json, which can change type-checking behavior and surface new compile-time failures across the repo. Runtime impact is minimal, but CI/typecheck and docs generation may be affected.

Overview
Restores the intended TypeScript checker behavior under TypeScript 6 by updating tsconfig.json (explicitly setting strict: false, suppressing TS6 deprecations via ignoreDeprecations, and re-enabling broad @types discovery with types: ["*"]).

Bumps tooling/dev dependencies (typescript, typedoc, and various @types/* packages) and refreshes package-lock.json accordingly.

Updates an integration test to delete globalThis.navigation via Reflect.deleteProperty to satisfy newer DOM typings.

^{Reviewed by Cursor Bugbot for commit 19e2c53. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Build Branch

Branch	pr-releases/jkt/auto/dependency-update-risk-analysis-c062
Commit	690c74e307
Updated	May 13, 2026 at 12:53:35 PM UTC

Static preview entry points

• Docs: docs/index.html
• Static pages: build/integration/pages/index.html
• Integration pages: injected/integration-test/test-pages/index.html

QR codes (mobile preview)

Entry point	QR code
Docs
Static pages
Integration pages

Integration commands

npm (Android / Extension):

npm i github:duckduckgo/content-scope-scripts#pr-releases/jkt/auto/dependency-update-risk-analysis-c062

Swift Package Manager (Apple):

.package(url: "https://github.com/duckduckgo/content-scope-scripts.git", branch: "pr-releases/jkt/auto/dependency-update-risk-analysis-c062")

git submodule (Windows):

git -C submodules/content-scope-scripts fetch origin pr-releases/jkt/auto/dependency-update-risk-analysis-c062
git -C submodules/content-scope-scripts checkout origin/pr-releases/jkt/auto/dependency-update-risk-analysis-c062

Pin to exact commit

npm (Android / Extension):

npm i github:duckduckgo/content-scope-scripts#690c74e3071fbf67fac1935e42070218576d0bfa

Swift Package Manager (Apple):

.package(url: "https://github.com/duckduckgo/content-scope-scripts.git", revision: "690c74e3071fbf67fac1935e42070218576d0bfa")

git submodule (Windows):

git -C submodules/content-scope-scripts fetch origin pr-releases/jkt/auto/dependency-update-risk-analysis-c062
git -C submodules/content-scope-scripts checkout 690c74e3071fbf67fac1935e42070218576d0bfa

[github-actions]

[Beta] Generated file diff

Time updated: Wed, 13 May 2026 12:54:01 GMT

[cursor]

Web Compatibility Assessment

No blocking findings.

• injected/integration-test/pages.spec.js lines 80-84, severity: info. The delete globalThis.navigation to Reflect.deleteProperty(globalThis, 'navigation') change is confined to Playwright page.addInitScript() test setup for simulating missing Navigation API support. It does not ship in injected runtime code and does not alter API wrapping, descriptors, toString() masking, DOM timing, or platform bundle behavior.
• package.json lines 56-58, injected/package.json lines 51-53, package-lock.json lines 33-56 and 1598-2108, severity: info. Dependency changes are dev/checker/docs type-surface changes (typescript, typedoc, @types/*, TypeDoc transitive packages). No production dependency, injected feature, wrapper utility, platform entry point, or runtime browser API surface changed.
• tsconfig.json lines 9-13, severity: info. The TypeScript 6 checker settings are noEmit build-time config only. They do not affect generated content-scope runtime behavior, remote config evaluation, or page-world API fidelity.

Security Assessment

No blocking findings.

• No changes touch injected/src/captured-globals.js, wrapper-utils.js, DDGProxy, message bridge, messaging transports, origin checks, postMessage, iframe access, config gating, or stack-trace exemption logic.
• The only new uncaptured global-looking use (Reflect.deleteProperty) is inside test-page initialization, not hostile production page execution.

Risk Level

Low Risk: this is a devDependency/checker-config/test-only PR with no injected runtime or security-boundary changes.

Recommendations

• No code changes requested from a web compatibility or security perspective.
• Keep the remaining CI checks green before merge. I locally verified npm ci, generated injected artifacts, npm run tsc, npm run tsc-strict-core, and npm run docs successfully.

  

_{Sent by Cursor Automation: Web compat and sec}

[cursor]

Web Compatibility Assessment

No findings. The diff is limited to dev dependency/tooling updates, tsconfig.json, and a Playwright test-infra change in injected/integration-test/pages.spec.js; it does not touch injected runtime features, wrapper utilities, API shims, DOM manipulation, messaging, captured globals, or platform entry points.

Security Assessment

No findings. I did not see new message paths, origin handling changes, postMessage, network requests, global captures, prototype patches, or page-controlled data flows.

Risk Level

Low Risk: this is a TypeScript/tooling and test-only change with no direct injected runtime behavior change; the main risk is CI/build-tool compatibility from the TypeScript 6 upgrade.

Recommendations

No blocking recommendations. Keep the existing follow-up discussion for migrating off deprecated moduleResolution: "node" separate from this PR.

Verified locally:

• npm ci
• npm run build --workspace=injected
• npm run tsc
• npm run tsc-strict-core
• npm run lint
• npm run docs

  

_{Sent by Cursor Automation: Web compat and sec}