You may already have this configuration file as it is used by many tools in the ecosystem, like autoprefixer, stylelint, eslint-plugin-compat and many others.īy default will use browserslist config sources unless either the targets or ignoreBrowserslistConfig options are set. Browserslist Integration įor browser- or Electron-based projects, we recommend using a. The shippedProposals option will include Stage 3 proposals that some browsers have already takes any target environments you've specified and checks them against its mappings to compile a list of plugins and passes it to Babel.
Those would need to be included manually. Note: won't include any JavaScript syntax proposals less than Stage 3 because at that stage in the TC39 process, it wouldn't be implemented by any browsers anyway. We leverage these data sources to maintain mappings of which version of our supported target environments gained support of a JavaScript syntax or browser feature, as well as a mapping of those syntaxes and features to Babel transform plugins and core-js polyfills. How Does it Work? would not be possible if not for a number of awesome open-source projects, like browserslist, compat-table, and electron-to-chromium.
0 kommentar(er)
