-
Notifications
You must be signed in to change notification settings - Fork 139
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
Support workspaces #1500
Support workspaces #1500
Conversation
The location of `node_modules` is not guaranteed to be relative to the current directory (e.g. in yarn workspaces). A better solution here is to update package.json `exports` to include the file.
@@ -1,5 +1,6 @@ | |||
import yargs from "yargs"; | |||
import { hideBin } from "yargs/helpers"; | |||
import { join } from "node:path"; |
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.
Looks like it's not being used
Good catch, thank you for opening this PR @bradleyayers |
One thing to check is whether require.resolve is the correct API to use for ESM output, i'm not sure. And also the point about instead of doing a manual path concat i think it's better if the target file is made one of the exports in package.json. |
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.
remove unused imports
Hey @bradleyayers Do you think you'll have time to do it or should I take over the task (and credit you in my commit)? |
Please take this over that would be amazing, thank you. |
Superseded by #1514 |
The location of
node_modules
is not guaranteed to be relative to the current directory (e.g. in yarn workspaces).A better solution here is to update package.json
exports
to include the file.Description
Breaking change?
Example
Checklist