Dart News & Updates

Hot reload on save By request, we now support doing a hot reload on file save. On an explicit save (cmd-s / ctrl-s or File > Save All), if there’s an app currently running we will try to reload changes into that app. This integrates well with how IntelliJ’s save action works — the default behavior of the action maps to a save-all command. If there are analysis errors on save, instead of reloading we will highlight errors in the analysis view. This behavior is off by default and can be turned on in Settings > Languages & Frameworks > Flutter. Feedback on this feature is much appreciated and will help us make additional improvements to the workflow. In particular, should we enable this feature by default? Improved project wizard We’ve updated the new project wizard! You can now choose which type of Flutter project to create: an app, a plugin project – to expose native services, or a package – to create a reusable Dart library. In add...

One of the most important features for Dart 2.0, strong mode , has been available for several releases. Migrate to strong mode now to take advantage of the new sound type system that finds errors at compile time (rather than letting your users discover them). You may even find bugs that have been lurking in your code.  If you are using Flutter, it already uses strong mode, so you have met this requirement.  Strong mode is the primary breaking change for 2.0, but there are likely to be other updates. For more information, see Dart 2.0 Updates.