Skip to content

fix(test): repair the deprecation warning tests on main - #468

Open
dmae97 wants to merge 1 commit into
mainfrom
fix/deprecation-test-arity
Open

dmae97 wants to merge 1 commit into
mainfrom
fix/deprecation-test-arity

Conversation

@dmae97

@dmae97 dmae97 commented Nov 18, 2026

Copy link
Copy Markdown
Owner

Problem

#467 landed on main at 3ebd3fb4 with seven two-argument calls to warnDeprecation(message). A focused TypeScript 6.0.3 check reproduces TS2554 for those calls. The repo also requires explicit .ts suffixes on these relative imports.

Change

Pass the warning text as the single argument, assert the full formatted warning in the first test, and restore the console.warn spy after each test. Only the test file changes. Refs #464, #467.

Verification

  • Focused tsc --noEmit --skipLibCheck --strict --allowImportingTsExtensions --module nodenext --target es2022 passes on the corrected test.
  • Four Node assertions passed against the existing module and locked chalk dependency for the warning text, deduplication, distinct warnings, and reset.
  • The pinned Vitest runner could not start in the offline environment because tinyrainbow@3.2.0 was unavailable. Full repository verification is pending CI.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant