changedOutput schema / description
Previous value: -"A product to put into the user's project: what `npx shadcn@latest add @upfork/<slug>` installs. It counts as an install, as the CLI's does."New value: +"A product to put into the user's project: what `npx shadcn@latest add @upfork/<slug>` installs, or a mobile (React Native) component's files, assets and Expo packages. It counts as an install, as the CLI's does."
addedOutput schema / properties / assets
Added value: +{
+ "default": null,
+ "description": "A mobile component's assets, to download to their paths; null for shadcn products (the files load UpFork's hosted copies).",
+ "items": {
+ "description": "One of a mobile component's pictures, fonts, videos or sounds: download it from its url to its path in the app.",
+ "properties": {
+ "kind": {
+ "description": "image, font, video, audio or data.",
+ "type": "string"
+ },
+ "path": {
+ "description": "Where it goes from the Expo app's root, e.g. assets/images/hero.png: the code requires it by that path.",
+ "type": "string"
+ },
+ "url": {
+ "description": "Where UpFork hosts it.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "path",
+ "url",
+ "kind"
+ ],
+ "type": "object"
+ },
+ "type": [
+ "array",
+ "null"
+ ]
+}
changedOutput schema / properties / command / description
Previous value: -"The same install with the shadcn CLI, for a project set up for UpFork (see setup). Or write the files below yourself."New value: +"The same install with the shadcn CLI, for a project set up for UpFork (see setup). Or write the files below yourself. For a mobile component: the `npx expo install` line for its packages, run in the Expo app's folder once its files are in."
changedOutput schema / properties / files / items / properties / path / description
Previous value: -"Its path in the product, e.g. components/glow-card.tsx. Put it where the project keeps such files, through its aliases (components under @/components), as the shadcn CLI does."New value: +"Its path in the product, e.g. components/glow-card.tsx. Put it where the project keeps such files, through its aliases (components under @/components), as the shadcn CLI does. A mobile component's files go at their paths from the Expo app's root."
changedOutput schema / properties / files / items / properties / target / description
Previous value: -"Where it goes from the project's root when its place is fixed (pages, stylesheets); null: by the project's aliases."New value: +"Where it goes from the project's root when its place is fixed (pages, stylesheets; every file of a mobile component); null: by the project's aliases."
changedOutput schema / properties / files / items / properties / type / description
Previous value: -"registry:component, registry:lib, registry:hook, registry:page, registry:file or registry:style."New value: +"registry:component, registry:lib, registry:hook, registry:page, registry:file or registry:style; for a mobile component, mobile:file or mobile:demo (a screen showing it in use)."
addedOutput schema / properties / format
Added value: +{
+ "default": "shadcn",
+ "description": "shadcn (a React + Tailwind CSS component or page) or mobile (a React Native component for Expo apps).",
+ "type": "string"
+}
addedOutput schema / properties / versions
Added value: +{
+ "additionalProperties": {
+ "type": "string"
+ },
+ "default": null,
+ "description": "A mobile component's packages (its demos' too) at the versions UpFork's install check installed and type-checked them with in a fresh Expo app; `npx expo install` picks matching ones.",
+ "type": [
+ "object",
+ "null"
+ ]
+}