@clerk/vue@2.1.0

Minor Changes

• Expose OAuthConsent as a public component export for Vue and Nuxt. (#8381) by @wobsoriano

  Example:

  <script setup lang="ts">
  import { OAuthConsent } from '@clerk/vue';
  </script>
  
  <template>
    <OAuthConsent />
  </template>

Patch Changes

• Updated dependencies [785f057, 90beaeb, 244920d]:
  • @clerk/shared@4.9.0

@clerk/ui@1.7.0

Minor Changes

• Render OAuthConsent organization selector from user:org:read scope. (#8415) by @wobsoriano

• Expose OAuthConsent as a public component export across React-based SDKs. (#8381) by @wobsoriano

  Example:

  import { OAuthConsent } from '@clerk/react';
  
  export default function Page() {
    return <OAuthConsent />;
  }

Patch Changes

• Updated dependencies [785f057, 90beaeb, 244920d]:
  • @clerk/shared@4.9.0
  • @clerk/localizations@4.5.8

@clerk/testing@2.0.24

Patch Changes

• Updated dependencies [785f057, 90beaeb, 244920d]:
  • @clerk/shared@4.9.0
  • @clerk/backend@3.4.4

@clerk/tanstack-react-start@1.2.0

Minor Changes

• Add an env-var shortcut for unsafe_disableDevelopmentModeConsoleWarning across the Astro, Nuxt, React Router, and TanStack Start integrations so the development-keys console warning can be suppressed without threading the option through <ClerkProvider> manually: (#8402) by @jacekradko

  • Astro: PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
  • Nuxt: NUXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
  • React Router: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)
  • TanStack Start: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)

  The Next.js equivalent (NEXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING) already existed; the JSDoc on unsafe_disableDevelopmentModeConsoleWarning now lists every framework's env-var shortcut and clarifies that suppressing the warning at source also keeps it from being mirrored to the dev-server terminal (e.g. Next.js with experimental.browserDebugInfoInTerminal).

• Expose OAuthConsent as a public component export across React-based SDKs. (#8381) by @wobsoriano

  Example:

  import { OAuthConsent } from '@clerk/react';
  
  export default function Page() {
    return <OAuthConsent />;
  }

Patch Changes

• Updated dependencies [785f057, 90beaeb, 244920d]:
  • @clerk/shared@4.9.0
  • @clerk/react@6.5.0
  • @clerk/backend@3.4.4

@clerk/shared@4.9.0

Minor Changes

• Add internal API methods to manage enterprise connections (#8421) by @LauraBeatris

• Expose OAuthConsent as a public component export across React-based SDKs. (#8381) by @wobsoriano

  Example:

  import { OAuthConsent } from '@clerk/react';
  
  export default function Page() {
    return <OAuthConsent />;
  }

Patch Changes

• Add an env-var shortcut for unsafe_disableDevelopmentModeConsoleWarning across the Astro, Nuxt, React Router, and TanStack Start integrations so the development-keys console warning can be suppressed without threading the option through <ClerkProvider> manually: (#8402) by @jacekradko

  • Astro: PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
  • Nuxt: NUXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
  • React Router: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)
  • TanStack Start: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)

  The Next.js equivalent (NEXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING) already existed; the JSDoc on unsafe_disableDevelopmentModeConsoleWarning now lists every framework's env-var shortcut and clarifies that suppressing the warning at source also keeps it from being mirrored to the dev-server terminal (e.g. Next.js with experimental.browserDebugInfoInTerminal).

@clerk/react@6.5.0

Minor Changes

• Expose OAuthConsent as a public component export across React-based SDKs. (#8381) by @wobsoriano

  Example:

  import { OAuthConsent } from '@clerk/react';
  
  export default function Page() {
    return <OAuthConsent />;
  }

Patch Changes

• Updated dependencies [785f057, 90beaeb, 244920d]:
  • @clerk/shared@4.9.0

@clerk/react-router@3.2.0

Minor Changes

• Add an env-var shortcut for unsafe_disableDevelopmentModeConsoleWarning across the Astro, Nuxt, React Router, and TanStack Start integrations so the development-keys console warning can be suppressed without threading the option through <ClerkProvider> manually: (#8402) by @jacekradko

  • Astro: PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
  • Nuxt: NUXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
  • React Router: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)
  • TanStack Start: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)

  The Next.js equivalent (NEXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING) already existed; the JSDoc on unsafe_disableDevelopmentModeConsoleWarning now lists every framework's env-var shortcut and clarifies that suppressing the warning at source also keeps it from being mirrored to the dev-server terminal (e.g. Next.js with experimental.browserDebugInfoInTerminal).

• Expose OAuthConsent as a public component export across React-based SDKs. (#8381) by @wobsoriano

  Example:

  import { OAuthConsent } from '@clerk/react';
  
  export default function Page() {
    return <OAuthConsent />;
  }

Patch Changes

• Updated dependencies [785f057, 90beaeb, 244920d]:
  • @clerk/shared@4.9.0
  • @clerk/react@6.5.0
  • @clerk/backend@3.4.4

@clerk/nuxt@2.3.0

Minor Changes

• Expose OAuthConsent as a public component export for Vue and Nuxt. (#8381) by @wobsoriano

  Example:

  <script setup lang="ts">
  import { OAuthConsent } from '@clerk/vue';
  </script>
  
  <template>
    <OAuthConsent />
  </template>

• Add an env-var shortcut for unsafe_disableDevelopmentModeConsoleWarning across the Astro, Nuxt, React Router, and TanStack Start integrations so the development-keys console warning can be suppressed without threading the option through <ClerkProvider> manually: (#8402) by @jacekradko

  • Astro: PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
  • Nuxt: NUXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING
  • React Router: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)
  • TanStack Start: VITE_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING (or CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING)

  The Next.js equivalent (NEXT_PUBLIC_CLERK_UNSAFE_DISABLE_DEVELOPMENT_MODE_CONSOLE_WARNING) already existed; the JSDoc on unsafe_disableDevelopmentModeConsoleWarning now lists every framework's env-var shortcut and clarifies that suppressing the warning at source also keeps it from being mirrored to the dev-server terminal (e.g. Next.js with experimental.browserDebugInfoInTerminal).

Patch Changes

• Updated dependencies [244920d, 785f057, 90beaeb, 244920d]:
  • @clerk/vue@2.1.0
  • @clerk/shared@4.9.0
  • @clerk/backend@3.4.4

@clerk/nextjs@7.3.0

Minor Changes

• Expose OAuthConsent as a public component export across React-based SDKs. (#8381) by @wobsoriano

  Example:

  import { OAuthConsent } from '@clerk/react';
  
  export default function Page() {
    return <OAuthConsent />;
  }

Patch Changes

• Updated dependencies [785f057, 90beaeb, 244920d]:
  • @clerk/shared@4.9.0
  • @clerk/react@6.5.0
  • @clerk/backend@3.4.4

@clerk/localizations@4.5.8

Patch Changes

• Updated dependencies [785f057, 90beaeb, 244920d]:
  • @clerk/shared@4.9.0