Skip to content

Patch JavaScript SDK development dependencies - #19

Merged
MudassarTariq merged 1 commit into
masterfrom
fix/development-security-updates
Oct 29, 2026
Merged

MudassarTariq merged 1 commit into
masterfrom
fix/development-security-updates

Conversation

@MudassarTariq

@MudassarTariq MudassarTariq commented Oct 29, 2026 •

Copy link
Copy Markdown
Member

Update Vitest and coverage to 4.1.12, Vite to 7.3.7 and source-map-js to 1.2.2 to address the eight open development-dependency alerts. Keep Vite on the existing major version. The SDK version, public source, Node.js 18+ requirement and README remain unchanged.

Add CI checks for builds, types and package exports on Node.js 18, 22 and 24, unit tests on 22 and 24, and audits of development and production dependencies. Vitest already requires Node.js 20+, so the Node.js 18 job checks the built package independently.

Validation:

  • All three GitHub CI jobs passed on Node.js 18.20.8, 22.23.4 and 24.22.1. The Node.js 18 job checks the package build and imports; unit tests run on 22 and 24.
  • All 55 unit tests, type checking and the build pass locally.
  • Development and production audits both report zero findings.
  • All four generated JavaScript/declaration files are byte-for-byte identical before and after the update.
  • ESM and CommonJS imports, declarations and client construction pass the package checks.

The existing npm run test:coverage command fails its 90% thresholds both before and after the update: 76.52% lines, 76.55% statements, 66.21% branches and 88.98% functions. The coverage configuration is unchanged.

No SDK release, bundle publication or production deployment is required for these tooling-only changes. Live API tests were not run.

@MudassarTariq
MudassarTariq marked this pull request as ready for review October 29, 2026 16:20
@MudassarTariq
MudassarTariq merged commit da23191 into master Oct 29, 2026
3 checks passed
@MudassarTariq
MudassarTariq deleted the fix/development-security-updates branch October 29, 2026 16:21
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