Revert "fix(backend): add size limits on uploaded file contents to prevent memory exhaustion"

[suresh1319]

Reverts #139

[Copilot]

Pull request overview

This PR reverts the previously-added upload size enforcement for batched file uploads, removing both client-side and server-side limits around uploaded file contents.

Changes:

• Removes client-side per-file content size checks during upload (EditorPage upload handler).
• Removes server-side validation for per-file and per-room stored content size before persisting uploads (FS_UPLOAD_BATCH handler).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
src/pages/EditorPage.js	Reverts client-side size-guard logic and adjusts upload reading flow for images/binary/text files.
server.js	Reverts server-side fileContents size validation prior to mutating room file state.

Comments suppressed due to low confidence (1)

server.js:319

• FS_UPLOAD_BATCH stores arbitrary fileContents into in-memory room state without any size limits. A client can repeatedly upload <=1MB chunks (or whatever Socket.IO allows) and grow roomState[roomId].fileContents without bound, reintroducing the memory-exhaustion/DoS risk that the reverted change was mitigating. Validate per-file and per-room cumulative size before mutating the file system / contents map, and reject the upload with an ack message when limits are exceeded.

    for (const node of nodes) {
      fs[node.id] = node;
      if (fs[node.parentId]) {
        if (!fs[node.parentId].children) fs[node.parentId].children = [];
        // Avoid adding duplicate child references

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.