search

ecwyne / meteor-polymer

Meteor smart package for Google's opinionated web component framework 'Polymer'
https://atmospherejs.com/ecwyne/polymer
141 stars 17 forks source link

configuring components path #17

Closed lukejagodzinski closed 9 years ago

lukejagodzinski commented 10 years ago

Hi thanks again for great work with this package. It would be great if you could make components path configurable. For example:

MeteorPolymer.config({
  "directory" : "public/components"
});

or just read .bowerrc for path to components

Urigo commented 10 years ago

+1

ecwyne commented 10 years ago

Do you guys have any thoughts on how to implement this. Currently the polymer platform and polymer elements are downloaded/installed before any application code is run. having something like MeteorPolymer.config() wouldn't been seen until after polymer had already been installed.

lukejagodzinski commented 10 years ago

Hmm I though that polymer is being downloaded when Meteor is started. I can see message installing polymer into public directory... after I start fresh Meteor project with Meteor Polymer. If not, as you said, it would hard to do. Let's us know what exactly happens, so we will together figure out a solution.

ecwyne commented 10 years ago

I've started work on another package that will be much more flexible in how/where web-components are installed and plan on creating an API to automatically add <link rel="import" tags into your application. Polymer can be installed in this way, but this will also open up the whole world of web components to be easily installed in a meteor application.

https://github.com/ecwyne/meteor-web-components

lukejagodzinski commented 10 years ago

Nice can't wait to see it working :). If you need some ideas etc. I can provide some :)

rcampoamor commented 9 years ago

I was setting this up for the first time and noticed that if you don't have a .bowerrc file indicating where the local components are, the meteor startup fails with this error: Error: Request to https://bower.herokuapp.com/packages/polymer failed with 503 Which would (incorrectly) indicate that the call to the herokuapp was failing.