landlubber
v2.0.0
Published
The quickest way to write commands for yargs without leaving the shore.
Downloads
1,506
Readme
Landlubber
The quickest way to write commands for yargs without leaving the shore.
Description
Landlubber is a tiny wrapper around yargs.
- Streamline writing commands as individual ES modules.
- Has pretty logging with pino and pino-pretty.
- Written in TypeScript so command arguments and context are fully typed.
Installation
Add this as a dependency to your project using npm with
$ npm install landlubber
Usage
Hello world
TypeScript
hello.ts
import type { Builder, Command, Describe, Handler } from 'landlubber'
interface Options {
name: string
}
export const command: Command = 'hello name'
export const describe: Describe = 'Say hello'
export const builder: Builder = {
name: {
type: 'string',
default: 'landlubber',
describe: 'Who to greet'
}
}
export const handler: Handler<Options> = async ({ name, logger }) => {
logger.info({ landlubber: name }, 'Ahoy!')
}
index.ts
#!/usr/bin/env tsx
import landlubber from 'landlubber'
import * as hello from './hello.js'
const commands = [hello]
await landlubber(commands).parse()
JavaScript
hello.js
export const command = 'hello name'
export const describe = 'Say hello'
export const builder = {
name: {
type: 'string',
default: 'landlubber',
describe: 'Who to greet'
}
}
export const handler = async ({ name, logger }) => {
logger.info({ landlubber: name }, 'Ahoy!')
}
index.js
#!/usr/bin/env node
import landlubber from 'landlubber'
import * as hello from './hello.js'
const commands = [hello]
await landlubber(commands).parse()
Development and Testing
Quickstart
$ git clone https://github.com/razor-x/landlubber.git
$ cd landlubber
$ nvm install
$ npm install
Run the command below in a separate terminal window:
$ npm run test:watch
Primary development tasks are defined under scripts
in package.json
and available via npm run
.
View them with
$ npm run
Source code
The source code is hosted on GitHub. Clone the project with
$ git clone [email protected]:razor-x/landlubber.git
Requirements
You will need Node.js with npm and a Node.js debugging client.
Be sure that all commands run under the correct Node version, e.g., if using nvm, install the correct version with
$ nvm install
Set the active version for each shell session with
$ nvm use
Install the development dependencies with
$ npm install
Publishing
Use the npm version
command to release a new version.
This will push a new git tag which will trigger a GitHub action.
Publishing may be triggered using a workflow_dispatch on GitHub Actions.
GitHub Actions
GitHub Actions should already be configured: this section is for reference only.
The following repository secrets must be set on GitHub Actions:
NPM_TOKEN
: npm token for installing and publishing packages.GH_TOKEN
: A personal access token for the user.GIT_USER_NAME
: The GitHub user's real name.GIT_USER_EMAIL
: The GitHub user's email.GPG_PRIVATE_KEY
: The GitHub user's GPG private key.GPG_PASSPHRASE
: The GitHub user's GPG passphrase.
These must be set manually.
Contributing
Please submit and comment on bug reports and feature requests.
To submit a patch:
- Fork it (https://github.com/razor-x/landlubber/fork).
- Create your feature branch (
git checkout -b my-new-feature
). - Make changes.
- Commit your changes (
git commit -am 'Add some feature'
). - Push to the branch (
git push origin my-new-feature
). - Create a new Pull Request.
License
This npm package is licensed under the MIT license.
Warranty
This software is provided by the copyright holders and contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the copyright holder or contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.