mgechev / bazel-demo

Simple demo for building a TypeScript project with Bazel.

Bazel TypeScript Demo

This repository contains the code from my blog post "Building TypeScript with Bazel".

Usage

To setup the project run:

yarn

To build the project:

./node_modules/.bin/bazel build :bundle

Execute the produced bundle:

node bazel-bin/bundle.js

License

MIT

bazel-demo's Issues

IDE TS2307 Cannot find module 'lang/*'.ts

Hi,
Cloning the project and opening the test.ts file (in either WebStorm or VS Code) I see my IDE cannot resolve any of the three imports from the lang folder. After I add the following my IDE is satisfied and I get the intellisense I'd expect (the baseUrl and the paths are what I've added.)

{
  "compilerOptions": {
    "experimentalDecorators": true,
    "strict": true,
    "noImplicitAny": false,
    "baseUrl": "./",
    "paths": {
      "lang/*": [
        "./*"
      ]
    }
  },
  "bazelOptions": {
    "workspaceName": ""
  }
}

I then however see the following from Bazel after building.

[jallen@laptop bazel-demo]$ ./node_modules/.bin/bazel build :bundle
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
INFO: Analyzed target //:bundle (212 packages loaded, 5721 targets configured).
INFO: Found 1 target...
INFO: From Compiling TypeScript (devmode) //lexer:lexer:

WARNING: your tsconfig.json file specifies options which are overridden by Bazel:
 - compilerOptions.paths is determined by the module_name attribute in transitive deps[]
 - compilerOptions.rootDir and compilerOptions.baseUrl are always the workspace root directory


INFO: From Compiling TypeScript (prodmode) //lexer:lexer:

WARNING: your tsconfig.json file specifies options which are overridden by Bazel:
 - compilerOptions.paths is determined by the module_name attribute in transitive deps[]
 - compilerOptions.rootDir and compilerOptions.baseUrl are always the workspace root directory


INFO: From Compiling TypeScript (devmode) //parser:parser:

WARNING: your tsconfig.json file specifies options which are overridden by Bazel:
 - compilerOptions.paths is determined by the module_name attribute in transitive deps[]
 - compilerOptions.rootDir and compilerOptions.baseUrl are always the workspace root directory


INFO: From Compiling TypeScript (prodmode) //parser:parser:

WARNING: your tsconfig.json file specifies options which are overridden by Bazel:
 - compilerOptions.paths is determined by the module_name attribute in transitive deps[]
 - compilerOptions.rootDir and compilerOptions.baseUrl are always the workspace root directory


INFO: From Compiling TypeScript (devmode) //interpreter:interpreter:

WARNING: your tsconfig.json file specifies options which are overridden by Bazel:
 - compilerOptions.paths is determined by the module_name attribute in transitive deps[]
 - compilerOptions.rootDir and compilerOptions.baseUrl are always the workspace root directory


INFO: From Compiling TypeScript (prodmode) //interpreter:interpreter:

WARNING: your tsconfig.json file specifies options which are overridden by Bazel:
 - compilerOptions.paths is determined by the module_name attribute in transitive deps[]
 - compilerOptions.rootDir and compilerOptions.baseUrl are always the workspace root directory


INFO: From Compiling TypeScript (prodmode) //:app:

WARNING: your tsconfig.json file specifies options which are overridden by Bazel:
 - compilerOptions.paths is determined by the module_name attribute in transitive deps[]
 - compilerOptions.rootDir and compilerOptions.baseUrl are always the workspace root directory


Target //:bundle up-to-date:
  bazel-bin/bundle.min.js
  bazel-bin/bundle.min.js.map
INFO: Elapsed time: 33.207s, Critical Path: 13.65s
INFO: 10 processes: 10 linux-sandbox.
INFO: Build completed successfully, 51 total actions
[jallen@laptop bazel-demo]$ 

Are the TypeScript warnings above expected?.. or is there a more proper Bazel + TypeScript approach?