Haha hey again
Netlify Dev is awesome! Love that you’re experiencing that too. I’m a big fan as well.
Auth - Auth is interesting with dev because it doesn’t actually run a local auth server- it hits the same auth endpoint as your production / branch / preview sites. IIRC they all share a single GoTrue auth instance hosted by Netlify. So as far as dev goes, that should be transparent. Where things do get tricky is that you may have the same JWT or JWT carry-over from your prod site or other site tiers. My best recommendation with auth, especially in local dev, is to use Private tabs generously and always double-test with private tabs to make sure that a totally fresh session workflow will behave the way you want it to since dev uses the same back-end auth instance, there definitely are cases where it can feel fiddly
Gating - So gating when running locally via Netlify Dev actually should work across the board. I wonder if this adds to the confusion in the other thread we have because this is just part of the local redirect engine (all redirects should work locally) and you can read the source for it here - note that the JWT token and roles are accounted for. So, like I said, this should run locally just fine and accomplish the ‘gating’ without issue - but I’ll reference the above as well and stress the necessity for running in a private tab / fresh session to really make sure it’s working correctly the way you’d like it to. I did just verify this is working correctly on one of my demo auth projects running locally (just double check to make sure you’re hitting port :8888 because I spent a couple minutes hitting :8000 and scratching my head )
404 Routing - Can you elaborate a bit on what you were seeing locally and what you expected to see instead? I’m guessing this may also be an issue with auth/gating so maybe the above will help
Function logging - When running Netlify Dev locally, all function logs should dump out directly to the STDOUT of the process that you kicked off Netlify Dev with. Generally that should be really seamless and if you have a function that runs
console.log('foo') you should definitely see that in your process output do you have a sample of where you may not be seeing that?
Hope that helps!