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
if createClient is called and the supabaseKey passed in is null or undefined then a non-specfic error thrown. This can happen if you make a call like this:
TypeError: Cannot read property 'length' of undefined
at SupabaseClient.initClient (/Users/zlwaterfield/programming/switch-log/node_modules/@supabase/supabase-js/lib/index.js:7:263)
at SupabaseClient.select (/Users/zlwaterfield/programming/switch-log/node_modules/@supabase/supabase-js/lib/index.js:7:920)
at CategoryRepository.findByLabel (webpack-internal:///./repositories/CategoryRepository.ts:12:54)
at LogEntry._findCategory (webpack-internal:///./services/LogEntryService.ts:86:42)
at LogEntry.timeStart (webpack-internal:///./services/LogEntryService.ts:17:31)
at __webpack_exports__.default (webpack-internal:///./pages/api/log.ts:11:31)
at apiResolver (/Users/zlwaterfield/programming/switch-log/node_modules/next/dist/next-server/server/api-utils.js:8:7)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async DevServer.handleApiRequest (/Users/zlwaterfield/programming/switch-log/node_modules/next/dist/next-server/server/next-server.js:45:397)
at async Object.fn (/Users/zlwaterfield/programming/switch-log/node_modules/next/dist/next-server/server/next-server.js:37:176)
We should add validation that the supabaseKey is passed in or at least fix this line so the error is better handled.
The text was updated successfully, but these errors were encountered:
- Fixes#32 Major DX change: response and error handling
- Fixes#49 When no `supabaseKey` is passed in it throws an error
- Fixes#31 chore: set up semantic releases
- Fixes#15 `supabase.auth.logout()` throws "Invalid user" error.
- Fixes#20 Auth: Change DX of user management
- Fixes#30 Supabase auth interface missing informiation
- Fixessupabase/supabase#147supabase/supabase#147
- Partial fix for supabase/realtime-js#53 - if there is no token provided. The error needs to be caught at a socket level.
- Adds magic links
## BREAKING CHANGES
- See all breaking changes in RELEASE.md v1.0.0
- Errors are now returned and not thrown
- Auth now uses `@supabase/gotrue-js` interface
- `supabase.getSubscriptions()` only returns open subscriptions
* Updates the config
* chore: Migrates the basic outline to TS
* Adds a simple example showing how it can be used.
* chore: Moves tests to jest
* chore: Adds semantic releases
* Moves the subscription into it's own class
* Updates the todo readme with simple instructions
* Updates installs
* Revverts commented code - sorry for the spam
* docs: adds JSDoc to some functions
* chore: Adds a function for backwards compat
* chore: migrates the client to SupabaseClient
* This change attempts to make the naming conventions the same as Thor's previously
* Updates GoTrue to latest version
* Adds generic type to the from, and updates the name of the query builder
* Updates to latest versions of all packages
* Updates the example to make sure it's working
* Refactor SupabaseQueryBuilder
* Adds prettier hook
* Add TypeScript next.js example.
* Declutter SupabaseClient and make work with gotrue-js changes.
* Bumps the GoTrue version
* Bumps postgrest to include the types
* Temporarily adds the spec so that I can use it in our docs
* Update examples and add resetPassword.
* Bump gotrue-js version.
* Update lockfile.
* Add auth magic link capabilities.
* Gotrue-js user and session method updates.
* chore: Adds release notes
Co-authored-by: Thorsten Schaeff <[email protected]>
Co-authored-by: Thor 雷神 Schaeff <[email protected]>
Chore
Describe the chore
if
createClient
is called and thesupabaseKey
passed in isnull
orundefined
then a non-specfic error thrown. This can happen if you make a call like this:and the env variable is empty.
The error is:
We should add validation that the
supabaseKey
is passed in or at least fix this line so the error is better handled.The text was updated successfully, but these errors were encountered: