@tapizlabs/ui 0.1.5 → 0.2.1

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tapizlabs/ui",
3
- "version": "0.1.5",
3
+ "version": "0.2.1",
4
4
  "description": "Centralized design system, theming foundation, and reusable React UI components for the Tapiz platform.",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -50,10 +50,10 @@
50
50
  },
51
51
  "scripts": {
52
52
  "build": "tsup && npm run build:css && npm run build:assets",
53
- "build:assets": "powershell -ExecutionPolicy Bypass -File ./scripts/build-assets.ps1",
53
+ "build:assets": "node scripts/build-assets.mjs",
54
54
  "build:css": "node scripts/copy-theme.mjs",
55
55
  "typecheck": "tsc --noEmit",
56
- "prepublishOnly": "npm run typecheck && npm run build",
56
+ "prepublishOnly": "npm run typecheck && npm run build && npm run pack:check",
57
57
  "pack:check": "npm pack --dry-run"
58
58
  },
59
59
  "peerDependencies": {
@@ -62,12 +62,12 @@
62
62
  "tailwindcss": ">=4"
63
63
  },
64
64
  "devDependencies": {
65
- "@tailwindcss/cli": "^4.1.13",
66
65
  "@fontsource/ibm-plex-mono": "^5.2.7",
67
66
  "@fontsource/ibm-plex-sans": "^5.2.8",
68
- "@types/react": "^19.2.16",
67
+ "@tailwindcss/cli": "^4.3.0",
68
+ "@types/react": "^19.2.17",
69
69
  "@types/react-dom": "^19.2.3",
70
- "tailwindcss": "^4.1.13",
70
+ "tailwindcss": "^4.3.0",
71
71
  "tsup": "^8.5.1",
72
72
  "typescript": "^5.9.3"
73
73
  }
@@ -1,47 +0,0 @@
1
- # Tapiz UI Framework Boundary
2
-
3
- This document defines what belongs in `@tapizlabs/ui` and what should remain inside consuming applications.
4
-
5
- ## Belongs In `@tapizlabs/ui`
6
-
7
- The package is the shared UI framework layer for Tapiz frontends. It should contain:
8
-
9
- - design tokens and global theme contract from `theme.css`
10
- - shared font loading
11
- - shared iconography
12
- - reusable React primitives
13
- - generic feedback, modal, table, and form building blocks
14
- - generic page building blocks such as `PageHeader`, `Pagination`, `SearchInput`, `StatusBadge`, and `ActionMenu`
15
- - generic skeleton primitives and reusable loading patterns
16
-
17
- Add something to the package when it is:
18
-
19
- - reused across multiple Tapiz apps
20
- - visually part of the shared Tapiz language
21
- - not tightly coupled to one app's routes, translations, queries, or storage rules
22
-
23
- ## Stays App-Specific
24
-
25
- The following should remain in consumer apps unless they are intentionally generalized:
26
-
27
- - app layout shells like `UILayout`, sidebars, drawers, tenant shells, and role-based navigation
28
- - domain selectors like `SubjectSelector`
29
- - app-specific translation adapters such as wrappers that inject local `i18n` labels
30
- - SEO and document metadata helpers like `SEOHead`
31
- - language/session/settings flows tied to app state or local storage
32
- - page-specific skeleton compositions that represent one screen instead of a reusable primitive
33
- - domain widgets and chart assemblies that depend on product-specific data contracts
34
-
35
- ## Current Intentional App Adapters
36
-
37
- As of this migration, a few local adapters remain by design in `tapiz-reactjs-ui`:
38
-
39
- - `SearchInput` wrapper for localized placeholder and clear label
40
- - `Pagination` wrapper for localized labels
41
- - `StatusBadge` wrapper for attendance/admin status mapping
42
-
43
- These wrappers are acceptable because they adapt shared framework primitives to app-level language and domain semantics without forking the visual system.
44
-
45
- ## Rule Of Thumb
46
-
47
- If removing product data, routing, and translation concerns still leaves a useful component, it probably belongs in `@tapizlabs/ui`.