fix: added package name prefix to all console.
methods in src/
#699
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
After upgrading @supabase/supabase-js, I stumbled on an error message (
No storage option exists to persist the session, which may result in unexpected behavior when using auth. If you want to set persistSession to true, please provide a storage option or you may set persistSession to false to disable this warning.
).It took me a while to figure out from which package this comes and why. Found it only because it was reported in the nuxt/supabase repo nuxt-modules/supabase#188.
I therefore suggest to prefix console.error / console.warning with this package's name, so you can easily check where this random error in your console comes from.
What is the current behavior?
Errors are logged into the server console without me having an idea from which package they come from.
What is the new behavior?
Now every error/warning has the package name
[@supabase/gotrue-js]
prefixed.