Hey team - has anyone started seeing this issue after updating

@thoughtspot/visual-embed-sdk

? We're working to move from 1.42.0 to 1.48.0 and there appear to have been changes to how the bundle is created that are breaking our builds. ./node_modules/@thoughtspot/visual-embed-sdk/lib/src/embed/ts-embed.js:602:33-40 - Error: Should not import the named export 'version' (imported as 'version') from default-exporting module (only default export is available soon) ./node_modules/@thoughtspot/visual-embed-sdk/lib/src/mixpanel-service.js:80:20-27 - Error: Should not import the named export 'version' (imported as 'version') from default-exporting module (only default export is available soon)

message has been deleted

Solution: Yes — this can happen when a build toolchain is strict about ESM/CommonJS interop, and the SDK package internals changed between

1.42.0

and

1.48.0

. Your error is specifically about named-importing

version

from a module your bundler now treats as default-only. What to do (most practical order): 1. Avoid importing from internal SDK paths (

lib/src/...

) anywhere in your app/build config. Only import from:

js
   import { init, AuthType, LiveboardEmbed } from '@thoughtspot/visual-embed-sdk';

2. Align bundler/transpiler settings for ESM interop (Webpack/Babel/TS config), especially if you recently tightened module rules. 3. Pin to a known-good version temporarily (for release safety), then test the upgrade in isolation: - keep

1.42.0

in production - create a repro branch for

1.48.0

4. If this is blocking, raise with ThoughtSpot support/community including your bundler + exact config, since this looks like packaging/interop behavior rather than embed API usage. I could not find an official ThoughtSpot doc entry that explicitly documents this specific

named export 'version'

regression/error pattern in

ts-embed.js

/

mixpanel-service.js

. --- Suggestions: - Create a minimal repro with just

init()

+ one embed component; if it builds there, diff your monorepo/toolchain settings. - Check lockfile for duplicate SDK versions (common in workspaces). - If you’re on Webpack 5, test toggling strict ESM behavior in a branch to confirm root cause quickly. - As a fallback, test the UMD build route (if compatible with your app architecture) since docs confirm both ESM and UMD distribution formats. --- Docs: - Visual Embed SDK quickstart/imports: https://developers.thoughtspot.com/docs/getting-started#_step_1_import_the_visual_embed_sdk - Code samples: https://developers.thoughtspot.com/docs/code-samples - General developer docs: https://developers.thoughtspot.com/docs

Hi, we've released a new SDK version (1.49.1) containing the fix. Could you please verify whether the issue has been resolved on your end?

Hi Aditya - this update resolved the issue - thank you for the quick resolution on this one!

message has been deleted