Yea, typically, I would say there wouldn’t be an easy way to test Identity locally but your workaround/solution will work. You’d just want to make sure not to use that instance of Chrome to browser anywhere except your localhost due to the lower security.
Hi guys, im new to netlify, and i had same issue, netlify identity throw cors errors when using netlify dev or in preview deployments but not in prod, I was reading few post similar and people said that it should work when using netlify dev but it doesnt for me, and in this post @Dennis im understanding that identity cors will never work locally even using netlify dev am I right?
Hey @jjalonso,
I believe Niklison got it working by disabling the CORS check in Chrome, as described here:
This is not secure for regular browsing, so what Dennis is saying above is to be sure to only use the Chrome instance where you disable the CORS check for local browsing and testing your app.
Hey @jjalonso, not super familiar with the hot reload module you are using (hottie). Have you tried using something other than that. Have you tried using something like parcel or create-react-app that both have hot reload functionality built in?
My apologies guys, I think the hottie thing was some typo or thing of the spell corrector and not sure what i meant to say, actually i didnt even know that hottie is some sort or tool or similar lool
@jjalonso , can you explain again in a different way what the problem is and what you have already tried? i think we are all feeling a bit lost! thanks.
I solved it using a chrome extension, since it only happen in development and not in production it could work for me but is just because i have a ‘disable cors’ extension on my chrome browser.
The question is, should CORS error be thrown when using gotrue library from cli ‘netlify dev’ ?