You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!-- ⚠️ This README has been generated from the file(s) "blueprint.md" ⚠️-->
2
-
[](#demos-and-development)
3
-
4
-
## Demos and Development
5
-
6
-
7
-
### Repo Setup
8
-
9
-
The repo uses submodules. If you did not clone with ` --recursive` then you need to call
10
-
```
11
-
git submodule update --init
12
-
```
13
-
14
-
The package manager used to install and link dependencies must be `pnpm` or `yarn`. `npm` wont work.
15
-
16
-
To develop and test:
17
-
if you use `yarn` then run `yarn`
18
-
if you use `pnpm` then run `pnpm i`
19
-
20
-
**Interactive Menu:**
21
-
22
-
To start the interactive menu, run `npm start` (or `yarn start` or `pnpm start`). This will list all of the commonly used scripts.
23
-
24
-
### Build
25
-
26
-
```bash
27
-
npm run build.all
28
-
```
29
-
30
-
### Demos
31
-
32
-
```bash
33
-
npm run demo.[ng|react|svelte|vue].[ios|android]
34
-
35
-
npm run demo.svelte.ios # Example
36
-
```
37
-
38
-
39
-
[](#contributing)
40
-
41
-
## Contributing
42
-
43
-
### Update repo
44
-
45
-
You can update the repo files quite easily
46
-
47
-
First update the submodules
48
-
49
-
```bash
50
-
npm run update
51
-
```
52
-
53
-
Then commit the changes
54
-
Then update common files
55
-
56
-
```bash
57
-
npm run sync
58
-
```
59
-
Then you can run `yarn|pnpm`, commit changed files if any
60
-
61
-
### Update readme
62
-
```bash
63
-
npm run readme
64
-
```
65
-
66
-
### Update doc
67
-
```bash
68
-
npm run doc
69
-
```
70
-
71
-
### Publish
72
-
73
-
The publishing is completely handled by `lerna` (you can add `-- --bump major` to force a major release)
74
-
Simply run
75
-
```shell
76
-
npm run publish
77
-
```
78
-
<br><br><!-- ⚠️ This README has been generated from the file(s) "blueprint.md" ⚠️-->
1
+
<!-- ⚠️ This README has been generated from the file(s) "blueprint.md" ⚠️--><!-- ⚠️ This README has been generated from the file(s) "blueprint.md" ⚠️-->
WARNING: it seems `yarn build.all` wont always work (not finding binaries in `node_modules/.bin`) which is why the doc explicitly uses `npm run`
1131
+
1132
+
### Demos
1133
+
1134
+
```bash
1135
+
npm run demo.[ng|react|svelte|vue].[ios|android]
1136
+
1137
+
npm run demo.svelte.ios # Example
1185
1138
```
1186
1139
1187
-
**Install Dependencies:**
1140
+
Demo setup is a bit special in the sense that if you want to modify/add demos you dont work directly in `demo-[ng|react|svelte|vue]`
1141
+
Instead you work in `demo-snippets/[ng|react|svelte|vue]`
1142
+
You can start from the `install.ts` of each flavor to see how to register new demos
1143
+
1144
+
1145
+
[](#contributing)
1146
+
1147
+
1148
+
[](#contributing)
1149
+
1150
+
## Contributing
1151
+
1152
+
### Update repo
1153
+
1154
+
You can update the repo files quite easily
1155
+
1156
+
First update the submodules
1157
+
1158
+
```bash
1159
+
npm run update
1160
+
```
1161
+
1162
+
Then commit the changes
1163
+
Then update common files
1164
+
1165
+
```bash
1166
+
npm run sync
1167
+
```
1168
+
Then you can run `yarn|pnpm`, commit changed files if any
1169
+
1170
+
### Update readme
1171
+
```bash
1172
+
npm run readme
1173
+
```
1174
+
1175
+
### Update doc
1188
1176
```bash
1189
-
npm i # or 'yarn install' or 'pnpm install'
1177
+
npm run doc
1178
+
```
1179
+
1180
+
### Publish
1181
+
1182
+
The publishing is completely handled by `lerna` (you can add `----bump major` to force a major release)
1183
+
Simply run
1184
+
```shell
1185
+
npm run publish
1186
+
```
1187
+
1188
+
### modifying submodules
1189
+
1190
+
The repo uses https:// for submodules which means you won't be able to push directly into the submodules.
1191
+
One easy solution is t modify `~/.gitconfig` and add
1192
+
```
1193
+
[url "ssh://git@github.com/"]
1194
+
pushInsteadOf = https://github.com/
1195
+
```
1196
+
1197
+
1198
+
[](#questions)
1199
+
1200
+
1201
+
[](#questions)
1202
+
1203
+
## Questions
1204
+
1205
+
If you have any questions/issues/comments please feel free to create an issue or start a conversation in the [NativeScript Community Discord](https://nativescript.org/discord).
1206
+
1207
+
1208
+
[](#demos-and-development)
1209
+
1210
+
## Demos and Development
1211
+
1212
+
1213
+
### Repo Setup
1214
+
1215
+
The repo uses submodules. If you did not clone with `--recursive` then you need to call
1190
1216
```
1217
+
git submodule update --init
1218
+
```
1219
+
1220
+
The package manager used to install and link dependencies must be `pnpm` or `yarn`. `npm` wont work.
1221
+
1222
+
To develop and test:
1223
+
if you use `yarn` then run `yarn`
1224
+
if you use `pnpm` then run `pnpm i`
1191
1225
1192
1226
**Interactive Menu:**
1193
1227
@@ -1196,10 +1230,9 @@ To start the interactive menu, run `npm start` (or `yarn start` or `pnpm start`)
1196
1230
### Build
1197
1231
1198
1232
```bash
1199
-
npm run build
1200
-
1201
-
npm run build.angular # or for Angular
1233
+
npm run build.all
1202
1234
```
1235
+
WARNING: it seems `yarn build.all` wont always work (not finding binaries in `node_modules/.bin`) which is why the doc explicitly uses `npm run`
1203
1236
1204
1237
### Demos
1205
1238
@@ -1208,12 +1241,63 @@ npm run demo.[ng|react|svelte|vue].[ios|android]
1208
1241
1209
1242
npm run demo.svelte.ios # Example
1210
1243
```
1244
+
1245
+
Demo setup is a bit special in the sense that if you want to modify/add demos you dont work directly in `demo-[ng|react|svelte|vue]`
1246
+
Instead you work in `demo-snippets/[ng|react|svelte|vue]`
1247
+
You can start from the `install.ts` of each flavor to see how to register new demos
1248
+
1211
1249
1212
-
[](#questions)
1250
+
[](#contributing)
1213
1251
1252
+
## Contributing
1253
+
1254
+
### Update repo
1255
+
1256
+
You can update the repo files quite easily
1257
+
1258
+
First update the submodules
1259
+
1260
+
```bash
1261
+
npm run update
1262
+
```
1263
+
1264
+
Then commit the changes
1265
+
Then update common files
1266
+
1267
+
```bash
1268
+
npm run sync
1269
+
```
1270
+
Then you can run `yarn|pnpm`, commit changed files if any
1271
+
1272
+
### Update readme
1273
+
```bash
1274
+
npm run readme
1275
+
```
1276
+
1277
+
### Update doc
1278
+
```bash
1279
+
npm run doc
1280
+
```
1281
+
1282
+
### Publish
1283
+
1284
+
The publishing is completely handled by `lerna` (you can add `----bump major` to force a major release)
1285
+
Simply run
1286
+
```shell
1287
+
npm run publish
1288
+
```
1289
+
1290
+
### modifying submodules
1291
+
1292
+
The repo uses https:// for submodules which means you won't be able to push directly into the submodules.
1293
+
One easy solution is t modify `~/.gitconfig` and add
1294
+
```
1295
+
[url "ssh://git@github.com/"]
1296
+
pushInsteadOf = https://github.com/
1297
+
```
1214
1298
1215
1299
[](#questions)
1216
1300
1217
1301
## Questions
1218
1302
1219
-
If you have any questions/issues/comments please feel free to create an issue or start a conversation in the [NativeScript Community Discord](https://nativescript.org/discord).
1303
+
If you have any questions/issues/comments please feel free to create an issue or start a conversation in the [NativeScript Community Discord](https://nativescript.org/discord).
0 commit comments