Not sure if this is the best approach to "silencing" <script> tags, but my vote would go to removing them from templates altogether and this is what this PR does.

Hi,

I understand the need for the script removal but we all know that at some point someone will put a tag script in a template and report this a bug. And I can see a use for it (if you want to load jquery plugin in that component, you can either do it via import * from "libs/myjqueryplugin" or add a tag script on the template.

@pkozlowski-opensource can you consider printing a warning message to the console, when in dev mode, to at least warn the developer about the removal of the script tags? (or give a compile error)

And I can see a use for it (if you want to load jquery plugin in that component, you can either do it via import * from "libs/myjqueryplugin" or add a tag script on the template.

Using <script> tags as a loader is the very thing we want to avoid here. With ES6 modules you can pull dependencies via import so there is not much reason in enabling inferior mechanism that has negative security implications

can you consider printing a warning message to the console, when in dev mode, to at least warn the developer about the removal of the script tags? (or give a compile error)

I don't think we've got good story for warning messages, so if anything, I would throw. Let's see what others got to say.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}