clean up the script loader and polyfill situation #346

tilgovi opened this Issue Mar 27, 2013 · 12 comments

4 participants


Right now I have a copy of yepnope.js copied into the embed code template.

Problems with it include:

  • Small number of tests and polyfills. We could do slightly better I bet.
  • The asset bundling is cumbersome.

We should probably remove yepnope in favor of a server-side include of a modernizr build and access the webassets bundles by name more directly from the template, like we do in, rather than passing them all from the embed code view.


Why does this issue have the "mobile" label?


No idea.


This is what I'm thinking these days:


Going to give this another look in relation to #1445 . Yepnope also adds some lag on the FF extension, so I believe its time has come.


@BigBlueHat think you meant #1445.


Yep. He did. 😄


@tilgovi @aron @csillag

To replace yepnope.js, we need:

  • feature detection & conditional script loading?
  • in-order JS asset loading / processing?
  • post-asset-loading call back triggering?

Things are a bit neater with the embed code now, but we should still switch to a module system so we can load everything async or bundle it all. Also, yepnope development has been discontinued.

@tilgovi tilgovi removed the 1 - Ready label Oct 7, 2014

Closed by #1639

@aron aron closed this Nov 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment