Not showing any errors while Building on local. but vercel doesn't build next.js app without showing any errors.

mthakur5 commented 11 months ago

Link to the code that reproduces this issue

https://github.com/mthakur5/www.haroth.com

To Reproduce

npm run build

when running same web app in localhost. building time was 18-20 min. but when i trying to build on vercel it is not showing any errors, even it is conconfusing because building time was more than 45 min. but build stop in 6 min. without any errors.

https://imgur.com/o3Ofzmx

Please find attached picture above.

Current vs. Expected behavior

This project should build in 20-25 min.

Verify canary release

[X] I verified that the issue exists in the latest Next.js canary release

Provide environment information

{
  "name": "client",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint",
    "sitemap": "node generateSitemap.js"
  },
  "dependencies": {
    "@reduxjs/toolkit": "^1.9.5",
    "@vercel/analytics": "^1.0.2",
    "axios": "^1.4.0",
    "dotenv": "^16.3.1",
    "framer-motion": "^10.12.18",
    "js-cookie": "^3.0.5",
    "next": "13.4.7",
    "next-auth": "^4.22.1",
    "next-sitemap": "^4.2.3",
    "nextjs-progressbar": "^0.0.16",
    "node-cron": "^3.0.2",
    "nodemailer": "^6.9.4",
    "onesignal": "^0.1.2",
    "otp-gen-agent": "^1.1.2",
    "qs": "^6.11.2",
    "razorpay": "^2.9.0",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-hook-form": "^7.45.1",
    "react-hot-toast": "^2.4.1",
    "react-icons": "^4.10.1",
    "react-multi-carousel": "^2.8.4",
    "react-otp-input": "^3.0.2",
    "react-redux": "^8.1.1",
    "react-responsive-carousel": "^3.2.23",
    "react-spinners": "^0.13.8",
    "sharp": "^0.32.4",
    "shortid": "^2.2.16",
    "sitemap": "^7.1.1"
  },
  "devDependencies": {
    "autoprefixer": "^10.4.14",
    "eslint": "8.44.0",
    "eslint-config-next": "13.4.7",
    "postcss": "^8.4.24",
    "tailwindcss": "^3.3.2"
  }
}

Which area(s) are affected? (Select all that apply)

Not sure

Additional context

I have tested in localhost and it working fine. took 18-20 min. for build while app.

i don't understand what is wrong with this. please help me asap.

timneutkens commented 11 months ago

Can't access the provided repository but there are 2000 log lines that you can open in the provided screenshot.

mthakur5 commented 11 months ago

Can't access the provided repository but there are 2000 log lines that you can open in the provided screenshot.

i have also build in local and it is fine. even i have tried to build in my ec2 instance. there is also fine builded.

sir you can visit repository. please refresh your browser.

Thank you for considering this.

mthakur5 commented 11 months ago

anyone help me?

i don't understand why this project build properly in localhost or ec2. while hosting on vercel it failed? i have to switch vercel to aws amplify if not getting help.

timneutkens commented 11 months ago

The repository is not available still.

mthakur5 commented 11 months ago

The repository is not available still.

https://github.com/vercel/next.js/assets/138131563/40f19013-9522-4274-b3a7-71aa4945b0cc

hi Tim,

i have sent you invitation for this repository. please accept && As this repository is production site. i can't keep in public for long time. hope you can understand. 😊😊😊

mthakur5 commented 11 months ago

someone help me please, i am still figuring out why i can't publish on vercel. i couldn't even update my production site.

github-actions[bot] commented 11 months ago

We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.

Why was this issue closed?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository (template for App Router, template for Pages Router), but you can also use these templates: CodeSandbox: App Router or CodeSandbox: Pages Router.

The bug template that you filled out has a section called "Link to the code that reproduces this issue", which is where you should provide the link to the reproduction.

If you did not provide a link or the link you provided is not valid, we will close the issue.
If you provide a link to a private repository, we will close the issue.
If you provide a link to a repository but not in the correct section, we will close the issue.

What should I do?

Depending on the reason the issue was closed, you can do the following:

If you did not provide a link, please open a new issue with a link to a reproduction.
If you provided a link to a private repository, please open a new issue with a link to a public repository.
If you provided a link to a repository but not in the correct section, please open a new issue with a link to a reproduction in the correct section.

In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.

My repository is private and cannot make it public

In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:

Remove any code that is not related to the issue. (pages, API routes, components, etc.)
Remove any dependencies that are not related to the issue.
Remove any third-party service that would require us to sign up for an account to reproduce the issue.
Remove any environment variables that are not related to the issue.
Remove private packages that we do not have access to.
If the issue is not related to a monorepo specifically, try to reproduce the issue without a complex monorepo setup

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.

I think my reproduction is good enough, why aren't you looking into it quickly?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

vercel / next.js