mirror of https://github.com/dart-lang/sdk synced 2024-11-02 10:28:02 +00:00

History

Srujan Gaddam 35cae2d4da [pkg:js] Rename export and mock transformers and separate them Per previous review comment - this separates the three components into separate files. Change-Id: I601bd9ac29ddd032e913a60ce2b5b7dd81e39efc Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/264603 Reviewed-by: Riley Porter <rileyporter@google.com> Reviewed-by: Joshua Litt <joshualitt@google.com>		2022-10-26 16:34:38 +00:00
..
_fe_analyzer_shared
_js_interop_checks	[pkg:js] Rename export and mock transformers and separate them	2022-10-26 16:34:38 +00:00
analysis_server
analysis_server_client
analyzer
analyzer_cli
analyzer_plugin
analyzer_utilities
async_helper
build_integration
compiler	[pkg:js] Rename export and mock transformers and separate them	2022-10-26 16:34:38 +00:00
dart2js_info
dart2js_runtime_metrics
dart2js_tools
dart2native
dart2wasm	[pkg:js] Rename export and mock transformers and separate them	2022-10-26 16:34:38 +00:00
dart_internal
dartdev
dds	[dds/dap] Allow debug adapters to register multiple mappings for org-dartland-sdk URIs	2022-10-26 14:26:01 +00:00
dds_service_extensions
dev_compiler	[pkg:js] Rename export and mock transformers and separate them	2022-10-26 16:34:38 +00:00
expect
front_end	[cfe] Handle function calls and null shorting on record types	2022-10-26 14:44:56 +00:00
frontend_server
js
js_ast
js_runtime
js_shared
kernel
language_versioning_2_7_test
meta
modular_test
native_stack_traces
nnbd_migration
scrape
smith
sourcemap_testing
status_file
telemetry
test_runner
testing
vm
vm_service
vm_snapshot_analysis
wasm_builder
.gitignore
BUILD.gn
OWNERS
pkg.status
README.md

README.md

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