Deploy to AWS Amplify
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.7k
- Forks
- 746
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 3
Description
Environment
- @nuxt/content: 3.13.0
- Operating System: AmazonLinux2
- Node Version: 22
- Nuxt Version: 4.4.2
- Nitro Version: 2.13.2
- Package Manager: npm 11.5.2
Version
v3.13.0
Reproduction
should be reproducible on any Linux OS with GLIBC 2.26
Description
AWS Amplify (and probably AWS EC2) runs on OS AmazonLinux2, which has GLIBC 2.26
Nuxt content requires better-sqlite3 and better-sqlite3 requires a higher version then GLIBC 2.26, therefore better-sqlite3 does not work on AWS.
With nuxt/content v3.5.1 you can install sqlite3 and nuxt/content will then use sqlite3 instead of better-sqlite3, works on AWS.
With nuxt/content v3.13.0 better-sqlite3 is a hard requirement and therefore will not work on AWS.
I tried adding this in nuxt.config.ts:
content: {
experimental: {
sqliteConnector: 'sqlite3',
}
}
but then better-sqlite3 is still a hard requirement
Additional context
No response
Logs
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 with the nuxt.config.ts sqliteConnector setting and the dependency behavior described for @nuxt/content v3.13.0. Reproduce installation and runtime on AmazonLinux2 with GLIBC 2.26, then verify that the supported sqlite3 configuration no longer requires an incompatible better-sqlite3 dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, nuxtjs, sqlite, typescript
- Domain
- backend, cloud, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100