Not possible to have optional object property compatible with both Closure Compiler and Intellisense

• VSCode Version: 1.32.3 x64
• OS Version: Ubuntu 18.04

Steps to Reproduce:

1. Enable "checkJs": true in jsconfig.json.
2. Create a Javascript file:

class A {

  /**
   * @param {{field: string|undefined}} obj 
   */
  constructor(obj) {
    this.obj = obj;
  }
}

let a = new A({});

Results in this error:

Adding error text here for duplicate detection:
Argument of type '{}' is not assignable to parameter of type '{ field: string; }'.
Property 'field' is missing in type '{}' but required in type '{ field: string; }' .ts(2345)

Does this issue occur when all extensions are disabled?: Yes

Expected behaviour:
Some way to mark object properties as optional compatible both with Closure Compiler and VsCode intellisense. Either through @typedef, through structural interfaces with @record, direct @param notation using string|undefined, or something similar.

This notation works fine today, but it is not recognized by Closure Compiler. It is debatable whether this is an issue with Intellisense or lacking support from Closure Compiler.

class A {

  /**
   * @param {AParam} obj 
   */
  constructor(obj) {
    this.obj = obj;
  }
}

/** @typedef {{field?: string|undefined}} */
var AParam;
let a = new A({});

Comienza con la reproducción en jsconfig.json usando checkJs y las formas de JSDoc @param y @typedef mostradas en el informe. Compara cómo TypeScript gestiona la notación de propiedades opcionales con respecto al requisito de compatibilidad indicado para Closure Compiler. Se considera terminado cuando una notación compatible permite new A({}) sin el error indicado de propiedad ausente y sigue siendo compatible con Closure Compiler.