Search Results for "setup-2a bin"

Get the current package's binary path (using the package.json bin field). This is useful when testing a package's binary. Using get-bin-path (as opposed to hard-coding the path to the binary). Validates that the package.json bin field is correctly setup. Decouples the binary path from the tests, which allows moving the file without rewriting the tests. This package is an ES module and must be loaded using an import or import() statement, not require(). ...

...It runs everywhere Neovim runs (across Linux, macOS, Windows, etc.), with only a small set of external requirements needed. Packages are installed in Neovim's data directory (:h standard-path) by default. Executables are linked to a single bin/ directory, which mason.nvim will add to Neovim's PATH during setup, allowing seamless access from Neovim builtins (shell, terminal, etc.) as well as other 3rd party plugins.