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

Turbopack: trace HMR errors through sourcemaps correctly #61360

Closed
wants to merge 7 commits into from

Conversation

wbinnssmith
Copy link
Member

@wbinnssmith wbinnssmith commented Jan 30, 2024

Turbopack: trace HMR errors through sourcemaps correctly

Requires vercel/turbo#7160

Previously, we attempted to trace stacks through the source map for the entire chunk rather than the map for the chunk update.

Test Plan: Now passing event handler error test in acceptance-app/error-recovery.ts

Closes PACK-2318

Requires vercel/turbo#7160

Previously, we attempted to trace stacks through the source map for the entire chunk rather than the map for the chunk update.

Test Plan: Now passing event handler error test in `acceptance-app/error-recovery.ts`
@wbinnssmith wbinnssmith changed the title wbinnssmith/hmr sourcemap overlay Turbopack: trace HMR errors through sourcemaps correctly Jan 30, 2024
Copy link
Member

@sokra sokra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a big fan of accessing internals, but ok for now

timneutkens added a commit that referenced this pull request Jan 30, 2024
@timneutkens timneutkens mentioned this pull request Jan 30, 2024
timneutkens added a commit that referenced this pull request Jan 30, 2024
This reverts commit 18eed36.
timneutkens added a commit that referenced this pull request Jan 30, 2024
This reverts commit cbc4e8f.

Co-authored-by: Will Binns-Smith <wbinnssmith@gmail.com>
@timneutkens
Copy link
Member

Opened a new PR as this one somehow isn't known to git: #61369

timneutkens added a commit that referenced this pull request Jan 30, 2024
## What?

Same PR as #61360, somehow that branch could not be checked out / wasn't
available in git.

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->


Closes NEXT-2295

---------

Co-authored-by: Will Binns-Smith <wbinnssmith@gmail.com>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants