You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The published package has source maps but no src/ directory, so I can't just jump to where the error came from in my IDE, I have to come here, find the tag for the right version, and look in the source directory. This is tedious and painful.
Reproducible Example
What do you expect to happen?
I can jump to where the error occured by ctrl+clicking the stack trace locations in the VSCode console.
What is actually happening?
I can't, because the file in the stack trace is not included in the published package.
Environment
Sequelize version: 6.37.1
Node.js version: 20.10.0
If TypeScript related: TypeScript version:
Database & Version: Postgres 14
Connector library & Version: pg 8.11.3
Would you be willing to resolve this issue by submitting a Pull Request?
No, I don't have the time, and I understand that I will need to wait until someone from the community or maintainers is interested in resolving my issue.
Indicate your interest in the resolution of this issue by adding the 👍 reaction. Comments such as "+1" will be removed.
The text was updated successfully, but these errors were encountered:
WikiRik
added
type: other
For issues and PRs. Something that does not fit in any of the other "type:" labels.
and removed
pending-approval
Bug reports that have not been verified yet, or feature requests that have not been accepted yet
type: bug
labels
May 8, 2024
Issue Creation Checklist
Bug Description
The published package has source maps but no
src/
directory, so I can't just jump to where the error came from in my IDE, I have to come here, find the tag for the right version, and look in the source directory. This is tedious and painful.Reproducible Example
What do you expect to happen?
I can jump to where the error occured by ctrl+clicking the stack trace locations in the VSCode console.
What is actually happening?
I can't, because the file in the stack trace is not included in the published package.
Environment
Would you be willing to resolve this issue by submitting a Pull Request?
Indicate your interest in the resolution of this issue by adding the 👍 reaction. Comments such as "+1" will be removed.
The text was updated successfully, but these errors were encountered: