Research
Security News
Kill Switch Hidden in npm Packages Typosquatting Chalk and Chokidar
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
browser-env
Advanced tools
Simulates a global browser environment using
jsdom
.
This allows you to run browser modules in Node.js 6 or newer with minimal or no effort. Can also be used to test browser modules with any Node.js test framework. Please note, only the DOM is simulated, if you want to run a module that requires more advanced browser features (like localStorage
), you'll need to polyfill that seperately.
Use browser-env@2
to support older Node.js versions.
❗️Important note
This module adds properties from the
jsdom
window namespace to the Node.js global namespace. This is explicitly recommended against byjsdom
. There may be scenarios where this is ok for your use case but please read through the linked wiki page and make sure you understand the caveats. If you don't need the browser environment enabled globally,window
may be a better solution.
npm install --save browser-env
Or if you're just using for testing you'll probably want:
npm install --save-dev browser-env
// Init
require('browser-env')();
// Now you have access to a browser like environment in Node.js:
typeof window;
// 'object'
typeof document;
// 'object'
var div = document.createElement('div');
// HTMLDivElement
div instanceof HTMLElement
// true
By default everything in the jsdom
window namespace is tacked on to the Node.js global namespace (excluding existing Node.js properties e.g console
, setTimout
). If you want to trim this down you can pass an array of required properties:
// Init
require('browser-env')(['window']);
typeof window;
// 'object'
typeof document;
// 'undefined'
You can also pass a config object straight through to jsdom
. This can be done with or without specifying required properties.
require('browser-env')(['window'], { userAgent: 'My User Agent' });
// or
require('browser-env')({ userAgent: 'My User Agent' });
You can of course also assign to a function:
var browserEnv = require('browser-env');
browserEnv();
// or
import browserEnv from 'browser-env';
browserEnv();
browser-env
can also be preloaded at node startup as:
node -r browser-env/register test.js
window
- Exports a jsdom window objectMIT © Luke Childs
FAQs
Simulates a global browser environment using jsdom
The npm package browser-env receives a total of 16,496 weekly downloads. As such, browser-env popularity was classified as popular.
We found that browser-env demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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 found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
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.