Used eslint-config-jitsi and modified code (#25)

1 files changed, 6 insertions, 33 deletions

diff --git a/.eslintrc.js b/.eslintrc.js
index bbec37f..72f02be 100644
--- a/.eslintrc.js
+++ b/.eslintrc.js
@@ -1,37 +1,10 @@
 module.exports = {
-    'env': {
-        'browser': true,
-        'commonjs': true,
-        'es6': true
-    },
-    'extends': 'eslint:recommended',
-    'globals': {
-        // The globals that (1) are accessed but not defined within many of our
-        // files, (2) are certainly defined, and (3) we would like to use
-        // without explicitly specifying them (using a comment) inside of our
-        // files.
-        '__filename': false
-    },
-    'parserOptions': {
-        'ecmaFeatures': {
-            'experimentalObjectRestSpread': true
-        },
-        'sourceType': 'module'
-    },
+    'extends': [
+        'eslint-config-jitsi'
+    ],
     'rules': {
-        'new-cap': [
-            'error',
-            {
-                'capIsNew': false // Behave like JSHint's newcap.
-            }
-        ],
-        // While it is considered a best practice to avoid using methods on
-        // console in JavaScript that is designed to be executed in the browser
-        // and ESLint includes the rule among its set of recommended rules, (1)
-        // the general practice is to strip such calls before pushing to
-        // production and (2) we prefer to utilize console in lib-jitsi-meet
-        // (and jitsi-meet).
-        'no-console': 'off',
-        'semi': 'error'
+        'no-new': 1,
+        'no-shadow': 1,
+        'max-params': 1
     }
 };