fix: pin data table to TanStack Table v8

This commit is contained in:
2026-08-10 11:18:47 +09:00
parent ade3204b4d
commit fd5b7d1998
6 changed files with 8 additions and 4 deletions

View File

@@ -12,6 +12,7 @@ When implementing or changing frontend UI, use this order:
### Installation and Ownership
- Inspect the registry item and its dependencies before installation. Use the shadcn CLI with the approved registry endpoint under `https://ui-registry.kric.com/r/` instead of copying files from `dist/r` manually.
- `kri-data-table` uses the TanStack Table v8 API. Keep `@tanstack/react-table` within the supported `^8.21.3` range and do not upgrade it to v9 until KriUiRegistry provides an explicitly migrated component contract.
- Respect the consumer project's component aliases, target paths, package manager, styling system, React version, and existing design tokens.
- The shadcn workflow copies component source into the consumer repository. After installation, treat that copy as project-owned code; do not assume registry updates propagate automatically.
- Do not overwrite an existing project component without reviewing the diff and confirming that local behavior and accessibility are preserved.

View File

@@ -234,6 +234,7 @@ When implementing or changing frontend UI, use this order:
### Installation and Ownership
- Inspect the registry item and its dependencies before installation. Use the shadcn CLI with the approved registry endpoint under `https://ui-registry.kric.com/r/` instead of copying files from `dist/r` manually.
- `kri-data-table` uses the TanStack Table v8 API. Keep `@tanstack/react-table` within the supported `^8.21.3` range and do not upgrade it to v9 until KriUiRegistry provides an explicitly migrated component contract.
- Respect the consumer project's component aliases, target paths, package manager, styling system, React version, and existing design tokens.
- The shadcn workflow copies component source into the consumer repository. After installation, treat that copy as project-owned code; do not assume registry updates propagate automatically.
- Do not overwrite an existing project component without reviewing the diff and confirming that local behavior and accessibility are preserved.

View File

@@ -41,6 +41,8 @@ kri-layout
kri-dialog
```
`kri-data-table`은 TanStack Table v8 API를 사용하며 `@tanstack/react-table@^8.21.3` 범위를 지원합니다. KriUiRegistry에서 별도의 마이그레이션 버전을 제공하기 전에는 v9으로 올리지 않습니다.
개별 설치 예시:
```powershell

4
package-lock.json generated
View File

@@ -1,12 +1,12 @@
{
"name": "kri-ui-registry",
"version": "0.10.0",
"version": "0.11.5",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "kri-ui-registry",
"version": "0.10.0",
"version": "0.11.5",
"devDependencies": {
"@tanstack/react-table": "^8.21.3",
"@tiptap/extension-color": "^3.27.1",

View File

@@ -1,6 +1,6 @@
{
"name": "kri-ui-registry",
"version": "0.11.4",
"version": "0.11.5",
"private": true,
"description": "KRI internal shadcn UI registry",
"scripts": {

View File

@@ -266,7 +266,7 @@
"table"
],
"dependencies": [
"@tanstack/react-table",
"@tanstack/react-table@^8.21.3",
"lucide-react"
],
"files": [