ReferenceError: URL is not defined

[sbardian]

ReferenceError: URL is not defined

[matteomanzo]

It works now! Thanks a lot you've been very quick!

[ing-norante]

Same here...

[sbardian]

Do you also have the plugin gatsby-plugin-remove-trailing-slashes ? Just a thought off the top of my head. I can do more testing on my end later today as well.

[sbardian]

Also, be sure to check out the Gotchas section if you missed it?

https://github.com/sbardian/gatsby-plugin-breadcrumb#gotchas

[matteomanzo]

@sbardian yes I have got gatsby-plugin-remove-trailing-slashes installed and I made sure that my config respects the gotchas you mentioned, unfortunately this error keeps occurring.

[sbardian]

Thanks @matteomanzo. I'll do more troubleshooting on my end and see if I can reproduce.

[matteomanzo]

Thank you very much @sbardian

[sbardian]

I had a friend run through the Sitemap docs. Seems I need to update some of the docs as they made sense to me writing them, but he was confused on some of them. I will do that soon. Otherwise he was able to use them and it seemed to work fine for him.

I think this might be because of your version of node. I think URL was introduced in node version 10. Which I didn't even think about. Could try updating your node and see, or I can try running a lower version of node and test on my end tonight. If this is the case I might need to use something else other than URL for this. Let me know if you are able to bump your node version and test, otherwise I'll test tonight.

[sbardian]

I tried using sitemap with node v8.10.0 and I get the same error. So, I think its a pretty good guess this is why you are seeing this. I will look into alternative modules that are supported by earlier versions of node. For now I would use something like nvm / n / etc. to use a 10+ version of node to compile when using sitemap.

[sbardian]

🎉 This issue has been resolved in version 2.1.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sbardian]

Let me know if this doesn't fix the issue for you guys! Hopefully it now supports node v8. Sorry for the troubles.