chore(nextjs): Add deprecation warning for app-beta subpath export

[dimkl]

Description

The implementation in app-beta was an attempt to support the NextJS app-router early on. Since the app-router release is stable we will deprecate the @clerk/nextjs/app-beta subpath export and suggest using the stable @clerk/nextjs exports instead.

In this PR the following hacks were applied to add JSDocs and console warnings deprecations:

• we could not add a single deprecation warning in the app-beta/index.ts because it did not work so deprecated was added in each file
• Replaced import from @clerk/clerk-react with module to show deprecation warning (see: packages/nextjs/src/app-beta/client/clerk-react.ts)
• Use import with aliases for re-exported modules of @clerk/clerk-react to add JSDoc deprecations only for the exports from the app-beta

Since the whole folder app-beta will be removed in the next major version, there is no need to worry about those hacks.

Checklist

• npm test runs as expected.
• npm run build runs as expected.
• (If applicable) JSDoc comments have been added or updated for any package exports
• (If applicable) Documentation has been updated

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other:

Packages affected

• @clerk/clerk-js
• @clerk/clerk-react
• @clerk/nextjs
• @clerk/remix
• @clerk/types
• @clerk/themes
• @clerk/localizations
• @clerk/clerk-expo
• @clerk/backend
• @clerk/clerk-sdk-node
• @clerk/shared
• @clerk/fastify
• @clerk/chrome-extension
• gatsby-plugin-clerk
• build/tooling/chore

[changeset-bot]

🦋 Changeset detected

Latest commit: 78eb66f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@clerk/nextjs	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[brkalow]

@dimkl What were the issues you ran into with adding the deprecation warning to app-beta/index?

[dimkl]

@brkalow , @LekoArts adding a deprecation in the app-beta/index.ts seems to be ignored.
I have created the following screenshots to showcase that add a warning to the module, the warning is visible to the console but the warning in the index.ts is not.
The following steps were applied:

• add deprecation warning to index.ts and to auth.ts and a console.log
• <javascript_repo> git status to show that those changes were saved
• <javascript_repo> npm run build -- --force && npm run yalc:all to create clean build and push that build to the playground
• <javascript_repo>/playground/nextjs npm run dev to start an application with NextJS app-beta
• navigate to http://localhost:4011 to trigger application logs
• Search for deprecation warnings and console log in the application logs

[LekoArts]

Ok, makes sense 👍 I'd need to dive deeper into how you could run a side-effect when a module is imported. With a quick search I couldn't find previous art on this.

[clerk-cookie]

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.