derry 0.0.8+1

Derry is a script manager for Dart. It helps you define script shortcuts and use them effortlessly, and performantly as it should be.

Derry

Derry is a script manager for Dart.

Overview

Derry helps you define shortcut scripts, and save you from having to type very long and forgettable long lines of scripts, again and again.

Instead of running this every time,

pub run build_runner build --delete-conflicting-outputs

Add this to pubspec.yaml,

scripts:
  build: pub run build_runner build --delete-conflicting-outputs

and run

derry run build
# or by alias
derry build

Installation

Install derry as a global dependency from Pub as follows.

pub global activate derry

Then use derry to run a command from the current dart/flutter project.

derry run [script]

Usage

When called, derry will look for a pubspec.yaml file in the current directory, and will throw an error if not exist. The scripts can be declared within the scripts node of the pubspec.yaml file.

scripts:
  build: pub run build_runner build

derry build
# or use `silent` option to hide outputs
derry build --silent
# or even with additional arguments
derry build -- --delete-conflicting-outputs

API Documentation

Use definition file

Scripts can be configured just inside the pubspec.yaml file or within a separate file. When using a separate file to configure scripts, pass the file name as the value of the scripts node in the pubspec.yaml file.

# pubspec.yaml
scripts: derry.yaml

# derry.yaml
build: pub run build_runner build

Use scripts as List

A script can either be a single string or a list of strings. If it is a list, the strings inside of the list will be executed synchronously in the given order of the list.

build:
  - pub run test
  - echo "test completed"
  - pub run build_runner build

Use aliases

Most used scripts are defined as aliases that you can use with a shorter derry command. Options available with derry run command will also be available with these aliases. No other functionalities are added to these aliases, they are just extensions of derry run command.

derry build # instead of derry run build
derry test # instead of derry run test

Nested scripts

Scripts can be nested as the user needed. For example, you can use them to use different implementations of the build script based on operating system.

# derry.yaml
build:
  windows:
    - echo 0 # do something
  mac:
    - echo 1 # do something else

And you can use them by calling derry build windows on windows and derry build mac on macOS.

Configure execution type

Note that in the list of scripts, executions will happen in separate processes, use && to execute multiple scripts in the same process. Alternatively, you can also configure the execution value. To separate the configuration values from nested scripts, wrap the keys of the configurations with parenthesis as in (execution).

build:
  (execution): once # multiple by default
  (scripts):
    - cat generated.txt
    - pub run build_runner build # won't be called if generated.txt does not exist

This will be the same as using && but it saved the user from having very long lines of scripts.

Use subcommands

When defining scripts, the user can also define subcommands. Subcommands are references to commands/scripts that won't be executed with a separate derry process. For example,

test:
  - pub run test
  - echo "test completed"
build:
  - $test # instead of using derry test
  - flutter build

derry test will spawn a new derry process to execute, while subcommands are not, reducing the time took to run dart code, and spawn that process.

List available scripts

Use this command to see what scripts are available in the current configuration.

derry ls

Why & How

Honestly, I needed it. It was easy to make, though I had a hard time implementing the script execution. Since Dart's Process isn't good at executing system commands, I used Rust with the help of Foreign Function Interfaces. For execution, currently cmd is used for Windows and bash is used for Linux and Mac. I know that's not optimal and I'm still looking for a way to allow users to use the current shell for executions.

Currently Supported Platforms

64bit Linux, Windows, and Mac are currently supported.

License

MIT © Frenco Jobs