Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Utility for mananging node development environments.
npm i nenv --save
function nenv([environments, get, set])
var env = require('nenv')();
if(!env.defined) {
// do something when no environment was specified
// maybe: env.set(env.DEVEL) or whichever default you want
}else if(!env()) {
// do something when the specified environment is invalid
}else if(env.test) {
// do something for test environment
}
environments
: Array or object of custom environments, if not specified the defaults
are used.get
: A custom function for getting the environment value (optional).set
: A custom function for setting the environment value (optional).Determines if an environment value is valid. Returns false
is the supplied value is invalid or the string key for the environment if valid.
If no value is supplied then env.value
is used which allows testing whether the default value is valid by calling with no arguments.
The value returned from get()
when nenv()
was called, the initial environment value.
Boolean that determines whether env.value
is a recognised environment.
Determines whether an initial value (env.value
) was defined.
Get the current value of the environment, the default implementation returns process.env.NODE_ENV
.
Set the current value of the environment, the default implementation returns false
if the supplied value is not a known environment alias otherwise a function that may be called to revert to the previous value.
Default values to use.
['test', 'devel', 'stage', 'production'];
Pass an object or array to define your available environments:
var nenv = require('nenv')
, env = nenv({production: ['production', 'pro'], dev: 'dev', test: 'test'});
console.log(env.keys);
var env = require('./')()
, str = JSON.stringify(env.jsonify(), undefined, 2);
process.stdout.write(str);
Executed with NODE_ENV=devel
, yields:
{
"TEST": "test",
"DEVEL": "devel",
"STAGE": "stage",
"PRODUCTION": "production",
"value": "devel",
"valid": true,
"defined": true,
"map": {
"test": [
"test"
],
"devel": [
"devel"
],
"stage": [
"stage"
],
"production": [
"production"
]
},
"keys": [
"test",
"devel",
"stage",
"production"
],
"test": false,
"devel": true,
"stage": false,
"production": false
}
Run the test specifications:
npm test
Generate the project readme file (requires mdp):
npm run readme
Everything is MIT. Read the license if you feel inclined.
Generated by mdp(1).
FAQs
Node development environment manager
The npm package nenv receives a total of 3 weekly downloads. As such, nenv popularity was classified as not popular.
We found that nenv demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 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.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.