feat(repo): playground workspace: protocol

[jacekradko]

Description

Checklist

• pnpm test runs as expected.
• pnpm 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:

[changeset-bot]

⚠️ No Changeset found

Latest commit: 808a4f6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
clerk-js-sandbox	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 21, 2024 4:08am

[BRKalow]

@jacekradko does this include all the playgrounds as workspaces? Not sure if we want to do that...we don't want to have to install all of these deps by default.

[jacekradko]

@BRKalow Yes, it would. I am just testing this out and seeing what impact if would have on install times. pnpm should mitigate most of the additional cost of additional packages getting install, especially if we lean into catalog: protocol to use as few versions of the same package as possible.

I think there is a case to be made for these packages to be treated as part of the workspace as it makes DX within the monorepo much easier. No need for yalc-ing things around and automatically getting interlinked packages