History

Update packages + fix tests for javascript mime change (#118617 )

Update test expectations from application/javascript -> text/javascript

`package:mime` now uses `text/javascript` and not `application/javascript`.

See https://github.com/dart-lang/mime/pull/76.
See https://datatracker.ietf.org/doc/html/rfc9239.

> This document defines equivalent processing requirements for the various script media types. The most widely supported media type in use is `text/javascript`; all others are considered historical and obsolete aliases of `text/javascript`.

2023-01-19 09:54:40 -05:00

android

[Android] Bump Kotlin and Android Gradle plugin versions in tests (#112728 )

2022-10-07 12:30:27 +00:00

ios

Add Info.plist from build directory as input path to Thin Binary build phase (#118209 )

2023-01-13 13:41:08 -06:00

lib

Revert "Speed up first asset load by encoding asset manifest in binary rather than JSON (#113637 )" (#116662 )

2022-12-07 17:29:05 +00:00

money_asset_manifest.json

Add asset manifest parsing benchmark (#112836 )

2022-10-07 13:39:35 +00:00

pubspec.yaml

Update packages + fix tests for javascript mime change (#118617 )

2023-01-19 09:54:40 -05:00

README.md

Restore the original name of the velocity tracker microbenchmark (#64060 )

2020-08-19 00:41:06 -07:00

README.md

microbenchmarks

To run these benchmarks on a device, first run `flutter logs' in one window to see the device logs, then, in a different window, run any of these:

flutter run --release lib/gestures/velocity_tracker_bench.dart
flutter run --release lib/gestures/gesture_detector_bench.dart
flutter run --release lib/stocks/animation_bench.dart
flutter run --release lib/stocks/build_bench.dart
flutter run --release lib/stocks/layout_bench.dart

The results should be in the device logs.

Avoid changing names of the benchmarks

Each microbenchmark is identified by a name, for example, "catmullrom_transform_iteration". Changing the name of an existing microbenchmarks will effectively remove the old benchmark and create a new one, losing the historical data associated with the old benchmark in the process.