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
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).
213
+
214
+
[](#demos-and-development)
215
+
216
+
## Demos and Development
217
+
218
+
219
+
### Repo Setup
220
+
221
+
The repo uses submodules. If you did not clone with ` --recursive` then you need to call
222
+
```
223
+
git submodule update --init
224
+
```
225
+
226
+
The package manager used to install and link dependencies must be `pnpm` or `yarn`. `npm` wont work.
227
+
228
+
To develop and test:
229
+
if you use `yarn` then run `yarn`
230
+
if you use `pnpm` then run `pnpm i`
231
+
232
+
**Interactive Menu:**
233
+
234
+
To start the interactive menu, run `npm start` (or `yarn start` or `pnpm start`). This will list all of the commonly used scripts.
235
+
236
+
### Build
237
+
238
+
```bash
239
+
npm run build.all
240
+
```
241
+
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`
242
+
243
+
### Demos
244
+
245
+
```bash
246
+
npm run demo.[ng|react|svelte|vue].[ios|android]
247
+
248
+
npm run demo.svelte.ios # Example
249
+
```
250
+
251
+
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]`
252
+
Instead you work in `demo-snippets/[ng|react|svelte|vue]`
253
+
You can start from the `install.ts` of each flavor to see how to register new demos
254
+
255
+
256
+
[](#contributing)
257
+
258
+
## Contributing
259
+
260
+
### Update repo
261
+
262
+
You can update the repo files quite easily
263
+
264
+
First update the submodules
265
+
266
+
```bash
267
+
npm run update
268
+
```
269
+
270
+
Then commit the changes
271
+
Then update common files
272
+
273
+
```bash
274
+
npm run sync
275
+
```
276
+
Then you can run `yarn|pnpm`, commit changed files if any
277
+
278
+
### Update readme
279
+
```bash
280
+
npm run readme
281
+
```
282
+
283
+
### Update doc
284
+
```bash
285
+
npm run doc
286
+
```
287
+
288
+
### Publish
289
+
290
+
The publishing is completely handled by `lerna` (you can add `-- --bump major` to force a major release)
291
+
Simply run
292
+
```shell
293
+
npm run publish
294
+
```
295
+
296
+
### modifying submodules
297
+
298
+
The repo uses https:// for submodules which means you won't be able to push directly into the submodules.
299
+
One easy solution is t modify `~/.gitconfig` and add
0 commit comments