Issue with sitemap: null
See original GitHub issueHi. After the plugin update, I’m getting an error when building my Gatsby page. In the configuration, I use sitemap: null
Error:
"gatsby-plugin-robots-txt" threw an error while running the onPostBuild lifecycle:
Invalid URL: null
73 | ) {
74 |
> 75 | mergedOptions.sitemap = new URL(path.posix.join(pathPrefix, 'sitemap', 'sitemap-index.xml'), mergedOptions.host).toString();
| ^
76 | } else {
77 | try {
78 | new URL(mergedOptions.sitemap)
File: node_modules/gatsby-plugin-robots-txt/src/gatsby-node.js:75:29
Error: TypeError [ERR_INVALID_URL]: Invalid URL: null
Issue Analytics
- State:
- Created 2 years ago
- Reactions:6
- Comments:20 (7 by maintainers)
Top Results From Across the Web
My sitemap is blank, what's wrong? • Yoast
A blank sitemap is basically a white screen with no header, no links, nothing at all. There could be several things wrong: Sitemap...
Read more >SiteMap.CurrentNode returns null - MSDN - Microsoft
NET 4 application and I am using the SiteMap.CurrentNode property because I need to get the current SiteMap node. I can not use...
Read more >Why SiteMap.CurrentNode always null in web application?
Your web application current page always null with sitemap, maybe it was because of routing or query-string in url.
Read more >Why is my Sitemap.CurrentNode null? - Stack Overflow
Making the Sitemap.CurrentNode work in my code is oddly a problem. I haven't figured out how to list code on STOF yet... so...
Read more >Fixing Sitemap Errors For Better Indexing of Submitted URLs
Google has issues crawling your sitemap URLs · Sitemap contains URLs which are blocked by robots.txt · URLs not accessible error means that...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
🎉 This issue has been resolved in version 1.6.9 🎉
The release is available on:
Your semantic-release bot 📦🚀
@mdreizin Please re-open the issue. The fix wasn’t merged in
1.6.8
CI outputsemantic-release
didn’t generate a new version. I think it happened because PR didn’t include a commit message with the wordfix
.