urls to static resources about component HOT 11 CLOSED

yeah that works, I think this part will be pretty ad-hoc, what we do is loop through out component.json files, grab the filenames and set up matching routes with express and res.sendfile(), definitely more than one way to solve this portion

from component.

Can either of you give any guidance on a decent way to handle this? I'm doing stupid stuff like this in my makefile:

release: replace
    @component build

replace:
  @cat ./css/font-awesome.css | sed -e 's/\.\.\/font\//..\/components\/timoxley-font-awesome\/font\//g' > ./release/font-awesome.css

This, seems wrong.

Related tickets: #28, #11

from component.

I originally created rework for the css manip stuff, I'll try out a few things at least as reasonable defaults. This does get a bit more complicated depending on how you use components

from component.

@visionmedia I'll have a look into rework. If you couldn't tell, the use case here is an icon-font component. I was thinking about perhaps having the component inject the css into the dom so it could manipulate the paths dynamically… but then you lose cachability. Perhaps something along those lines might work.

from component.

even a simple regexp would do we dont really need rework for that part but i had other things in mind for the future. just need to figure out the least leaky abstraction possible for this

from component.

by default in --dev this will prefix urls with ./ so that they work with file://, and without --dev they will not be prefix so you'll end up with urls like /my-component/images/maru.png, and I added --prefix url for cases like /public/my-component/images/maru.png depending on your serving technique

from component.

👍 👍

from component.

how can we disable URL rewriting for CSS? I prefer to handle all static assets myself since they're all going into a CDN.

from component.

well you wont want to PUT the data to a cdn each time you change something in dev, that would be a separate build when you're deploying. if you disable url rewriting with component they simply wont point to the correct files, but nothing else changes

from component.

Oh of course not. My question is just how to disable url rewriting so /images/image.png doesn't become /mycomponent/images/image.png when building. I don't see any options anywhere.

from component.

@timoxley @visionmedia

Finding that building a component referencing FontAwesome on windows is causing a problem which I think relates to this.

The result is:

 @font-face {
   font-family: "FontAwesome";
   src: url("\timoxley-font-awesome\font\fontawesome-webfont.eot");
   src: url("\timoxley-font-awesome\font\fontawesome-webfont.eot?#iefix") format('eot'), url("\timoxley-font-awesome\font\fontawesome-webfont.woff") format('woff'), url("\timoxley-font-awesome\font\fontawesome-webfont.ttf") format('truetype'), url("\timoxley-font-awesome\font\fontawesome-webfont.svg#FontAwesome") format('svg');
   font-weight: normal;
   font-style: normal;
 }

Note that \t is a tab character so the escaping isn't working right, however, even so, I'm not convinced a backslash for a css url is ever appropriate - even on windows?

Thanks

from component.