Plans for seeding auth token when running on vercel?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 160
- Forks
- 42
- Avg merge
- 19h 36m
- Merged PRs (30d)
- 16
Description
On build or on runtime, do you guys have plans for seeding system tokens, like in gh actions for ease of usage and maintainability?
Since this package is new, I'm wondering If I'm doing wrong to manually set the auth token
(my usecase will be using vercel sdk on nextjs route handlers for custom domain integrations)
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
The issue does not name a file, test, or entry point. Start by tracing how the TypeScript SDK currently receives the auth token and consider the build/runtime distinction described for Next.js route handlers. Done would require an agreed mechanism and documented behavior for seeding system tokens; the issue currently provides no acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100