chore(deps): update dependency eslint-plugin-svelte to v3 #101
No reviewers
Labels
No labels
area: arcade
area: art-studio
area: calendar
area: chapel
area: content
area: design
area: field-guide
area: infra
area: library
area: os
area: portal
area: sync
area: typing
blocked
breaking
bug
content: approved
content: changes-requested
content: drafting
content: needs-doctrinal-review
content: needs-review
dependencies
documentation
duplicate
enhancement
epic
github_actions
good first issue
help wanted
invalid
javascript
needs-triage
priority: high
priority: low
priority: medium
question
type: enhancement
type: feature
type: fix
type: perf
type: security
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Bosco/bosco!101
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/eslint-plugin-svelte-3.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
^2.46.1->^3.0.0Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below:
File name: pnpm-lock.yaml
Held from the v0.3.0 dependency sweep: eslint-plugin-svelte v3 introduces the new
svelte/no-navigation-without-resolverule (17 errors — hrefs needresolve()) plus a parser error; needs a code migration, not a mechanical bump. Kept open pending a focused migration; the other 5 compatible majors landed in v0.3.0.Landed on
developin5e23963(signed, verified). eslint-plugin-svelte v3 needed a real migration, not a mechanical bump:*.svelte.ts/*.svelte.jstoo, so the four runes-modules were given the typescript-eslint sub-parser (the documented v3 setup); this cleared the 4Parsing errors.svelte/no-navigation-without-resolve: off — it wantsresolve('/route/[p]', {p}), which emits slash-less route paths and would break Bosco'strailingSlash: 'always'invariant +guard:offline(both require trailing-slash content hrefs); base is permanently''(apex-hosted). Off by architectural choice, with rationale in the config. Aresolve()migration is filed as separate follow-up.eslint-disable-next-linefor two intentional, in-file-documented patterns unmasked by the parser fix:svelte/no-dom-manipulating(Avatar SVG-namespace innerHTML) andsvelte/prefer-svelte-reactivity(manager#openers, a deliberately non-reactive DOM registry).Full 10-step CI gate green locally. Closing.
Pull request closed