Doma
Closing due to conflicts
@WhiteYin 博主这种博客模式推荐使用 hexo + gitment
Any update on this? Agree that it should not report positive on SFCs that have explicit names - which is almost every component in 2022. ```jsx function DontComplainAboutMyName() { return...
> it doesn’t report on those, as far as I’m aware. Oops, turns out it was reporting anonymous arrow function components wrapped with `forwardRef`. My mistake.
Hi @PrinOrange, could you show me your `postcss-loader`/`postcss` options and versions?
Looks like it's an [issue within `customize-cra`](https://github.com/arackaf/customize-cra/issues/315). Consider replacing it with tools like `craco`. We may also have to update our documentation.
> Same problem I encountered. Latest version of customize-cra and less-loader were installed. See if [this solution](https://github.com/arackaf/customize-cra/issues/315#issuecomment-1017081592) works.
> is it related? Not really. That warning is due to react-virtualized, one of our dependency package that has been incompatible with react 18 until recently.
> we need to consider a lighter-weight solution to replace it Some users have switched to [virtuoso](https://github.com/petyosi/react-virtuoso) according to [this comment](https://github.com/bvaughn/react-virtualized/pull/1656#issuecomment-1095018609). However react-virtualized seems to be looking for a new...
Would appreciate it if you could help make it as good as the alternative you like to use then.