@mindw1n/webnative 3.0.1 → 3.0.3
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 +2 -1
- package/readme.md +17 -1
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mindw1n/webnative",
|
|
3
3
|
"type": "module",
|
|
4
|
-
"version": "3.0.
|
|
4
|
+
"version": "3.0.3",
|
|
5
5
|
"scripts": {
|
|
6
6
|
"build": "esbuild src/index.ts --bundle --platform=node --format=esm --target=es2020 --outfile=index.js --banner:js=\"#!/usr/bin/env node\" --minify"
|
|
7
7
|
},
|
|
@@ -9,6 +9,7 @@
|
|
|
9
9
|
"webnative": "./index.js"
|
|
10
10
|
},
|
|
11
11
|
"files": [
|
|
12
|
+
"LICENSE",
|
|
12
13
|
"index.js",
|
|
13
14
|
"prebuilds/dist",
|
|
14
15
|
"template",
|
package/readme.md
CHANGED
|
@@ -8,10 +8,12 @@
|
|
|
8
8
|
Build desktop and mobile applications using web technologies you already know.
|
|
9
9
|
No cross-compilation or config hell. No manual dependencies. Just you and your beautiful app.
|
|
10
10
|
|
|
11
|
+
|
|
12
|
+
|
|
11
13
|
## Why webnative?
|
|
12
14
|
|
|
13
15
|
Most cross-platform frameworks make you choose — either great DX or great results.
|
|
14
|
-
Electron ships Chromium (150MB+). Tauri requires Rust. Capacitor
|
|
16
|
+
Electron ships Chromium (150MB+). Tauri requires Rust. Capacitor mostly targets mobile.
|
|
15
17
|
|
|
16
18
|
webnative is different:
|
|
17
19
|
|
|
@@ -51,3 +53,17 @@ webnative handles the switching — you just write your app.
|
|
|
51
53
|
|
|
52
54
|
- Node.js 22+
|
|
53
55
|
- Docker (sometimes needed for cross-compilation)
|
|
56
|
+
|
|
57
|
+
## Contributing to webnative
|
|
58
|
+
|
|
59
|
+
webnative is actively looking for contributors!
|
|
60
|
+
If you're interested in helping out, you can:
|
|
61
|
+
|
|
62
|
+
- Pick up an open issue or suggest a new one
|
|
63
|
+
- Help bring a new platform to life
|
|
64
|
+
- Improve docs or examples
|
|
65
|
+
|
|
66
|
+
To get started, fork the repo, make your changes, and open a PR.
|
|
67
|
+
For bigger changes, open an issue first so we can discuss the direction.
|
|
68
|
+
|
|
69
|
+
All skill levels welcome — if you're curious about how it works, just reach out.
|