Revert "chore: update default port from 8080 to 3000 and use nullish coalesci…"

[oliursahin]

User description

Reverts #1004

---

Important

Reverts default port in environment.loader.js from 3000 to 8080, using logical OR instead of nullish coalescing.

• Behavior:
  • Reverts default port change in environment.loader.js from 3000 back to 8080.
  • Replaces nullish coalescing (??) with logical OR (||) for PORT assignment.

^{This description was created by for 1740217. You can customize this summary. It will automatically update as commits are pushed.}

---

CodeAnt-AI Description

• The default port in environment.loader.js is reverted from 3000 to 8080.
• The assignment for PORT now uses the logical OR operator (||) instead of the nullish coalescing operator (??).

This PR restores the previous behavior for the backend's port configuration, ensuring that if process.env.PORT is not set or is a falsy value, the application will default to port 8080. This change also improves compatibility with environments where the logical OR operator is preferred or required.

---

Changes walkthrough

	Relevant files
Bug fix	environment.loader.js Revert default port to 8080 and use logical OR for PORT assignment apps/backend/src/loaders/environment.loader.js Reverts the default port assignment from 3000 back to 8080. Changes the assignment operator from nullish coalescing (??) to logical OR (||) for the PORT environment variable. +1/-1

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[github-actions]

Hey there! 👋

We require pull request titles to follow the Conventional Commits specification.

Valid types:

• feat: A new feature
• fix: A bug fix
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code
• refactor: A code change that neither fixes a bug nor adds a feature
• perf: A code change that improves performance
• test: Adding missing or correcting existing tests
• build: Changes that affect the build system or external dependencies
• ci: Changes to CI configuration files and scripts
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit

Format: type: description

Error details:

No release type found in pull request title "Revert "chore: update default port from 8080 to 3000 and use nullish coalesci…"". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat
 - fix
 - docs
 - ui
 - refac
 - perf
 - test
 - build
 - ci
 - chore
 - revert

[codeant-ai]

CodeAnt AI is reviewing your PR.

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 1740217 in 1 minute and 22 seconds. Click for details.

• Reviewed 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 3 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. apps/backend/src/loaders/environment.loader.js:7

• Draft comment:
  Consider whether || is the intended fallback operator here. Using || will trigger the default even if process.env.PORT is an empty string. If an empty string should be used instead, use the nullish coalescing operator (??) instead.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% For a PORT environment variable, an empty string is not a valid value - we need a number. The || operator will treat empty string as falsy and fall back to 8080, which is actually the desired behavior here. The ?? operator would only fall back on null/undefined, potentially letting an empty string through. Maybe there's a case where an empty string PORT is valid that I'm not considering? Or maybe the original author had a specific reason for using ??. No, a PORT must be a valid number for the server to listen on. An empty string would cause runtime errors. The || operator is the correct choice here to handle empty strings. The comment should be deleted because it's suggesting a change that would make the code less robust by allowing empty strings for PORT.

2. apps/backend/src/loaders/environment.loader.js:7

• Draft comment:
  Reverting default port to 8080 is intentional. Note: using '||' falls back on 8080 if PORT is any falsy value (e.g., empty string). If you only want to default on null/undefined, consider using '??'.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

3. apps/backend/src/loaders/environment.loader.js:24

• Draft comment:
  Typographical error: The property 'LINER_WEBHOOK_SECRET' appears to be a typo. Considering the consistent naming convention used for similar variables (e.g., 'LINEAR_CLIENT_ID', 'LINEAR_CLIENT_SECRET'), it might have been intended as 'LINEAR_WEBHOOK_SECRET'. Please verify and correct if necessary.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_qw3oAgno35Jmcf9d

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[codeant-ai]

Pull Request Feedback 🔍

🔒 No security issues identified

⚡ Recommended areas for review Default Port Reversion The new code reverts the default port to 8080 and switches from the nullish coalescing operator to logical OR. Please verify that this change in fallback behavior is intentional, as the logical OR operator will consider any falsy value (e.g., an empty string) as a trigger to use the default, which may not have been the case with the nullish coalescing operator.

[codeant-ai]

Suggestion: Validate and convert PORT by implementing an inline function that checks if the numeric value is valid, ensuring a fallback to 8080 per the reverted business logic. [Security Configuration]

Suggested change

	PORT: process.env.PORT || 8080,
	PORT: (() => {
	const port = parseInt(process.env.PORT, 10);
	return (Number.isNaN(port) || port <= 0 || port > 65535) ? 8080 : port;
	})(),

[codeant-ai]

CodeAnt AI finished reviewing your PR.