Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

No server-side file size limit on uploads (v0)

Open
#313 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
aws, typescript
Domain
api, backend, cloud

Research direction

Start with src/routes/(app)/storage/api/upload/+server.ts and trace how the request stream is passed to @aws-sdk/lib-storage Upload. The issue defers the limit until typical object sizes are known, so first establish that configuration and completion criteria before changing behavior. Done means a configurable MAX_UPLOAD_BYTES guard exists without buffering uploads in memory.

Written by the indexing model from the issue text.

Description

File: src/routes/(app)/storage/api/upload/+server.ts

The upload endpoint imposes no maximum file size. S3's 5 TB single-object limit applies as a natural backstop. For v0 this is acceptable; large uploads will consume server-side streaming resources proportionally but do not buffer the body in memory (the stream is piped directly to the @aws-sdk/lib-storage Upload). Add a configurable MAX_UPLOAD_BYTES guard in a future iteration once typical object sizes are known.

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
22h 6m
Merged PRs (30d)
12

Contributor guide

No contributing guide indexed for this repository

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.

More from stackabletech/cockpit

All issues in stackabletech/cockpit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.