clean up the script loader and polyfill situation #346

Closed
tilgovi opened this Issue Mar 27, 2013 · 12 comments

4 participants

@tilgovi

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 app.pt, rather than passing them all from the embed code view.

@csillag

Why does this issue have the "mobile" label?

@tilgovi

No idea.

@tilgovi

This is what I'm thinking these days: https://github.com/cujojs/curl

@BigBlueHat

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.

@aron

@BigBlueHat think you meant #1445.

@BigBlueHat

Yep. He did. 😄

@BigBlueHat

@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?
@tilgovi
@tilgovi
@tilgovi

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
@aron

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