Jayson Harshbarger

@greenify, If I understand correctly the four options above are regarding html imports. But html imports is not a necessity of web components. From https://hacks.mozilla.org/2015/06/the-state-of-web-components/: > We’ve been working with...

@greenify we are working on the same thing. SystemJS knows where the modules are based on the System.config.js. Using jspm this is automatic. `jspm install d3=github:github:mbostock/[email protected]` then in the module...

It is additionally complicated if you want to use bundling. SystemJS builder won't bundle into html files.

Here is one way to bootstrap a Web Component using SystemJS: http://plnkr.co/edit/w3L3FB I used commonjs because I couldn't get traceur working in plunker.

Thanks. Here is one more demo before I call it a night: http://plnkr.co/edit/JJp6jp Here I made a dumb systemjs plugin to do the HTML importing. This allows you to use...

FYI... https://github.com/Hypercubed/systemjs-plugin-html

You are correct. Bundling wont work. The css plugin has it's own mechanism for bundling that I did not implement. The inline css and js are NOT processed at all...

Found this... https://github.com/nevir/html-exports/tree/master/dist/sysjs-plugin Haven't had a chance to look in detail.

For me, as a potential BioJS3 module consumer, I am happy using jspm/SystemJS/ES6. I think, however, npm/Browserify/CommonJS has more traction currently and may be more familiar to BioJS2 users and...

@herkulano I don't think we want to be using the System.import directly, this wont work for bundling. I took your plunker and added and es6 module, a generated (by hand)...