-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
Add conditions to require.resolve options #34901
Comments
This comment has been minimized.
This comment has been minimized.
@aduh95 What is supported? This issue is about programmatic options of require.resolve("some/module", { conditions: ... }) |
Oops, sorry I clearly misread the OP. |
There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment. For more information on how the project manages feature requests, please consult the feature request management document. |
There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment. For more information on how the project manages feature requests, please consult the feature request management document. |
There is PR was implemented to support custom user
--conditions
#34637
I wonder why not add this param to
require.resolve
options
, which now contains onlypaths
, this would allow using require in some custom resolution scenarios, where it is not possible to use cli flag.But also probably it should not fully mimic
--conditions
which still puts leavesrequire
andnode
conditions preferable, but this option should allow overriding the full list of the used condition while resolution.@guybedford
The text was updated successfully, but these errors were encountered: