You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks to me like browser-sync is looking for the first > char, right after <body to inject the script tag — but I could be wrong. And as you can see, when using Stimilus and using the <body> element as a Stimulus controller, it can cause some issues.
Steps to reproduce/test case
Set up a simple 11ty website
Add an attribute to the body tag such as data-action="access:notify->notification#show" — I believe you can avoid setting up Stimulus altogether
Witness the body tag get messed up as follows:
Source:
Issue details
So, I'm using 11ty, which comes bundled with browser-sync by default.
All good so far.
But I'm also using Stimulus, which relies on a specific syntax to set actions: https://stimulus.hotwired.dev/reference/actions
It looks to me like browser-sync is looking for the first
>
char, right after<body
to inject the script tag — but I could be wrong. And as you can see, when using Stimilus and using the<body>
element as a Stimulus controller, it can cause some issues.Steps to reproduce/test case
data-action="access:notify->notification#show"
— I believe you can avoid setting up Stimulus altogetherSource:
Please specify which version of Browsersync, node and npm you're running
Affected platforms
Browsersync use-case
for all other use-cases, (gulp, grunt etc), please show us exactly how you're using Browsersync
{Browsersync init code here}
The text was updated successfully, but these errors were encountered: