@bitrise/bitkit-v2 0.3.211 → 0.3.212
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.
|
@@ -198,14 +198,11 @@ If your codebase has a local `card.tsx` wrapper around v1 Card (e.g. Shadcn-styl
|
|
|
198
198
|
|
|
199
199
|
// Breadcrumb v2
|
|
200
200
|
<BitkitBreadcrumb>
|
|
201
|
-
<BitkitBreadcrumb.Item href="
|
|
201
|
+
<BitkitBreadcrumb.Item href="/path">Label</BitkitBreadcrumb.Item>
|
|
202
202
|
<BitkitBreadcrumb.CurrentItem>Current</BitkitBreadcrumb.CurrentItem>
|
|
203
203
|
</BitkitBreadcrumb>
|
|
204
204
|
```
|
|
205
205
|
|
|
206
|
-
**HashRouter gotcha**: `BitkitBreadcrumb` uses plain `href`. With HashRouter all links need the `#/` prefix (e.g. `href="#/sessions"`), otherwise navigation breaks silently.
|
|
207
|
-
|
|
208
|
-
**Version requirement**: `BitkitBreadcrumb` requires `@bitrise/bitkit-v2 >= 0.3.210`.
|
|
209
206
|
|
|
210
207
|
### textStyle tokens
|
|
211
208
|
|
|
@@ -223,20 +220,6 @@ Common tokens: `body/sm/regular`, `body/md/regular`, `body/md/semibold`, `body/l
|
|
|
223
220
|
|
|
224
221
|
---
|
|
225
222
|
|
|
226
|
-
## Action menus
|
|
227
|
-
|
|
228
|
-
If the codebase has a hand-rolled dropdown/action menu (state + ref + `useEffect` for click-outside), replace it with `BitkitActionMenu`:
|
|
229
|
-
|
|
230
|
-
```tsx
|
|
231
|
-
<BitkitActionMenu.Root trigger={<button>...</button>}>
|
|
232
|
-
<BitkitActionMenu.Item onClick={...}>Edit</BitkitActionMenu.Item>
|
|
233
|
-
<BitkitActionMenu.Separator />
|
|
234
|
-
<BitkitActionMenu.Item onClick={...} danger>Delete</BitkitActionMenu.Item>
|
|
235
|
-
</BitkitActionMenu.Root>
|
|
236
|
-
```
|
|
237
|
-
|
|
238
|
-
---
|
|
239
|
-
|
|
240
223
|
## Color tokens: `text/*` vs `icon/*`
|
|
241
224
|
|
|
242
225
|
Use `text/*` tokens on `<Text>` (and other text elements), and `icon/*` tokens on `<Icon*>` components. Most pairs resolve to the same underlying color, so a mismatch won't be visible — but the semantics matter.
|
|
@@ -256,10 +239,6 @@ Use `text/*` tokens on `<Text>` (and other text elements), and `icon/*` tokens o
|
|
|
256
239
|
After the migration, audit `package.json` carefully — v1 pulled in transitive deps that may still be listed:
|
|
257
240
|
|
|
258
241
|
- `@emotion/react` — you may no longer need to list it directly in your app's `package.json`; `@bitrise/bitkit-v2` brings it transitively
|
|
259
|
-
- `lucide-react` — if icons are now from `@bitrise/bitkit-v2`
|
|
260
|
-
- `zustand` — if Bitkit's sidebar hook was the only consumer
|
|
261
|
-
- `@types/luxon`, `patch-package`, `postcss` — check if still used
|
|
262
|
-
|
|
263
242
|
Also check `scripts` in `package.json` for any `postinstall` entries referencing removed packages (e.g. `"postinstall": "patch-package"`) — these will silently break CI.
|
|
264
243
|
|
|
265
244
|
---
|
|
@@ -281,7 +260,6 @@ Migrating a large repo component-by-component is token-intensive. What works wel
|
|
|
281
260
|
- [ ] Identify local wrapper components around v1 Bitkit components
|
|
282
261
|
- [ ] Identify hand-rolled alternatives to v2 components (dropdowns, modals, etc.)
|
|
283
262
|
- [ ] Check `@bitrise/bitkit-v2` changelog for version requirements per component
|
|
284
|
-
- [ ] Check if HashRouter is in use (affects Breadcrumb `href`)
|
|
285
263
|
- [ ] Note any buttons with complex children (non-string) — these need `chakra.button`
|
|
286
264
|
|
|
287
265
|
## Post-migration checklist
|