Martin Kustermann
19caeb8604
* It had already the assumption there's a `.` in the name but didn't check for it => Validate that the output file ends with `.wasm` * Make the unoptimized wasm (if emitted) be `.unopt.wasm` => It's a wasm file, so it should have a .wasm extension This is a step towards making flutter use `dart compile wasm` directly without the AOT snapshot of pkg/dart2wasm/bin/dart2wasm and wasm-opt separately. Which will allow removing of the duplicated wasm-opt flag list in flutter. Change-Id: I685bb1aaa9d95ab43936bab68add916a642eb296 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/347280 Reviewed-by: Michael Thomsen <mit@google.com> Commit-Queue: Martin Kustermann <kustermann@google.com>
Package validation
The packages in pkg/ are automatically validated on the LUCI CI bots. The
validation is largely done by the tools/package_deps package; it can be tested
locally via:
dart tools/package_deps/bin/package_deps.dart
Packages which are published
There are several packages developed in pkg/ which are published to pub.
Validation of these packages is particularly important because the pub tools are
not used for these packages during development; we get our dependency versions
from the DEPS file. Its very easy for the dependencies specified in a package's
pubspec file to get out of date wrt the packages and versions actually used.
In order to better ensure we're publishing correct packages, we validate some properties of the pubspec files on our CI system. These validations include:
- that the dependencies listed in the pubspec are used in the package
- that all the packages used by the source are listed in the pubspec
- that we don't use relative path deps to pkg/ or third_party/ packages
Packages which are not published
For packages in pkg/ which we do not intend to be published, we put the following comment in the pubspec.yaml file:
# This package is not intended for consumption on pub.dev. DO NOT publish.
publish_to: none
These pubspecs are still validated by the package validation tool. The contents are more informational as the pubspecs for these packages are not consumed by the pub tool or ecosystem.
We validate:
- that the dependencies listed in the pubspec are used in the package
- that all the packages used by the source are listed in the pubspec
- that a reference to a pkg/ package is done via a relative path dependency