Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plans for dependency management in Polymer #2049

Closed
wilzbach opened this issue Jul 8, 2015 · 2 comments
Closed

Plans for dependency management in Polymer #2049

wilzbach opened this issue Jul 8, 2015 · 2 comments

Comments

@wilzbach
Copy link

wilzbach commented Jul 8, 2015

Hey there,

we (the guys from BioJS) are currently working on a policy to be able to migrate all our components to web components. In fact we are super happy about this step as we finally will be able to provide encapsulated, custom html elements than can be used to visualize biological data in a browser and obviously we plan to use the amazing Polymer library :)

However we have been having a discussion over the last days on the dependency management in Polymer. To put it in a nutshell "html imports" are great, but not ideal as they enforce a relative structure on one's code base and can't handle version conflicts. In fact we have been experimenting with using SystemJS as a module loader.

So we would be super happy if you - as Polymer community - could give us an advice of how you plan to deal with dependencies in the future, so that we don't end up forking Polymer to "Biopolymer" ;-)

biojs/biojs3#4

Cheers,
Seb

@dfreedm
Copy link
Member

dfreedm commented Jan 27, 2016

Polymer uses HTML Imports right now, and we have plans to work with ES6 modules when they ship.

@dfreedm dfreedm closed this as completed Jan 27, 2016
@olegomon
Copy link

+1 ES6 Modules

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants