Sergey Zwezdin

@jgarth It would be useful to validate not `/*`, but objects that were really changed.

As for `` — it is not related to `AutoSizer`, the problem is actually here — https://github.com/bvaughn/react-virtualized/blob/e360d958b99fa965fd3f1caed4506403ad652cd3/source/Table/Table.js#L342 Waiting contributors to fix this - #1353

Not sure, why need `findDOMNode()` here if we already have ref there? https://github.com/bvaughn/react-virtualized/blob/e360d958b99fa965fd3f1caed4506403ad652cd3/source/Table/Table.js#L342

Hm, seems it's related to #567 @christianalfoni @grandevel @MaxSpiro Did you guys have a chance to look into this?

It is not - https://github.com/Resembli/react-virtualized-window/blob/main/packages/react-virtualized-window/package.json#L43-L45

@SukkaW Maybe it's possible to release npm themes support before of Hexo 5? I'd like to have it without waiting for next release of Hexo.

@SukkaW any update on this?

@SukkaW Could you give me a bit more context about it, so maybe I can help? I'd like to share the theme between two my websites, but don't want to...

@SukkaW Why complicated? It looks quite logically to me. 1. If you use regular theme (without `@scope`), we'll just trying to search it as `/node_modules/hexo-theme-`. 2. If you use @scoped-theme...

So the only change we need to introduce into the code that you mentioned above is to check having `@scope` in theme name, and adjust path a bit.