In Chrome/Firefox dev tools, it should pick up the source map for viewer.js and you should get back a friendlier looking stack trace.
Actually, if you want a friendlier dev experience, you should make an IIS virtual dir from /mapguide that points to the viewer directory of the git clone: eg. /mapguide/viewer-dev -> C:\tools\git\mapguide-react-layout\viewer And then either put a copy or symlink of webconfig.ini into C:\tools\git From there, you can run "yarn run watch:dev" that will make a full debug viewer bundle and webpack will continuously monitor and live-rebuild this bundle on any change of any .ts or .tsx file in the viewer source. A browser reload afterwards will pick up the live-rebuilt bundle. - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/The-customization-story-in-mapguide-react-layout-tp5311221p5312185.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users