-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relative paths in build output #165
Comments
Looks like this is a duplicate of #94. I guess I'll just need to wait for a new version on npm. |
awesome |
0.2.0 alpha is on npm, please give it a try and report any issues. #190 |
I had to set |
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? |
To be clear, if you set homepage to |
If you honour the value of You'll have to use hash-based routing if you need routing, that's the trade-off. |
We currently don’t honor blank |
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 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. |
I think |
My use case is similar to @insin's: I want to be able to host the files at any URL. I kinda prefer |
@vgrigoriu It should already work I think, did you have a chance to check it? |
Yes, it works. În vin., 29 iul. 2016 la 4:24 p.m. Dan Abramov notifications@github.com a
|
We have the same requirement for relative paths but using a 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. |
If you can figure out a way to fix
please send a PR! This probably won’t be a high priority for us so we’d need somebody who cares about this to solve this. |
@gaearon our use-case for relative paths are that we deploy the build folder to s3 using jenkins for every pull request (we call this our 'snapshot' build). The URL is generated based on the jenkins build tag so it looks something like: s3.amazonaws.com/my-bucket/jenkins-pr-1/index.html Seeing homepage: "./" works great but I don't agree with your characterization as "weird" 😄 |
I don't mean the use case is weird, I meant that this "solution" is weird. And as noted above, it breaks in some cases so I don't recommend it at all: #165 (comment). We plan a different solution for your use case in #937. |
@gaearon got it. I wanted to make sure you were aware of our use case! |
Hi there! Please test it and don't hesitate to reach out if this doesn't solve your specific use case! |
For further details, see: facebook/create-react-app#165
For further details, see: facebook/create-react-app#165
@gaearon Yes, i have this problem too ! |
Add support for fork-ts-checker-webpack-plugin
I don't know if this thread is still active, but if it is I would like to add a scenario where relative path in built index.html is required. |
Currently in the built index html, the js & css paths are absolute:
Is there a way to make them relative? I would like to host the app in a path below root.
The text was updated successfully, but these errors were encountered: