Skip to content

Fix linting errors blocking Vercel deployment#10

Open
Copilot wants to merge 2 commits intomainfrom
copilot/fix-vercel-deployment-issues
Open

Fix linting errors blocking Vercel deployment#10
Copilot wants to merge 2 commits intomainfrom
copilot/fix-vercel-deployment-issues

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Feb 8, 2026

Vercel build was failing during the lint step with 1900+ Prettier violations and multiple ESLint errors across the codebase.

Changes

  • Formatting: Auto-formatted all TS/TSX files with Prettier

    • Standardized quotes (single → double)
    • Fixed indentation and semicolons
  • ESLint violations:

    • Removed unused imports (Mail, Phone, Copy)
    • Removed unused variables (getTypeColor, awards, mounted)
    • Escaped HTML entities in JSX ('', "")
    • Fixed React Hook dependency array (added frames.length to useEffect)

Example

// Before
const [mounted, setMounted] = useState(false);
<p>Let's collaborate!</p>

// After  
const [, setMounted] = useState(false);
<p>Let&apos;s collaborate!</p>

Lint now passes cleanly (npm run lint ✓), unblocking Vercel deployment.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • fonts.googleapis.com
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/Rohan-Portfolio/Rohan-Portfolio/node_modules/.bin/next build (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Original prompt

having issues while deploying on vercel pnmp fix: remove pnpm requirement and add npm lockfile for Vercel deployment - b9ba2f


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.


Summary by cubic

Fix Vercel deployment by switching to npm and cleaning up formatting/lint errors. Vercel now builds with default settings.

  • Bug Fixes

    • Added package-lock.json so Vercel uses npm.
    • Replaced pnpm scripts with npm equivalents in package.json.
    • Removed pnpm-specific engine/config to prevent build failures.
    • Formatted code with Prettier and fixed ESLint issues (unused imports/vars, hooks deps, unescaped entities).
  • Migration

    • Remove node_modules and run npm ci (or npm install).
    • Use npm locally to avoid lockfile conflicts.

Written for commit 8bc4653. Summary will update on new commits.

@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Feb 8, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
rohan-portfolio Ready Ready Preview, Comment Feb 8, 2026 11:49am
rohan-portfolio- Ready Ready Preview, Comment Feb 8, 2026 11:49am

@RohanExploit RohanExploit marked this pull request as ready for review February 8, 2026 11:44
Copilot AI review requested due to automatic review settings February 8, 2026 11:44
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.


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

…eployment

Co-authored-by: RohanExploit <178623867+RohanExploit@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix deployment issues on Vercel by removing pnpm requirement Fix linting errors blocking Vercel deployment Feb 8, 2026
Copilot AI requested a review from RohanExploit February 8, 2026 11:49
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 issues found across 29 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="app/page.tsx">

<violation number="1" location="app/page.tsx:73">
P2: Add rel="noopener noreferrer" to external links that use target="_blank" to prevent reverse tabnabbing.</violation>
</file>

<file name="app/components/particles.tsx">

<violation number="1" location="app/components/particles.tsx:20">
P3: Remove the console log from the particlesLoaded callback to avoid noisy production logging.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

<a href={`mailto:${ROHAN_DATA.contact.email}`} className="text-text-tertiary hover:text-error transition-all hover:scale-110"><Mail className="h-6 w-6" /></a>
<a
href="https://github.com/RohanExploit"
target="_blank"
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot Feb 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: Add rel="noopener noreferrer" to external links that use target="_blank" to prevent reverse tabnabbing.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At app/page.tsx, line 73:

<comment>Add rel="noopener noreferrer" to external links that use target="_blank" to prevent reverse tabnabbing.</comment>

<file context>
@@ -64,10 +68,33 @@ export default function Home() {
-                <a href={`mailto:${ROHAN_DATA.contact.email}`} className="text-text-tertiary hover:text-error transition-all hover:scale-110"><Mail className="h-6 w-6" /></a>
+                <a
+                  href="https://github.com/RohanExploit"
+                  target="_blank"
+                  className="text-text-tertiary hover:text-accent transition-all hover:scale-110"
+                >
</file context>
Suggested change
target="_blank"
target="_blank"
rel="noopener noreferrer"
Fix with Cubic

console.log(container);
};
const particlesLoaded = async (container?: Container): Promise<void> => {
console.log(container);
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot Feb 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3: Remove the console log from the particlesLoaded callback to avoid noisy production logging.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At app/components/particles.tsx, line 20:

<comment>Remove the console log from the particlesLoaded callback to avoid noisy production logging.</comment>

<file context>
@@ -1,106 +1,106 @@
-        console.log(container);
-    };
+  const particlesLoaded = async (container?: Container): Promise<void> => {
+    console.log(container);
+  };
 
</file context>
Fix with Cubic

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.

3 participants