Skip to content

fix(container.js): TypeScript import to handle default export - #5604

Merged
DavertMik merged 1 commit into
4.xfrom
5603-bug-correctly-handle-typescript-module-imports-in-esm-environments-this-is-a-known-interop-issue
Jun 5, 2026
Merged

fix(container.js): TypeScript import to handle default export#5604
DavertMik merged 1 commit into
4.xfrom
5603-bug-correctly-handle-typescript-module-imports-in-esm-environments-this-is-a-known-interop-issue

Conversation

@kobenguyent

@kobenguyentkobenguyent commented Jun 5, 2026

Copy link
Copy Markdown
Collaborator

Motivation/Description of the PR

Applicable helpers:

  • Playwright
  • Puppeteer
  • WebDriver
  • REST
  • FileHelper
  • Appium

Applicable plugins:

  • aiTrace
  • autoDelay
  • autoLogin
  • customLocator
  • pause
  • coverage
  • heal
  • retryFailedStep
  • screenshot
  • selenoid
  • stepTimeout
  • subtitles

Type of change

  • 🔥 Breaking changes
  • 🚀 New functionality
  • 🐛 Bug fix
  • 🧹 Chore
  • 📋 Documentation changes/updates
  • ♨️ Hot fix
  • 🔨 Markdown files fix - not related to source code
  • 💅 Polish code

Checklist:

  • Tests have been added
  • Documentation has been added (Run npm run docs)
  • Lint checking (Run npm run lint)
  • Local tests are passed (Run npm test)

@kobenguyentkobenguyent changed the title Fix TypeScript import to handle default exportfix(container.js): TypeScript import to handle default exportJun 5, 2026
@DavertMik
DavertMik merged commit a493212 into 4.xJun 5, 2026
13 checks passed
@DavertMik
DavertMik deleted the 5603-bug-correctly-handle-typescript-module-imports-in-esm-environments-this-is-a-known-interop-issue branch June 5, 2026 09:00
Sign up for freeto 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.

BUG: correctly handle typescript module imports in ESM environments (this is a known interop issue)

2 participants

@kobenguyent@DavertMik