Research
Security News
Threat Actor Exposes Playbook for Exploiting npm to Build Blockchain-Powered Botnets
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
@jellydn/eslint-fixer
Advanced tools
We will continue to use @typescript-eslint/parser
and @typescript-eslint/eslint-plugin
to lint TypeScript files until this issue ☂️ Type-aware linter · Issue #3187 · biomejs/biome is resolved.
The following rules are enabled to effectively lint TypeScript files:
{
"@typescript-eslint/await-thenable": "error",
"@typescript-eslint/no-floating-promises": "error",
"@typescript-eslint/no-for-in-array": "error",
"@typescript-eslint/no-misused-promises": "error",
"@typescript-eslint/no-redundant-type-constituents": "error",
"@typescript-eslint/no-unnecessary-type-assertion": "error",
"@typescript-eslint/require-await": "error"
}
# Install eslint-fixer
npm install -g @jellydn/eslint-fixer
# Or Run eslint-fixer
npx @jellydn/eslint-fixer "examples/**/*.ts,examples/**/*.tsx"
To use eslint-fixer with lazy.nvim and nvim-lint, you should define as a custom linter:
return {
{
"mfussenegger/nvim-lint",
event = "VeryLazy",
opts = {
linters_by_ft = {
-- Other linters
typescript = { "oxlint", "eslint_fixer" },
},
},
init = function()
-- Register customer linter
require("lint").linters.eslint_fixer = {
name = "eslint_fixer",
cmd = "eslint-fixer", -- e.g: npm install -g @jellydn/eslint-fixer
stdin = false,
stream = "stdout",
ignore_exitcode = true,
parser = function(output, bufnr)
local trimmed_output = vim.trim(output)
if trimmed_output == "" then
return {}
end
-- Skip if Parsing error on output
if string.match(trimmed_output, "Parsing error") then
return {}
end
-- Parse output base on Eslint errorformat
local diagnostic = require("lint.parser").from_errorformat("%f %l:%c %m", {
error = vim.diagnostic.severity.ERROR,
})(trimmed_output, bufnr)
return diagnostic
end,
}
end,
config = function(_, opts)
-- Your setup here
end,
},
}
To use eslint-fixer in GitHub Actions, follow these steps:
name: ESLint Fixer
on:
push:
branches:
- main
jobs:
eslint-fixer:
name: ESLint Fixer
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npx --yes @jellydn/eslint-fixer@0.0.0 "examples/**/*.ts" # change to the latest release
oxlint:
name: Lint JS
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npx --yes oxlint@0.0.0 --deny-warnings # change to the latest release
quality:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Setup Biome
uses: biomejs/setup-biome@v2
with:
version: latest
- name: Run Biome
run: biome ci .
make release
👤 Dung Huynh
Give a ⭐️ if this project helped you!
FAQs
Welcome to @jellydn/eslint-fixer 👋
The npm package @jellydn/eslint-fixer receives a total of 2 weekly downloads. As such, @jellydn/eslint-fixer popularity was classified as not popular.
We found that @jellydn/eslint-fixer demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.