@envsa/browserslist-config
Advanced tools
Browserslist configuration for @envsa/shared-config.
Browserslist configuration for @envsa/shared-config.
It's a shared Browserslist config.
See @envsa/shared-config for the recommended single-package approach.
To use just this browserslist config in isolation:
Install the .npmrc in your project root. This is required for correct PNPM behavior:
pnpm dlx @envsa/repo-config --init
Add the package:
pnpm add -D @envsa/browserslist-config
Integrate with your package.json scripts as you see fit, for example:
"browserslist": ["extends @envsa/browserslist-config"]
or use the cli
browserslist-config --initBrowserslist configuration for @envsa/shared-config.
Usage:
browserslist-config --init
| Option | Description |
|---|---|
--init-i | Add browserslist key to package.json. |
--help-h | Print this help info. |
--version-v | Print the package version. |
MIT © Liam Rella
FAQs
Browserslist configuration for @envsa/shared-config.
The npm package @envsa/browserslist-config receives a total of 28 weekly downloads. As such, @envsa/browserslist-config popularity was classified as not popular.
We found that @envsa/browserslist-config demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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
Research
Socket researchers have discovered malicious npm packages targeting crypto developers, stealing credentials and wallet data using spyware delivered through typosquats of popular cryptographic libraries.
Security News
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.
Security News
A Stanford study reveals 9.5% of engineers contribute almost nothing, costing tech $90B annually, with remote work fueling the rise of "ghost engineers."