Gökhan Kurt

Added `pool` property to all elements, accepting either boolean or string. This will group similar elements in a pool and recycle elements from that pool instead of creating/destroying them each...

Any hope we can get this feature? I see you closed #13371 that basically solved this issue 3 years ago, and suggested no replacement at all.

@fi3ework any concerns about this?

> Pretty cool. I've tried your solution for Storyblok with field level translation [nextjs13-i18n-storyblok](https://github.com/Robin-Gustafsson/nextjs13-i18n-storyblok) and it's working pretty well until you want to use client. Looking forward to find a...

Implemented all `border`, `border-image`, `background` and similar features using meshes now, instead of shaders. This will improve performance a lot, as well as allow anti-aliasing.

In my opinion, no amount of new CSS features will be enough to replace Sass completely. For me, Sass is more useful for having a modular code structure. It is...

I solved the `TypeError` by adding `"fork-ts-checker-webpack-plugin": "^6.5.3"` to devDependencies, removing node_modules and lock file and reinstalling. If it doesn't work, make sure the correct version of `fork-ts-checker-webpack-plugin` is installed...

I just run into this problem in a Vite project. I read the whole thread and unless I am missing something, no big changes are needed for this to work....

My bad, I just realized that my change fixes the issues with `Bundler` module resolution but not for `NodeNext`. File extensions are required after all.

Sorry for flooding. But there was a simple solution after all. Created PR at #4540 In summary: > The problem was, since the package.json has type: module, Typescript is treating...