Skip to content

chore: update TypeScript and @types/node dev dependency pins - #17

Draft
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
devin/1786352694-update-dev-deps
Draft

chore: update TypeScript and @types/node dev dependency pins#17
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
devin/1786352694-update-dev-deps

Conversation

@devin-ai-integration

Copy link
Copy Markdown
Contributor

Summary

Refresh the exact dev-dependency pins to the latest versions within their current major:

-"@types/node": "22.10.1",
-"typescript": "5.7.2"
+"@types/node": "22.20.1",
+"typescript": "5.9.3"

ts-node is 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 commit package-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 i then npx tsc --noEmit index.ts → clean, no type errors or deprecation warnings.
  • LAUNCHDARKLY_SDK_KEY=… npm start against a real environment:
info: [LaunchDarkly] Opened LaunchDarkly stream connection
*** SDK successfully initialized!
*** The 'sample-feature' feature flag evaluates to false.

(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

Co-Authored-By: jbailey@launchdarkly.com <accounts@sidewaysgravity.com>
@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants