Dr. Derek Austin

Note: This includes [this commit](https://github.com/alan2207/bulletproof-react/pull/12/commits/e924e7fae96d900912ddbf15a7a5da8b5006895d) from #13 because I managed to commit twice. At least it will make it easier to merge both PRs (if you agree & do so)...

per https://github.com/prettier/prettier-eslint#this-solution the answer is **yes** that `eslint --fix` will run Prettier first. That was the whole idea of the plugin, apparently.

> > > @dandv, I didn't have to monkeypatch. It's actually something you can change with a legit setting in gatsby-config. Here's what I have: > > ```js > {...

Hey I wanted to elaborate some @devuxer @dandv ... For me, as I just said, adding the `/` removes the warning, but doesn't fix the behavior in production at Netlify...

@devuxer @dandv @epilande Also I tried the gatsby-plugin-remove-trailing-slashes along with Pretty URLs turned on. That meant the redirect went to /auth/callback in production instead of /auth/callback/ in production, though I...

@jacobcarrington Would you suggest the default for `gatsby-theme-auth0` should be `/auth/callback/` for the callback URL instead? Currently, it's `/auth/callback` without the trailing slash.

@Qurus Did you get it working? I'm having the same issues with Netlify. I think it has to do with the /auth/callback/ path not having a trailing slash.

Hey @jacobcarrington That would be great, as I'm working on a tutorial based on this plugin. I'd also love to hear if you have a suggestion for a auth0-react or...

@jacobcarrington Awesome, thank you so much!! I'll try it out tomorrow. That does seem a little weird, but I'm not super familiar with it.

Great, thank you 👍