nextauthjs / nextauthjs/next-auth

The sveltekit-auth-example fails to deploy

Open
#7,552 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

triage
Dominant language
TypeScript
Stars
28.4k
Forks
4k
PR merge metrics
No merged PRs in 30d

Description

Environment

I used the Deploy button on the Vercel SvelteKit Authentication page. My development environment was not involved as the failure occurred during the vercel automation. That being said, this is the requested output:

System:
OS: macOS 13.3.1
CPU: (8) x64 Intel(R) Core(TM) i7-7920HQ CPU @ 3.10GHz
Memory: 315.02 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.15.0 - /usr/local/bin/node
Yarn: 1.22.18 - ~/.yarn/bin/yarn
npm: 9.6.4 - /usr/local/bin/npm
Browsers:
Chrome: 113.0.5672.92
Firefox: 109.0.1
Safari: 16.4

Reproduction URL

https://github.com/nextauthjs/sveltekit-auth-example

Describe the issue

The deployment fails. The first hard error is:

Error: @sveltejs/adapter-vercel >=2.x (possibly installed through @sveltejs/adapter-auto) requires @sveltejs/kit version 1.5 or higher. Either downgrade the adapter or upgrade @sveltejs/kit

The full log is attached.

vercel-skeltekit-auth-deploy-failure-log.txt

How to reproduce

Simply go to the Vercel page, click the Deploy button, provide the necessary env variables, and then click the submit button.

Expected behavior

The deployment should be successful.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the sveltekit-auth-example repository linked in the issue and inspect its dependency versions alongside the attached Vercel deployment log. Reproduce the Deploy-button failure with the required environment variables, then verify that the example deploys successfully after the dependency mismatch is addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
cloud, devops
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.