Gathering detailed insights and metrics for pure-prompt-nvm
Gathering detailed insights and metrics for pure-prompt-nvm
Gathering detailed insights and metrics for pure-prompt-nvm
Gathering detailed insights and metrics for pure-prompt-nvm
npm install pure-prompt-nvm
Typescript
Module System
Node Version
NPM Version
Shell (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
2 Stars
348 Commits
2 Branches
1 Contributors
Updated on Jan 10, 2025
Latest Version
1.0.10
Package Id
pure-prompt-nvm@1.0.10
Unpacked Size
55.56 kB
Size
19.70 kB
File Count
5
NPM Version
6.13.2
Node Version
13.3.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
No dependencies detected.
Pretty, minimal and fast zsh prompt with nvm integration
This is a fork of sindresorhus/pure that supports nvm instead of virtualenv.
The screenshot above shows how this prompt integrates with the lukechilds/zsh-nvm ZSH plugin installed and NVM_AUTO_USE
set to true
.
nvm
is activegit
branch and whether it's dirty (with a *
).git
commits with up/down arrows. (Check is done asynchronously!)0
.Can be installed with npm
or manually. Requires Git 2.0.0+ and ZSH 5.2+. Older versions of ZSH are known to work, but they are not recommended.
1$ npm install --global pure-prompt-nvm
That's it. Skip to Getting started.
$HOME/.zsh/pure
.1git clone https://github.com/madeleinedaly/pure-nvm.git "$HOME/.zsh/pure"
$fpath
in $HOME/.zshrc
.1# .zshrc 2fpath+=$HOME/.zsh/pure
Initialize the prompt system (if not so already) and choose pure
:
1# .zshrc 2autoload -U promptinit; promptinit 3prompt pure
Option | Description | Default value |
---|---|---|
PURE_CMD_MAX_EXEC_TIME | The max execution time of a process before its run time is shown when it exits. | 5 seconds |
PURE_GIT_PULL=0 | Prevents Pure from checking whether the current Git remote has been updated. | |
PURE_GIT_UNTRACKED_DIRTY=0 | Do not include untracked files in dirtiness check. Mostly useful on large repos (like WebKit). | |
PURE_GIT_DELAY_DIRTY_CHECK | Time in seconds to delay git dirty checking when git status takes > 5 seconds. | 1800 seconds |
PURE_PROMPT_SYMBOL | Defines the prompt symbol. | ❯ |
PURE_PROMPT_VICMD_SYMBOL | Defines the prompt symbol used when the vicmd keymap is active (VI-mode). | ❮ |
PURE_GIT_DOWN_ARROW | Defines the git down arrow symbol. | ⇣ |
PURE_GIT_UP_ARROW | Defines the git up arrow symbol. | ⇡ |
As explained in ZSH's manual, color values can be:
$TERM
is xterm-256color
, see this chart.black
, red
, green
, yellow
, blue
, magenta
, cyan
, white
, and default
(the terminal’s default foreground)#
followed by an RGB triplet in hexadecimal format, for example #424242
. Only if your terminal supports 24-bit colors (true color) or when the zsh/nearcolor
module is loaded.Colors can be changed by using zstyle
with a pattern of the form :prompt:pure:$color_name
and style color
. The color names, their default, and what part they affect are:
execution_time
(yellow) - The execution time of the last command when exceeding PURE_CMD_MAX_EXEC_TIME
.git:arrow
(cyan) - For PURE_GIT_UP_ARROW
and PURE_GIT_DOWN_ARROW
.git:branch
(242) - The name of the current branch when in a Git repository.git:branch:cached
(red) - The name of the current branch when the data isn't fresh.git:action
(242) - The current action in progress (cherry-pick, rebase, etc.) when in a Git repository.git:dirty
(218) - The asterisk showing the branch is dirty.host
(242) - The hostname when on a remote machine.path
(blue) - The current path, for example, PWD
.prompt:error
(red) - The PURE_PROMPT_SYMBOL
when the previous command has failed.prompt:success
(magenta) - The PURE_PROMPT_SYMBOL
when the previous command has succeded.prompt:continuation
(242) - The color for showing the state of the parser in the continuation prompt (PS2). It's the pink part in this screenshot, it appears in the same spot as virtualenv
. You could for example matching both colors so that Pure has a uniform look.user
(242) - The username when on remote machine.user:root
(default) - The username when the user is root.nvm_version
(242) - The current nvm
version when not set to system
.The following diagram shows where each color is applied on the prompt:
┌───────────────────────────────────────────────────── path
│ ┌────────────────────────────────────────── git:branch
│ │ ┌─────────────────────────────────── git:action
| | | ┌─────────────────────────── git:dirty
│ │ │ │ ┌───────────────────────── git:arrow
│ │ │ │ │ ┌──────────────── host
│ │ │ │ │ │
~/dev/pure master|rebase-i* ⇡ zaphod@heartofgold 42s
v8.12.0 ❯ │ │
│ │ │ └──── execution_time
│ │ └─────────────────────────── user
│ └───────────────────────────────────────────── prompt
└───────────────────────────────────────────────────── nvm_version (or prompt:continuation)
There are two ways to use RGB colors with the hexadecimal format. The correct way is to use a terminal that support 24-bit colors and enable this feature as explained in the terminal's documentation.
If you can't use such terminal, the module zsh/nearcolor
can be useful. It will map any hexadecimal color to the nearest color in the 88 or 256 color palettes of your termial, but without using the first 16 colors, since their values can be modified by the user. Keep in mind that when using this module you won't be able to display true RGB colors. It only allows you to specify colors in a more convenient way. The following is an example on how to use this module:
1# .zshrc 2zmodload zsh/nearcolor 3zstyle :prompt:pure:path color '#FF0000'
1# .zshrc 2 3autoload -U promptinit; promptinit 4 5# optionally define some options 6PURE_CMD_MAX_EXEC_TIME=10 7 8# change the path color 9zstyle :prompt:pure:path color white 10 11# change the color for both `prompt:success` and `prompt:error` 12zstyle ':prompt:pure:prompt:*' color cyan 13 14prompt pure
In the screenshot you see pure-nvm running in iTerm2 with the dracula theme and Menlo font.
To have commands colorized as seen in the screenshot, install zsh-syntax-highlighting.
ZSH_THEME=""
in your .zshrc
to disable oh-my-zsh themes.vi-mode
, virtualenv
.NOTE: oh-my-zsh
overrides the prompt so Pure must be activated after source $ZSH/oh-my-zsh.sh
.
Symlink (or copy) pure.zsh
to ~/.prezto/modules/prompt/functions/prompt_pure_setup
alongside Prezto's other
prompts. Then set zstyle ':prezto:module:prompt' theme 'pure'
in ~/.zpreztorc
.
Add zmodule madeleinedaly/pure-nvm --source async.zsh --source pure.zsh
to your .zimrc
and run zimfw install
.
Update your .zshrc
file with the following two lines (order matters). Do not use the antigen theme
function.
1antigen bundle mafredri/zsh-async 2antigen bundle madeleinedaly/pure-nvm
Update your .zshrc
file with the following two lines (order matters):
1antibody bundle mafredri/zsh-async 2antibody bundle madeleinedaly/pure-nvm
Update your .zshrc
file with the following two lines:
1zplug mafredri/zsh-async, from:github 2zplug madeleinedaly/pure-nvm, use:pure.zsh, from:github, as:theme
Update your .zshrc
file with the following two lines (order matters):
1zplugin ice pick"async.zsh" src"pure.zsh" 2zplugin light madeleinedaly/pure-nvm
There are currently no FAQs.
See FAQ Archive for previous FAQs.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
0 existing vulnerabilities detected
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
project is archived
Details
Reason
no SAST tool detected
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More