Add linter to Chrome Extension (#4044). (#4174)

* feat: configure eslint rules by replicating those in the twenty-front package and introduce scripts for linting, formatting code and removing build output

* fix: ensure each file of the extension package satisfies linting rules and disable some rules where necessary

* fix: update relative imports to absolute imports throughout extension code with the defined tilde and at symbols

* fix: import the updated ui module from the front package to the chrome extension package to prevent eslint rules from breaking subject to the recent merged changes into main

* fix: commit the case change for files that were missed by Git in the earlier commits due to default configuration
This commit is contained in:
Abdullah
2024-02-25 21:32:08 +05:00
committed by GitHub
parent f543191552
commit d14bb2ea11
67 changed files with 783 additions and 567 deletions

View File

@ -1,6 +1,7 @@
import { defineConfig, Plugin } from 'vite';
import { crx } from '@crxjs/vite-plugin';
import react from '@vitejs/plugin-react';
import { defineConfig, Plugin } from 'vite';
import tsconfigPaths from 'vite-tsconfig-paths';
import manifest from './src/manifest';
@ -9,7 +10,7 @@ const viteManifestHack: Plugin & {
} = {
// Workaround from https://github.com/crxjs/chrome-extension-tools/issues/846#issuecomment-1861880919.
name: 'manifestHack',
renderCrxManifest(_manifest, bundle) {
renderCrxManifest: (_manifest, bundle: any) => {
bundle['manifest.json'] = bundle['.vite/manifest.json'];
bundle['manifest.json'].fileName = 'manifest.json';
delete bundle['.vite/manifest.json'];
@ -33,6 +34,6 @@ export default defineConfig(() => {
hmr: { port: 3002 },
},
plugins: [viteManifestHack, crx({ manifest }), react()],
plugins: [viteManifestHack, crx({ manifest }), react(), tsconfigPaths()],
};
});