Publishing raw files

[optilude]

The way bower resources are published, they are subject to Meteor's magic unless listed in the main or additionalFiles configuration.

I tried to include Polymer, for instance, which causes dozens of packages to be installed. These all reference each other via HTML imports. However, when the browser resolves e.g. /packages/bower/polymer/polymer.html the returned document is a Meteorified document, not the raw files.

I don't think there's ever a situation where we want this. The /packages/bower virtual path should behave like the /public path. Is that possible?

[dapearce]

Is there any update on this? I too am trying to use Polymer with this package and having trouble getting the correct html files imported.

[dapearce]

I was able to solve my issue by adding a .bowerrc file, which directed the components to be installed in the public directory

[Urigo]

@dapearce @optilude have you seen the meteor-polymer package https://github.com/ecwyne/meteor-polymer ?

[dapearce]

Yes, was looking for a little more control over updating (since Polymer is releasing so frequently). However, I was able to get things working without either package. Just using bower with a bower.json and .bowerrc file now, which can be set to install in the public directory.

[Urigo]

That's cool!
Where do you place the bower and bowerrc files and how they look?

[dapearce]

They both go in the root directory.

bower.json:

{
  "name": "Project Name",
  "version": "0.0.0",
  "homepage": "http://projecturl.com",
  "authors": [],
  "license": "",
  "private": true,
  "ignore": [
    "**/.*",
    "node_modules",
    "bower_components",
    "test",
    "tests"
  ],
  "dependencies": {
    "polymer": "Polymer/polymer#~0.4.2",
    "core-elements": "Polymer/core-elements",
    "paper-elements": "Polymer/paper-elements"
  }
}

.bowerrc

{"directory":"public/components/"}

Make sure to have bower installed on your machine (http://bower.io/#install-bower), and then run "bower update" from the terminal (while in your project), and it will install everything to the public/components folder.

[Urigo]

@mquandalle it looks like a needed feature - supporting the .bowerrc directory change (or in any other way..)

Is there a plan to support this soon?

@dapearce I would still prefer to use meteor-bower package then simple bower because that way I know meteor-bower will take care of the installation without any needed actions from me, but that is a nice solution

[dapearce]

You can still use a .bowerrc file with the bower package. Just put it in your root directory. 

—
Sent from Mailbox for iPhone

On Sat, Oct 11, 2014 at 7:05 PM, Uri Goldshtein notifications@github.com
wrote:

@mquandalle it looks like a needed feature - supporting the .bowerrc directory change (or in any other way..)
Is there a plan to support this soon?

@dapearce I would still prefer to use meteor-bower package then simple bower because that way I know meteor-bower will take care of the installation without any needed actions from me, but that is a nice solution

Reply to this email directly or view it on GitHub:
#31 (comment)

[Urigo]

But then I will need to run bower separately no?

[lorensr]

I agree this is needed for polymer. Support for .bowerrc being worked on in PR #42