flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harbs <harbs.li...@gmail.com>
Subject Re: [FlexJS] Compiler outputs (nearly) empty map file
Date Wed, 27 Sep 2017 09:28:37 GMT
I’m not sure what the state of source maps for MXML files is. The last time I paid attention,
it was not working.

Alex or Josh would have a better idea.

FWIW, I got into the habit of doing my debugging in Chrome…


> On Sep 27, 2017, at 12:24 PM, Idylog - Nicolas Granon <ngranon@idylog.com> wrote:
> We are trying to use FlexJS 0.8 with a Visual Studio Code (VSCode) setup
> (nextgen actionscript extension).
> Everything works fine. However, when we use the -source-map option of the
> compiler (in the asconfig.json) a source map file is created ({project
> name}.js.map) with the correct keys, but no values !
> Here is a copy of the content of the {project name}.js.map :
> {
> "version":3,
> "file":"myproject03.js",
> "lineCount":1,
> "mappings":";",
> "sources":[],
> "names":[]
> }
> I have understood that the map generated from MXML files should be named
> .mxml.map. But this is not our concern (we can rename the file until this
> small bug is fixed).
> The problem is of course that the file is "empty".
> The project consists of a single mxml file (with a button, a label and a
> listener displaying an Alert, nothing very complicated !).
> The listener is inside a script tag, of course, not inlined.
> We have the latest version of VSCode (august 2017), the latest version of
> NextGenAS extension (0.6.0).
> The only specific (?) setting is that we use the --output argument since we
> want to sent the compiled output to our web server (the output dir is one
> level BELOW the web root but of course the output dir is specified as an
> absolute windows path, not as a URL). And also we output JS only (--target
> JSFlex).
> The generated output in bin-debug runs fine...
> What did we miss ?
> Many thanks
> Nicolas

View raw message