Commit activity
Last 12 weeks · 17 commits
Community health
2 of 6 standards met
50
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Active · Last activity 2h ago
See all on GitHub →
See https://github.com/sindresorhus/eslint-plugin-unicorn/releases and each commit's description. Let me know if any rule should globally or locally disabled rather than fixed. I recommend going through the commits individually when reviewing.
A small correction to the example in the rule description. After reading the current version, I was a little confused for a few seconds :)
Please describe what the rule should do: Detect and prevent the use of smart quotes (curly) quotes inside the `` annoying, since that where most of my translation are defined. What category should the rule belong to? [x] Enforces code style (layout) [ ] Warns about a potential error (problem) [ ] Suggests an alternate way of doing something (suggestion) [ ] Other (please specify:) Provide 2-3 code examples that this rule should warn about: Additional context
Recent fixes
Bumps the dev ESLint to v10. Peer deps already allow v10 and Node 18 support is unchanged, so nothing changes for consumers. 9→10, 10→11, 4→5, 0.6→0.8 (the last for v10 peer support) was removed in v10; the scripts now use the regular class v10 auto-loads nested files, so linting descended into and tried to load the fixtures' built plugin — now ignored CI: drop Node 18 from the main test matrix (v10/espree 11 need Node 20+), rename the v10 job to v9, and pin for the typescript-eslint v7 job since parser v7 doesn't support v10
See https://prettier.io/blog/2026/06/27/3.9.0#change-18827-2. Unblocks #3090.
Problem I saw: could report a valid default when a prop type mixed an imported type with a native literal type. For example, if a union includes an imported type that resolves to boolean in user code, the rule may not be able to see that without type services. It then keeps only the known native part and can require the wrong default type. What I changed: I changed the rule to skip reporting when the inferred type list still contains the unresolved type placeholder. That keeps this path aligned with the rule's existing behavior for native types it cannot know for sure, instead of guessing from the remaining resolved pieces. How I checked it: The new issue-repro valid case failed before the guard. After the fix, the focused rule suite passed with 73 tests. The full lib suite passed with 11,495 tests after build, and changed-file ESLint, the changed-file TypeScript check, , and branch hygiene were clean. Closes #2279
Structured data for AI agents
Repository: vuejs/eslint-plugin-vue. Description: Official ESLint plugin for Vue.js Stars: 4594, Forks: 711. Primary language: TypeScript. Languages: TypeScript (78.4%), JavaScript (21.6%), Vue (0%). License: MIT. Homepage: https://eslint.vuejs.org/ Topics: eslint, eslint-plugin, html, javascript, npm, npm-module, npm-package, static-analysis, vue. Latest release: v10.9.2 (4w ago). Open PRs: 18, open issues: 184. Last activity: 2h ago. Community health: 50%. Top contributors: ota-meshi, michalsnik, FloEdelmann, ST-DDT, mysticatea, armano2, waynzh, 9romise, github-actions[bot], chrisvfritz and others.