frosty 0.0.101 → 0.0.102
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 +23 -0
- package/package.json +1 -1
- package/packages/frosty-cli/bin/frosty.sh +3 -0
package/README.md
CHANGED
|
@@ -43,6 +43,29 @@ export default App;
|
|
|
43
43
|
|
|
44
44
|
See the [comprehensive documentation](./docs) for detailed guides, API reference, and advanced usage patterns.
|
|
45
45
|
|
|
46
|
+
## Application Entry Point
|
|
47
|
+
|
|
48
|
+
Your application entry point (the main file you pass to Frosty CLI) must export your root component as the **default export**. This is required for Frosty to properly identify and render your application.
|
|
49
|
+
|
|
50
|
+
```tsx
|
|
51
|
+
// app.tsx or app.js
|
|
52
|
+
import { useState } from 'frosty';
|
|
53
|
+
|
|
54
|
+
function MyApp() {
|
|
55
|
+
// Your application logic here
|
|
56
|
+
return <div>Hello World!</div>;
|
|
57
|
+
}
|
|
58
|
+
|
|
59
|
+
// Required: Export your root component as default
|
|
60
|
+
export default MyApp;
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
This default export pattern ensures that:
|
|
64
|
+
- Frosty CLI can automatically detect your application component
|
|
65
|
+
- Server-side rendering (SSR) works correctly
|
|
66
|
+
- Client-side hydration functions properly
|
|
67
|
+
- Your app integrates seamlessly with the Frosty build system
|
|
68
|
+
|
|
46
69
|
## Usage
|
|
47
70
|
|
|
48
71
|
To run your app with Frosty CLI using `npx`:
|
package/package.json
CHANGED