Browserslist Config

A browserslist configuration for all browsers and devices supported within the Galaxy.

Installation

npm install --save-dev @theholocron/browserslist-config

Table of Contents

• Usage
• Browsers & Devices
• Changelog
• Versioning
• Contribution
• Support
• License

Usage

In your project package.json add the following:

{
  "browserslist": [
    "extends @theholocron/browserslist-config"
  ]
}

Which Browsers & Devices We Support

Typically the configuration commonly used contains last 2 versions; the problem with that is now we're supporting browsers like QQ and Baidu forever even though there isn't more that 0.23% global market share. The configuration adopted here was originally taken from this article, and requires the browser has more than 0.25% market share globally as well as not IE11 (Edge and up only) nor any of Opera Mini.

| IE / Edge | Firefox | Chrome | Safari | iOS Safari | Opera | | --------- | --------- | --------- | --------- | --------- | --------- | | Edge| last 10 versions| last 8 versions| last 2 versions| last 2 versions| last 2 versions

Alternative browsers which use the latest version of WebKit, Blink, or Gecko, whether directly or via the platform's web view API, are not explicitly supported. However, it should (in most cases) display and function correctly in these browsers as well. More specific support information is provided below.

How We Track Changes

This project uses a CHANGELOG and GitHub releases which contains a curated, chronologically ordered list of notable changes for each version of a project. Read more about changelogs.

How We Version

We use SemVer for its versioning providing us an opt-in approach to releases. This means we add a version number according to the spec, as you see below. So rather than force developers to consume the latest and greatest, they can choose which version to consume and test any newer ones before upgrading. Please the read the spec as it goes into further detail.

Given a version number MAJOR.MINOR.PATCH, increment the:

• MAJOR version when you make incompatible API changes.
• MINOR version when you add functionality in a backward-compatible manner.
• PATCH version when you make backward-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

How to Contribute

Have a bug or a feature request? Looking to contribute to advance the project? Read our contribution guide or maintenance guide first in order to understand how we do things around here. Or you could look at some of our other guides below:

• Ask or Say Something?
  • Request Support
  • Report an Error or Bug
  • Request a Feature
• Make Something?
  • Setup the Project
  • Create an Issue
  • Create a Feature Request
  • Contribute Documentation
  • Contribute Code
  • Join the Team
• Manage Something
  • Provide Support on Issues
  • Label Issues
  • Clean Up Issues and PRs
  • Create a Pull Request
  • Review Pull Requests
  • Merge Pull Requests
  • Tag a Release
  • Release a Version

Where to Find Support

Looking to talk to someone or need some help? Please read our support guidelines.

License

©2020 GNU General Public License v3. See LICENSE for specifics.