Gathering detailed insights and metrics for @nabla/vite-plugin-eslint
Gathering detailed insights and metrics for @nabla/vite-plugin-eslint
Gathering detailed insights and metrics for @nabla/vite-plugin-eslint
Gathering detailed insights and metrics for @nabla/vite-plugin-eslint
npm install @nabla/vite-plugin-eslint
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
129 Stars
38 Commits
4 Forks
3 Watching
1 Branches
4 Contributors
Updated on 27 Nov 2024
Minified
Minified + Gzipped
JavaScript (91.69%)
HTML (8.31%)
Cumulative downloads
Total Downloads
Last day
2.5%
5,545
Compared to previous day
Last week
6%
31,081
Compared to previous week
Last month
3%
133,641
Compared to previous month
Last year
64.6%
1,299,390
Compared to previous year
Plugs ESLint into Vite dev server.
Because of this, the plugin can't fail the build and is only applied in dev. Like typechecking, linting should be done before or in parallel of the build command.
yarn add --dev @nabla/vite-plugin-eslint
1import { defineConfig } from "vite"; 2import eslintPlugin from "@nabla/vite-plugin-eslint"; 3 4export default defineConfig({ 5 plugins: [eslintPlugin()], 6});
{ cache: true }
Note: the fix
option is only supported from 1.3.4
(path: string) => boolean
(path) => path.match(/\/src\/[^?]*\.(vue|svelte|m?[jt]sx?)$/)
You can use DEBUG=eslint node_modules/.bin/vite
to debug this option (available in 1.4.0
)
string | ((result: ESLint.LintResult) => void)
If provided, the value is passed to eslint.loadFormatter
. Use stylish
to get a CRA like output. Async formatters are supported in 1.5.0
. Function support was added in 2.0.2
.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
4 existing vulnerabilities detected
Details
Reason
Found 0/24 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More