You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The error that the SDK logs about the scheme of the base URL not being HTTPS is very annoying in local development, especially when running against localhost which is obviously not a production environment.
I get this error logged like 20 times while the build is running locally, and then again on every page visit.
Describe the ideal solution
I think this warning should explicitly ignore domains that contain "localhost" since it's most likely that someone is running npm build && npm start locally if that is what the environment variable is set to.
Alternatives and current workarounds
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Thanks for the feedback! We've removed the warning log in the latest release to be more inline with v3's behavior and to reduce the noise from logs during builds and running apps via next start in tests and locally.
Checklist
Describe the problem you'd like to have solved
The error that the SDK logs about the scheme of the base URL not being HTTPS is very annoying in local development, especially when running against localhost which is obviously not a production environment.
I get this error logged like 20 times while the build is running locally, and then again on every page visit.
Describe the ideal solution
I think this warning should explicitly ignore domains that contain "localhost" since it's most likely that someone is running
npm build && npm start
locally if that is what the environment variable is set to.Alternatives and current workarounds
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: