I’m not sure what’s going on, but while trying to eliminate the Blaze package from my React codebase (which can be super tricky when you have a lot of packages by the way, since there’s no way to find out which one is depending on it) I narrowed it down to accounts-twitter.
Looking at the code it looks like it depends on accounts-base, which itself has a weak dependency on templating. Now the weird part is that having accounts-base in my codebase doesn’t cause Blaze to be loaded, but adding accounts-twitter does…?
Oh, good find! So does that mean there’s a bunch of React apps with Twitter log-in out there that still include Blaze for no good reason? That seems like it could be a pretty big issue in terms of loading speed.
Unfortunately yes - and it looks like the dependency on Blaze is just needed to show the login service configuration dialog. Sounds like PR time! (for someone else that is … my caffeine levels are dangerously low today; I’d end up replacing the Blaze dependency with Spark …)
My project is pulling in Blaze (and thus jQuery) and the only thing I can trace it back to is accounts-base. You sure it was just twitter pulling in Blaze? How about accounts-facebook and accounts-google?
Edit: Removed static-html as it depends on templating. No change though…
firstname.lastname@example.org # Packages every Meteor app needs to have
#email@example.com # Packages for a great mobile UX
firstname.lastname@example.org # The database Meteor supports right now
email@example.com # Reactive variable for tracker
firstname.lastname@example.org # Meteor's client-side reactive programming library
email@example.com # JS minifier run for production mode
firstname.lastname@example.org # ECMAScript 5 compatibility for older browsers.
email@example.com # Enable ECMAScript2015+ syntax in app code