Been playing around a bit with Lighthouse in the Chrome DevTools, always trying to increase the scoring. Not always a productive use of time, but always learning new things. I've been playing around with source maps and one of the things it suggests, even for production, is to include source maps for large JS files. I can turn on the option to generate the map files in release mode, but for some reason these are getting a little extra junk at the top that is causing it to fail.
)]}'
{"version":3,"file":"ActoriousClient_1_0_3288.js","sources":["../../../../../../../AppData/Local/tmssoftware/registered/TMS WEB Core RSXE12/Core Source/RTL/tms_1_0_3288.js","../../../../../../../AppData/Local/tmssoftware/registered/TMS WEB Core RSXE12/Core
Also, if I enable obfuscation (default in release mode) the map file still generates, but no link to it is added to the .js file. As the map file size didn't change, I'm assuming that this is because the obfuscation 'breaks' whatever was generated with the map file, or that the obfuscation happens after the map file is generated. Might not make sense to have both a map file and obfuscation, but maybe there is. The obfuscation reduces my js from around 1,000 KB to about 800 KB, so it might be nice to have both. Not sure if that is sensible though.