John Hunter

The way I resolved it was to add `postcss` as a top level dependency. I've since upgraded to `[email protected]`. Just checked now and removing the `postcss` top level dependency has...

I have the following and it works: ``` new OptimizeCssAssetsPlugin({ cssProcessorPluginOptions: { preset: ['default', { discardComments: { removeAll: true } }], } }); ``` The settings are for the default...

Still working for me. My full plugin config is: ``` new OptimizeCssAssetsPlugin({ cssProcessorPluginOptions: { assetNameRegExp: /\.css$/g, preset: ['default', { discardComments: { removeAll: true } }], } }); ``` Plugin version...

@clovisp your/our issue is due to poor UX in the MacOS file picker. See the screen recording in #1191 for the aha moment 🙂

I'm seeing the same thing with `[email protected]` The new default "modern" timer mocking works as expected. However asserting `expect(setTimeout).toHaveBeenCalled...` reports the `[Function setTimeout]` as stated by @s100 Reverting to the...

@Smrtnyk That fits with what I'm seeing. If modern timers are not going to conform to the mock signature then the documentation should be updated to reflect it. The Timer...

As of jest 29 legacy timers no longer seem to work. Did I miss that in the release notes? ``` jest.useFakeTimers('legacy') ... console.log(setTimeout.mock.calls); // -> undefined ```

> As of jest 29 legacy timers no longer seem to work. Did I miss that in the release notes? So adding a separate spy to the non-legacy fake timer...

I wonder if there has been change on the drag event handling were the component returns a [`DataTransferItem`](https://developer.mozilla.org/en-US/docs/Web/API/DataTransferItem) rather than a `File`. Would be worth checking if the validator argument...

Similar issue with [`role="row"`](https://www.w3.org/TR/wai-aria-1.1/#row) which is equivalent to an HTML `` element.