Original issue in Nuxt.js repository:

• esm() breaks console.*() functions in esm-styled nuxt.config.js · Issue #6808 · nuxt/nuxt.js

Currently we have the following tests:

[esm/compiler-tests.mjs at a3b8290074ccd2a708ed9b985a2f89d4f4cdd026 · standard-things/esm](https://github.com/standard-things/esm/blob/a3b8290074ccd2a708ed9b985a2f89d4f4c

Requested Update

I was asked today if there was a tool to check if the transpiled code was ES5 and I referred to this project but I just checked and es-check es5 ... does not catch Promise from ES2015.

Why Is This Update Needed?

The reason I was asked is that they have continuous issues with bug reports because they forget to add polyfills to their projects. They need an automated w

In order to improve the startup-time, both the modV & dekk integrations should not start automatically, but if someone actually wants them to run.

Decide whether to ship ES6 or ESnext typescript target.

ES6:

• Widely supported

• Ugly ts hacks generated
• Bundle size is larger than for esnext

ESNext:

• Readable source code

• Not yet fully supported