Tony Brix

Sure, it looks like vite uses rollup anyways so I don't see the point in adding a new layer. But if you create a PR we can see what the...

If it can reduces the size of the npm package I think it would be worth it. The gzip size grew dramatically after switching to typescript. Mainly because we now...

Option 1 is already available for your project. You can use Babel to compile marked to whatever version of es you need. We decided to drop support a while ago...

> Do you have relevant data supporting the conclusion that the ES5 version of 'marked' is 30% slower than the ESNext version? No, I encourage you to test it yourself....

@jjblumenfeld you can use [babel](https://babeljs.io/) to transpile the code you send to your users if you need to support older browsers. You may need to tell it to transpile node_modules...

Before #3103 and if we merge this PR the type retuned be marked.parse could be wrong. If you are ok with not knowing the correct return type, just don't use...

The first one will also break at runtime with this PR and before #3103

So I think the only solution to not break at runtime if the developer doesn't know if they added an async extension is to leave it the way it is...

If the developer does know that they didn't add an async extension than `as string` seems to be the cleanest solution to me.

If this was complete we could merge it in the next major version. A couple of things that need to be fixed: - throw an error instead of warn when...