Relative import paths need explicit file extensions in ECMAScript imports

[philkunz]

Describe the bug

File: node_modules/.pnpm/@WebContainer+api@1.6.1/node_modules/@webcontainer/api/dist/entities.d.ts (1 error)

Line 1, Col 41: TS2835 - Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './preview-message-types.js'?
import type { PreviewMessageType } from './preview-message-types';

Link to the blitz that caused the error

does not need link

Steps to reproduce

does not need.

Expected behavior

compile without skiplibcheck

Parity with Local

• I have run the project in my local machine and I could not reproduce the issue.

Screenshots

No response

Platform

• OS: [e.g. macOS, Windows, Linux]
• Browser: [e.g. Chrome, Safari, Firefox]
• Version: [e.g. 91.1]

Additional context

No response

[github-actions]

We noticed that you did not provide a StackBlitz or Bolt reproduction link. Please update the issue and add a link to a public project.