Google Git
Sign in
dart / sdk / 66a2ecd082481470fef8010641b54ba0aa24f401 / . / pkg
tree: 414bc3e53f2fd1d9e05dcf56bcbeeb8baeda30d4 [path history] [tgz]
  1. _fe_analyzer_shared/
  2. _js_interop_checks/
  3. _macros/
  4. analysis_server/
  5. analysis_server_client/
  6. analysis_server_plugin/
  7. analyzer/
  8. analyzer_cli/
  9. analyzer_plugin/
  10. analyzer_utilities/
  11. async_helper/
  12. bisect_dart/
  13. build_integration/
  14. compiler/
  15. dart2bytecode/
  16. dart2js_info/
  17. dart2js_runtime_metrics/
  18. dart2js_tools/
  19. dart2native/
  20. dart2wasm/
  21. dart_internal/
  22. dart_service_protocol_shared/
  23. dartdev/
  24. dds/
  25. dds_service_extensions/
  26. dev_compiler/
  27. dtd/
  28. dtd_impl/
  29. dynamic_modules/
  30. expect/
  31. front_end/
  32. frontend_server/
  33. heap_snapshot/
  34. js/
  35. js_ast/
  36. js_runtime/
  37. js_shared/
  38. json/
  39. kernel/
  40. language_versioning_2_12_test/
  41. linter/
  42. macros/
  43. meta/
  44. mmap/
  45. modular_test/
  46. native_stack_traces/
  47. record_use/
  48. reload_test/
  49. scrape/
  50. server_plugin/
  51. smith/
  52. sourcemap_testing/
  53. status_file/
  54. telemetry/
  55. test_runner/
  56. testing/
  57. vm/
  58. vm_service/
  59. vm_service_interface/
  60. vm_service_protos/
  61. vm_snapshot_analysis/
  62. wasm_builder/
  63. .gitignore
  64. analysis_options.yaml
  65. BUILD.gn
  66. OWNERS
  67. pkg.dart
  68. pkg.status
  69. README.md
pkg/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. It‘s 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