pdf.js/web/.eslintrc

{
  "extends": [
    ../.eslintrc
  ],

  "rules": {
    // Variables
    "no-restricted-globals": ["error",
      "ReadableStream",
      "URL",
      "WritableStream",
    ],

    // ECMAScript 6
    "no-var": "error",
  },
}
Enable the `no-var` ESLint rule in the `/web` folder https://eslint.org/docs/rules/no-var Please note that two files were excluded: 1. `web/debugger.js`, since there's code in other files that currently depend on the global availability of code in `web/debugger.js`. Furthermore, since that file isn't used in production, doing a ES6 conversion probably isn't a priority. 2. `web/grab_to_pan.js`, since that file could be considered to be "external" code. We have made smaller changes to that file over the years, however doing a full ES6 `class` conversion might be a step too far!? 2017-11-04 13:50:58 +01:00			`{`
			`"extends": [`
			`../.eslintrc`
			`],`

			`"rules": {`
Stop exposing the `URL` polyfill in the global scope This moves/exposes the `URL` polyfill similarily to the existing `ReadableStream` polyfill, rather than exposing it globally, to avoid interfering with any "outside" code. Both the `URL` and `ReadableStream` polyfills are now exposed on the `pdfjsLib` object, such that they are accessible to the viewer components. Furthermore, the `no-restricted-globals` ESLint rule is also enabled to prevent accidental usage of the native `URL`/`ReadableStream` implementations directly in the `src/` and `web/` folders; see also https://eslint.org/docs/rules/no-restricted-globals Addresses the remaining TODO in https://github.com/mozilla/pdf.js/projects/6 2018-07-03 18:32:39 +02:00			`// Variables`
			`"no-restricted-globals": ["error",`
			`"ReadableStream",`
			`"URL",`
			`"WritableStream",`
			`],`

Enable the `no-var` ESLint rule in the `/web` folder https://eslint.org/docs/rules/no-var Please note that two files were excluded: 1. `web/debugger.js`, since there's code in other files that currently depend on the global availability of code in `web/debugger.js`. Furthermore, since that file isn't used in production, doing a ES6 conversion probably isn't a priority. 2. `web/grab_to_pan.js`, since that file could be considered to be "external" code. We have made smaller changes to that file over the years, however doing a full ES6 `class` conversion might be a step too far!? 2017-11-04 13:50:58 +01:00			`// ECMAScript 6`
			`"no-var": "error",`
			`},`
			`}`