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
{{ message }}
This repository was archived by the owner on Jun 7, 2021. It is now read-only.
@@ -41,6 +50,10 @@ A Webpack Starter kit featuring:
41
50
* TS quality/style checks (TSLint)
42
51
* TS code documentation generation (TSDoc)
43
52
* development and production configurations
53
+
* optimizations for production (minification, compression, ...)
54
+
* security best practices
55
+
* Content Security Policy (CSP)
56
+
* ...
44
57
* ...
45
58
46
59
Check out the [change log](CHANGELOG.MD)
@@ -54,29 +67,23 @@ Note that this starter kit is derived from the Angular 2 Starter Kit: https://gi
54
67
Check out the issues/labels & milestones to get an idea of what's next. For existing features, refer to the previous section.
55
68
56
69
## Installation
57
-
...
70
+
First of all, make sure that you have installed NodeJS & npm: https://nodejs.org/en/.
58
71
59
-
## Upgrade
60
-
Check out the [upgrade](UPGRADE.MD) page
61
-
62
-
## Frequently Asked Questions (FAQ)
63
-
### Proxy
64
-
If you are behind a corporate proxy, you should ensure that your configuration allows you to work correctly.
72
+
Two approaches:
73
+
* clone this repository: `git clone https://github.com/dsebastien/angularjs-webpack-starter.git`
74
+
* download a zip: https://github.com/dsebastien/angularjs-webpack-starter/archive/master.zip
65
75
66
-
First, you should be able to configure the `HTTP_PROXY` and `HTTPS_PROXY` in your environment so that all CLI tools (e.g., git, typings, ...) can go through the proxy.
76
+
Now you can download all the necessary dependencies using the setup script: `npm run setup`.
67
77
68
-
Don't forget to also define the `NO_PROXY` variable to avoid going through the proxy for local resources (e.g., localhost, local domains, etc).
78
+
Finally, you can start the development server using `npm start`.
69
79
70
-
Note that the .typingsrc file is there to avoid issues caused by SSL termination that is often done in corporate environments. Note that the configuration we provide is INSECURE as it just disables certificate checks. Rather, you should adapt the .typingsrc configuration file so that it continues to check the certificate chain but accepts self-signed certificates generated by your company. Refer to the documentation of typings for more details about the possibilities: https://github.com/typings/typings
80
+
Check out the scripts section below for more information about the available commands.
71
81
72
-
If the above does not work in your case, then check to make sure that the user agents are allowed through the proxy. Some corporate environments filter Web access to specific user agents (e.g., IE). The following user agents should be allowed through:
73
-
* npm/
74
-
* node/
75
-
* git/
76
-
* typings/
82
+
## Upgrade
83
+
Check out the [upgrade](UPGRADE.MD) page
77
84
78
-
## Build tasks
79
-
*`npm run setup`: install typings and project dependencies
85
+
## Scripts
86
+
*`npm run setup`: install required global dependencies and project dependencies
80
87
*`npm start`: start the development server
81
88
*`npm run start:hmr`: start the development server with Hot Module Replacement enabled
82
89
*`npm run build:prod`: build the production version (in /dist)
@@ -106,6 +113,22 @@ If the above does not work in your case, then check to make sure that the user a
106
113
*`npm run webdriver:start`: start the Webdriver Manager
107
114
*`npm run webdriver:update`: update Webdriver
108
115
116
+
## Frequently Asked Questions (FAQ)
117
+
### Proxy
118
+
If you are behind a corporate proxy, you should ensure that your configuration allows you to work correctly.
119
+
120
+
First, you should be able to configure the `HTTP_PROXY` and `HTTPS_PROXY` in your environment so that all CLI tools (e.g., git, typings, ...) can go through the proxy.
121
+
122
+
Don't forget to also define the `NO_PROXY` variable to avoid going through the proxy for local resources (e.g., localhost, local domains, etc).
123
+
124
+
Note that the .typingsrc file is there to avoid issues caused by SSL termination that is often done in corporate environments. Note that the configuration we provide is INSECURE as it just disables certificate checks. Rather, you should adapt the .typingsrc configuration file so that it continues to check the certificate chain but accepts self-signed certificates generated by your company. Refer to the documentation of typings for more details about the possibilities: https://github.com/typings/typings
125
+
126
+
If the above does not work in your case, then check to make sure that the user agents are allowed through the proxy. Some corporate environments filter Web access to specific user agents (e.g., IE). The following user agents should be allowed through:
0 commit comments