Crates.io | rung |
lib.rs | rung |
version | 0.2.0 |
source | src |
created_at | 2020-11-24 18:50:22.285171 |
updated_at | 2020-12-04 19:24:14.699345 |
description | Useful command-line tools for Angular projects written in Rust. |
homepage | |
repository | https://github.com/DenysVuika/rung |
max_upload_size | |
id | 315918 |
size | 90,575 |
Useful command-line tools for Angular projects written in Rust.
Commands:
Use the --help
argument to get more details about the program or specific command:
rung --help
rung <command> --help
Provides listing of the contents of the angular.json
file.
USAGE:
rung ls [OPTIONS] [SUBCOMMAND]
OPTIONS:
-c, --config <PATH> [default: angular.json]
SUBCOMMANDS:
apps List all applications
help Prints this message or the help of the given subcommand(s)
libs List all libraries
Examples:
# list all projects and libraries
rung ls
# list all applications
rung ls apps
# list all libraries
rung ls libs
By default, the CLI expects the angular.json
file to be in the current directory.
It is also possible to provide a custom path:
rung ls libs -c ./assets/angular/angular.json
Creates a new Angular application with Angular CLI.
Requires an Angular CLI to be installed.
USAGE:
rung new [OPTIONS] <name>
ARGS:
<name> The name of the new workspace and initial project.
OPTIONS:
-d, --directory <DIR> The directory name to create the workspace in.
Differences to running ng new <name>
command directly:
Examples:
# creates new application `app1` in the current directory
rung new app1
# creates a new application `app2` in the `/tmp/apps` directory
rung new app2 -d /tmp/apps
Runs a lightweight web server.
USAGE:
rung serve [FLAGS] [OPTIONS] <dir>
ARGS:
<dir> Target directory
FLAGS:
-o, --open Opens the url in default browser.
OPTIONS:
-h, --host <HOST> Host address [default: 127.0.0.1]
-p, --port <PORT> Port number [default: 8080]
Examples:
# serves application at http://localhost:8081
rung serve ./dist/app1 -p 8081
# serves the application and opens default system browser
rung serve ./dist/app1 -p 8081 --open
Verifies that the JSON file is valid based on the JSON schema.
Usage:
rung check json --file <FILE> --template <TEMPLATE>
OPTIONS:
-f, --file <FILE> input file to validate
-t, --template <TEMPLATE> template file
Examples:
run check json \
-f ./assets/json/example.json \
-t ./assets/json/example.schema.json
Verifies that the file(s) header is matching one or multiple templates. Typically, used for license header checks in source code files.
Main features:
USAGE:
rung check header --file <FILE> --template <TEMPLATE>...
OPTIONS:
-f, --file <FILE> input file
-t, --template <TEMPLATE>... template file
Examples:
# using multiple templates
rung check header \
-f ./assets/files/example-1.ts.txt \
-t ./assets/templates/template-asf.txt \
-t ./assets/templates/template-mit.txt
# using multiple files and templates
rung check header \
-f ./assets/files/* \
-t ./assets/templates/*
Rung is primarily distributed under the terms of the Apache License (Version 2.0).
See LICENSE for more details.