I\'m using this angular 4 seed app: https://github.com/2sic/app-tutorial-angular4-hello-dnn
It uses webpack and works fine.
It only seems to serve the dev fi
ng serve
will work as normal, and it doesn't require a prior build. It generates files in memory, and has some additional features like auto reload.
A little tips
so you avoid to install globally
install in your root
npm i http-server
in your package.json
"scripts": {
"pwa": "http-server ./dist"
}
than
npm run pwa
I serve the dist folder with the Angular CLI...
ng serve --prod=true
When true, sets the build configuration to the production target. All builds make use of bundling and limited tree-shaking. A production build also runs limited dead code elimination.
https://angular.io/cli/serve
I tried with http-server by installing it globally
npm install -g http-server
then moved to the dist/project-folder and tried with
http-server -o
output in console
[Fri Sep 13 2019 15:19:57 GMT+0530 (India Standard Time)] "GET /" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132
Safari/537.36"
Then this solution worked with all the steps same but instead of using http-server try angular-http-server
It worked for me.
I use the VS Code extension Live Server.
ng build
which will output the dist/
folder with index.html
dist/
folderAt least for Angular apps, angular-http-server
seems to be a nicer option.
First install it with your prefered package manager, say
npm install angular-http-server -g
or
yarn global add angular-http-server
Then execute it:
angular-http-server --path path/to/dist/folder
Look at the repo for more information about usage.
PS: According the author, it should also work with other SPA frameworks (React, Vue and so forth).
PPS: Do not use angular-http-server
for production, use this solution for testing purposes only.