npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

mert

v0.9.0

Published

An iTerm 3-compatible window, tab, and pane manager.

Downloads

128

Readme

An iTerm 3-compatible window, tab, and pane manager.

Installation

npm install -g mert

Usage

mert init [type]   # Create new .mertrc file. Options: global or local
mert start [name]  # Start project by name or by specifying file path (defaults to .mertrc in cwd)

Overview

mert is a simple command line tool for managing your windows, tabs, and pane configurations for iTerm 3 and iTerm 2. A little yaml config file (called the .mertrc file) along with some JXA (Javascript + Applescript), you can have your iTerm environment up and running in no time.

mert uses a combination of a "global" file at ~/.mertrc and/or one in your current directory to spin up your iTerm environment.

Examples

mert supports window, tab, and pane management. Examples live inside of ./tests/examples, so that's a great place to start.

Take the following two .mertrc files:

Global Config

# ~/.mertrc
foo:
  root: ~/code/foo
  layout:
    -
      - echo "Row 1, Pane 1"
      - echo "Row 1, Pane 2"
    -
      - echo "Row 2, Pane 1"

Local Config

# /Users/brian/code/bar/.mertrc
layout:
  -
    - echo "Row 1, Pane 1 in bar"
    - echo "Row 1, Pane 2 in bar"
  -
    - echo "Row 2, Pane 1 in bar"

Running the following:

mert start foo

would result in the following iTerm window, each command running in ~/code/foo:

+-------------------------------------------+
| "Row 1, Pane 1"     | "Row 1, Pane 2      |
|                     |                     |
|---------------------|---------------------|
| "Row 2, Pane 2"     | "Row 2, Pane 2      |
|                     |                     |
+---------------------|---------------------+

Conversely, running:

cd /Users/brian/code/bar/.mertrc
mert start

Would spin up the .mertrc file within the parent directory.

Checkout the demo below:

mert demo

Split Strategy

By default mert adopts a vertical-first split strategy. This behavior can be changed by explicitly setting the split_strategy option to 'horizontal' in the .mertrc file.

Take for example the following .mertrc:

layout:
  -
    - echo "Row 1, Pane 1"
  -
    - echo "Row 2, Pane 1"
    - echo "Row 2, Pane 2"

This would result in the following iTerm window:

+-------------------------------------------+
| "Row 1, Pane 1"                           |
|                                           |
|---------------------|---------------------|
| "Row 2, Pane 2"     | "Row 2, Pane 2      |
|                     |                     |
+---------------------|---------------------+

Whereas a .mertrc with the split_strategy configuration set, as shown here:

split_strategy: "vertical"
layout:
  -
    - echo "Col 1, Pane 1"
  -
    - echo "Col 2, Pane 1"
    - echo "Col 2, Pane 2"

would produce an iTerm window like the one below:

+---------------------|---------------------+
| "Col 1, Pane 1"     | "Col 2, Pane 1      |
|                     |                     |
|                     |---------------------|
|                     | "Col 2, Pane 2      |
|                     |                     |
+---------------------|---------------------+

Launch Strategy

By default mert will start a new iTerm window and launch your layout into it. You can choose to launch your layout into a new tab, or into the current pane, instead by using the root-level launch_strategy option.

See Tab Launch Strategy and In-Place Launch Strategy for an example.

Profiles

By default mert will use the Default iTerm profile. You can use a different profile for your layout by adding the root-level profile option.

To use a different profile, set the profile configuration on the .mertrc file:

profile: "MyProfile"
layout:
  -
    - echo "Col 1, Pane 1"
  -
    - echo "Col 2, Pane 1"
    - echo "Col 2, Pane 2"

Testing

npm run test

License

Released under the MIT License.

Questions?

Brought to you by eggplanet.

Contributors