Feature Request: Allow executable `script` tags about react

[Minebomber]

I'm not sure I understand. In what cases would a script tag be necessary? Can you provide an example?

I came across this issue as I was developing a JS library intended to be included through a script tag. For non-React projects, a simple <script async src="..." onload="// configure library"></script> works fine. However, when testing compatibility with React I noticed that the script & event handlers never run. This can obviously be solved by running a block in useEffect to run document.createElement('script') and add the source and onload there, but I feel that this should be supported by React out of the box.

[pwbriggs]

I'm not sure I understand. In what cases would a script tag be necessary? Can you provide an example?

[rickhanlonii]

We have support for this in the canary channel, can you try it in the canary to confirm it does what you want?

Here are some in-progress docs we're working on for the feature: https://react-mpvnsvyqg-fbopensource.vercel.app/reference/react-dom/components/script

[Minebomber]

We have support for this in the canary channel, can you try it in the canary to confirm it does what you want?

Here are some in-progress docs we're working on for the feature: https://react-mpvnsvyqg-fbopensource.vercel.app/reference/react-dom/components/script

That's cool that this feature is being worked on. I tried out the latest canary 18.3.0-canary-b2d637128-20240123, and I observed the special rendering where scripts are moved to the head and the script did get loaded. However, I'm still unable to get the onLoad handler to fire. Perhaps I'm not implementing it correctly and need some additional code to get it working.

For example:

<MyApp>
    <script src="https://cdn.tailwindcss.com" onLoad={() => { console.log("Loaded!"); }}></script>
</MyApp>

In this case neither the tailwindcss library nor the onLoad handler get executed.

from react.

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!