public vs. private component specs

[jonathanong]

there are different rules for public and private components, but right now the spec doesn't distinguish between them. for example repo and version are not required for local components, and local and paths is not allowed for public components.

[tj]

yeah good call, definitely worth mentioning. I wouldn't put toooo much work into the spec though because we're going to need a massive overhaul for all the ES6/web component stuff

[jonathanong]

i think you're a little optimistic on es6 stuff. it won't be finalized until the end of next year. who knows how long microsoft is going to take to implement it, but we'd have to wait until a majority of browsers support it anyways. safari 5.1 was released more than 2 years ago, but there are still more 5.1 users than 6, 6.1, and 7 according to stat counter.

either way, it's only JS, and we still need better specs for CSS and stuff.

[jonathanong]

i'm thinking a "es6": true flag in the component.json file and compiling down to CJS until we can move everything to es6 modules.

[tj]

definitely, but it will happen sooner or later, and once more and more things get added the polyfills will be less crazy and possibly usable haha, just trying to think about the end goal

[tj]

just like if node doesn't go ahead and adopt ES6 modules it will eventually be clobbered by something that does, just a matter of time