Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error running a new project #46632

Closed
1 task done
abdofariss opened this issue Mar 1, 2023 · 6 comments
Closed
1 task done

Error running a new project #46632

abdofariss opened this issue Mar 1, 2023 · 6 comments
Labels
bug Issue was opened via the bug report template. please add a complete reproduction The issue lacks information for further investigation

Comments

@abdofariss
Copy link

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
Platform: win32
Arch: x64
Version: Windows 10 Pro
Binaries:
Node: 18.14.0
npm: N/A
Yarn: N/A
pnpm: N/A
Relevant packages:
next: 13.2.3
eslint-config-next: N/A
react: 18.2.0
react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

CLI (create-next-app)

Link to the code that reproduces this issue

npx create-next-app@latest

To Reproduce

npx create-next-app@latest nextjs-blog
cd nextjs-blog
npm run dev

Describe the Bug

When i run the new created project the first time, i got this error:

unhandledRejection: TypeError: trace.getSpan is not a function

i tried creating the project using npx create-next-app@latest & npx create-next-app@latest nextjs-blog --use-npm --example "https://github.com/vercel/next-learn/tree/master/basics/learn-starter"

i got the same error

Expected Behavior

I just expected to see the default home page of a new created Nextjs project

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

@abdofariss abdofariss added the bug Issue was opened via the bug report template. label Mar 1, 2023
@balazsorban44
Copy link
Member

Could you please link to a repository? I cannot reproduce based on the description.

@balazsorban44 balazsorban44 added the please add a complete reproduction The issue lacks information for further investigation label Mar 1, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Mar 1, 2023

We cannot recreate the issue with the provided information. Please add a reproduction in order for us to be able to investigate.

Why was this issue marked with the please add a complete reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository (template), but you can also use a tool like CodeSandbox or StackBlitz.

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue.

Please test your reproduction against the latest version of Next.js (next@canary) to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

What happens if I don't provide a sufficient minimal reproduction?

Issues with the please add a complete reproduction label that receives no meaningful activity (e.g. new comments with a reproduction link) are automatically closed and locked after 30 days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue with the required reproduction.

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. Furthermore, you can upvote the issue using the 👍 reaction on the topmost comment (please do not comment "I have the same issue" without reproduction steps). Then, we can sort issues by votes to prioritize.

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

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

@abdofariss
Copy link
Author

He

Could you please link to a repository? I cannot reproduce based on the description.

Hi,

I just created a repo: https://github.com/fariss/nextjs-new-project

Screenshot: https://ibb.co/PrYqTK1

@ciruz
Copy link
Contributor

ciruz commented Mar 2, 2023

@fariss works for me, also your repo works for me.

My System is the same like yours:

    Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.14.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.2.3
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

image

image

@abdofariss
Copy link
Author

Very strange, I solved it by installing @opentelemetry, as suggested here: https://stackoverflow.com/questions/75571462/nextjs-13-2-1-unhandledrejection-error-in-next-js-project-typeerror-trace-g
npm install @opentelemetry/api @opentelemetry/resources @opentelemetry/semantic-conventions @opentelemetry/sdk-trace-node @opentelemetry/instrumentation

@github-actions
Copy link
Contributor

github-actions bot commented Apr 1, 2023

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template. please add a complete reproduction The issue lacks information for further investigation
Projects
None yet
Development

No branches or pull requests

3 participants