pdf.js/extensions/chromium/.eslintrc

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

  "env": {
    "webextensions": true
  },

  "plugins": [
    "mozilla"
  ],

  "parserOptions": {
    "sourceType": "script"
  },

  "rules": {
    "mozilla/import-globals": "error",
    "no-var": "off",
  },
}
Enable babel translation to enable ES module support. 2017-03-06 08:42:48 -06:00			`{`
			`"extends": [`
			`../../.eslintrc`
			`],`

Use eslint-plugin-mozilla and the webextensions environment to avoid defining globals in each file. 2017-05-17 10:30:46 +01:00			`"env": {`
			`"webextensions": true`
			`},`

			`"plugins": [`
			`"mozilla"`
			`],`

Enable babel translation to enable ES module support. 2017-03-06 08:42:48 -06:00			`"parserOptions": {`
			`"sourceType": "script"`
			`},`
Enable the `object-shorthand` ESLint rule Please see http://eslint.org/docs/rules/object-shorthand. Unfortunately, based on commit https://github.com/mozilla/pdf.js/commit/9276d1dcd97b4b0dc45342608a7f1b1a7f1e9c5b, it seems that we still need to maintain compatibility with old Node.js versions, hence certain files/directories that are executed in Node.js are currently exempt from this rule. Furthermore, since the files specific to the Chromium extension are not run through Babel, the `/extensions/chromium/` directory is also exempt from this rule. 2017-04-28 13:40:47 +02:00
			`"rules": {`
Use eslint-plugin-mozilla and the webextensions environment to avoid defining globals in each file. 2017-05-17 10:30:46 +01:00			`"mozilla/import-globals": "error",`
Enable the ESLint `no-var` rule globally A significant portion of the code-base has now been converted to use `let`/`const`, rather than `var`, hence it should be possible to simply enable the ESLint `no-var` rule globally. This way we can ensure that new code won't accidentally use `var`, and it also removes the need to manually enable the rule in various folders. Obviously it makes sense to continue the efforts to replace `var`, but that should probably happen on a file and/or folder basis. Please note that this patch excludes the following code: - The `extensions/` folder, since that seemed easiest for now (and I don't know exactly what the support situation is for the Chromium-extension). - The entire `external/` folder is ignored, since most of it's currently excluded from linting. For the code that isn't imported from elsewhere (and should be ignored), we should probably (at some point) bring the code up to the same linting/formatting standard as the rest of the code-base. - Various files in the `test/` folder are ignored, as necessary, since the way that a lot of this code is loaded will require some care (or perhaps larger re-factoring) when removing `var` usage. 2021-03-13 15:51:44 +01:00			`"no-var": "off",`
Enable the `object-shorthand` ESLint rule Please see http://eslint.org/docs/rules/object-shorthand. Unfortunately, based on commit https://github.com/mozilla/pdf.js/commit/9276d1dcd97b4b0dc45342608a7f1b1a7f1e9c5b, it seems that we still need to maintain compatibility with old Node.js versions, hence certain files/directories that are executed in Node.js are currently exempt from this rule. Furthermore, since the files specific to the Chromium extension are not run through Babel, the `/extensions/chromium/` directory is also exempt from this rule. 2017-04-28 13:40:47 +02:00			`},`
Enable babel translation to enable ES module support. 2017-03-06 08:42:48 -06:00			`}`