Alan Agius 46304a4f83 feat(ivy): show error when trying to publish NGCC'd packages (#32031) ... Publishing of NGCC packages should not be allowed. It is easy for a user to publish an NGCC'd version of a library they have workspace libraries which are being used in a workspace application. If a users builds a library and afterwards the application, the library will be transformed with NGCC and since NGCC taints the distributed files that should be published. With this change we use the npm/yarn `prepublishOnly` hook to display and error and abort the process with a non zero error code when a user tries to publish an NGCC version of the package. More info: https://docs.npmjs.com/misc/scripts PR Close #32031		2019-08-08 11:17:38 -07:00
..
integrationtest	build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824)	2019-07-26 15:01:25 -07:00
ngcc	feat(ivy): show error when trying to publish NGCC'd packages (#32031)	2019-08-08 11:17:38 -07:00
src	fix(ivy): speed up ngtsc if project has no templates to check (#31922)	2019-07-31 16:20:38 -07:00
test	build: TypeScript 3.5 upgrade (#31615)	2019-07-25 17:05:23 -07:00
BUILD.bazel	build: fix build failures with worker mode cache and @types/events (#31325)	2019-07-01 14:16:43 -07:00
index.ts	refactor(ivy): implement a virtual file-system layer in ngtsc + ngcc (#30921)	2019-06-25 16:25:24 -07:00
ngtools2.ts	refactor(compiler-cli): expose ngtools api separately (#18978)	2017-08-31 14:37:13 -07:00
package.json	build: TypeScript 3.5 upgrade (#31615)	2019-07-25 17:05:23 -07:00
tsconfig-build.json	perf(ivy): ngcc - only find dependencies when targeting a single entry-point (#30525)	2019-07-09 09:40:46 -07:00
tsconfig.json	perf(ivy): ngcc - only find dependencies when targeting a single entry-point (#30525)	2019-07-09 09:40:46 -07:00