solimant

@PJ-CM - your solution works because you've explicitly configured `output.path`. If you remove it, `clean-webpack-plugin` will fail to clean up things. @evpaassen - the behavior is consistent with any kind...

It is worth mentioning that beginning Webpack 5.20.0+, there is an [`output.clean`](https://webpack.js.org/configuration/output/#outputclean) option that cleans the output directory before emit: ```js module.exports = { //... output: { clean: true, //...

@PJ-CM - if you're on Webpack 5.20.0+, yes, at least for basic clean-up needs, in my opinion.

Probably similar? `Bug.test.tsx` ```tsx import styled from "styled-components"; import React from "react"; import {mount} from "enzyme"; import 'jest-styled-components'; const Foo = () => ( Bar ); const StyledFoo = styled(Foo)`...

Working on it

> This is more a general question, do we want it to be the first thing that Tab lands on when you open the page? It seems to make sense...

> Pretty nice, seems to work well! I'm happy for this to go in as is, just gonna list some things that I noted/future work perhaps that can be done....

> @solimant @LFDanLu I did find this https://www.algolia.com/doc/ui-libraries/autocomplete/guides/creating-a-renderer/ > so this might be something we could do in the future to handle the complete rendering ourselves @snowystinger - From what...

> @solimant I agree with @snowystinger that the default Algolia search results have accessibility problems, for example each returned result in the listbox is announced as `"Link to the result"`...

> Looks like their docsearch uses this API client under the hood: https://www.npmjs.com/package/algoliasearch. IMO it would be better if we used our own components for this. We put a lot...