Gatsby: How to completely remove trailing slashes

[pawelotto]

I desperately need to NOT generate any trailing slashes for Gatsby pages.

I'm currently using gatsby-plugin-remove-trailing-slashes but the plugin seems to give me more problems than it solves:

• it doesn't work when JS is disabled (my site works great also with JS disabled and I don't want any trailing slashes for the SSRendered pages when JS is disabled - good for crawler bots!)
• the plugin adds ugly 301 redirects instead of sanitizing urls and I'm getting enormous amounts of warnings in Google Webmaster Tools about the redirects. Something I want to avoid at all cost.

Anyone could tell me how to force Gatsby to NOT generate any trailing slashes while generating pages?
Thanks

[rstacruz]

I've found one way to prevent this from happening is to use createPage with a .html extension. This prevents Gatsby from making a folder with an index.html for that page when doing gatsby build. https://www.gatsbyjs.org/docs/actions/#createPage

// Creates /public/my-sweet-new-page/index.html
createPage({ path: '/my-sweet-new-page/' })

// Creates /public/my-sweet-new-page.html
createPage({ path: '/my-sweet-new-page.html' })

(Disclaimer: I'm still investigating this too! There might be better ways than this.)

[pawelotto]

Nice workaround, however, trailing .html is something I want to avoid also. Any other ideas?

[himynameistimli]

There's a discussion about this issue going on here: https://github.com/gatsbyjs/gatsby/issues/9207

For my side, I stopped trying to solve it within Gatsby, we handle it on Lambda@Edge instead. If that's something you can do, you can see my comment in the above issue https://github.com/gatsbyjs/gatsby/issues/9207#issuecomment-479359403

[gatsbot[bot]]

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.

Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community!