vaderjs-native 1.0.5 → 1.0.7
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 → README.md} +1 -5
- package/package.json +1 -1
package/{README.MD → README.md}
RENAMED
|
@@ -1,7 +1,3 @@
|
|
|
1
|
-
Ah! Got it — since this is **VaderNative** (focused on building native mobile apps with Bun/Vader.js), we should tweak your README to emphasize **native app development**, Android/iOS support, native components, and speed, rather than generic web usage. Here's a polished, VaderNative-focused version:
|
|
2
|
-
|
|
3
|
-
---
|
|
4
|
-
|
|
5
1
|
<p align="center">
|
|
6
2
|
<a href="https://vader-js.pages.dev">
|
|
7
3
|
<picture>
|
|
@@ -83,7 +79,7 @@ VaderNative uses **file-based routing** inspired by Next.js. Simply create a `pa
|
|
|
83
79
|
|
|
84
80
|
## 🛠 Configuration
|
|
85
81
|
|
|
86
|
-
Create a `config.ts` at your project root to define your app’s metadata, platform settings, and plugins:
|
|
82
|
+
Create a `vader.config.ts` at your project root to define your app’s metadata, platform settings, and plugins:
|
|
87
83
|
|
|
88
84
|
```ts
|
|
89
85
|
import defineConfig from "vaderjs-native/config";
|