angular-cn/integration/ngcc/test.sh

#!/bin/bash

set -e -x

PATH=$PATH:$(npm bin)

ivy-ngcc --help

# node --inspect-brk $(npm bin)/ivy-ngcc -f esm2015
ivy-ngcc

# Did it add the appropriate build markers?

# - fesm2015
ls node_modules/@angular/common | grep __modified_by_ngcc_for_fesm2015
if [[ $? != 0 ]]; then exit 1; fi
# - esm2015
ls node_modules/@angular/common | grep __modified_by_ngcc_for_esm2015
if [[ $? != 0 ]]; then exit 1; fi

ngc -p tsconfig-app.json

# Did it compile the main.ts correctly?
grep "directives: \[\S*\.NgIf\]" dist/src/main.js
if [[ $? != 0 ]]; then exit 1; fi
test(ivy): add an integration test for ngcc (#25406) This commit adds an integration test for ngcc, which runs ngcc against most @angular packages. It does not yet make any assertions on the result. PR Close #25406 2018-08-09 09:23:56 -04:00			`#!/bin/bash`

feat(ivy): find all packages to be compiled by ngcc (#25406) PR Close #25406 2018-08-09 08:54:20 -04:00			`set -e -x`
test(ivy): add an integration test for ngcc (#25406) This commit adds an integration test for ngcc, which runs ngcc against most @angular packages. It does not yet make any assertions on the result. PR Close #25406 2018-08-09 09:23:56 -04:00
			`PATH=$PATH:$(npm bin)`

fix(ivy): ngcc should compile entry-points in the correct order (#25862) The compiler should process all an entry-points dependencies before processing that entry-point. PR Close #25862 2018-08-09 10:59:10 -04:00			`ivy-ngcc --help`

			`# node --inspect-brk $(npm bin)/ivy-ngcc -f esm2015`
			`ivy-ngcc`

feat(ivy): implement ngcc build marker (#25557) `ngcc` adds marker files to each folder that has been compiled, containing the version of the ngcc used. When compiling, it will ignore folders that contain these marker files, as long as the version matches. PR Close #25557 2018-08-17 17:00:00 -04:00			`# Did it add the appropriate build markers?`
fix(ivy): ngcc should compile entry-points in the correct order (#25862) The compiler should process all an entry-points dependencies before processing that entry-point. PR Close #25862 2018-08-09 10:59:10 -04:00
			`# - fesm2015`
feat(ivy): implement ngcc build marker (#25557) `ngcc` adds marker files to each folder that has been compiled, containing the version of the ngcc used. When compiling, it will ignore folders that contain these marker files, as long as the version matches. PR Close #25557 2018-08-17 17:00:00 -04:00			`ls node_modules/@angular/common \| grep __modified_by_ngcc_for_fesm2015`
			`if [[ $? != 0 ]]; then exit 1; fi`
fix(ivy): ngcc should compile entry-points in the correct order (#25862) The compiler should process all an entry-points dependencies before processing that entry-point. PR Close #25862 2018-08-09 10:59:10 -04:00			`# - esm2015`
feat(ivy): implement ngcc build marker (#25557) `ngcc` adds marker files to each folder that has been compiled, containing the version of the ngcc used. When compiling, it will ignore folders that contain these marker files, as long as the version matches. PR Close #25557 2018-08-17 17:00:00 -04:00			`ls node_modules/@angular/common \| grep __modified_by_ngcc_for_esm2015`
			`if [[ $? != 0 ]]; then exit 1; fi`

test(ivy): add an integration test for ngcc (#25406) This commit adds an integration test for ngcc, which runs ngcc against most @angular packages. It does not yet make any assertions on the result. PR Close #25406 2018-08-09 09:23:56 -04:00			`ngc -p tsconfig-app.json`

feat(ivy): implement ngcc build marker (#25557) `ngcc` adds marker files to each folder that has been compiled, containing the version of the ngcc used. When compiling, it will ignore folders that contain these marker files, as long as the version matches. PR Close #25557 2018-08-17 17:00:00 -04:00			`# Did it compile the main.ts correctly?`
			`grep "directives: \[\S*\.NgIf\]" dist/src/main.js`
			`if [[ $? != 0 ]]; then exit 1; fi`