search

vercel / next.js

The React Framework
https://nextjs.org
MIT License
126.78k stars 26.95k forks source link

✓ Starting... TypeError: fetch failed | 'UNABLE_TO_VERIFY_LEAF_SIGNATURE' | [Error: Next.js package not found #64876

Closed PiwkaNorbert closed 6 months ago

PiwkaNorbert commented 6 months ago

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/github/codesandbox/sandbox-templates/tree/main/nextjs?file=%2Fpackage.json%3A1%2C1-28%2C1

To Reproduce

p / npm run dev

I can't get it to reproduce on the sandbox...

Current vs. Expected behavior

My dependencies:

{
  "name": "cdu_hub",
  "version": "3.3.3",
  "private": true,
  "scripts": {
    "dev": "next dev -p 5173",
    "build": "next build",
    "start": "next start",
    "lint": "next lint"
  },
  "dependencies": {
    "@motionone/utils": "^10.17.0",
    "@tanstack/react-query": "^5.18.1",
    "@tanstack/react-query-devtools": "^5.18.1",
    "@types/lodash.debounce": "^4.0.9",
    "@vercel/analytics": "^1.1.2",
    "@vercel/speed-insights": "^1.0.9",
    "clsx": "^2.1.0",
    "fast-xml-parser": "^4.3.4",
    "framer-motion": "^11.0.3",
    "isomorphic-dompurify": "^2.3.0",
    "lodash.debounce": "^4.0.8",
    "next": "14.2.0-canary.18",
    "next-auth": "^4.24.5",
    "next-themes": "^0.2.1",
    "react": "^18.2.0",
    "react-countup": "^6.5.0",
    "react-debounce-input": "^3.3.0",
    "react-dom": "^18.2.0",
    "react-hot-toast": "^2.4.1",
    "react-loading-skeleton": "^3.4.0",
    "sharp": "^0.33.2",
    "tailwind-merge": "^2.2.1",
    "use-debounce": "^10.0.0"
  },
  "devDependencies": {
    "@tailwindcss/typography": "^0.5.10",
    "@types/node": "^20.11.16",
    "@types/react": "^18.2.52",
    "@types/react-dom": "^18.2.18",
    "autoprefixer": "^10.4.17",
    "eslint": "^8.56.0",
    "eslint-config-next": "14.1.0",
    "postcss": "^8.4.33",
    "postcss-preset-env": "^9.3.0",
    "prettier": "^3.2.5",
    "prettier-plugin-tailwindcss": "^0.5.11",
    "tailwindcss": "^3.4.1",
    "typescript": "^5.3.3"
  }
}

As I pnpm run dev I get an initial:


 ✓ Starting...
TypeError: fetch failed
    at node:internal/deps/undici/undici:12618:11
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

![dasadsdaasdasass](https://github.com/vercel/next.js/assets/71353104/0c1e7659-e2da-4243-aade-1fc5e868ef36)

I've removed the whole folder, recloned the repo and one commit before the HEAD. upgraded all packages, reinstalled nodeJS, rebooted my Laptop and turned that SSL option in node to false but to no avail this issue hasn't been resolved and I don't understand why. I've been running 14.2.0-canary.18 since it's release with no issues even in production. and what's ironic, before all of this the current build is currently working on vercel running just fine

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 32421
  Available CPU cores: 20
Binaries:
  Node: 20.12.2
  npm: N/A
  Yarn: N/A
  pnpm: 8.10.5
Relevant Packages:
  next: 14.2.0-canary.18
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: N/A

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

Not sure, Runtime

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

next dev (local), next build (local), next start (local)

Additional context

No response

github-actions[bot] commented 6 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.

What should I do?

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

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:

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.

Useful Resources