Repository navigation
feat: publish the design system to npm as pandacn - #3
Merged
Merged
Conversation
Renames @chakra-ui/shadcn-panda to pandacn and consumes it from npm: the monorepo app via workspace:*, standalone-app and panda-app via a normal ^0.1.0 dependency. Drops the tarball/pack-ds machinery. Adds a publish workflow and repository metadata so the npm page points back at examples/monorepo/packages/ds. Links use npmx.dev.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📚 Description
Publishes the design system to npm as
pandacnand consumes it like any normal package. This addresses the review feedback: no committed tarball, and the npm page points straight back at the source so it's obvious where the code lives.Supersedes #2 (the generate-the-tarball approach) — publishing removes the tarball problem entirely.
⛳️ Current behavior
The design system was
@chakra-ui/shadcn-panda, consumed by the two app examples via a committed.tgzand afile:dependency.🚀 New behavior
pandacn(published:pandacn@0.1.0).monorepoconsumes it viaworkspace:*;standalone-appandpanda-appinstall"pandacn": "^0.1.0"from npm — a normal install.pack-ds.sh.Publish pandacnGitHub Action (manual dispatch or apandacn-v*tag,NPM_TOKENsecret).repository.directory+homepagelink the npm page toexamples/monorepo/packages/ds, so provenance is clear. Package links use npmx.dev.💣 Is this a breaking change?
No — it swaps the local tarball for the published package.
📝 Additional information
pandacn@0.1.0is live: https://npmx.dev/pandacnpnpm run check-examplespasses for all three (no skips) — the consumers resolvepandacnfrom npm and build.packages/dsispandacn, and each consumer README links back to the source.