Note that there's basically nothing about switching from HTML imports to JS modules involved here. Both only support URLs as imports natively. It's really the switch from Bower to npm, and from custom to standard tools, that necessitated the change to use package names.
On Thu, Sep 12, 2019, 1:46 AM Max Waterman <[email protected]> wrote: > That helps a lot, thanks. The open-wc.org web site is especially > interesting. > > I'm glad that the value of build-less development is not lost on those > working on 'the platform'. I find myself wondering if the dropping of html > imports was done a bit too soon, but I guess it's really more like the > alternatives are taking too long to arrive to replace them. > > Anyway, thanks. > > Regards, > > Max. > > On Thu, 12 Sep 2019, at 12:37 AM, Justin Fagnani wrote: > > When we moved to npm we needed a way for modules to reference each > > other, and unlike with Bower where all packages are siblings of each > > other, there's no stable relative URL that we could use for this. The > > overwhelming community pattern on npm is to use package names for > > cross-package references and a tool (or Node) to resolve them. So we > > went with the community standard and used package names, knowing that > > there are a plethora of tools that can resolve ment, and that future > > browser standards like import maps will support package name resolution > > directly in the browser. > > > > Until import-maps land, you can use a number of tools: > > * `polymer serve` will automatically resolve bare specifiers on the > > fly. > > * open-wc.org tooling will as well > > * Bundlers like Rollup, Parcel, and Webpack will resolve names. Rollup > > with the rollup-node-resolve plugin. > > > > Hope that helps! > > > > On Tue, Sep 10, 2019 at 10:51 PM Max Waterman > > <[email protected]> wrote: > > > Hi, > > > > > > Is there a way to use a polymer element in a project without having a > build step - neither one I run manually (eg polymer build), or > automatically (eg polymer serve)? > > > > > > I recently attempted this, but it seemed like I needed to have some > import paths converted, and so I needed to use 'polymer serve'. > > > > > > I don't recall needing any such step with the older versions of > polymer - I just added an html import, and used the element. Perhaps I'm > mis-remembering. > > > > > > Is there a way to avoid any build step? > > > > > > Regards, > > > > > > Max. > > > > > Follow Polymer on Google+: plus.google.com/107187849809354688692 > > > --- > > > You received this message because you are subscribed to the Google > Groups "Polymer" group. > > > To unsubscribe from this group and stop receiving emails from it, > send an email to [email protected]. > > > To view this discussion on the web visit > https://groups.google.com/d/msgid/polymer-dev/d725e36a-04b7-4d0a-8974-571d8336bff1%40googlegroups.com > < > https://groups.google.com/d/msgid/polymer-dev/d725e36a-04b7-4d0a-8974-571d8336bff1%40googlegroups.com?utm_medium=email&utm_source=footer > >. > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CAEKsHmA5H-PTtdUd6ZbrNukZ8khV5vEk6q5cqUQBdcFtNRBszA%40mail.gmail.com.
