fix: surrealdb compatibility regression — module.json indicates ^3.21.0 || ^4.3.0
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 354
- Avg merge
- 10h 18m
- Merged PRs (30d)
- 12
Description
The sync step detects a compatibility regression for surrealdb:
Module was marked as Nuxt 4 compatible (>=3.10.0) but module.json indicates only ^3.21.0 || ^4.3.0
This causes CI to fail with exit code 1 for all PRs.
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.
Research direction
Start by inspecting the affected module's module.json and the sync step that reports the compatibility mismatch. Update the compatibility declaration so it matches the Nuxt compatibility detected by the check, then rerun the relevant CI or sync validation and confirm PRs no longer fail with exit code 1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt, typescript
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100