-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
prefixLink not working as expected with webpack url loader? #473
Comments
I don't think the problem here is gatsby/lib/utils/webpack.config.js Line 61 in 3007f58
|
@KyleAMathews If the |
Oh true... that's confusing. Hmmm... yeah this should be handled consistently — either with React router actually added support for setting a |
I think with 1.0 you should just scrap |
Yeah, sounds like a good plan. I'll create an issue to clean this up in 1.0. |
@f0rr0 any other fixes you want in before I roll another release? |
@KyleAMathews Nope, this seems good enough for now! Thanks |
0.12.10 is out 🎉 |
The publicPath stuff was fixed in #502 |
I require an image like so:
The image is not base64 encoded. A url is returned from url loader. In dev mode it looks something like
http://0.0.0.0:8000/423d290eaf378bf7e0361ddf2a3ed695.jpeg
but running this in production withlinkPrefix = "/xyz"
returns/xyz423d290eaf378bf7e0361ddf2a3ed695.jpeg
Using
fixes the issue in production but breaks it in dev. The output is
/http://0.0.0.0:8000/423d290eaf378bf7e0361ddf2a3ed695.jpeg
The text was updated successfully, but these errors were encountered: