Viktor Lukashov

> I do not exactly understand why the form package needs to be handled differently from other packages (i.e. the form web components) but may git subtrees could help here...

If we really want to keep the comment AND make the file JSON-compliant, we could consider a hack like in ```json { "__COMMENT__": [ "This TypeScript configuration file is generated...

> This also happens in 14.1.27 A `tsconfig.json` file in a Vaadin 14.1.27 app? That sounds very confusing to me as I am pretty confident Vaadin 14.x does not have...

Thanks! Now I understand the issue better. The screenshot shows that Eclipse complains about a file deep inside the `node_modules` folder. While this is not in direct control of Vaadin...

This issue here would offer a possibility to work around the existing limitation _ASAP_, as well as a mechanism for fine tuning the defaults in the future. I do not...

Another use case where something like this would be useful: restrict the possible values of a `string`-typed property: I want to configure the Fusion TS type generator to produce ```ts...

This is probably the same issue: https://embed.plnkr.co/eD8BeYrzTuWyGF3wLCWd/ Polymer elements in an angular form appear initially dirty whereas native elements appear initially pristine. In order to reset the pristine flag, it...

Looks like an interface or a mixin is missing that would make all router-added properties and callbacks known to TypeScript. What do you think of a syntax like below? ```typescript...

Hi @moebiusmania! Have you already checked https://github.com/web-padawan/polymer3-webpack-starter? It has an example of using Vaadin Router with Webpack and lazy-loading.

Point to consider: how would the `router.urlForName('x-my-view')` method work when the route component is defined via the `module` property.