generate appropriate packages/ paths for entrypoints nested within web/ or example/ #17596
Comments
|
Added 1.5 label. |
|
Removed this from the 1.5 milestone. |
|
This requires also a fix in code_transformers/lib/assets.dart and how we allow resolving packages. |
|
This comment was originally written by robert.w.ha...@gmail.com I experienced this as well. But for me there was a packages ordner with just the "browser"-package in it, but nothing else. Cool this might get fixed soon! :) I had the problem with using the polymer package. |
|
Added Pkg-Polymer label. |
|
Removed Pkg-Polymer label. |
|
Removed Library-PolymerBuild label. |
|
Removed Area-Polymer label. |
|
Removed this from the Polymer0.10 milestone. |
|
Customer request to address in the 1.6 build. Happy to provide more context. Thanks! Removed Priority-Medium label. |
|
This comment was originally written by @zoechi I think this is also related to https://code.google.com/p/dart/issues/detail?id=16947 |
|
Added C8 label. |
|
Removed this from the 1.6 milestone. |
|
Removed Polymer-P-1 label. |
|
Added PolymerMilestone-Next label. |
|
Removed Polymer-Milestone-Next label. |
|
Added this to the 1.6 milestone. |
sigmundch
added
Type-Defect
P1
|
This issue has been moved to dart-archive/polymer-dart#381. |
Our code generation logic assumes that there is a packages/ folder next to the entrypoint. But pub-build will only have one next to the top-level folder (web/ or example/).
Code generated in example/a/b/c.html, should have references to the polyfills like this:
<html><head>
<script src="../../packages/shadow_dom/shadow_dom.debug.js"></script>
<script src="../../packages/custom_element/custom-elements.debug.js"></script>
<script src="../../packages/browser/interop.js"></script>
The text was updated successfully, but these errors were encountered: