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
{{ message }}
This repository has been archived by the owner on Jun 3, 2022. It is now read-only.
Remixer has a few dependencies in the iframe overlay, such as Firebase, MDL, and React. They are pulled in via running npm install. However this makes using remixer in online tools such as codepen difficult, as you cannot simply import remixer by itself, and instead need to include all the dependencies.
As a suggestion, lets consider instead pulling in these dependencies via their recommended hosted CDNs from within the iframe.
We don't need to worry about performance here, as the iframe loads in background not needed immediately at page startup.
I know Michael (who runs unpkg) and trust him to be a good person. I've run plenty of code he's written. Still, I'm wary to recommend that people load code from servers we don't control (and hence, can't vouch for the security of).
It's probably fine (React even links to that URL from their homepage), but it's still something I'm wary of as a Googler.
What's the bundle size difference between including these and externalizing them?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Remixer has a few dependencies in the iframe overlay, such as Firebase, MDL, and React. They are pulled in via running
npm install
. However this makes using remixer in online tools such as codepen difficult, as you cannot simply import remixer by itself, and instead need to include all the dependencies.As a suggestion, lets consider instead pulling in these dependencies via their recommended hosted CDNs from within the iframe.
We don't need to worry about performance here, as the iframe loads in background not needed immediately at page startup.
For reference, the iframe calling code is here.
Suggested CDNs:
The text was updated successfully, but these errors were encountered: