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

Component filename missing from error message during build #5733

Closed
1 task
nzakas opened this issue Jan 3, 2023 · 0 comments · Fixed by #5743
Closed
1 task

Component filename missing from error message during build #5733

nzakas opened this issue Jan 3, 2023 · 0 comments · Fixed by #5743
Assignees
Labels
- P2: nice to have Not breaking anything but nice to have (priority) feat: errors Related to error handling / messages (scope)

Comments

@nzakas
Copy link

nzakas commented Jan 3, 2023

What version of astro are you using?

1.8.0

Are you using an SSR adapter? If so, which one?

None

What package manager are you using?

npm

What operating system are you using?

Windows

Describe the Bug

When an error occurs while rendering a page during npm run build, the filename of the component in which the error occurs is missing.

In live preview I see this:
Screenshot 2023-01-03 at 12-41-17 On leaving Yahoo! and what's next - Human Who Codes

In the build log, I see this:
Screenshot 2023-01-03 at 12-43-51 Deploy details humanwhocodes

I'm not sure how to repro this in Stackblitz because I can't run npm run build separately there (or at least, I don't know how). All you need to do is throw an error from inside a component.

Link to Minimal Reproducible Example

https://stackblitz.com/edit/github-e4puyr?file=src/components/Card.astro

Participation

  • I am willing to submit a pull request for this issue.
@Princesseuh Princesseuh self-assigned this Jan 3, 2023
@Princesseuh Princesseuh added feat: errors Related to error handling / messages (scope) - P2: nice to have Not breaking anything but nice to have (priority) labels Jan 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
- P2: nice to have Not breaking anything but nice to have (priority) feat: errors Related to error handling / messages (scope)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants