Skip to content

Fix backend crash, missing imports, and update dependencies#172

Closed
rizwan749 wants to merge 1 commit into
anubhavxdev:mainfrom
rizwan749:main
Closed

Fix backend crash, missing imports, and update dependencies#172
rizwan749 wants to merge 1 commit into
anubhavxdev:mainfrom
rizwan749:main

Conversation

@rizwan749
Copy link
Copy Markdown

Description
This PR resolves the critical installation and startup bugs in the backend folder. The following specific fixes have been implemented:

  1. package.json & package-lock.json: Fixed a structural JSON syntax error (EJSONPARSE) caused by misplaced brackets and the test script being placed outside the main scripts block. This now allows npm install to run cleanly without errors.
  2. src/server.js: Resolved immediate runtime crashes during npm run dev by fixing missing core imports and correcting undefined variable references that were breaking the server initialization.
  3. src/routes/authRoutes.js: Fixed broken routing definitions and missing dependency imports to ensure smooth authentication endpoint handling.

Closes #171

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • I have linked the specific issue ([BUG] EJSONPARSE error in package.json and backend server crashes #171) that this PR resolves.
  • I have described my changes in detail according to the modified files.
  • I have tested my changes locally, and the server syntax/imports are fully verified.
  • My changes do not introduce any new breaking changes.
  • I have performed a self-review of my own code.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 17, 2026

@rizwan749 is attempting to deploy a commit to the anubhav12302387's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions
Copy link
Copy Markdown

👋 Thanks for opening a PR, @rizwan749!

Your PR has entered the 🎯 EventOne GSSoC PR Review Pipeline.

🟢 GSSoC PR detected — your PR will be routed to an approved GSSoC mentor for Stage 2 review.

What happens next

Stage Reviewer Checks
Stage 1 — Automated Validation 🤖 Bot Title format · Issue link · AI Slop · Branch check
Stage 2 — Mentor Review 🧑‍🏫 GSSoC Mentor Code + Quality Review
Stage 3 — Admin Final Gate 🔑 @anubhavxdev Label check + Final Merge Decision

A pipeline status comment will appear below and update automatically as your PR progresses.


While you wait

  • Sign all commits using git commit -s
  • Link your issue with Closes #123
  • Use a feature branch — not main
  • Avoid unrelated changes in the same PR
  • Write your own description — no AI-generated content

This comment is posted only once.

EventOne × GSSoC Automated Pipeline

@github-actions
Copy link
Copy Markdown

❌ PR Format Check — Failed — Please Fix Below

Hi @rizwan749! Please fix the issues below before your PR can proceed to mentor review.

❌ Must Fix Before Proceeding

Title format invalid — Use Conventional Commits format

Examples: feat: add login page, fix: button alignment, docs: update readme

PRs from main branch not allowed — Create a feature branch

Run: git checkout -b feat/your-feature-name

⚠️ Warnings (recommended)

⚠️ No testing steps mentioned — Add how reviewers can verify your changes


📋 EventOne PR Guidelines (click to expand)

Title format — Conventional Commits:
feat: · fix: · docs: · style: · refactor: · test: · chore: · perf:

Always link an issue: Closes #number

Use a feature branch — never PR directly from main

Write your own description — AI-generated content = gssoc:ai-slop label

EventOne × GSSoC Pipeline — Stage 1 Automated Check

@anubhavxdev
Copy link
Copy Markdown
Owner

Hey @rizwan749! Closing this as it does not follow Conventional Commits format. Your newer PR #180 looks better — please make sure it has proper description and links an issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] EJSONPARSE error in package.json and backend server crashes

2 participants