-
-
**Proposal** we only support esm (import only, no require)?
Argument:
- CJS is probably gonna die (esm can use cjs easy, not the other way)
- use of the sdk is already async (`entropy.ready`)
- …
-
## 🐛 Bug Report
```js
import t from './file';
import d from './directory/'
```
These should both fail to resolve, but since we use the same resolver as for CJS, it doesn't, and the import wil…
-
- `getCommonOptions`:
```ts
const getCommonOptions = () => {
// ...
platform: 'browser', // 'node' | browser | neutral,
format: 'esm',
}
```
- `build`:
```ts
const buildSwr =…
-
### Current behavior
When a plugin fails for some reason (in this case it is [semantic-release-backmerge](https://github.com/kilianpaquier/semantic-release-backmerge)) it seems semantic-release has…
-
Would very much like to just simply use (async) import from a CDN without bundling the code
-
During the build, the following error may occur:
ERROR [nitro] [unhandledRejection] Cannot destructure property 'usingNuxtContent' of 'useRuntimeConfig(...).nuxt-robots' as it is undefined.
at …
-
While the generator binary can still use CJS, it should be possible to setup generator to emit consumable ESM module including the generated types and resolvers.
The scope of the changes:
- change…
-
### Describe the bug
When bundling WebWorkers in the `es` format, all the modules imported by the worker are inlined inside the worker chunk and no import syntax is used.
In the following reproduc…
-
In my yaml, a `job` as follows.
```
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v2
- name: Use Node.js 20
…