Priyajeet Hora

I do notice that once the babel-loader is removed from the webpack rules, then tree shaking happens fine. But unfortunately you need that loader, for say React etc.

Currently I am working around this issue by using the webpack string replace loader as follows: ``` javascript preLoaders: [ { test: js, loader: StringReplacePlugin.replace({ replacements: [ { pattern: /\_\_\(`(.*?)\`\)/ig,...

Another thing that should be done is to run this plugin as a loader (quite like the StringReplacePlugin allows), so that it can be run before the babel loader. Then...

@addula Unfortunately we only support these two scenerios right now: 1] If you are a React app that can import our react components directly using ES2015 syntax, use UI Elements...

I am having an issue with this too. But mostly when using React 18 / react-testing-library v13.3 for unit testing via a memory router. The same unit test worked fine...

Also want to echo what @mastercactapus mentioned about the warning and silently preventing a navigate. Not sure what was the reasoning behind this as it is hard to decipher what...

Thanks for the PR @42shadow42. Removal of the flag helps! But the warning will likely come back, if the child component also uses useLayoutEffect() to trigger the navigate for whatever...

BTW @42shadow42 probably should change the git commit message to say `fix:...` so that release bot knows it is a patch release fix. Unless ofc someone else needs to do...

BTW there is a possibility this issue applies to multi-selection. Trying to see when it broke, likely when we switched to paging.

In order to properly fix this, and frankly make it less confusing, we may have to get rid of the reference mutations and keep selected isolated from currentCollection.items. I am...