Closed Buslowicz closed 7 years ago
once this goes in, i will update the version and push another release/tag for tslib@1.3
.
how do you want to handle the registration update?
I will also update the readme before that for steps for bower users.
About the html files, that is actually the key for HTML5 imports (which is base for libraries like Polymer). Without it, any component that would require tslib, would reimport it over and over again. With these, they are imported just once. They do not need to be updated, so I don't see the reason why not to keep them. I am aware that HTML Imports spec is not going to get implemented everywhere with current shape (for now work natively in Chrome and Opera), but there will be HTML Modules which will probably work similar and probably use ES6 modules under the hood. Until that is finished, HTML Imports are easy to polyfill and will be used in Web Component based libraries and Frameworks.
As for bower registration update, I asked a question on bower github if there is a secure way of transfering the repo. We could wait a bit more for their solution. More info here: https://github.com/bower/bower/issues/2407.
Adding bower support and HTML5 importable modules (#15).