Jerome Louis

> @jhomarolo why not use [`graphql-scalars` many date related scalars](https://www.graphql-scalars.dev/docs/scalars/date)? There's actually a potential difference of behavior between SSR and CSR when using that: https://github.com/Urigo/graphql-scalars/discussions/957

I don't see why tsc would call eslint-parser tbh. I'm thinking tsc is just loading the babel types for some reason, and that's what causes the GC error. It's gonna...

I noticed that `@babel/types` was an indirect dependency of `jest`: ``` └─┬ [email protected] └─┬ @jest/[email protected] ├─┬ [email protected] │ └─┬ [email protected] │ ├─┬ @types/[email protected] │ │ ├── @babel/[email protected] deduped │ │...

Looks like those types are coming from [here](https://github.com/floating-ui/floating-ui/blob/v2.x/src/types.js#L135), which was [fixed a few months ago](https://github.com/floating-ui/floating-ui/commit/593aefe2d558efe586367ed31d7586da249b70e5).

So maybe updating `@popperjs/core` to the latest v2 minor would do the trick?

Just an idea, but even though there is still no support for `event.key` on Safari (although hopefully coming soon), we might be able to use that instead of `event.keyCode` to...

Here is a branch where you can reproduce the issues: https://github.com/jlowcs/webpack-babel-multi-target-plugin/tree/bug-ContextReplacementPlugin When using `BabelMultiTargetPlugin`, 2 plugin chunks (well, 4 if you count the modern files) are generated by the `es6-dynamic-import`...

I'm still experiencing this issue on 2.1.5. It's adding a lot of noise in the console and in the terminal when building with webpack.

I'm seeing these on my end: ``` ● Validation Warning: Unknown option "coverageReporters" with value ["lcovonly", "html", "json-summary", "json", "text"] was found. This is probably a typing mistake. Fixing it...

That is something I might need. Any reason this hasn't been merged into master?