angular · Feb 16, 2021 · Mar 18, 2021 · Mar 19, 2021 · Mar 31, 2021 · Mar 31, 2021
diff --git a/.bazelrc b/.bazelrc
diff --git a/.github/workflows/node.js.yml b/.github/workflows/node.js.yml
@@ -0,0 +1,23 @@
+name: CI
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+    # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
+    - name: Use Node.js 15.x
+      uses: actions/setup-node@v2
+      with:
+        node-version: 15.x
+    - run: yarn
+    - run: yarn run build
+    - run: yarn test
diff --git a/.gitignore b/.gitignore
@@ -7,8 +7,5 @@
 # VSCode directory
 .vscode
 
-# Bazel working directories
-/bazel-*
-
-# Created by bazel run :npm_package.pack
-tsickle-*.tgz
+# Build output
+/out
diff --git a/BUILD b/BUILD
diff --git a/README.md b/README.md
@@ -1,4 +1,4 @@
-# Tsickle - TypeScript to Closure Translator [![Build Status](https://circleci.com/gh/angular/tsickle.svg?style=svg)](https://circleci.com/gh/angular/tsickle) [![Windows build](https://ci.appveyor.com/api/projects/status/puxdblmlqbofqqt1/branch/master?svg=true)](https://ci.appveyor.com/project/alexeagle/tsickle/branch/master)
+# Tsickle - TypeScript to Closure Translator [![Build Status](https://github.com/angular/tsickle/actions/workflows/node.js.yml/badge.svg)](https://github.com/angular/tsickle/actions/workflows/node.js.yml)
 
 Tsickle converts TypeScript code into a form acceptable to the [Closure
 Compiler]. This allows using TypeScript to transpile your sources, and then
@@ -120,29 +120,19 @@ Example:
   [NVM](https://github.com/nvm-sh/nvm)
 - yarn. Install from your operating system's package manager or by following
   [instructions on yarnpkg.com](https://yarnpkg.com/en/docs/install).
-- bazel. Install from your operating system's package manager or by [following
-  instructions here](https://docs.bazel.build/versions/master/install.html).
 
 ### One-time setup
 
-Run `bazel run @nodejs//:yarn` to install dependencies.
+Run `yarn` to install dependencies.
 
-### Bazel install
+### Build & Test commands
 
-We use [bazel](https://bazel.build/) to build, and are pinned to a specific
-version of it in `package.json` for reproducible builds. The build rules check
-for a compatible version of bazel, so it is generally safe to use your local
-installed version. If in doubt, you can run `yarn bazel` instead of `bazel` in
-any of the below commands to make sure you are using the right version.
-
-### Test commands
-
-- `ibazel test test:unit_test` executes the unit tests in watch mode (use `bazel test test:unit_test` for a single run),
-- `bazel test test:e2e_test` executes the e2e tests,
-- `bazel test test:golden_test` executes the golden tests,
-- `node check_format.js` checks the source code formatting using
-  `clang-format`,
-- `yarn test` runs unit tests, e2e tests and checks the source code formatting.
+- `yarn build` builds the code base.
+- Run `tsc --watch` for an interactive, incremental, and continuous build.
+- `yarn lint` checks for lint.
+- `yarn test` runs unit tests, e2e tests and checks for lint (but make sure to
+  `yarn build` first or run tsc!). Set the `TEST_FILTER` environment variable
+  to filter what golden tests to run.
 
 ### TypeScript AST help
 
@@ -151,13 +141,13 @@ visualize and inspect a TypeScript AST.
 
 ### Debugging
 
-You can debug tests by using `bazel run` and passing `--node_options=--inspect`
-or `--node_options=--inspect-brk` (to suspend execution directly after startup).
+You can debug tests by passing `--node_options=--inspect` or
+`--node_options=--inspect-brk` (to suspend execution directly after startup).
 
 For example, to debug a specific golden test:
 
 ```shell
-TEST_FILTER=my_golden_test ibazel run //test:golden_test -- --node_options=--inspect-brk
+TEST_FILTER=my_golden_test node --inspect-brk=4332 ./node_modules/.bin/jasmine out/test/*.js
 ```
 
 Then open [about:inspect] in Chrome and choose "about:inspect". Chrome will
@@ -168,19 +158,15 @@ to `localhost:9229`, so things should work out of the box.
 The break in specific code locations you can add `debugger;` statements in the
 source code.
 
-Note: IDEs such as VS Code have support for the inspect protocol, but the
-integration does not work due to bazel's complex directory layout.
-
 ### Updating Goldens
 
-Run `UPDATE_GOLDENS=y bazel run test:golden_test` to have the test suite update
-the goldens in `test_files/...`.
+Run `UPDATE_GOLDENS=y yarn test` to have the test suite update the goldens in
+`test_files/...`.
 
 ### Environment variables
 
-Pass the flag `--action_env=TEST_FILTER=<REGEX>` to bazel test to limit the
-end-to-end test (found in `test_files/...`) run tests with a name matching the
-regex.
+Set the environment variable `TEST_FILTER=<REGEX>` to limit the golden tests
+(found in `test_files/...`) to only run tests with a name matching the regex.
 
 ### Releasing
 
@@ -220,5 +206,7 @@ https://github.com/angular/tsickle/releases) will be implicitly created.
 From the master branch run:
 
 ```
-bazel run :npm_package.publish -- --registry https://wombat-dressing-room.appspot.com
+npm config set registry https://wombat-dressing-room.appspot.com
+npm login
+npm publish -- --registry https://wombat-dressing-room.appspot.com
 ```
diff --git a/WORKSPACE b/WORKSPACE
diff --git a/demo/demo.ts b/demo/demo.ts
@@ -156,6 +156,7 @@ export function toClosureJS(
   const filesToProcess = new Set(absoluteFileNames);
   const rootModulePath = options.rootDir || getCommonParentDirectory(absoluteFileNames);
   const transformerHost: tsickle.TsickleHost = {
+    rootDirsRelative: (f: string) => f,
     shouldSkipTsickleProcessing: (fileName: string) => {
       return !filesToProcess.has(path.resolve(fileName));
     },
@@ -176,6 +177,7 @@ export function toClosureJS(
   const diagnostics = ts.getPreEmitDiagnostics(program);
   if (diagnostics.length > 0) {
     return {
+      tsMigrationExportsShimFiles: new Map(),
       diagnostics,
       modulesManifest: new tsickle.ModulesManifest(),
       externs: {},

diff --git a/package.json b/package.json
@@ -1,40 +1,40 @@
 {
   "name": "tsickle",
-  "version": "0.40.0",
+  "version": "0.41.0",
   "description": "Transpile TypeScript code to JavaScript with Closure annotations.",
-  "main": "src/tsickle.js",
-  "typings": "src/tsickle.d.ts",
+  "main": "out/src/tsickle.js",
+  "typings": "out/src/tsickle.d.ts",
   "directories": {
     "test": "test"
   },
   "files": [
-    "src/*"
+    "out/src/*"
   ],
   "peerDependencies": {
-    "typescript": "~4.0.5"
+    "typescript": "~4.3"
   },
   "devDependencies": {
-    "@bazel/bazel": "^0.29.0",
-    "@bazel/jasmine": "^0.38.0",
-    "@bazel/typescript": "^0.38.0",
     "@types/diff-match-patch": "^1.0.32",
     "@types/glob": "5.0.35",
-    "@types/jasmine": "2.8.8",
+    "@types/jasmine": "^3.7.7",
     "@types/node": "^10.5.6",
-    "diff-match-patch": "^1.0.1",
+    "@types/source-map-support": "^0.5.3",
+    "diff-match-patch": "^1.0.5",
     "glob": "7.1.2",
     "google-closure-compiler": "^20190929.0.0",
-    "jasmine": "3.1.0",
+    "jasmine": "^3.7.0",
+    "jasmine-node": "^3.0.0",
     "source-map": "^0.7.3",
-    "source-map-support": "^0.5.6",
-    "tslib": "1.11",
-    "tslint": "5.11.0",
-    "typescript": "4.0"
+    "source-map-support": "^0.5.19",
+    "tslib": "^2.2.0",
+    "tslint": "^6.1.3",
+    "typescript": "~4.3"
   },
   "scripts": {
-    "build": "bazel build //:npm_package",
+    "build": "tsc ",
+    "clean": "rm -r out",
     "lint": "tslint -c tslint.json -p tsconfig.json",
-    "test": "yarn lint && bazel test ..."
+    "test": "jasmine out/test/*.js && npm run lint"
   },
   "repository": {
     "type": "git",
@@ -56,5 +56,7 @@
     "url": "https://github.com/angular/tsickle/issues"
   },
   "homepage": "https://github.com/angular/tsickle",
-  "private": true
+  "dependencies": {
+    "@types/minimist": "^1.2.1"
+  }
 }
diff --git a/src/BUILD b/src/BUILD
diff --git a/src/closure_externs.js b/src/closure_externs.js
@@ -112,3 +112,22 @@ var EventListenerObject;
 
 /** @record */
 function ImportMeta() {};
+
+// Representations for TS' EventMap objects.
+// These are types that contain a mapping from event names to event object
+// types. User code can augment them, which produces externs.js files that then
+// reference the EventMap types - even though they are not defined in Closure.
+// Defining them here works around the problem.
+
+/** @interface */
+class HTMLElementEventMap {}
+/** @interface */
+class ElementEventMap {}
+/** @interface */
+class DocumentEventMap {}
+/** @interface */
+class WindowEventMap {}
+/** @interface */
+class GlobalEventHandlersEventMap {}
+/** @interface */
+class DocumentAndElementEventHandlersEventMap {}
diff --git a/src/clutz.ts b/src/clutz.ts
@@ -202,7 +202,7 @@ function generateClutzAliases(
   for (const symbol of localExports) {
     let localName = symbol.name;
     const declaration =
-        symbol.declarations.find(d => d.getSourceFile() === origSourceFile);
+        symbol.declarations?.find(d => d.getSourceFile() === origSourceFile);
     if (declaration && ts.isExportSpecifier(declaration) &&
         declaration.propertyName) {
       // If declared in an "export {X as Y};" export specifier, then X (stored
@@ -350,7 +350,7 @@ function clutzSymbolFromNode(
  * file extension.
  */
 function importPathForSymbol(sym: ts.Symbol): string|undefined {
-  if (sym.declarations.length === 0) {
+  if (!sym.declarations || sym.declarations.length === 0) {
     // This can happen if an import or symbol somehow references a nonexistent
     // type, for example in a case where type checking failed or via 'any'.
     return undefined;