Wrong typings of LDOptionsCommon

[cuong-nguyenquoc-tpv-clv]

Is this a support request?
No

Describe the bug
LDOptionsCommon from "@launchdarkly/js-server-sdk-common" expose incorrect parameter types.
The expected options to work with ldcli dev-server is to have configuration key like below. Meanwhile, the typings from package expose options keys with postfix Uri instead of Url

import { init as LdInit } from '@launchdarkly/node-server-sdk';

const client = LdInit(LAUNCHDARKLY_SDK_KEY, {
  baseUrl: 'http://localhost:8765',
  streamUrl: 'http://localhost:8765',
  eventsUrl: 'http://localhost:8765',
});

To reproduce

1. Install ldcli and run ldcli dev-server start
2. Config LD client initialization like below for nodejs repo:

import { init as LdInit } from '@launchdarkly/node-server-sdk';

const client = LdInit(LAUNCHDARKLY_SDK_KEY, {
  baseUri: 'http://localhost:8765',
  streamUri: 'http://localhost:8765',
  eventsUri: 'http://localhost:8765',
});

3. Start the nodejs project

Expected behavior
Logs

2025-10-08T16:50:40.410Z [undefined] [debug] [LaunchDarklyService] : Received put event
2025-10-08T16:50:40.412Z [undefined] [debug] [LaunchDarklyService] : Initializing all data

Logs

2025-10-08T16:45:32.737Z [undefined] [error] [LaunchDarklyService] : Not Found
2025-10-08T16:45:32.737Z [undefined] [error] [LaunchDarklyService] : Received error 404 for streaming request - giving up permanently

SDK version
9.10.2

Language version, developer tools
NodeJs 20.19.0

OS/platform
macOS Tahoe 26.1

[kinyoklion]

Hello @cuong-nguyenquoc-tpv-clv,

Thank you for the report. I am not certain what it is you are reporting though. The typing all uses the Uri suffix and is routinely used in many configurations. As well as used in the validation contract tests.

Is the ldcli providing you with instructions that say to use Url? If so then the ldcli is incorrect.

Thank you,
Ryan

[cuong-nguyenquoc-tpv-clv]

hi @kinyoklion , I tried to use Uri as defined in the parameters type of init function. However, It turned out using Url is correct.

[github-actions]

This issue is stale because it has been open for 90 days without activity. Remove the stale label or comment, or this will be closed in 14 days.