@naverpay/browserslist-config
Advanced tools
Shareable Browserslist configuration for @naverpay/frontend
This package provides a unified and maintainable list of supported browsers and Node.js versions for all NAVERPAY frontend services.
Current support range: >= 1%, not dead, not op_mini all, not ie >= 0, not ios_saf < 16, ios_saf >= 16, node >= 18.18.0, Chrome >= 106
npm install --save-dev @naverpay/browserslist-config
# or
yarn add -D @naverpay/browserslist-config
# or
pnpm add -D @naverpay/browserslist-config
package.json{
"browserslist": ["extends @naverpay/browserslist-config"]
}
.browserslistrc fileextends @naverpay/browserslist-config
See the full, up-to-date list here: browsersl.ist Query (KR)
Q: Why use a shared Browserslist config? A: It ensures every @naverpay/frontend project follows the same browser support policy—less redundancy, fewer mistakes.
Q: How often is it updated? A: As the business/project requirements or browser landscape changes. Check CHANGELOG for details.
Q: How do I check the resolved browser list? A:
npx browserslist
Or use browsersl.ist with the query above.
ISC
FAQs
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
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.
Research
Malicious versions of the Telnyx Python SDK on PyPI delivered credential-stealing malware via a multi-stage supply chain attack.
Security News
TeamPCP is partnering with ransomware group Vect to turn open source supply chain attacks on tools like Trivy and LiteLLM into large-scale ransomware operations.