Relative paths in build output

[vgrigoriu]

Currently in the built index html, the js & css paths are absolute:

<script type="text/javascript" src="/main.bb7fdae8a3a384b182b2.js">

Is there a way to make them relative? I would like to host the app in a path below root.

[vgrigoriu]

Looks like this is a duplicate of #94. I guess I'll just need to wait for a new version on npm.

[xieqingtian]

awesome

[gaearon]

0.2.0 alpha is on npm, please give it a try and report any issues. #190

[vgrigoriu]

I had to set homepage to ./ to get relative paths. I don't know if it's 'right' but it works for me, so thanks!

[gaearon]

Hmm, can you describe your use case for purely relative paths? They won't work with client side routing. Is your app served from different paths?

[gaearon]

To be clear, if you set homepage to mysite.com/myfolder, you will get absolute paths that start with /myfolder. Would that not solve your problem?

[insin]

If you honour the value of homepage when it's present but blank, a blank publicPath will let you build apps which can be served from any URL, root or not.

You'll have to use hash-based routing if you need routing, that's the trade-off.

[gaearon]

We currently don’t honor blank homepage: https://github.com/facebookincubator/create-react-app/blob/ca7d227ae0354e04941ba0e4f76c0bcbf3050dfa/config/webpack.config.prod.js#L20-L23. But we can, I guess. I’d like to hear more about the use case though.

[insin]

Serving at any URL without being tied to a specific one and being able to build apps which don't need a server, just open the .html file in a browser.

I've found the latter handy for sending people little prototypes and tools at work instead of having to keep it serving from my machine or deploying it to our sandbox thing.

[gaearon]

I think "homepage": "./" would do the trick. It’s kinda weird of course.

[vgrigoriu]

My use case is similar to @insin's: I want to be able to host the files at any URL. I kinda prefer "homepage": "./" because it seems more explicit than "homepage": "".

[gaearon]

@vgrigoriu It should already work I think, did you have a chance to check it?

[vgrigoriu]

Yes, it works.

În vin., 29 iul. 2016 la 4:24 p.m. Dan Abramov notifications@github.com a
scris:

@vgrigoriu https://github.com/vgrigoriu It should already work I think,
did you have a chance to check it?

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
#165 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAF10GW7XtihILfmbaONqzDtvqfSC_eTks5qaf8kgaJpZM4JTx7M
.

[robcaldecott]

We have the same requirement for relative paths but using a homepage of ./ breaks image URLs in CSS (it ends up looking for the image in a static folder within the css folder when it is actually a level above). This is simple to reproduce if required.

We are desperate for a way to use relative paths. If anyone has any ideas I would be very grateful. At least a way to have 3rd-party CSS unmolested by Webpack when creating a production build.