Add deno support
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- deno, eslint, nuxt, typescript
- Domain
- tooling
Research direction
Start with the package.json reproduction and the listed @nuxt/eslint, ESLint, TypeScript, Nuxt, and Deno versions. Reproduce installation and project startup under Deno, then inspect the package's existing runtime assumptions. Done means @nuxt/eslint can be installed and run in the reported Deno environment.
Written by the indexing model from the issue text.
Description
Environment
------------------------------
- Operating System: Windows_NT
- Node Version: v22.19.0
- Nuxt Version: 4.1.1
- CLI Version: 3.28.0
- Nitro Version: 2.12.5
- Package Manager: deno@deno 2.4.5 (stable, release, x86_64-pc-windows-msvc)
v8 13.7.152.14-rusty
typescript 5.8.3
- Builder: -
- User Config: devtools, modules, css, compatibilityDate
- Runtime Modules: @nuxt/ui@3.3.3, @nuxt/eslint@1.9.0, @nuxt/content@3.6.3, @nuxt/fonts@0.11.4, @nuxt/icon@2.0.0, @nuxt/image@1.11.0, @nuxt/scripts@0.11.13, @nuxt/test-utils@3.19.2
- Build Modules: -
------------------------------
Package
@nuxt/eslint
Reproduction
package.json
"devDependencies": {
"@nuxt/eslint": "^1.9.0",
"eslint": "^9.35.0",
"typescript": "^5.9.2"
}
Returns
Describe the bug
Not sure how to fix it so I had te remove it to be able to install and run the project😭
Additional context
No response
Logs
- Dominant language
- TypeScript
- Stars
- 639
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nuxt/eslint
-
pending triage
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
pending triage
-
@nuxt/eslint pulls h3@2.0.1-rc.22 through devframe causing npm hoisting conflict with Nuxt Nitro h3 Openpending triage
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
pending triage
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
pending triage
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·