[Analyser][Schema] Using Typescript as input results in TS file path in `def.declaration.module` rather than complied JS output about custom-elements-manifest HOT 2 CLOSED

We are pointing at the input TS files since we strip all documentation out of the compiled version, and so lose features like CSS Part, etc. Is there some better way of doing this that would avoid this problem altogether?

... a plugin for the analyzer that uses the output d.ts.map to change this value on output

This describes exactly the problem :) The manifest, according to the Schema, should be pointing at the distributed code. However, we can't make assumptions on what kind of build systems of config settings every project has, so it's not feasible for the analyzer itself to make those assumptions. Instead you should indeed use a plugin that changes the paths/file extensions, like the one you built, or something like https://www.npmjs.com/package/cem-plugin-module-file-extensions

Additionally, running the analyzer on the TS output would lose a bunch of information.

from custom-elements-manifest.

Thanks for the response, makes a lot of sense. Cheers!

from custom-elements-manifest.