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
+2-2
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ Fundamentally, the repository is a NodeJS project, so it contains the standard N
43
43
*`/buildScripts/` — the folder containing the scripts used to build the bundled versions of the module and the module's documentation site, including its UML diagrams.
44
44
*`/dist/` — the target folder into which the build scripts will publish the bundled versions of the module, ready for distribution. **Do not edit the contents of this folder directly!**
45
45
*`/docs/` — the target folder into which the build scripts will publish the generated documentation. This folder's contents will be published at the project's website. **Do not edit the contents of this folder directly!**
46
-
*`/docs-other/` — the folder containing the parts of the documentation that are not generated from documentation comments.
46
+
*`/docs-other/` — the folder containing the parts of the documentation that are not generated from documentation comments. This folder also includes a **README** file that includes instructions on how to get started.
47
47
*`/docs-other/diagrams/` — the target folder into which the build scripts will publish PNG versions of the project's UML diagrams. The source for these diagrams are the Mermaid files in `/src-diagrams/`. **Do not edit the contents of this folder directly!**
48
48
*`/src/` — the folder containing the module's source code and test suite.
49
49
*`/src-diagrams/` — the folder containing the source code for the UML diagrams describing the module. These files will be in Mermaid format and will be transformed into PNG files in `/docs-other/diagrams/` by a build script.
@@ -99,7 +99,7 @@ This module is versioned using the Semantic Versioning System, or [SemVer](https
99
99
* Until the project reaches version 1.0.0 any contributions that make progress towards the initial implementation can be merged into the `main` branch
100
100
* Once the project reaches version 1.0.0 all contributions must be *atomic*, i.e. must be a complete unit. For code contributions that means:
101
101
1. All tests must pass
102
-
2.News tests must be included to cover all new functionality
102
+
2.New tests must be included to cover all new functionality
103
103
3. The Doc Comments must be updated as appropriate
Copy file name to clipboardExpand all lines: docs-other/README.md
+9-3
Original file line number
Diff line number
Diff line change
@@ -14,9 +14,15 @@ npm run cov # run the tests again but this time with test coverage. Coverage sho
14
14
15
15
## Hot build and reload
16
16
17
-
The easiest way to achieve this is opening 2 Terminal windows in the root directory of this project.
17
+
The easiest way to achieve this is opening a Terminal window in the root directory of this project.
18
18
19
-
In one Terminal enter `npm run watch` to start the automatic build of Webpack. Webpack watches for changes in your files and automatically starts the build.
20
-
In the other Terminal enter `npm run start` to start a local webserver that automatically restarts when there is a new build.
19
+
In the Terminal enter `npm run start` to start a local webserver.
20
+
This script will watch for any change in any file, and automatically start a
21
+
a webpack build and restarts the server when there is a new build.
21
22
22
23
In your webbrowser enter `http://localhost:8080` to find the webapp.
24
+
25
+
## JS Docs
26
+
27
+
If you want to see the docs locally, run `npm run docs`.
28
+
You will find them in /dist/docs and also through the webapp in the Actions menu.
0 commit comments