Inconsistent behavior for <script> tags in livewire components

[dorgan]

Livewire version

4.1.4

Laravel version

12.51.0

Which PHP version are you using?

PHP 8.2

What is the problem?

<script> tags inside of livewire component not wrapped in @script/@endscript work locally on mac with herd, but when deployed to ubuntu environment fail with a "Livewire only supports one HTML element per component. Multiple root elements detected for component: XXXX" error ### Code snippets ```blade

<script> alert('test') </script>?

```

How do you expect it to work?

Should be consistent across platforms

Please confirm (incomplete submissions will not be addressed)

• I have provided easy and step-by-step instructions to reproduce the bug.
• I have provided code samples as text and NOT images.
• I understand my bug report will be removed if I haven't met the criteria above.

[joshhanley]

@dorgan thanks for reporting this! I suspect this is caused by differences in the libxml2 library version between your two environments. Livewire uses DOMDocument::loadHTML() (which depends on libxml2) to count root elements, and older libxml2 versions are known to parse <script> tag content inconsistently.

Could you check the following on both your macOS and Ubuntu environments and paste the results here?

PHP and libxml2 versions:

php -r "echo 'PHP: ' . PHP_VERSION . PHP_EOL . 'libxml2: ' . LIBXML_DOTTED_VERSION . PHP_EOL;"

Also, is APP_DEBUG=true on both environments? This check only runs when debug mode is enabled, so if it's false on macOS but true on Ubuntu, that alone would explain the difference.

Finally, could you share the actual component template that's triggering the error? Your example shows the <script> tag nested inside the <div> — I'd like to confirm whether your real component has it nested inside the root element or as a sibling alongside it.

[dorgan]

I'll get your the version numbers when I am back in front of the computer tomorrow. But I can confirm the the script tag is not a sibling of the root element and is inside the root dig. The reason I know this is because it originally was a sibling and I moved it inside as I thought that might have been the initial issue. And yes APP_DEBUG=true on both local and dev environment.

[dorgan]

@joshhanley sorry for the delay in getting back to you on this:

Local Dev (Mac)
PHP: 8.2.30
libxml2: 2.15.1

Remove Dev (Ubuntu)
PHP: 8.2.30
libxml2: 2.9.14

[joshhanley]

@dorgan thanks for confirming! That libxml2 difference is likely the cause (2.15 vs 2.9). I've submitted PR #10055 with a fix.

In the meantime, setting APP_DEBUG=false on your Ubuntu environment will avoid the error.