chore: update TypeScript and @types/node dev dependency pins - #17
Draft
devin-ai-integration[bot] wants to merge 1 commit into
Draft
chore: update TypeScript and @types/node dev dependency pins#17devin-ai-integration[bot] wants to merge 1 commit into
devin-ai-integration[bot] wants to merge 1 commit into
Conversation
Co-Authored-By: jbailey@launchdarkly.com <accounts@sidewaysgravity.com>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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.
Summary
Refresh the exact dev-dependency pins to the latest versions within their current major:
ts-nodeis already at its latest (10.9.2). The LaunchDarkly SDK constraint is intentionally left alone:"@launchdarkly/node-server-sdk": ">= 9.0.0"already resolves to the latest 9.x (9.13.0) and the repo does not commitpackage-lock.json, so bumping the floor would be a no-op.Dev-dependency/build-config only, hence
chore:— no shipped code or user-facing requirement changes.How I tested
npm ithennpx tsc --noEmit index.ts→ clean, no type errors or deprecation warnings.LAUNCHDARKLY_SDK_KEY=… npm startagainst a real environment:(the flag key does not exist in the test environment, so the default is returned — the SDK initializes and evaluates as expected)
Limitations
Console app, so no screenshots. No deprecated LaunchDarkly SDK APIs are used by
index.ts.Link to Devin session: https://app.devin.ai/sessions/d79f078387654901af6066a98700021e
Requested by: @jsonbailey