Can you please create new release for the latest changes on Master branch

[abdulkader]

Current Behavior

Currrent published version of tsdx on NPM registry is really outdated (published 2years ago) and there have been new changes pushed to main branch. Can we create new release from this latest master. It also has fixes for supporting latest terser feature which lack in the previous version.

eg: if I use optional chaining operator in my library, when building with tsdx it fails. With latest changes in the master, it works perfectly.

Desired Behavior

We need to have latest version release on NPM so that everyone get the benefits of latest updates

Suggested Solution

Who does this impact? Who is this for?

Describe alternatives you've considered

Additional context

[aarjithn]

Related: #1129

[ctjlewis]

cc @agilgur5, anything I can do to help? I reached out to Jared on Discord but I know he's super busy now with Vercel etc. Would be nice to see the large ESM interop merge hit a release as well.

[ayush-seth]

I'm looking forward to that as well for the typescript version upgrade

[zackdotcomputer]

It feels like this should either happen or else this package should be flagged as not maintained? It's misleading to have the package's latest merge be 4 months after the latest publish since it can lead to misdiagnosing issues (e.g. from the Typescript mismatch).

[ctjlewis]

This is basically no longer maintained. I’d use tsmodule and create TS ESM packages instead. See tsmodule convert.