Re: VSCode Build Taking Really Long

[Alex Harui]

I found that hard to read, but I think I see on line 657 that js-output is set 
to "." and that makes me wonder if the compiler will then choose whatever the 
working directory is at the time it is launched.  If that working directory is 
changed by VSCode to be the last output directory (maybe to launch the results 
in a browser), that might cause the compiler to nest the next output in that 
output directory and cause the observed results.

HTH,
-Alex

On 2/27/19, 12:04 AM, "Olaf Krueger" <m...@olafkrueger.net> wrote:

    Hi Alex,
    
    >Right. The goal was to see what output options were actually being received
    by the compiler in order to understand how those options could be causing
    the compiler to generate nested output folders.  I'm curious to know if the
    js options are in the dump file.  Can't tell since you cut them out. 
    
    
    Sorry, I misunderstood this.
    But I am still not sure what do you mean with "js options".
    I've created a gist which contains the entire dump [1].
    Maybe you can find some time to look at it?
    
    Thanks!
    Olaf
    
    
    [1] 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.github.com%2Folafkrueger%2F8e045b33cae493deb56b38f9430afa14&amp;data=02%7C01%7Caharui%40adobe.com%7C114a62222a504a5999b408d69c8a271a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636868514618842104&amp;sdata=c8MjMvPC747ooXKaXZ9Pp0%2BhZZBtZwOUnbeT6HeP1n0%3D&amp;reserved=0
    
    
    
    
    --
    Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C114a62222a504a5999b408d69c8a271a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636868514618842104&amp;sdata=D0xylr0g6bUUVGpbUYFnwL%2BNe0I4oAM57FpmlowEuS0%3D&amp;reserved=0