tynarus / angular-seed Goto Github PK

Looks like source maps are created only for first build then in sequential builds it will not build new .js & .map files leading to errors.
The config is built quite straight forward and I cant understand why this happens.
But for example deleting the .js/.map files manually and then running build again will not re-create the .js/.map files , the only files that are created are the dist bundles.
I have posted a very detailed question about this issue on stackoverflow you can read it here.

Add the ability to build multiple different styles of production environments

• Add DevConfig type file that stores the current environment (local, prod, other prod types)
• Add ability to specify which environment name to use when running prod builds, ie npm run build --env=NONPROD

Add support for Protractor end-to-end testing

Issues with ts-loader not finding nested ts-config.json prompting switch to awesome-typescript-loader

Remove templating engine PugJS

May not seem like an enhancement to some, but PugJS doesn't play terribly well with some of Angular's functionality, so best it be removed.

Add a global, application-wise, SCSS file

Also remove ViewEncapsulation.None from app.component.ts and remove all app-wise css from app.component.scss

Add support for AOT production builds

Due to the many changes made for 2.0.0, the integrity of production builds needs to be investigated further to ensure no defects were introduced.

• Push develop to master
• Create 2.0.0 release tag
• Add release to Github
• Create CHANGELOG file

Investigate any changes needed for the upcoming Angular 5 version

Add a flag to enable/disable unit test coverage reporting to the karma config file.

Currently coverage reporting is stuck to ON in develop, hence this is a bug

Bring vendor.ts up to spec

1 - tsconfig is not in root - so it causes compilaton problems :

https://i.imgur.com/8HPpusN.jpg

2- when running npm run start it does compile :

https://i.imgur.com/tleMeB3.jpg

But at 3000 there is an error :

https://i.imgur.com/4MJL3SU.jpg

here is the small demo project : https://ufile.io/j184w

Is there any way to map the SCSS files so I can see what file produced given CSS rule? Except for global styles, which are excluded from the rule and compiled to the styles file, every component SCSS gets dumped into the tag. Is it possible to avoid that, so Chrome Dev Tools would be able to tell where the rules originate from?