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: webui-webpage/README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ To run the build, clone this repo and open a command line in the `webui-webpage`
21
21
// on Windows
22
22
gradlew build
23
23
24
-
// on linux/osx
24
+
// on linux/macOS
25
25
./gradlew build
26
26
```
27
27
@@ -31,23 +31,23 @@ This will produce a `.modl` file in the `build` directory, which can be installe
31
31
32
32
This project uses a number of build tools in order to complete the various parts of its assembly. It's important to note that these tools are just some example options. You may use any tool you want (or no tool at all). These examples use:
33
33
34
-
*[Gradle](https://gradle.org/)- the primary build tool. Most tasks executed in a typical workflow are gradle tasks.
34
+
*[Gradle](https://gradle.org/)— the primary build tool. Most tasks executed in a typical workflow are gradle tasks.
35
35
and 'packages' in the same git/hg repository without having to do a lot of complicated symlinking/publishing to pull in changes from one project to another. It's mostly useful from the commandline, outside of Gradle.
36
-
*[yarn](https://yarnpkg.com/)- is a JavaScript dependency (package) manager that provides a number of improvements
36
+
*[yarn](https://yarnpkg.com/)— is a JavaScript dependency (package) manager that provides a number of improvements
37
37
over npm, though it shares many of the same commands and api. Much like Ivy or Maven, yarn is used to resolve and download dependencies hosted on remotely hosted repositories. Inductive Automation publishes our own dependencies through the
38
38
same nexus repository system we use for other sdk artifacts. To correctly resolve the Inductive Automation node packages,
39
39
an `.npmrc` file needs to be added to the front end projects to tell yarn/npm where to find packages in the `@inductiveautomation` namespace. You will find examples of these in the `web-ui/` directory.
40
-
*[Typescript](https://www.typescriptlang.org/)- the language used to write the front end parts. TypeScript is not required but is strongly recommended. TypeScript can be thought of as modern JavaScript with types added (though this is a simplification). The addition of types to JS results in a far better developer experience through much better tooling
40
+
*[TypeScript](https://www.typescriptlang.org/)— the language used to write the front end parts. TypeScript is not required but is strongly recommended. TypeScript can be thought of as modern JavaScript with types added (though this is a simplification). The addition of types to JS results in a far better developer experience through much better tooling
41
41
support. This can improve maintainability, refactoring, code navigation, bug discovery, etc. TypeScript has its own compiler which emits JavaScript. This compiler is frequently paired with other build tools in a way that it emits the JavaScript, but
42
42
other tools handle the actual bundling of assets, CSS, and other supporting dependencies. Think of TypeScript as the
43
43
java compiler without jars or resources. It just takes TypeScript files in, and emits the JavaScript files.
44
-
*[Webpack](https://webpack.js.org/)- the 'bundler' that we use to take the JavaScript emitted by the TypeScript compiler and turn it into an actual package that includes the necessary assets, dependencies, generates sourcemaps, etc.
44
+
*[Webpack](https://webpack.js.org/)— the 'bundler' that we use to take the JavaScript emitted by the TypeScript compiler and turn it into an actual package that includes the necessary assets, dependencies, generates sourcemaps, etc.
45
45
46
46
47
47
## How it works
48
48
1. The React component that represents your page will need to be bundled into a single UMD JS file.
49
49
- We use webpack in this example.
50
-
- This example uses Gradle to download tools necessary to build the project (node, yarn and NPM) and then runs a yarn install to install all of the dependencies listed in the package.json. After this is complete, it will use the webpack.config.js file to build the JS bundle and place it in proper location.
50
+
- This example uses Gradle to download tools necessary to build the project (node, yarn and NPM) and then runs a yarn install to install all the dependencies listed in the package.json. After this is complete, it will use the webpack.config.js file to build the JS bundle and place it in proper location.
51
51
52
52
53
53
2. The file will need to be served on the gateway using the Module Resource API.
0 commit comments