Enable --wasm flag for production builds

[johnpryan]

The UI is working nicely when built with the latest version Flutter engine, so it would be great to start using Wasm for the production version of DartPad. (The remaining issues with platform views have been fixed on the main channel of the SDK.)

Here's a staged version built with the --wasm flag, using the latest Flutter SDK (main channel): https://dart-pad-a3c64--wasm-cdjiko6q.web.app/

I made sure to update the Flutter SDK images to the latest version of the main channel of the SDK in GCP, so once this is merged it should use those images.

[parlough]

Cool. Thanks!

Here's a staged version built with the --wasm flag, using the latest Flutter SDK (main channel): https://dart-pad-a3c64.web.app/

I'm able to run other Flutter web apps with Wasm, but the staged version at the link you sent seems to still be running with (or picking) JS. Is it the wrong link or do you still expect that?

[johnpryan]

Sorry, wrong link: https://dart-pad-a3c64--wasm-cdjiko6q.web.app/

[johnpryan]

It looks like the platform view is blank when changing between different samples:

[johnpryan]

This doesn't appear to be related to Wasm, but seems to be happening due to a timing issue related to calling refresh() on the Codemirror API. I patched this issue by adding an artificial delay whenever a new CodeMirror platform view is created: 75542ec

[johnpryan]

Updated staging link: https://dart-pad-a3c64--wasm-cdjiko6q.web.app/

[devoncarew]

With this link: https://dart-pad-a3c64--wasm-cdjiko6q.web.app/, I don't see content in the codemirror editor until I click inside it.

(ed: perhaps an intermittent issue?)

[johnpryan]

I don't see content in the codemirror editor until I click inside it.
We should add a brief comment for why we have this delay.

63b1d9d should fix that.

Updated staging link: https://dart-pad-a3c64--wasm-cdjiko6q.web.app/

[devoncarew]

🎉