challenge-algorithms-v2.0-s.../node_modules/browserslist
2022-10-27 15:51:35 -03:00
..
browser.js feat: Resolve o exercício 01-greeting 2022-10-27 15:51:35 -03:00
cli.js feat: Resolve o exercício 01-greeting 2022-10-27 15:51:35 -03:00
error.d.ts feat: Resolve o exercício 01-greeting 2022-10-27 15:51:35 -03:00
error.js feat: Resolve o exercício 01-greeting 2022-10-27 15:51:35 -03:00
index.d.ts feat: Resolve o exercício 01-greeting 2022-10-27 15:51:35 -03:00
index.js feat: Resolve o exercício 01-greeting 2022-10-27 15:51:35 -03:00
LICENSE feat: Resolve o exercício 01-greeting 2022-10-27 15:51:35 -03:00
node.js feat: Resolve o exercício 01-greeting 2022-10-27 15:51:35 -03:00
package.json feat: Resolve o exercício 01-greeting 2022-10-27 15:51:35 -03:00
parse.js feat: Resolve o exercício 01-greeting 2022-10-27 15:51:35 -03:00
README.md feat: Resolve o exercício 01-greeting 2022-10-27 15:51:35 -03:00

Browserslist Cult Of Martians

Browserslist logo by Anton Popov

The config to share target browsers and Node.js versions between different front-end tools. It is used in:

All tools will find target browsers automatically, when you add the following to package.json:

  "browserslist": [
    "defaults and supports es6-module",
    "maintained node versions"
  ]

Or in .browserslistrc config:

# Browsers that we support

defaults and supports es6-module
maintained node versions

Developers set their version lists using queries like last 2 versions to be free from updating versions manually. Browserslist will use caniuse-lite with Can I Use data for this queries.

You can check how config works at our playground: browsersl.ist

browsersl.ist website

Docs

Read full docs on GitHub.