Skip to content

Latest commit

 

History

History
 
 

pkg

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
_fe_analyzer_shared
_fe_analyzer_shared
 
 
_js_interop_checks
_js_interop_checks
 
 
analysis_server
analysis_server
 
 
analysis_server_client
analysis_server_client
 
 
analyzer
analyzer
 
 
analyzer_cli
analyzer_cli
 
 
analyzer_plugin
analyzer_plugin
 
 
analyzer_utilities
analyzer_utilities
 
 
async_helper
async_helper
 
 
build_integration
build_integration
 
 
compiler
compiler
 
 
dart2js_info
dart2js_info
 
 
dart2js_runtime_metrics
dart2js_runtime_metrics
 
 
dart2js_tools
dart2js_tools
 
 
dart2native
dart2native
 
 
dart_internal
dart_internal
 
 
dartdev
dartdev
 
 
dds
dds
 
 
dev_compiler
dev_compiler
 
 
diagnostic
diagnostic
 
 
expect
expect
 
 
front_end
front_end
 
 
frontend_server
frontend_server
 
 
js
js
 
 
js_ast
js_ast
 
 
js_runtime
js_runtime
 
 
kernel
kernel
 
 
language_versioning_2.7_test
language_versioning_2.7_test
 
 
meta
meta
 
 
modular_test
modular_test
 
 
native_stack_traces
native_stack_traces
 
 
nnbd_migration
nnbd_migration
 
 
scrape
scrape
 
 
smith
smith
 
 
sourcemap_testing
sourcemap_testing
 
 
status_file
status_file
 
 
telemetry
telemetry
 
 
test_runner
test_runner
 
 
testing
testing
 
 
vm
vm
 
 
vm_service
vm_service
 
 
vm_snapshot_analysis
vm_snapshot_analysis
 
 
.gitignore
.gitignore
 
 
BUILD.gn
BUILD.gn
 
 
README.md
README.md
 
 
pkg.status
pkg.status
 
 

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