How about this: href for URLs. mref to resolve URLs through the module system. package.json and registry and all.
@jrburke I have concerns about HTML imports and module interaction @kriskowal
-
-
@wycats@kriskowal yup. Wanted just a custom resolver js API at very least, but happy for it to just to be delegated to es module loader -
@jrburke@wycats@kriskowal but I also don’t like the idea of loading a ES Loader hammer: JS, CSS, fonts, etc. i.e. https://github.com/jrburke/requirejs/wiki/Plugins … -
@ericf would be good to know of other options. hrefid, srcid may be a good one@wycats@kriskowal -
@jrburke a good bundling solution would go a long way (we made progress at the last TAG)@ericf@kriskowal -
@wycats hmm, bundling seems separate from specifying deps@ericf@kriskowal
End of conversation
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wycats at very least, an html-only import mechanism that mandates usage of urls is so 1999. script tags all over again.@kriskowal -
@jrburke been messing with polymer and html imports, everything is much simpler when its html, no opinion yet though@wycats@kriskowal -
@ryanflorence once there are pkg managers to install custom elements w/ nested custom element deps, urls will break down@wycats@kriskowal
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.