-
Notifications
You must be signed in to change notification settings - Fork 327
Comparing changes
Open a pull request
base repository: clerk/javascript
base: @clerk/clerk-react@4.3.3-staging.1
head repository: clerk/javascript
compare: @clerk/clerk-react@4.3.3-staging.3
- 12 commits
- 47 files changed
- 4 contributors
Commits on Nov 1, 2022
-
feat(clerk-js,types): Organization invitation metadata
Added support for OrganizationInvitation publicMetadata. They can be set when calling the Organization#inviteMember() method.
Configuration menu - View commit details
-
Copy full SHA for 87764b8 - Browse repository at this point
Copy the full SHA 87764b8View commit details -
Merge pull request #486 from clerkinc/org-invitation-metadata
feat(clerk-js,types): Organization invitation metadata
Configuration menu - View commit details
-
Copy full SHA for d3280cd - Browse repository at this point
Copy the full SHA d3280cdView commit details -
Configuration menu - View commit details
-
Copy full SHA for 18dd5c4 - Browse repository at this point
Copy the full SHA 18dd5c4View commit details -
feat(backend-core): Organization invitation metadata
Added support for passing public metadata when creating an organization invitation.
Configuration menu - View commit details
-
Copy full SHA for 7bc4691 - Browse repository at this point
Copy the full SHA 7bc4691View commit details -
Merge pull request #487 from clerkinc/backend-org-invitation-metadata
feat(backend-core): Organization invitation metadata
Configuration menu - View commit details
-
Copy full SHA for 2685b27 - Browse repository at this point
Copy the full SHA 2685b27View commit details -
fix(clerk-js): Take into account enabled attributes and not first fac…
…tors for Sign Up form This commit fixes a bug in our UI Sign Up component. Until now for Sign up inputs, we were taking into account attributes that were used as first factors. This was wrong as first factors applies to Sign in only. For Sign up, we should take into account any enabled attribute or a valid combination between them (username + password) https://www.notion.so/clerkdev/Fix-PSU-with-required-emails-when-using-Sign-in-with-Metamask-32ef5f2f7261407cb3136b877fb20133
Configuration menu - View commit details
-
Copy full SHA for d3fdb1d - Browse repository at this point
Copy the full SHA d3fdb1dView commit details
Commits on Nov 2, 2022
-
fix(clerk-react): Add frontendAPI on window as a fallback
Store frontendAPI value on window as a fallback. This value can be used as a fallback during ClerkJS hot loading in case ClerkJS fails to find the "data-clerk-frontend-api" attribute on its script tag. This can happen when the DOM is altered completely during client rehydration. For example, in Remix with React 18 the document changes completely via `hydrateRoot(document)`. For more information refer to: - remix-run/remix#2947 - facebook/react#24430
Configuration menu - View commit details
-
Copy full SHA for 06f8b37 - Browse repository at this point
Copy the full SHA 06f8b37View commit details -
fix(clerk-js): Fix globalObject for UMD packaging
Current our webpack-powered UMD packaging was setting `seld` as the output global object. Historically, accessing the global object has required different syntax in different JavaScript environments. On the web you can use window, self, or frames - but in Web Workers only self will work. In Node.js none of these work, and you must instead use global. The this keyword could be used inside functions running in non–strict mode, but this will be undefined in Modules and inside functions running in strict mode. You can also use Function('return this')(), but environments that disable eval(), like CSP in browsers, prevent use of Function in this way. This issue came up in Remix when ClerkJS is not hotloaded and should be bundled in the application. To fix it we use the globalThis property. The globalThis property provides a standard way of accessing the global this value (and hence the global object itself) across environments. Unlike similar properties such as window and self, it's guaranteed to work in window and non-window contexts. In this way, you can access the global object in a consistent manner without having to know which environment the code is being run in. More information at: - https://webpack.js.org/configuration/output/#outputglobalobject - https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/globalThis
Configuration menu - View commit details
-
Copy full SHA for 7499207 - Browse repository at this point
Copy the full SHA 7499207View commit details -
- @clerk/backend-core@2.10.0-staging.0 - @clerk/clerk-js@4.13.0-staging.0 - @clerk/edge@1.12.6-staging.0 - @clerk/clerk-expo@0.9.68-staging.0 - @clerk/nextjs@4.5.6-staging.0 - @clerk/clerk-react@4.3.3-staging.0 - @clerk/remix@1.3.10-staging.0 - @clerk/clerk-sdk-node@4.4.6-staging.0 - @clerk/shared@0.4.2-staging.0 - @clerk/themes@1.2.21-staging.0 - @clerk/types@3.14.0-staging.0
Configuration menu - View commit details
-
Copy full SHA for 25a8bd2 - Browse repository at this point
Copy the full SHA 25a8bd2View commit details -
- @clerk/backend-core@2.10.0-staging.1 - @clerk/clerk-js@4.13.0-staging.1 - @clerk/edge@1.12.6-staging.1 - eslint-config-custom@0.0.2-staging.0 - @clerk/clerk-expo@0.9.68-staging.1 - @clerk/nextjs@4.5.6-staging.1 - @clerk/clerk-react@4.3.3-staging.1 - @clerk/remix@1.3.10-staging.1 - @clerk/clerk-sdk-node@4.4.6-staging.1 - @clerk/shared@0.4.2-staging.1 - @clerk/themes@1.2.21-staging.1 - @clerk/types@3.14.0-staging.1
Configuration menu - View commit details
-
Copy full SHA for e6afbe0 - Browse repository at this point
Copy the full SHA e6afbe0View commit details -
- @clerk/backend-core@2.10.0-staging.2 - @clerk/clerk-js@4.13.0-staging.2 - @clerk/edge@1.12.6-staging.2 - eslint-config-custom@0.0.2-staging.1 - @clerk/clerk-expo@0.9.68-staging.2 - @clerk/nextjs@4.5.6-staging.2 - @clerk/clerk-react@4.3.3-staging.2 - @clerk/remix@1.3.10-staging.2 - @clerk/clerk-sdk-node@4.4.6-staging.2 - @clerk/shared@0.4.2-staging.2 - @clerk/themes@1.2.21-staging.2 - @clerk/types@3.14.0-staging.2
Configuration menu - View commit details
-
Copy full SHA for 1e48674 - Browse repository at this point
Copy the full SHA 1e48674View commit details -
- @clerk/backend-core@2.10.0-staging.3 - @clerk/clerk-js@4.13.0-staging.3 - @clerk/edge@1.12.6-staging.3 - eslint-config-custom@0.0.2-staging.2 - @clerk/clerk-expo@0.9.68-staging.3 - @clerk/nextjs@4.5.6-staging.3 - @clerk/clerk-react@4.3.3-staging.3 - @clerk/remix@1.3.10-staging.3 - @clerk/clerk-sdk-node@4.4.6-staging.3 - @clerk/shared@0.4.2-staging.3 - @clerk/themes@1.2.21-staging.3 - @clerk/types@3.14.0-staging.3
Configuration menu - View commit details
-
Copy full SHA for 4561f06 - Browse repository at this point
Copy the full SHA 4561f06View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff @clerk/clerk-react@4.3.3-staging.1...@clerk/clerk-react@4.3.3-staging.3