cli_pkg 2.1.4

cli_pkg: ^2.1.4 copied to clipboard

• Now merges "exports" objects declared in the original package.json when using JsRequires with a target other than all. Note that string and array values will still be overwritten.

• Don't mangle lists in automatically-extracted CHANGELOG entries for GitHub releases.

• Use dart pub commands rather than pub for compatibility with the latest Dart releases.

• Narrow the SDK constraint to reflect the use of a new API.

• Add pkg-github-$os-$arch tasks, which compile and upload binaries for the given operating system and architecture.

• pkg-github-linux, pkg-github-macos, and pkg-github-windows now compile and upload binaries for all supported architectures.

• Use dart pub commands rather than pub for compatibility with the latest Dart releases.

• Fix a bug where dynamic calls to require() would always be null in an npm package.

• Fix a bug where an npm package with target-specific JSRequires would include an invalid "main" field in its package.json.

• Work around an npm bug that was causing npm publish to fail.

• Breaking change: The jsRequires map has been changed to a list of JSRequire objects. These objects allow packages to specify exactly which target(s) a given dependency should be loaded on, so for example they can provide a package that loads the fs module for Node.js but can still be bundled for the browser without it.

• Callbacks passed to ConfigVariable.fn= can now return nullable values even for non-nullable types. Doing so will cause the variable to use its default value. The behavior for nullable types remains unchanged.

• Add pkg-standalone-linux-arm64 and pkg-standalone-mac-arm64 tasks, which compile Linux and Mac OS binaries respectively for 64-bit ARM architectures. As with other 64-bit architectures, these will compile native executables when invoked on the same OS/architecture combination they're targeting, and will compile script snapshots otherwise.

• pkg-standalone-all now compiles Linux and Mac OS binaries for 64-bit ARM architectures.

• Use dart compile exe and dart compile aot-snapshot instead of dart2native when compiling standalone executables.

• The space character is no longer forbidden in environment constants, since https://github.com/dart-lang/sdk/issues/46050 has been fixed.

• Properly run executables from source in testing.dart when their public names are different than their filenames.

• Add pkg.npmAdditionalFiles to make it possible to add custom files to npm packages.

• pkg.addChocolateyTasks() no longer automatically adds standalone tasks, since Chocolatey tasks no longer depend on standalone tasks.

• pkg-chocolatey now creates a file named LICENSE.txt rather than LICENSE, at the request of the Chocolatey reviewers.

• Add pkg.environmentConstants to make it possible to define custom environment constants for the compiled executables.

• Migrate to null-safety.

• Add a pkg.githubBearerToken to make it easier to integrate with GitHub actions.

• Generate a fully standalone executable on Linux rather than a native snapshot.

• The main function generated by this package will return a Promise if the corresponding Dart main function returns a Future.

• Initial stable release.

Changes since 1.0.0-beta.13 #

• Don't fold link reference declarations like paragraphs when generating GitHub release notes.

• Add a ConfigVariable.defaultValue property to get the default value for variables that are overridden by functions.

• Fix a typo in error messages when files need to be regenerated for tests.

• Deploy Chocolatey packages as source files rather than a zip file, to avoid validation errors around the need for a VERIFICATION file.

• Properly load the Dart SDK license when it's in the directory above the SDK, as in a Homebrew installation.

• Use the latest version of the xml package.

• Breaking change: All configurable variables are now defined as ConfigVariable objects rather than top-level fields. These objects make it possible to configure variables with callback functions and to freeze those variables once execution has begun.

• Properly handle git repositories that use branch names other than master.

• Improve error messages if release notes can't be extracted from CHANGELOG.md.

• Fixes a bug when reading a CHANGELOG.md with Windows-style line endings.

• Breaking change: Dart snapshots are now named based on the executable name (specified in the pubspec or in pkg.executables) instead of the name of the Dart file in bin.

• Breaking change: Chocolatey now uses the choco CLI to build and deploy packages, rather than re-implementing its logic in Dart. In particular:

  • The pkg-chocolatey-build task has been renamed to pkg-chocolatey-pack to match the CLI's naming scheme.

  • The pkg-chocolatey-pack and pkg-chocolatey-deploy tasks must be run in an environment with the choco command available.

• Add a pkg-chocolatey command that builds an un-archived Chocolatey package directory.

• Rather than releasing binary snapshots on Chocolatey, compile the source code to compile native executables on users' machines.

• Add a chocolateyFiles getter that returns the files that should be included in the Chocolatey package.

• Depend on the correct version of pre-release Dart SDKs from Chocolatey packages.

• Use the correct URL when fetching GitHub release metadata.

• Add a pkg.npmDistTag getter that controls the distribution tag for an npm release.

• Add a pkg.homebrewCreateVersionedFormula getter that controls whether the Homebrew release creates a new formula or updates an existing one.

• Run pub publish --force so it doesn't hang forever.

• Properly parse GitHub repositories from HTTP URLs ending in .git.

• Drop support for Mac OS ia32 packages, since Dart 2.7 doesn't support them anymore.

• Add a cli_pkg/testing.dart library to make it easier for users to efficiently and reliably test their executables.

• Add a pkg-standalone-dev task for building a script that can be invoked for testing.

• Fix a bug where the version variable wouldn't be set for certain executables.

• Initial beta release.