Slava

Also, I can confirm that changing ```js ...pre.map((include) => `require(${stringifyRequest(include)});`), `module.exports = require(${stringifyRequest(`!!${remainingRequest}`)});`, ...post.map((include) => `require(${stringifyRequest(include)});`) ``` to ```js ...pre.map((include) => `import(${stringifyRequest(include)});`), `import * as xxx from ${stringifyRequest(`!!${remainingRequest}`)};`, `export default...

I have the same issue with Russian. Any chance to see it fixed?

Oh, sorry, haven't noticed the project is dead...

I think issue #https://github.com/webpack/webpack/issues/4589 is somehow linked to this issue. @zjcf, `require("expose?$!jquery")` works because its resource name is the same as resource name of exposed jquery in dll manifest: ```js...

Workaround, that works for me even with webpack 4 **webpack.vendor.config.js** ``` entry: { "vendor": [ ... "expose-loader?$!expose-loader?jQuery!jquery", ... ] } ``` **webpack.config.js** ``` resolve: { ... alias: { ... "jquery":...

@dmonad Also another issue is that on reconnection we can receive the current awareness state of others (e.g. https://github.com/yjs/y-websocket/blob/master/bin/utils.js#L278-L284). But their clocks could be still the same as we already...

We've finally come up with this style as a workaround: ```ts const { useName } = createEntityAccessor(entityId); const name = useName(); ```

Works for me on the latest master (ab62e58515956a35e54ded9ba55f2e6484b556a1)

And one more question — how to gracefully handle such an exception? I've tried `sub.on('error',...` but unsuccessfully.

Redis's MONITOR is showing `"UNSUBSCRIBE" "some1" "some2"`