Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Incorrect URLs generated when pathPrefix value is set
See original GitHub issueOverview
Using gatsby v2, I have a site with a value set for the pathPrefix parameter.
Before I added this parameter, Both gatsby develop and gatsby build --prefix-paths worked correctly. Now I am seeing 404 errors trying to load icons in both development and when running the site after a build.
Here are example URLs that are trying to be loaded:
http://sites/somename/icons-e09e4c81dabea7f47e8e80e2478342f9/favicon-32x32.png http://sites/somename/icons-e09e4c81dabea7f47e8e80e2478342f9/favicon-16x16.png
Here are examples within the built HTML files:
<link rel="apple-touch-icon" sizes="32x32" href="//sites/somename/icons-e09e4c81dabea7f47e8e80e2478342f9/favicon-32x32.png" />
<link rel="apple-touch-icon" sizes="16x16" href="//sites/somename/icons-e09e4c81dabea7f47e8e80e2478342f9/favicon-16x16.png" />
You can see this is missing the hostname (and port when I was testing on port 8080 locally).
Issue Analytics
- State:
- Created 5 years ago
- Reactions:6
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hey, @julien1619.
Just a kindly reminder 😊
Oh, looks like fixed the issue in https://github.com/Creatiwity/favicons-webpack-plugin/commit/0872de414061baaad0a2853c77ae75bc38b8bbbf
but
package.jsonof this repo points to old commit:https://github.com/Creatiwity/gatsby-plugin-favicon/blob/a2e579b2d96bfbd500fdb584abbb4b15697f5d16/package.json#L23
Could you update it?