Jacob Parker

@joaomoreno are you transforming files, or bundling them? The output generated for esm is pretty regexp-able. I used this to emulate UMD bundles in my [project](https://github.com/jacobp100/technicalc-core/blob/01f639cb3f49db1022f2c0751d0ebedc9d099ad9/packages/technicalc-prebuilt/build.js#L91-L101)

Just a note on this, we're doing layouts on 250,000 nodes. If this was immutable, it would add a lot of GC and memory overhead

Sorry, this is meant to be `.outline`, not `.curve`. I've added a concrete example to demonstrate the bug.

I haven't done it. Are you now getting warnings about needing to explicitly set `true`/`false`?

I can take a look when I have a bit more free time. Or I can take a look at PRs if anyone wants to take a stab at it.

Not officially at least. What would you need this to do to support that?

Sorry, I need to add the types to the project. You can use this though, ```ts declare module 'cssta/native' { type CssConstructor = ( css: TemplateStringsArray, ...values: (string | number...

Thanks for your interest! I’ve got a small refactor on the native side that’ll make use of React hooks, which will make some of the stuff easier to follow. Okay,...

> Is there some added benefit of supporting matching CSS variables during runtime? Do you support inheriting variables? Like a parent sets a variable, and the child uses it?

It can be useful for theming when you have multiple themes. But if you assume they don't inherit, it'll make stuff a lot easier for you, as you'll be able...