@frontfriend/sdk 1.2.0 → 1.2.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -1
- package/dist/cli.js +186 -185
- package/dist/lib/core/adoption.js +1 -1
- package/dist/lib/core/api-client.js +8 -8
- package/dist/lib/core/application-adoption.js +20 -20
- package/dist/lib/core/cached-components-config.js +17 -1
- package/dist/lib/core/credentials.js +9 -2
- package/dist/lib/core/token-artifact-client.js +15 -6
- package/dist/mcp.cjs +107 -107
- package/dist/next.js +17 -2
- package/dist/package.json +1 -1
- package/dist/vite.js +21 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
Connect your application to your Frontfriend Design System. Use design contracts on their own, or add generated tokens and components for React and Vue. The SDK includes the Frontfriend CLI, coding agent integrations, and runtime helpers.
|
|
4
4
|
|
|
5
|
-
[Documentation](https://frontfriend.dev/docs/
|
|
5
|
+
[Documentation](https://frontfriend.dev/docs/) · [Component catalogue](https://frontfriend.dev/components/)
|
|
6
6
|
|
|
7
7
|
## Install
|
|
8
8
|
|
|
@@ -242,6 +242,8 @@ Without a component or a selection flag, `frontfriend update` adopts what the Ap
|
|
|
242
242
|
|
|
243
243
|
An applied adoption installs the npm dependencies of the components it wrote that `package.json` lacks, with the package manager your lockfile names (`--no-install` prints the command instead). It then refreshes the token cache in `node_modules/.cache/frontfriend` when the token pin moved: a running Vite dev server reloads by itself, without a restart. With `--installed --replace`, a stock shadcn file that the Design System ships under another name (`sonner.tsx` → `toast`) is replaced by the Design System component and removed, and its imports point at the new module.
|
|
244
244
|
|
|
245
|
+
A private component deleted from the Design System leaves every Release. `update` removes its pin from `frontfriend.lock.json` and prints `custom/... was deleted from the design system. Its files in <path> were kept; remove them and their imports if you no longer use them.` It never deletes those files. `add` and `download` refuse a deleted component that the lock pins; `diff` and `doctor` report the pin until `update` removes it. `update --json` (with `--yes` or `--dry-run`) prints one JSON result on stdout, with the removed pins in `components_removed`.
|
|
246
|
+
|
|
245
247
|
To apply the latest published Release of the App's tag in one step (lock, component source, npm dependencies, token cache), run:
|
|
246
248
|
|
|
247
249
|
```bash
|