Geoffrey Booth

@bengl Actually I need to be more specific. The new flag was supposed to enable the import of extensionless _ES modules._ In normal `node` without using the new flag, import...

CommonJS doesn’t have a way to represent the “default plus named exports” feature of ES modules. The `__esModule` pattern that Babel and TypeScript use is meant to provide a workaround,...

Something worth considering is whether it might actually be okay to ship different builds to different targets for bundlers. For Node it’s an issue to ship a different instance for...

> To avoid that, we'd need to separate the import & require versions. But that's my point: if you separate them, does it fix the issue for bundlers? I would...

> bundlers support passing an ESM version to `require` but then `require( "jquery" )` returns `{ default: jQuery, $: jQuery, jQuery: jQuery }` What if the CommonJS version that bundlers...

For anyone else using Amazon S3 who wants paths without trailing slashes, I found a workaround: - In your `src/routes/+layout.js` file, add `export const trailingSlash = 'never'`. This will cause...

> So I guess specifically I disagree with two claims that @GeoffreyBooth makes: My point is that most websites don't have paths that end in slashes, and such URLs look...

https://www.typescriptlang.org/docs/handbook/esm-node.html recommends including the `.js` in the `import` statement within TypeScript files intended for running as ESM in Node. Isn’t the solution here to just update the TypeScript files for...

> Here is the guy who found the “fix” That’s not Joyee’s pronoun. Also, while `--experimental-require-module` is great, I’m not sure what it has to do with the request on...

Someone just triggered a fresh CI job on a PR of mine that had a passing CI, that I was waiting for the time limit to expire in order to...