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
The webpack build doesn't yet support lavamoat, but when it does we'll need to figure out why (in the gulp build) only some lockdown files are loaded when lavamoat is used.
The text was updated successfully, but these errors were encountered:
The lavamoat plugin will be responsible for injecting ses and calling lockdown. We need to figure out if we want to remove the --lockdown option from webpack. I vote for complete removal of the option (effectively making --lavamoat the same as doing --lavamoat --lockdown).
We might need to tweak how lockdown-more.js is injected into the bundle, as well as how snow and use-snow are bundled. Wrapping these in lavamoat runtime would cause problems.
The webpack build doesn't yet support
lavamoat
, but when it does we'll need to figure out why (in the gulp build) only some lockdown files are loaded when lavamoat is used.The text was updated successfully, but these errors were encountered: