Martin Probst

I'll be around tomorrow. Victor Berchet [email protected] schrieb am Mo., 3. Okt. 2016, 10:13: > in @NgCompoent, schemas can currently only use the following values: > - CUSTOM_ELEMENTS_SCHEMA -> allow...

I ran into this because the TypeScript .d.ts has toBuffer return ArrayBuffer in node, which then causes incorrect compilation errors. Any ideas on how to avoid that? Daniel Wirtz schrieb...

This has somewhat odd behaviour for callables, e.g. when calling `set` on a `DeepReadonly`: ``` Cannot invoke an expression whose type lacks a call signature. Type 'DeepReadonly Map>' has no...

I have this issue too – we have packages that contain both a `BUILD` and a `BUILD.bazel` file, one for blaze and one for bazel. It'd be nice if we...

@jplaisted is right, you'll need to use `tsickle` (https://github.com/angular/tsickle) to compile your code, which emits `goog.module` code, and then on the client side, it's using the Closure module system to...

I believe this is working as expected; you need to pass every JS source with the `--js` flag, including sources from node modules.

/CC @ChadKillingsworth Chad, can you take a look here?

I've also added this to the next sync meeting on open source support, we can take a look at what the current state is here.

If you are using Closure Compiler mostly to type check NodeJS code (i.e. you don't need optimization or other Closure Compiler specific features), it might be worth considering TypeScript instead....

I'll leave it to @ChadKillingsworth to comment on the problem specifically and whether we'll get around to fixing it. To manage expectations though, Google-internally we do not use CommonJS with...