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

window.Loader name conflict #1

Closed
guybedford opened this issue Aug 8, 2013 · 4 comments
Closed

window.Loader name conflict #1

guybedford opened this issue Aug 8, 2013 · 4 comments

Comments

@guybedford
Copy link

I just ran into this when trying to implement the ES6 module loader polyfill (https://github.com/ModuleLoader/es6-module-loader) in a project alongside Polymer.

window.Loader is currently in the ES6 module specification as the native loader global. Since Polymer is aiming to sit in the same sort of timescale as these implementations, ideally it would use another global name for the loader.

@ghost ghost assigned sjmiles Aug 12, 2013
@dfreedm
Copy link
Member

dfreedm commented Aug 12, 2013

This is a bigger change than just in tools, as Loader is used all over. Tracking in Polymer/polymer#237

@addyosmani
Copy link
Member

Thanks @azakus. We really appreciate your help trying to resolve the naming conflicts :)

@dfreedm
Copy link
Member

dfreedm commented Sep 9, 2013

window.PolymerLoader has replaced window.Loader

@dfreedm dfreedm closed this as completed Sep 9, 2013
@guybedford
Copy link
Author

Amazing, thanks so much for pushing this through.

rictic added a commit that referenced this issue Apr 7, 2018
* Fix the build.

It looks like the node v4 typings don't include definitions for `console` anymore? Seems like a bug, but moving to node v6 typings fixes.

* Use an explicit default value for FSUrlLoader's root
rictic pushed a commit that referenced this issue Apr 7, 2018
Adds npm install snippet, minor formatting changes.
rictic pushed a commit that referenced this issue Apr 7, 2018
Initial move from polymer-cli
rictic pushed a commit that referenced this issue Apr 7, 2018
…found (#276)

* add a (failing) test case for https://github.com/Polymer/polymer-cli/issues/936

* ensure the build fails when more than one source file is missing

The 'analyze' phase of the build process completes when all source files are analyzed (scanned). A source file is analized when all its dependencies are resolved or rejected. When the sources stream is complete, _all_ pending source file promises need to be rejected--not only the first one. If some of the deferred dependencies remain pending, the analysis of the toplevel source file never continues after 'await this._cache.dependencyGraph.whenReady(resolvedUrl);'. That leads of a premature end of the analysis phase (without any errors).

* update CHANGELOG

* add test for lazy-import with broken path (#1)

add a test case to verify that this PR also fixes the issue https://github.com/Polymer/polymer-cli/issues/904
rictic pushed a commit that referenced this issue Apr 7, 2018
justinfagnani added a commit that referenced this issue Apr 8, 2018
bicknellr pushed a commit that referenced this issue Apr 9, 2018
pull polymer workspaces logic into a standalone package
justinfagnani added a commit that referenced this issue Apr 10, 2018
usergenic pushed a commit that referenced this issue Apr 13, 2018
Simplify events (less runner/mocha centric)
usergenic pushed a commit that referenced this issue Jun 7, 2018
* convert to typescript

* Add a TODO to convert this library to use promises
justinfagnani added a commit that referenced this issue Jul 10, 2018
Rough version of html2js with import and exports rewriting
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

4 participants