You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to add the direct_install linker only for production builds?
You should be able to create a DevApp.gwt.xml which inherits your App.gwt.xml and in DevApp.gwt.xml you use a different linker for development. Or if you want it even more clear use something like BaseApp.gwt.xml, ProdApp.gwt.xml and DevApp.gwt.xml with prod and dev having their desired linkers and other settings (e.g. logging).
You should be able to create a DevApp.gwt.xml which inherits your App.gwt.xml and in DevApp.gwt.xml you use a different linker for development. Or if you want it even more clear use something like BaseApp.gwt.xml, ProdApp.gwt.xml and DevApp.gwt.xml with prod and dev having their desired linkers and other settings (e.g. logging).
Propably the only real option. <set-configuration-property> not allow conditions with <when-property-is>.
GWT version: 2.12.1
Browser (with version): Chromium: 131.0.6778.85
Description
Using direct_install linker or installCode false breaks the sourcemaps.
<add-linker name="direct_install"/>
<set-configuration-property name="installCode" value="false"/>
Sourcemaps are still loaded in SDM, but points to wrong source lines, which breaks debug capabilities.
Steps to reproduce
Add
<add-linker name="direct_install"/>
and let the CodeServer do a full build. After that sourcemaps point to wrong source lines.Known workarounds
Remove
<add-linker name="direct_install"/>
but getting CSP problems in production build.The text was updated successfully, but these errors were encountered: