The .js.map extension is the correct behavior. The name of a source map file is
based on extension of the output file rather then the input file. Both .as and
.mxml files will produce .js output, so the source map's extension should be
.js.map for both. Every tool that I've seen produce source maps for other
languages works this way. Compile-to-JS languages create .js.map files.
Compile-to-CSS languages create .css.map files.
In regards to relative versus absolute paths, I'm pretty sure that I checked
what the TypeScript compiler produced and made sure that the behavior was the
same in our compiler.
- Josh
On 2017-11-06 02:52, "Idylog - Nicolas Granon" <ngra...@idylog.com> wrote:
> It appears that, when generating the source map for debugging js output, the
> path to the source file ("sources" property) is using a relative path.
>
> Since it is possible (and often desirable) to send the output outside the
> workspace/project folder (with js-output argument) it seems to me that the
> path to the main source file should be an absolute path.
>
> Also, the map is named with a .js.map suffix even for a MXML main source
> file. It should follow the extension of the main source file (.js.map or
> .mxml.map, depending on the main source file).
>
> Nicolas Granon
>
>
>
>
>
>
