It might not expect that we're already within `<script>` scope
It might not expect that we're already within
<script>scope