Is it possible to catch a build-time error during a dynamic import?

[thelinuxlich]

Precheck

• I searched existing issues before opening this one to avoid duplicates
• I understand tsx aims for TypeScript parity and will not support arbitrary Node.js enhancements
• This request cannot be made to Node.js directly, and is specific to tsx
• I understand this form is not for addressing a bug or seeking help

Feature request

I have a codegen task watching a directory for changes and whenever there is a malformed TS file, TSX will throw a esbuild error and exit the watcher. I wish I could try-catch this error so the watcher restarts the task.

Motivations

I don't know if it's expected but I think it's a bit unintuitive that I can't trust this:

try {
   await import('./something')
} catch (e) {
   console.log(e)
}

Alternatives

No response

Additional context

No response

Contributions

• I plan to open a pull request for this issue
• I plan to make a financial contribution to this project

[privatenumber]

Not really sure what you're asking/reporting

[wesbos]

Also have this issue. I'm dynamically importing a path, and if that file has a syntax error in it, the watcher will crash and I need to restart the whole process.

In Node, you can catch the error like so:

try {
  const x = await import(`./file-with-syntax-error.js`);
  console.log(x);
} catch (e) {
  console.log(`caught error in try/catch block`);
  console.error(e);
}

But with tsx, esbuild throws and error and exits the process:

I supposed I could run nodemon or something to get around this, but was wondering if I could somehow catch the error on a dynamic require/import.

[privatenumber]

Ooh gotcha. The original issue didn't explain that dynamic import errors can't be caught. Thanks for explaining.

This would be a bug, and possibly related to #493

Feel free to submit a PR

[wesbos]

Okay thank you - that is also the issue i have. I think we can close this as a dupe.