pittaya 0.0.6 → 0.0.9
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 +60 -0
- package/dist/index.js +797 -241
- package/dist/index.js.map +1 -1
- package/package.json +57 -53
package/README.md
CHANGED
|
@@ -86,6 +86,66 @@ npx pittaya update --all --yes
|
|
|
86
86
|
npx pittaya update button --force
|
|
87
87
|
```
|
|
88
88
|
|
|
89
|
+
## list
|
|
90
|
+
|
|
91
|
+
Use the `list` command to view all available and installed components.
|
|
92
|
+
|
|
93
|
+
The `list` command shows all components from the registry organized by category with installation status.
|
|
94
|
+
|
|
95
|
+
```bash
|
|
96
|
+
npx pittaya list
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
### Example
|
|
100
|
+
|
|
101
|
+
```bash
|
|
102
|
+
# List all components
|
|
103
|
+
npx pittaya list
|
|
104
|
+
|
|
105
|
+
# List only installed components
|
|
106
|
+
npx pittaya list --installed
|
|
107
|
+
|
|
108
|
+
# List only available components
|
|
109
|
+
npx pittaya list --available
|
|
110
|
+
|
|
111
|
+
# JSON output for programmatic use
|
|
112
|
+
npx pittaya list --json
|
|
113
|
+
```
|
|
114
|
+
|
|
115
|
+
## debug
|
|
116
|
+
|
|
117
|
+
Use the `debug` command to diagnose component installation issues.
|
|
118
|
+
|
|
119
|
+
The `debug` command helps identify why a component is not being detected as installed, showing expected file paths and actual file locations.
|
|
120
|
+
|
|
121
|
+
```bash
|
|
122
|
+
npx pittaya debug --component [component]
|
|
123
|
+
```
|
|
124
|
+
|
|
125
|
+
### Example
|
|
126
|
+
|
|
127
|
+
```bash
|
|
128
|
+
# Debug general project setup
|
|
129
|
+
npx pittaya debug
|
|
130
|
+
|
|
131
|
+
# Debug specific component
|
|
132
|
+
npx pittaya debug --component installation-section
|
|
133
|
+
```
|
|
134
|
+
|
|
135
|
+
**What it shows:**
|
|
136
|
+
- Project structure detection (src/ vs root)
|
|
137
|
+
- Resolved alias paths
|
|
138
|
+
- Expected file locations
|
|
139
|
+
- Actual file existence
|
|
140
|
+
- Installation status
|
|
141
|
+
- Similar files found (helps identify naming mismatches)
|
|
142
|
+
|
|
143
|
+
**Common issues it helps diagnose:**
|
|
144
|
+
- File name mismatches (e.g., `InstallationSection.tsx` vs `installation-section.tsx`)
|
|
145
|
+
- Wrong directory structure (e.g., missing `src/` folder)
|
|
146
|
+
- Incorrect `components.json` aliases
|
|
147
|
+
- Components installed in unexpected locations
|
|
148
|
+
|
|
89
149
|
## Documentation
|
|
90
150
|
|
|
91
151
|
Visit https://pittaya-ui.vercel.app to view the documentation.
|