Skip to content

Commit 1435c7a

Browse files
committed
chore: readme
1 parent 3f933b3 commit 1435c7a

File tree

2 files changed

+127
-0
lines changed

2 files changed

+127
-0
lines changed

README.md

Lines changed: 112 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,7 @@
5555
* [Update readme ](#update-readme-)
5656
* [Update doc ](#update-doc-)
5757
* [Publish](#publish)
58+
* [modifying submodules](#modifying-submodules)
5859
* [Questions](#questions)
5960

6061

@@ -133,6 +134,7 @@ To start the interactive menu, run `npm start` (or `yarn start` or `pnpm start`)
133134
```bash
134135
npm run build.all
135136
```
137+
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`
136138

137139
### Demos
138140

@@ -142,6 +144,10 @@ npm run demo.[ng|react|svelte|vue].[ios|android]
142144
npm run demo.svelte.ios # Example
143145
```
144146

147+
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]`
148+
Instead you work in `demo-snippets/[ng|react|svelte|vue]`
149+
You can start from the `install.ts` of each flavor to see how to register new demos
150+
145151

146152
[](#contributing)
147153

@@ -186,9 +192,115 @@ Simply run
186192
npm run publish
187193
```
188194

195+
### modifying submodules
196+
197+
The repo uses https:// for submodules which means you won't be able to push directly into the submodules.
198+
One easy solution is t modify `~/.gitconfig` and add
199+
```
200+
[url "ssh://[email protected]/"]
201+
pushInsteadOf = https://github.com/
202+
```
203+
204+
205+
[](#questions)
206+
189207

190208
[](#questions)
191209

210+
## Questions
211+
212+
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
300+
```
301+
[url "ssh://[email protected]/"]
302+
pushInsteadOf = https://github.com/
303+
```
192304

193305
[](#questions)
194306

packages/ui-carto/README.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,7 @@
5252
* [Update readme ](#update-readme-)
5353
* [Update doc ](#update-doc-)
5454
* [Publish](#publish)
55+
* [modifying submodules](#modifying-submodules)
5556
* [Questions](#questions)
5657

5758

@@ -115,6 +116,7 @@ To start the interactive menu, run `npm start` (or `yarn start` or `pnpm start`)
115116
```bash
116117
npm run build.all
117118
```
119+
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`
118120

119121
### Demos
120122

@@ -124,6 +126,10 @@ npm run demo.[ng|react|svelte|vue].[ios|android]
124126
npm run demo.svelte.ios # Example
125127
```
126128

129+
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]`
130+
Instead you work in `demo-snippets/[ng|react|svelte|vue]`
131+
You can start from the `install.ts` of each flavor to see how to register new demos
132+
127133

128134
[](#contributing)
129135

@@ -165,6 +171,15 @@ Simply run
165171
npm run publish
166172
```
167173

174+
### modifying submodules
175+
176+
The repo uses https:// for submodules which means you won't be able to push directly into the submodules.
177+
One easy solution is t modify `~/.gitconfig` and add
178+
```
179+
[url "ssh://[email protected]/"]
180+
pushInsteadOf = https://github.com/
181+
```
182+
168183

169184
[](#questions)
170185

0 commit comments

Comments
 (0)