Burton
Burton
I hit this in Node 16.14.0 and 16.16.0. However, 16.13 appears to work as expected.
I recently prototyped such a component: https://codesandbox.io/s/pbh-date-selector-7cblk
So then I would pin all my services to avoid having to expand the tree in the future? Sounds like that would solve the particular UX problem we have but...
I'm experiencing this as well in v16.14+ v16.13 seems to work as expected.
I hit this issue on node v16.14.0 and v16.16.0. However, it works fine on v16.13.1. Is anyone looking into this?
Is there a bigger study on this topic? I tested the map change on an array containing 113,267 strings. The perf was measurably worse than the built in map.
Our team is using ag-grid enterprise to view up to 64mb of log data. Web worker support and other perf improvements would be very much appreciated 😄
> Regardless, I think a prerequisite for a maven plugin would be adding an IDE hook similar to the [one available for Spotless Gradle](https://github.com/diffplug/spotless/blob/main/plugin-gradle/IDE_HOOK.md). Is there any particular reason that...
This has been fixed in in Vite 5 per https://github.com/vitejs/vite/issues/13234#issuecomment-1797847644 Unfortunately Vite does not provide instructions on how to upgrade versions so I just used [npm-check-updates](https://www.npmjs.com/package/npm-check-updates#interactive-mode): ```console npx npm-check-updates -i...
Looks great - thanks for fixing this! Any eta as to when this will be merged?