Restore server-only guard in getEventTypeById.ts

Open
#30,488 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@Priyansh-dixit810 is already working on this.

Since Nov 3, 2026.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
nextjs, typescript
Domain
backend

Research direction

The title names getEventTypeById.ts as the file that lost its server-only guard, but the body is still the unfilled bug template, so the expected behaviour is not spelled out. Start by finding that file and checking the git history for where the guard was removed. Done means the guard is restored and a client-side import of the module fails at build time, which the maintainers should confirm before you start.

Written by the indexing model from the issue text.

Description

🐛 bug

Found a bug? Please fill out the sections below. 👍

Issue Summary

A summary of the issue. This needs to be a clear detailed-rich summary.

Steps to Reproduce
  1. (for example) Went to ...
  2. Clicked on...
  3. ...

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?

Actual Results
  • What's happening right now that is different from what is expected
Expected Results
  • This is an ideal result that the system should get after the tests are performed
Technical details
  • Browser version, screen recording, console logs, network requests: You can make a recording with Bird Eats Bug.
  • Node.js version
  • Anything else that you think could be an issue.
Evidence
  • How was this tested? This is quite mandatory in terms of bugs. Providing evidence of your testing with screenshots or/and videos is an amazing way to prove the bug and a troubleshooting chance to find the solution.
Dominant language
TypeScript
Stars
50k
Forks
15.6k
Avg merge
5d 1h
Merged PRs (30d)
15

Getting set up

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 calcom/cal.diy

All issues in calcom/cal.diy

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.