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
Copy file name to clipboardExpand all lines: README.md
+64-2Lines changed: 64 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,69 @@ npm start
14
14
-@nativescript/canvas-polyfill
15
15
-@nativescript/canvas-three
16
16
17
+
# How to use?
17
18
18
-
## License
19
+
This workspace manages the suite of plugins listed above.
20
+
21
+
In general, when in doubt with what to do, just `npm start`.
22
+
23
+
```bash
24
+
npm run setup
25
+
npm start
26
+
27
+
// Ensure all plugins build properly first
28
+
>type"build-all" (and hit ENTER)
29
+
```
30
+
31
+
If you don't build all the plugins, you will at least need to build `localize` to run the demos because it contains `hooks` that need to be built first.
32
+
33
+
If building only `localize`, type: `npm start` > `localize` (this will narrow down menu to `@nativescript.localize.build`) and then hit 'enter'. You can now run the demo apps.
34
+
35
+
In general, when in doubt with what to do, just `npm start`.
36
+
37
+
## How to add a new package to workspace?
38
+
39
+
```bash
40
+
npm run add
41
+
```
42
+
43
+
At the prompt, enter the name of the new package.
44
+
45
+
- This adds a plugin harness in `packages` with the necessary boilerplate to just start developing
46
+
- Updates all demo app flavors to support demoing the new package
47
+
- Adds shared code in `tools/demo` where you can write demo code **once** and share across all demo flavors
48
+
- Updates build tooling to support the new package
49
+
- Updates the `npm start` interactive display
50
+
- Updates the README here to list the new package
51
+
52
+
## How to add Angular compatibility to a package
53
+
54
+
```bash
55
+
npm run add-angular
56
+
```
57
+
58
+
At the prompt, enter the name of the package to add an `angular` folder to it with the necessary boilerplate to provide Angular support to the package.
59
+
60
+
## How to focus on just 1 package to develop in isolation
61
+
62
+
```bash
63
+
npm start
64
+
```
65
+
66
+
- Choose the focus commands for the package you wish to focus on and hit enter.
67
+
- All the demo app's will be updated to isolate that 1 package and for supported IDE's (currently VS Code), the source code will also become isolated in the workspace.
68
+
69
+
Note: _good to always clean the demo you plan to run after focusing. (You can clean any demo from `npm start` as well)_
70
+
71
+
## How to publish packages?
72
+
73
+
```bash
74
+
npm run publish-packages
75
+
```
76
+
77
+
- You will be prompted for the package names to publish. Leaving blank and hitting enter will publish them all.
78
+
- You will then be prompted for the version to use. Leaving blank will auto bump the patch version (it also handles prerelease types like alpha, beta, rc, etc. - It even auto tags the corresponding prelease type on npm).
0 commit comments