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.

Sign up for GitHub

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

Jump to bottom

Support Sourcemaps for Dev #456

Open
curran opened this issue Oct 8, 2024 · 1 comment · May be fixed by #457
Open

Support Sourcemaps for Dev #456

curran opened this issue Oct 8, 2024 · 1 comment · May be fixed by #457

Comments

@curran
Copy link

curran commented Oct 8, 2024

As a newcomer to the Unovis codebase, I want to be able to know the file and line number from which an error originated, so that I can figure out the cause.

Current behavior: in npm run dev, there seems to be no sourcemaps configured, so when an error occurs, it resolves to bundle.js, which is useless. Example:

image

Desired behavior: in npm run dev, the environment leverages sourcemaps to tell you where the error is coming from.
@curran curran linked a pull request Oct 8, 2024 that will close this issue
Open
@curran
Copy link
Author

curran commented Oct 9, 2024

But overall, the source maps don't seem to be working.

For example, when I add this change:

image

I get this error:

image

The source maps don't seem to be doing their job. Instead of bundle.js it should resolve to the specific line number and source file, but it does not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Enable sourcemaps in dev curran/unovis
1 participant
@curran