| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
if (!args.flag('strip-wasm')) '--no-strip-wasm',We could also always pass either `--strip-wasm` or `--no-strip-wasm` based on the value of the flag here. I think it would be slightly better as it wouldn't rely on the default value in dart2wasm CLI. Any thoughts?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
if (!args.flag('strip-wasm')) '--no-strip-wasm',We could also always pass either `--strip-wasm` or `--no-strip-wasm` based on the value of the flag here. I think it would be slightly better as it wouldn't rely on the default value in dart2wasm CLI. Any thoughts?
If we decide to pass one of the two flags always, we should do the same for other flags here, like `minify`, `print-kernel`.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
'Compile to a specific target sanitizer. Sanitizers are not offered with single-file executables because the sanitizers cannot symbolize embedded snapshots.',Note: this change is made by `dart format`.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
if (!args.flag('strip-wasm')) '--no-strip-wasm',We could also always pass either `--strip-wasm` or `--no-strip-wasm` based on the value of the flag here. I think it would be slightly better as it wouldn't rely on the default value in dart2wasm CLI. Any thoughts?
If we decide to pass one of the two flags always, we should do the same for other flags here, like `minify`, `print-kernel`.
Yeah we should probably update these to just pass along the value as-is so that dartdev doesn't have to know the default.
We can do that in a follow-up though.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |