feat(battery_plus)!: Migrate to package:web

[koji-1009]

Description

Migration to the web package and add missing API.

https://developer.mozilla.org/en-US/docs/Web/API/BatteryManager#browser_compatibility

BatteryManager API is only supported Chrome or Edge.
Safari and Firefox are not supported, so status is expected to be unknown.

Related Issues

• Related [Announcement]: 📢 package web migration and releases #2653

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I titled the PR using Conventional Commits.
• I did not modify the CHANGELOG.md nor the plugin version in pubspec.yaml files.
• All existing and new tests are passing.
• The analyzer (flutter analyze) does not report any problems on my PR.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
• No, this is not a breaking change.

[miquelbeltran]

when will be available a new version in pub.dev?

Please check the pinned issue: #2653

[koji-1009]

I am working on a strange problem.

In the case of flutter run or flutter run --release, we can try-catch the NoSuchMethodError that occurs on window.navigator.getWindow() with battery_plus_web.dart.

  bool get isSupported {
    try {
      web.window.navigator.getBattery();
      return true;
    } on NoSuchMethodError catch (_) {
      // flutter run mode, catch the exception
      return false;
    }
  }

However, if we have a flutter build, we cannot try-catch it in battery_plus_web.dart, but have to try-catch it in main.dart (in example).

  @override
  void initState() {
    super.initState();
    try {
      _battery.batteryState.then(_updateBatteryState);
      _batteryStateSubscription =
          _battery.onBatteryStateChanged.listen(_updateBatteryState);
    } catch (_) {
      // flutter build mode, catch the exception
    }
  }

[koji-1009]

Tested on local server, no problems. Therefore, I believe the problem is caused by hosting on GitHub Pages.

https://stackoverflow.com/questions/65536213/how-to-open-compiled-flutter-web-index-html-in-browser-locally

I'll update the code base and update the demo. And after adding comments (just in case), I will open the PR!

[koji-1009]

demo: https://koji-1009.github.io/plus_plugins/
pr: koji-1009#5

[koji-1009]

Another option is to add a method that determines the browser and returns true only for chrome or edge.
This would be different from other plugin implementations, but it seems like it would avoid Exception, so it may be worth considering.

[miquelbeltran]

Thank you Koji! This is already a big leap forward. We are going to be merging it for now, and our plan is to release all packages by Thursday, we are just waiting for another PR to land.