Skip to content

fix: resolve backend crash and package.json syntax errors#180

Open
rizwan749 wants to merge 3 commits into
anubhavxdev:mainfrom
rizwan749:fix/backend-crash
Open

fix: resolve backend crash and package.json syntax errors#180
rizwan749 wants to merge 3 commits into
anubhavxdev:mainfrom
rizwan749:fix/backend-crash

Conversation

@rizwan749
Copy link
Copy Markdown

There was an issue in the package.json file where the brackets were not closed properly and the test script was not in its right place. So whenever a developer used the command npm install, it crashed the app and threw an "EJSONPARSE" error.
I fixed the bracket problem and placed the test script in its right place.
(Fix configuration/syntax error in package.json)

After fixing the package.json file, when I used the npm run dev command, there was another crash due to the imports. Some imports were missing in server.js and authRoutes.js, even though the variables were already created.
I added the missing import statements and fixed the routes that were broken or not working properly.
(Resolve server crash by adding missing imports in server.js and authRoutes.js)

Closes #171

@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

github-actions Bot commented May 17, 2026

❌ 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

Issue #171 is not assigned to you (@rizwan749) — You must be assigned to the issue before submitting a PR.

Comment /assign on Issue #171 or ask a maintainer to assign it to you.

⚠️ 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

@github-actions github-actions Bot added gssoc:review GSSoC: Under review stage-1-approved Pipeline: Stage 1 automated checks passed labels May 17, 2026
@rizwan749
Copy link
Copy Markdown
Author

Hi @anubhavxdev, I noticed another PR was submitted shortly before mine, but I want to highlight that this PR completely resolves both the package.json parsing error AND the core server crash issues (server.js and authRoutes.js) together. Everything is verified locally. Looking forward to your review!

@anubhavxdev anubhavxdev added gssoc:approved GSSoC: Admin approved - counts for points mentor-review-requested Pipeline: Mentor review requested stage-3-ready Pipeline: Ready for admin final review labels May 17, 2026
@anubhavxdev
Copy link
Copy Markdown
Owner

👥 Stage 2 — Mentor Review

Two mentors assigned:

EventOne × GSSoC Pipeline

@anubhavxdev
Copy link
Copy Markdown
Owner

Hey @rizwan749! Merge conflicts hain. Please resolve: git fetch origin && git merge origin/main, fix conflicts, then git push.

@anubhavxdev
Copy link
Copy Markdown
Owner

Hey! Since some recent PRs were merged, this branch now has merge conflicts with upstream main. Please resolve them to get it merged!\n\nHere are the commands you can run to resolve the conflict:\nbash\ngit fetch origin\ngit merge origin/main\n# Resolve the conflicts in your files\ngit add .\ngit commit -m "merge: resolve conflicts with main"\ngit push\n

@anubhavxdev
Copy link
Copy Markdown
Owner

Hey @rizwan749! Merge conflicts hain. Please resolve: git fetch origin && git merge origin/main, fix conflicts, then git push.

1 similar comment
@anubhavxdev
Copy link
Copy Markdown
Owner

Hey @rizwan749! Merge conflicts hain. Please resolve: git fetch origin && git merge origin/main, fix conflicts, then git push.

@anubhavxdev
Copy link
Copy Markdown
Owner

Hi! This PR currently has merge conflicts with the base branch. Could you please fetch the latest changes and resolve the conflicts? Let us know once it's done so we can review and merge it. Thanks!

@anubhavxdev
Copy link
Copy Markdown
Owner

@copilot resolve the merge conflicts in this pull request

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

Labels

gssoc:approved GSSoC: Admin approved - counts for points gssoc:review GSSoC: Under review mentor-review-requested Pipeline: Mentor review requested stage-1-approved Pipeline: Stage 1 automated checks passed stage-3-ready Pipeline: Ready for admin final review

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