Repository navigation
Patch JavaScript SDK development dependencies - #19
Merged
Merged
Conversation
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.
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:
The existing
npm run test:coveragecommand 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.