-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
fix: Improve get caller file path util #7974
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
5 Skipped Deployments
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥇
Just curious, where do we use this helper? |
for the joiner config builder, basically since the choice was to make it fully magic and this builder is at different level in the application stack, I needed a way to retrieve the location of the original module caller |
… into fix/get-caller-file-path
@thetutlage as I was explaining to carlos, since node deprecated the callee and that the require.resolve parent is deprecated as well, I didnt get a choice 😂 if you have anyhting in mind let me know |
@adrien2p Nope. I am not questioning the implementation. Just curious, where do we/in which use cases we look for the callee path? |
Saw this comment now. Cool, makes sense! |
FIXES CORE-2492