@maximem/synap-js-sdk 0.4.1 → 0.4.2

package/bin/synap-js-sdk.js

@@ -3,7 +3,7 @@
  * Compatibility shim.
  *
  * `npx synap-js-sdk setup` used to build a Python virtualenv and install the
- * Python SDK into it. Since 1.0 the SDK is native TypeScript, so there is
+ * Python SDK into it. Since 0.4 the SDK is native TypeScript, so there is
  * nothing to set up.
  *
  * The command is kept, and kept exiting 0, because it appears in published
@@ -17,7 +17,7 @@
 const [, , command] = process.argv;
 
 const NOTE = `
-@maximem/synap-js-sdk 1.x is a native TypeScript SDK. It does not use Python,
+@maximem/synap-js-sdk 0.4+ is a native TypeScript SDK. It does not use Python,
 so there is no setup step and this command does nothing.
 
 If you are upgrading from 0.3.x:
@@ -37,7 +37,7 @@ switch (command) {
     break;
   case '--version':
   case '-v':
-    console.log(process.env['npm_package_version'] ?? '1.x');
+    console.log(process.env['npm_package_version'] ?? '0.4+');
     break;
   default:
     console.log(`Unknown command: ${command}\n\n${NOTE}`);

package/dist/index.cjs

@@ -1238,7 +1238,7 @@ function envPort() {
   return Number.isFinite(parsed) ? parsed : void 0;
 }
 function envTls() {
-  const raw = _chunkZKOJDUN4cjs.getEnv.call(void 0, "SYNAP_GRPC_USE_TLS");
+  const raw = _nullishCoalesce(_chunkZKOJDUN4cjs.getEnv.call(void 0, "SYNAP_GRPC_USE_TLS"), () => ( _chunkZKOJDUN4cjs.getEnv.call(void 0, "SYNAP_GRPC_TLS")));
   if (raw === void 0 || raw === "") return void 0;
   return !["0", "false", "no", "off"].includes(raw.trim().toLowerCase());
 }
@@ -2168,6 +2168,7 @@ var SynapClient = class {
   #fetchHooks;
   constructor(options = {}) {
     const credentials = resolveCredentials(options);
+    const resolvedBaseUrl = resolveBaseUrl(options);
     validateInstanceId(credentials.instanceId);
     const registryKey = buildRegistryKey(credentials.instanceId, credentials.apiKey);
     if (options._force_new !== true) {
@@ -2185,7 +2186,12 @@ var SynapClient = class {
     this.#registryKeys = options._force_new === true ? [] : [registryKey];
     this.#transport = new HttpTransport({
       credentials,
-      ...options.baseUrl !== void 0 ? { baseUrl: options.baseUrl } : {},
+      // SYNAP_BASE_URL is honoured, as Python does (sdk.py) and as the 0.3.x
+      // wrapper did. Ignoring it was a wrong-DESTINATION bug rather than a
+      // missing convenience: anyone pointing at a self-hosted or staging
+      // deployment through the environment would silently have started sending
+      // their data to production on upgrade.
+      ...resolvedBaseUrl !== void 0 ? { baseUrl: resolvedBaseUrl } : {},
       ...options.timeouts !== void 0 ? { timeouts: options.timeouts } : {},
       ...options.retryPolicy !== void 0 ? { retryPolicy: options.retryPolicy } : {},
       ...options.keepAlive !== void 0 ? { keepAlive: options.keepAlive } : {},
@@ -2635,6 +2641,11 @@ function pick3(o2, snake, camel) {
   const a = o2[snake];
   return a !== void 0 ? a : o2[camel];
 }
+function resolveBaseUrl(options) {
+  if (options.baseUrl !== void 0) return options.baseUrl;
+  const fromEnv = _optionalChain([_chunkZKOJDUN4cjs.getEnv.call(void 0, "SYNAP_BASE_URL"), 'optionalAccess', _51 => _51.trim, 'call', _52 => _52()]);
+  return fromEnv !== void 0 && fromEnv !== "" ? fromEnv : void 0;
+}
 function resolveCredentials(options) {
   const apiKey = _nullishCoalesce(options.apiKey, () => ( _chunkZKOJDUN4cjs.getEnv.call(void 0, "SYNAP_API_KEY")));
   if (!apiKey) {