Skip to content

List shadcn/ui in the client's third-party notices - #62

Merged
markbackman merged 1 commit into
mainfrom
mark/shadcn-notice
Sep 29, 2026
Merged

markbackman merged 1 commit into
mainfrom
mark/shadcn-notice

Conversation

@markbackman

@markbackman markbackman commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

The client build writes THIRD_PARTY_NOTICES.txt into client/dist by listing the npm packages whose code ends up in the bundle. shadcn/ui reaches the bundle two other ways, so its MIT license was missing from the notices: its components are copied into client/src/components/ui, and the shadcn stylesheet comes in through a CSS @import, which the generator doesn't see as a module.

  • Notices generator. thirdPartyNotices() now takes two options. packages names npm packages to include even when nothing imports them as modules. vendored lists code copied into the repo, each with a name, license, source link and license-text file. Vendored entries have no version, so they're listed by name alone.
  • Client config. The client passes shadcn as a package and the 21 components in src/components/ui as vendored code. The shadcn/ui license text is in client/licenses/vendored/shadcn-ui.txt, copied from upstream.
  • Result. The built notices list 76 entries, adding shadcn@4.21.0 and "shadcn/ui components (src/components/ui)", both with the MIT license text.

The shadcn/ui components are copied into client/src/components/ui and the shadcn stylesheet is pulled in through a CSS @import, so neither appears among the bundled npm packages the notices generator reads. The generator now takes packages to include explicitly and vendored code with its license text, and the client lists both.
@markbackman
markbackman merged commit 1a2b79a into main Sep 29, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant