Frederik Buchlák

For easier implementation I'm waiting for [1462](https://github.com/oxc-project/oxc/issues/1462) with this.

Hi @talyz @Misterio77 Don't want to necrobump, but is there something except minor comments blocking this PR? This feature would be handy.

Sure, nevermind. I've tried to create html injections for this, but without split grammar it seemed impossible. My initial idea was to modify attribute value in injection by adding curly...

I've ended up with injecting javascript for those component attributes. It's not perfect and might be confusing, but it's better than nothing. At least for basic highlighting. "solution" ```scm ;...

If you need to use 3.* version with leaflet-routing-machine, you can make geocoder compatible with this simple hack ```js function RoutingMachineGeocoder(geocoder) { const geocode = geocoder.geocode; if ('AsyncFunction' === geocode[Symbol.toStringTag])...

I've encountered similar issue. In my case I'm using twig components as much as possible to create reusable components for things like buttons, tags, etc. In real application (in dev...

> There is a new configuration option to disable the TwigComponent profiler, could you test ? > > ```yaml > twig_component: > profiler: false > ``` This resolves the issue...

Sure, I will test it. Just one question. Without live components you mean removing ux-live-component package from the application? Components I render in this scenario are neither live components or...

Sorry for the delayed response @smnandre I've tested it today (avg 10 runs with 440 twig components used) 1. twig components + live components (installed, not used) with profiler enabled...