How nygardk/react-share works
This repo is a frontend React component library published to npm as react-share. Its purpose is to provide:
• Share Button React components (open a share dialog/popup or invoke mailto:-style flows)
• Share Count React components (fetch counts from social network endpoints)
• A demo app under ./demo to showcase usage
• CI/release automation (GitHub Actions + Changesets)
Core library surface area (what consumers import)
• Many “leaf” components:
src/*ShareButton.ts (e.g., FacebookShareButton.ts)
src/*ShareCount.ts (e.g., RedditShareCount.ts)
Internal reusable building blocks (the “real architecture”)
• src/ShareButton.tsx – common base behavior for buttons (click handling, window open, disabled, etc.)
• src/hocs/
• createShareButton.tsx – factory/HOC generating network-specific share button components
• createShareCount.tsx – factory/HOC generating network-specific share count components
• src/hooks/useIsMounted.ts – used to avoid state updates after unmount (relevant for async share count fetching)
• src/utils/
• objectToGetParams.ts – encodes query parameters for share URLs
• assert.ts – internal invariants / runtime checks
Demo application (consumer reference)
• demo/ with Demo.tsx, index.tsx, index.html, Demo.css – a Vite-driven demo that imports from the library code.
Build / tooling / release
• vite.config.js, vite.demo.config.js – bundling for library and demo
• tsconfig.json, tsconfig.demo.json – TypeScript compilation
• .github/workflows/ci.yml, .github/workflows/release.yml – CI + publishing automation
• .changeset/ – Changesets-based versioning + changelog workflow
• package.json, package-lock.json – dependencies, scripts, build entrypoints
At runtime, react-share runs inside the consumer’s browser. There is no server component in this repo.
There are two main runtime flows:
User clicks <XShareButton url="…">…</XShareButton>
2. Button logic (from ShareButton.tsx + createShareButton.tsx) builds a network-specific share URL (via objectToGetParams)
Optional callbacks
• beforeOnClick (possibly async)
• onShareWindowClose
Key point to show: the share action is purely URL-based (README emphasizes “no external script loading / no SDKs”).
<RedditShareCount url="…"/> mounts
2. createShareCount.tsx triggers an async request to some network endpoint (varies by platform and may be proxied/deprecated depending on network)
useIsMounted prevents setting state after unmount
Left: Consumer App (React) + End User
Center: react-share package boundary containing:
• index.ts (public API)
• Share Buttons (generated via createShareButton + ShareButton.tsx)
• Share Counts (generated via createShareCount + useIsMounted)
• Utils (objectToGetParams, assert)
Right: External Social Platforms (Share endpoints + Count endpoints)
Bottom/Side: CI/Release lane (GitHub Actions + Changesets → npm)
That single view will capture: distribution, integration, internal design, and third-party interactions.