Pete Bacon Darwin a581773887 perf(ivy): ngcc - only find dependencies when targeting a single entry-point (#30525) ...

Previously, ngcc had to walk the entire `node_modules` tree looking for
entry-points, even if it only needed to process a single target entry-point
and its dependencies.

This added up to a few seconds to each execution of ngcc, which is noticeable
when being run via the CLI integration.

Now, if an entry-point target is provided, only that target and its entry-points
are considered rather than the whole folder tree.

PR Close #30525

2019-07-09 09:40:46 -07:00

..

integrationtest

build: fix build failures with worker mode cache and @types/events (#31325)

2019-07-01 14:16:43 -07:00

ngcc

perf(ivy): ngcc - only find dependencies when targeting a single entry-point (#30525)

2019-07-09 09:40:46 -07:00

src

perf(ivy): ngcc - add a cache to the FileSystem (#30525)

2019-07-09 09:40:46 -07:00

test

fix(ivy): handle namespaced imports correctly (#31367)

2019-07-09 09:40:30 -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: upgrade yargs package to 13.1.0 (#29722)

2019-04-26 16:29:29 -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