Security News
pnpm 10.0.0 Blocks Lifecycle Scripts by Default
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
get-shell-vars
Advanced tools
Code that sources correct profiles, so that you can use all Environment variables declared in them.
Code that sources correct profiles, so that you can use all Environment variables declared in them.
In case you want to use the default settings for current OS, just call getEnvironmentVariables
method without arguments.
npm install --save get-shell-vars
const shellVars = require("get-shell-vars");
shellVars.getEnvironmentVariables();
The result is an object with all environment variables.
In many cases, you may need to use specific SHELL or custom terminal settings, you may pass an object to getEnvironmentVariables
method and the module will respect them instead of the default ones.
The object has the following definition:
/**
* Defines the user specific configuration of the shell and terminal.
*/
interface IUserConfiguration {
/**
* Path to the shell that should be used.
* @example "/bin/sh"
* By default this value is taken from SHELL environment variable and in case it is not set, "/bin/bash" is used.
*/
shell: string;
/**
* Describes the configuration of the terminal that the user would like to have.
* These settings modify the behavior, i.e. which profile files of the respective shell will be loaded.
*/
terminalConfiguration: {
/**
* Defines if the terminal is interactive or no.
* `true` by default.
*/
isInteractive: boolean;
/**
* Defines if login session will be started.
* `false` by default on Linux.
* `true` on all other OSes.
*/
isLogin: boolean;
}
}
You can pass only the properties that you want to modify. For example:
const shellVars = require("get-shell-vars");
const userConfiguration = {
terminalConfiguration: {
isLogin: true
}
};
shellVars.getEnvironmentVariables(userConfiguration);
The module will use different shell settings on each OS.
The module will always return the value of process.env
.
The module will spawn a new interactive, non-login shell. The shell is taken from SHELL
environment variable.
The module will spawn a new interactive, login shell. The shell is taken from SHELL
environment variable.
The package requires Node.js 6.0.0 or later.
FAQs
Code that sources correct profiles, so that you can use all Environment variables declared in them.
The npm package get-shell-vars receives a total of 2 weekly downloads. As such, get-shell-vars popularity was classified as not popular.
We found that get-shell-vars demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.