vercel / vercel/next.js

Error failer to read source from (improvement)

Open
#84,385 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
142k
Forks
32.4k
Avg merge
2d 14h
Merged PRs (30d)
351

Description

Link to the code that reproduces this issue

https://codesandbox.io/signin?continue=/dashboard/sandboxes/?workspace=34fe4872-11eb-4bb3-89e1-eb50c364fb27

To Reproduce

just import something with wrong path

You will see this

Image

and when I click on that it don't opens a file
it can be improved

for example when I do build
I will see this

Image

And I can click on it and it opens a file

Current vs. Expected behavior

N/A

Provide environment information
N/A
Which area(s) are affected? (Select all that apply)

Not sure

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

next dev (local)

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the wrong-import error in the linked CodeSandbox during next dev and compare it with the clickable build error. The issue names no source files or tests; done means the development error can open the relevant file like the build error, with a regression test covering the behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, next.js
Domain
developer-experience
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.