fix(deps): bump supertokens-node from 15.1.1 to 18.0.2

[dependabot]

Bumps supertokens-node from 15.1.1 to 18.0.2.

Release notes

Sourced from supertokens-node's releases.

v18.0.2

Full Changelog: supertokens/supertokens-node@v18.0.1...v18.0.2

v18.0.1

What's Changed

• fix: error handling in doFetch by @​anku255 in supertokens/supertokens-node#864

Full Changelog: supertokens/supertokens-node@v18.0.0...v18.0.1

v18.0.0

What's Changed

• feat!: remove combination recipes (base PR) by @​rishabhpoddar in supertokens/supertokens-node#816
• fix: ci issues by @​porcellus in supertokens/supertokens-node#837
• ci: fix testing with older auth-react versions by @​porcellus in supertokens/supertokens-node#838
• ci: fix backwards compatibility code for older versions by @​porcellus in supertokens/supertokens-node#839
• chore: fix formatting error in changelog by @​porcellus in supertokens/supertokens-node#840
• ci: parallelize based on FDI versions by @​porcellus in supertokens/supertokens-node#841
• fix: thirdparty recursion and config reference issues by @​sattvikc in supertokens/supertokens-node#846

Full Changelog: supertokens/supertokens-node@v17.1.2...v18.0.0

v17.1.4

Full Changelog: supertokens/supertokens-node@v17.1.3...v17.1.4

v17.1.3

What's Changed

• fix: thirdparty recursion and config reference issues by @​sattvikc in supertokens/supertokens-node#842

Full Changelog: supertokens/supertokens-node@v17.1.2...v17.1.3

v17.1.2

What's Changed

• fix: Add a test to check session cookies are cleared if refresh api is called with an expired access token by @​anku255 in supertokens/supertokens-node#834
• fix: increase wait time to allow access token to expire by @​anku255 in supertokens/supertokens-node#836
• fix: Add workaround for unsupported 'cache' field in Cloudflare Workers by @​anku255 in supertokens/supertokens-node#835

Full Changelog: supertokens/supertokens-node@v17.1.1...v17.1.2

v17.1.1

What's Changed

• fix: handle getFormData returning FormData type by @​porcellus in supertokens/supertokens-node#831
• docs: add explanation comment for changes in 831 by @​porcellus in supertokens/supertokens-node#832
• fix: check if FormData is defined to fix old node versions by @​porcellus in supertokens/supertokens-node#833

Full Changelog: supertokens/supertokens-node@v17.1.0...v17.1.1

... (truncated)

Changelog

Sourced from supertokens-node's changelog.

[18.0.2] - 2024-07-09

• refreshPOST and refreshSession now clears all user tokens upon CSRF failures and if no tokens are found. See the latest comment on supertokens/supertokens-node#141 for more details.

[18.0.1] - 2024-06-19

Fixes

• Fix a bug that was preventing errors from being caught in the fetch function, thus bypassing our error handling.

[18.0.0] - 2024-05-23

Breaking change

• Removed ThirdPartyEmailPassword and ThirdPartyPasswordless recipes. Instead, you should use ThirdParty + EmailPassword or ThirdParty + Passwordless recipes separately in your recipe list.
• Removed rid query param from:
  • email verification links
  • passwordless magic links
  • password reset links
• The API for checking if an email exists in the passwordless recipe has changed to return true only if there exists a user with that email as a passwordless user. So for example, earlier, if a user existed with email [email protected] as an emailpassword user (and not passwordless user), the passwordless API for does email exist would return true, but now, it won't.

Changes

• Even if the rid header is present in an API call, the routing now not only depends on that. If the SDK cannot resolve a request handler based on the rid, request path and method, it will try to resolve a request handler only based on the request path and method (therefore ignoring the rid header).
• New API handlers are:
  • GET /emailpassword/email/exists => email password, does email exist API (used to be GET /signup/email/exists with rid of emailpassword or thirdpartyemailpassword which is now deprecated)
  • GET /passwordless/email/exists => email password, does email exist API (used to be GET /signup/email/exists with rid of passwordless or thirdpartypasswordless which is now deprecated)
  • GET /passwordless/phonenumber/exists => email password, does email exist API (used to be GET /signup/phonenumber/exists which is now deprecated)
• Support for FDI 2.0 and 3.0

Migration guide

• If you were using ThirdPartyEmailPassword, you should now init ThirdParty and EmailPassword recipes separately. The config for the individual recipes are mostly the same, except the syntax may be different. Check our recipe guides for ThirdParty and EmailPassword for more information.

• If you were using ThirdPartyPasswordless, you should now init ThirdParty and Passwordless recipes separately. The config for the individual recipes are mostly the same, except the syntax may be different. Check our recipe guides for ThirdParty and Passwordless for more information.

Fixes

• Fixes override recursion build-up in built-in providers due to the modification of the input.override object in the ThirdParty providers list.
• Fixes issue with reference to config object in TypeProvider in the provider override. The issue was the originalImplementation.config object did not have the updated config values that was being used in the provider implementation.

[17.1.2] - 2024-05-21

Fixes

• Add workaround for unsupported 'cache' field in Cloudflare Workers. We retry fetch requests without the 'cache' field if they fail due to it not being implemented.

[17.1.1] - 2024-05-16

Fixes

... (truncated)

Commits

• cdfa031 adding dev-v18.0.2 tag to this commit to ensure building
• 090e29a fixes issue of refresh not clearing tokens
• 2e992ae adding dev-v18.0.1 tag to this commit to ensure building
• 18cef83 rebuilds
• 528ea98 fix: error handling in doFetch (#864)
• fb3ffa7 adding dev-v18.0.0 tag to this commit to ensure building
• cf55c63 fix: circleci image
• 6331624 fix: thirdparty recursion and config reference issues (#846)
• d81a69c adding dev-v18.0.0 tag to this commit to ensure building
• 4bfea40 ci: parallelize based on FDI versions (#841)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #831.