honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/compiler-cli/BUILD.bazel

61 lines
1.5 KiB
Python
Raw Normal View History

build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768
2017-12-06 09:56:49 -05:00
package(default_visibility = ["//visibility:public"])
build: upgrade to rules_nodejs 1.0.0 (first stable release) (#34736) Brings in the fix for stamping which was preventing many targets from getting cached. PR Close #34736
2019-12-28 19:37:59 -05:00
load("//tools:defaults.bzl", "pkg_npm", "ts_library")
build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871) PR Close #28871
2019-02-20 12:54:42 -05:00
load("@npm_bazel_typescript//:index.bzl", "ts_config")
build: update to latest @bazel/typescript (#19277) Switches devmode output of an ng_module to UMD
2017-09-25 15:40:22 -04:00
ts_config(
name = "tsconfig",
src = "tsconfig-build.json",
build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768
2017-12-06 09:56:49 -05:00
deps = ["//packages:tsconfig-build.json"],
build: update to latest @bazel/typescript (#19277) Switches devmode output of an ng_module to UMD
2017-09-25 15:40:22 -04:00
)
build: Bazel builds ngfactories for packages/core (#18289) PR Close #18289
2017-07-21 17:20:34 -04:00
ts_library(
name = "compiler-cli",
build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768
2017-12-06 09:56:49 -05:00
srcs = glob(
[
"*.ts",
"src/**/*.ts",
],
build(compiler-cli): exclude command line scripts from compilation (#21053) PR Close #21053
2017-12-18 00:36:21 -05:00
exclude = [
"src/integrationtest/**/*.ts",
],
build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768
2017-12-06 09:56:49 -05:00
),
tsconfig = ":tsconfig",
build: Bazel builds ngfactories for packages/core (#18289) PR Close #18289
2017-07-21 17:20:34 -04:00
deps = [
build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768
2017-12-06 09:56:49 -05:00
"//packages/compiler",
refactor(ivy): introduce the 'core' package and split apart NgtscProgram (#34887) Previously, NgtscProgram lived in the main @angular/compiler-cli package alongside the legacy View Engine compiler. As a result, the main package depended on all of the ngtsc internal packages, and a significant portion of ngtsc logic lived in NgtscProgram. This commit refactors NgtscProgram and moves the main logic of compilation into a new 'core' package. The new package defines a new API which enables implementers of TypeScript compilers (compilers built using the TS API) to support Angular transpilation as well. It involves a new NgCompiler type which takes a ts.Program and performs Angular analysis and transformations, as well as an NgCompilerHost which wraps an input ts.CompilerHost and adds any extra Angular files. Together, these two classes are used to implement a new NgtscProgram which adapts the legacy api.Program interface used by the View Engine compiler onto operations on the new types. The new NgtscProgram implementation is significantly smaller and easier to reason about. The new NgCompilerHost replaces the previous GeneratedShimsHostWrapper which lived in the 'shims' package. A new 'resource' package is added to support the HostResourceLoader which previously lived in the outer compiler package. As a result of the refactoring, the dependencies of the outer @angular/compiler-cli package on ngtsc internal packages are significantly trimmed. This refactoring was driven by the desire to build a plugin interface to the compiler so that tsc_wrapped (another consumer of the TS compiler APIs) can perform Angular transpilation on user request. PR Close #34887
2020-01-17 19:00:07 -05:00
"//packages/compiler-cli/src/ngtsc/core",
"//packages/compiler-cli/src/ngtsc/core:api",
feat(ivy): produce contextual diagnostics in ngtsc mode (#25647) TypeScript has a more modern diagnostic emit function which produces contextually annotated error information, using colors in the console to indicate where in the code the error occurs. This commit swiches ngtsc to use this format for diagnostics when emitting them after a failed compilation. PR Close #25647
2018-08-23 17:33:38 -04:00
"//packages/compiler-cli/src/ngtsc/diagnostics",
refactor(ivy): implement a virtual file-system layer in ngtsc + ngcc (#30921) To improve cross platform support, all file access (and path manipulation) is now done through a well known interface (`FileSystem`). For testing a number of `MockFileSystem` implementations are provided. These provide an in-memory file-system which emulates operating systems like OS/X, Unix and Windows. The current file system is always available via the static method, `FileSystem.getFileSystem()`. This is also used by a number of static methods on `AbsoluteFsPath` and `PathSegment`, to avoid having to pass `FileSystem` objects around all the time. The result of this is that one must be careful to ensure that the file-system has been initialized before using any of these static methods. To prevent this happening accidentally the current file system always starts out as an instance of `InvalidFileSystem`, which will throw an error if any of its methods are called. You can set the current file-system by calling `FileSystem.setFileSystem()`. During testing you can call the helper function `initMockFileSystem(os)` which takes a string name of the OS to emulate, and will also monkey-patch aspects of the TypeScript library to ensure that TS is also using the current file-system. Finally there is the `NgtscCompilerHost` to be used for any TypeScript compilation, which uses a given file-system. All tests that interact with the file-system should be tested against each of the mock file-systems. A series of helpers have been provided to support such tests: * `runInEachFileSystem()` - wrap your tests in this helper to run all the wrapped tests in each of the mock file-systems. * `addTestFilesToFileSystem()` - use this to add files and their contents to the mock file system for testing. * `loadTestFilesFromDisk()` - use this to load a mirror image of files on disk into the in-memory mock file-system. * `loadFakeCore()` - use this to load a fake version of `@angular/core` into the mock file-system. All ngcc and ngtsc source and tests now use this virtual file-system setup. PR Close #30921
2019-06-06 15:22:32 -04:00
"//packages/compiler-cli/src/ngtsc/file_system",
feat(ivy): setup boilerplate for component indexing API (#30961) Set up the skeleton for a compiler API that indexes components and their templates on an independent indexing step. Part of #30959 PR Close #30961
2019-06-10 12:19:35 -04:00
"//packages/compiler-cli/src/ngtsc/indexer",
feat(ivy): performance trace mechanism for ngtsc (#29380) This commit adds a `tracePerformance` option for tsconfig.json. When specified, it causes a JSON file with timing information from the ngtsc compiler to be emitted at the specified path. This tracing system is used to instrument the analysis/emit phases of compilation, and will be useful in debugging future integration work with @angular/cli. See ngtsc/perf/README.md for more details. PR Close #29380
2019-03-18 14:16:38 -04:00
"//packages/compiler-cli/src/ngtsc/perf",
build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871) PR Close #28871
2019-02-20 12:54:42 -05:00
"@npm//@bazel/typescript",
build: fix build failures with worker mode cache and @types/events (#31325) Errors observed only in tests on CircleCI — was not reproducible locally. ``` ERROR: /home/circleci/ng/packages/http/test/BUILD.bazel:3:1: Compiling TypeScript (devmode) //packages/http/test:test_lib failed (Exit 1): tsc_wrapped failed: error executing command (cd /home/circleci/.cache/bazel/_bazel_circleci/9ce5c2144ecf75d11717c0aa41e45a8d/execroot/angular && \ exec env - \ BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1 \ PATH=/bin:/usr/bin:/usr/local/bin \ bazel-out/host/bin/external/npm/@bazel/typescript/bin/tsc_wrapped @@bazel-out/k8-fastbuild/bin/packages/http/test/test_lib_es5_tsconfig.json) Execution platform: //tools:rbe_ubuntu1604-angular Compilation failed Error: missing input digest for /home/circleci/.cache/bazel/_bazel_circleci/9ce5c2144ecf75d11717c0aa41e45a8d/execroot/angular/external/npm/node_modules/@types/events/index.d.ts. ERROR: /home/circleci/ng/packages/benchpress/test/BUILD.bazel:3:1: Compiling TypeScript (devmode) //packages/benchpress/test:test_lib failed (Exit 1): tsc_wrapped failed: error executing command (cd /home/circleci/.cache/bazel/_bazel_circleci/9ce5c2144ecf75d11717c0aa41e45a8d/execroot/angular && \ exec env - \ BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1 \ PATH=/bin:/usr/bin:/usr/local/bin \ bazel-out/host/bin/external/npm/@bazel/typescript/bin/tsc_wrapped @@bazel-out/k8-fastbuild/bin/packages/benchpress/test/test_lib_es5_tsconfig.json) Execution platform: //tools:rbe_ubuntu1604-angular Compilation failed Error: missing input digest for /home/circleci/.cache/bazel/_bazel_circleci/9ce5c2144ecf75d11717c0aa41e45a8d/execroot/angular/external/npm/node_modules/@types/events/index.d.ts ERROR: C:/codefresh/volume/angular/packages/compiler/test/css_parser/BUILD.bazel:3:1: Compiling TypeScript (devmode) //packages/compiler/test/css_parser:css_parser_lib failed (Exit 1): tsc_wrapped.exe failed: error executing command cd C:/users/containeradministrator/_bazel_containeradministrator/zquin2l6/execroot/angular SET PATH=C:\msys64\usr\bin;C:\msys64\bin;C:\Windows;C:\Windows\System32;C:\Windows\System32\WindowsPowerShell\v1.0 SET RUNFILES_MANIFEST_ONLY=1 bazel-out/host/bin/external/npm/@bazel/typescript/bin/tsc_wrapped.exe @@bazel-out/x64_windows-fastbuild/bin/packages/compiler/test/css_parser/css_parser_lib_es5_tsconfig.json Execution platform: @bazel_tools//platforms:host_platform Compilation failed Error: missing input digest for C:/users/containeradministrator/_bazel_containeradministrator/zquin2l6/execroot/angular/external/npm/node_modules/@types/events/index. d.ts ``` PR Close #31325
2019-06-22 00:52:00 -04:00
"@npm//@types/node",
build: remove dependency on `@types/chokidar` (#35371) We recently updated chokidar to `3.0.0`. The latest version of chokidar provides TypeScript types on its own and makes the extra dependency on the `@types` unnecessary. This seems to have caused the `build-packages-dist` script to fail with an error like: ``` [strictDeps] transitive dependency on external/npm/node_modules/chokidar/types/index.d.ts not allowed. Please add the BUILD target to your rule's deps. ``` It's unclear why that happens, but a reasonable theory would be that the TS compilation accidentally picked up the types from `chokidar` instead of `@types/chokidar`, and the strict deps `@bazel/typescript` check reported this as issue because it's not an explicit target dependency. PR Close #35371
2020-02-12 05:52:15 -05:00
"@npm//chokidar",
refactor(compiler-cli): add `removeDir()` to `FileSystem` (#35079) PR Close #35079
2020-01-31 16:07:59 -05:00
"@npm//fs-extra",
fix(bazel): update to tsickle 0.37.1 to fix peerDep warnings (#33788) tsickle 0.37.1 is compatible with typescript 3.6, so we should use it and fix peerDep warnings from npm/yarn. PR Close #33788
2019-11-13 02:17:06 -05:00
"@npm//minimist",
build: update rules_nodejs and clean up bazel warnings (#30370) Preserve compatibility with rollup_bundle rule. Add missing npm dependencies, which are now enforced by the strict_deps plugin in tsc_wrapped PR Close #30370
2019-05-09 17:51:51 -04:00
"@npm//reflect-metadata",
build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871) PR Close #28871
2019-02-20 12:54:42 -05:00
"@npm//tsickle",
"@npm//typescript",
build: Bazel builds ngfactories for packages/core (#18289) PR Close #18289
2017-07-21 17:20:34 -04:00
],
)
feat(bazel): change ng_package rule to APF v6 (#22782) Angular Package Format v6 stops bundling files in the esm5 and esm2015 directories, now that Webpack 4 can tree-shake per-file. Adds some missing files like package.json to make packages closer to what we publish today. Refactor ng_package to be a type of npm_package and re-use the packaging action from that rule. PR Close #22782
2018-03-13 14:00:53 -04:00
build: upgrade to rules_nodejs 1.0.0 (first stable release) (#34736) Brings in the fix for stamping which was preventing many targets from getting cached. PR Close #34736
2019-12-28 19:37:59 -05:00
pkg_npm(
feat(bazel): change ng_package rule to APF v6 (#22782) Angular Package Format v6 stops bundling files in the esm5 and esm2015 directories, now that Webpack 4 can tree-shake per-file. Adds some missing files like package.json to make packages closer to what we publish today. Refactor ng_package to be a type of npm_package and re-use the packaging action from that rule. PR Close #22782
2018-03-13 14:00:53 -04:00
name = "npm_package",
srcs = [
"package.json",
],
ci(ivy): configure CI environments for Ivy JIT and AOT (#24309) Two new CircleCI environments are created: test_ivy_jit and test_ivy_aot. Both run a subset of the tests that have been marked with Bazel tags as being appropriate for that environment. Once all the tests pass, builds are published to the *-builds repo both for the legacy View Engine compiled code as well as for ivy-jit and ivy-aot. PR Close #24309
2018-06-05 14:38:46 -04:00
tags = [
"release-with-framework",
],
build: restrict visibility of npm_package targets (#27611) dependencies on these cause very long rebuilds which have to re-package angular. Such tests belong in the integration/ folder PR Close #27611
2018-12-11 19:53:42 -05:00
# Do not add more to this list.
# Dependencies on the full npm_package cause long re-builds.
build: run offline_compiler_test using bazel (#28191) PR Close #28191
2019-01-22 12:46:51 -05:00
visibility = [
"//packages/compiler-cli/integrationtest:__pkg__",
],
feat(ivy): ngcc project skeleton (#24897) PR Close #24897
2018-07-16 03:49:56 -04:00
deps = [
":compiler-cli",
refactor(ivy): move ngcc into a higher level folder (#29092) PR Close #29092
2019-03-20 09:47:58 -04:00
"//packages/compiler-cli/ngcc",
feat(ivy): ngcc project skeleton (#24897) PR Close #24897
2018-07-16 03:49:56 -04:00
],
feat(bazel): change ng_package rule to APF v6 (#22782) Angular Package Format v6 stops bundling files in the esm5 and esm2015 directories, now that Webpack 4 can tree-shake per-file. Adds some missing files like package.json to make packages closer to what we publish today. Refactor ng_package to be a type of npm_package and re-use the packaging action from that rule. PR Close #22782
2018-03-13 14:00:53 -04:00
)