-
Notifications
You must be signed in to change notification settings - Fork 48
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
Resolve <link rel="import" href=...> as module import? #82
Comments
For a URL, Thankfully webpack has a special syntax to escape that: |
Missed the last part:
Using the |
Thanks!
In my previous setup (just using modules) i had Webpack setup so that import URLs were resolved not only against the And now that i got Webpack excerpt:
|
Sorry if i'm overlooking something but I've been trying to get my head around this for 2 days.
So i got the basic Polymer+Webpack setup working for the Starter kit.
Now i'm working on my own element.
My file structure is roughly as follows:
I have a simple
index.html
as the Webpack entrypoint. This includes my-special-icon component, which just displays a polymer icon.public
is my ouput folder.my-special-icon.html
has<link rel="import" href="../../../bower_components/iron-icons/maps-icons.html">
and then places the icon<iron-icon icon="maps:directions-bus"></iron-icon>
.My question, do i really need that 'ugly'
<link>
url?Can i not have Webpack look up the
'iron-icons/maps-icons.html'
like i can with my javascript imports?And can i have
index.html
just contain a<link rel="import" href="my-special-icon/my-special-icon.html">
and have Webpack lookup the correct url in mycomponents
folder?It works fine like it is now, but i can see it becoming a hassle when i start linking to my own elements, or moving stuff around in development stage.
The text was updated successfully, but these errors were encountered: