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).
508
+
509
+
[](#demos-and-development)
510
+
511
+
## Demos and Development
512
+
513
+
514
+
### Repo Setup
515
+
516
+
The repo uses submodules. If you did not clone with ` --recursive` then you need to call
517
+
```
518
+
git submodule update --init
519
+
```
520
+
521
+
The package manager used to install and link dependencies must be `pnpm` or `yarn`. `npm` wont work.
522
+
523
+
To develop and test:
524
+
if you use `yarn` then run `yarn`
525
+
if you use `pnpm` then run `pnpm i`
526
+
527
+
**Interactive Menu:**
528
+
529
+
To start the interactive menu, run `npm start` (or `yarn start` or `pnpm start`). This will list all of the commonly used scripts.
530
+
531
+
### Build
532
+
533
+
```bash
534
+
npm run build.all
535
+
```
536
+
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`
537
+
538
+
### Demos
539
+
540
+
```bash
541
+
npm run demo.[ng|react|svelte|vue].[ios|android]
542
+
543
+
npm run demo.svelte.ios # Example
544
+
```
545
+
546
+
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]`
547
+
Instead you work in `demo-snippets/[ng|react|svelte|vue]`
548
+
You can start from the `install.ts` of each flavor to see how to register new demos
549
+
550
+
551
+
[](#contributing)
552
+
553
+
## Contributing
554
+
555
+
### Update repo
556
+
557
+
You can update the repo files quite easily
558
+
559
+
First update the submodules
560
+
561
+
```bash
562
+
npm run update
563
+
```
564
+
565
+
Then commit the changes
566
+
Then update common files
567
+
568
+
```bash
569
+
npm run sync
570
+
```
571
+
Then you can run `yarn|pnpm`, commit changed files if any
572
+
573
+
### Update readme
574
+
```bash
575
+
npm run readme
576
+
```
577
+
578
+
### Update doc
579
+
```bash
580
+
npm run doc
581
+
```
582
+
583
+
### Publish
584
+
585
+
The publishing is completely handled by `lerna` (you can add `-- --bump major` to force a major release)
586
+
Simply run
587
+
```shell
588
+
npm run publish
589
+
```
590
+
591
+
### modifying submodules
592
+
593
+
The repo uses https:// for submodules which means you won't be able to push directly into the submodules.
594
+
One easy solution is t modify `~/.gitconfig` and add
0 commit comments