-
Notifications
You must be signed in to change notification settings - Fork 200
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
Comments
ghost
assigned sjmiles
Aug 12, 2013
This is a bigger change than just in tools, as |
Thanks @azakus. We really appreciate your help trying to resolve the naming conflicts :) |
|
Amazing, thanks so much for pushing this through. |
rictic
added a commit
that referenced
this issue
Apr 7, 2018
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
…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
bicknellr
pushed a commit
that referenced
this issue
Apr 9, 2018
pull polymer workspaces logic into a standalone package
aomarks
added a commit
that referenced
this issue
Apr 12, 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
Closed
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.The text was updated successfully, but these errors were encountered: