Hi, my opinion on this is that users'll want the capability to debug framework code by default and will prefer that to save bandwidth. sourceMaps is other thing that differentiate Royale over many JS basic libraries that does not have this built in and put us with the group that have it, so more in the group of "structured programing with debugging capabilities". So I think ANT should have as well sourceMaps on by default. Then if we can have a switch for opt-out will be great, but maybe a bit of work for something that probably will be low priority right now, or we could wait to someone to ask for, fill an issue and then work on it. About sourceRoot not mapping to anything, can't say since I thought that was not possible until now, so maybe others could respond to that thanks
El dom., 26 may. 2019 a las 5:23, Alex Harui (<[email protected]>) escribió: > Hi, > > In working through the release automation, it appears that the Maven build > puts source maps in the SWC for every JS file but the Ant build does not. > Should there be source maps in the SWCs? How do they work when the > sourceRoot doesn't map to anything? Or should that only be an option when > building everything from sources on your machine? It would save a lot in > terms of SWC size to not have source maps in the SWCs. > > Thoughts? > -Alex > > -- Carlos Rovira http://about.me/carlosrovira
