Skip to content

Add conditions to require.resolve options #34901

Closed
Closed
Add conditions to require.resolve options#34901
Labels
feature requestIssues requesting new Node.js features.moduleIssues and PRs related to the module subsystem.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

Description

@wclr
wclr
opened on Aug 24, 2020

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 only paths, 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 leaves require and node conditions preferable, but this option should allow overriding the full list of the used condition while resolution.

@guybedford

Activity

  1. PoojaDurgad
    added
    esmIssues and PRs related to the ECMAScript Modules implementation.
    on Oct 22, 2020

  2. aduh95 commented on Mar 21, 2021

    @aduh95
    aduh95
    on Mar 21, 2021 · Hidden as off-topic

  3. wclr commented on Mar 21, 2021

    @wclr
    wclr
    on Mar 21, 2021
    Author

    @aduh95 What is supported?

    This issue is about programmatic options of require.resolve, to be able to use conditions while resolving using API:

    require.resolve("some/module", { conditions: ... })

  4. aduh95 commented on Mar 21, 2021

    @aduh95
    aduh95
    on Mar 21, 2021
    Contributor

    Oops, sorry I clearly misread the OP.

  5. aduh95
    added
    feature requestIssues requesting new Node.js features.
    moduleIssues and PRs related to the module subsystem.
    and removed
    esmIssues and PRs related to the ECMAScript Modules implementation.
    on Mar 21, 2021

  6. github-actions commented on Mar 22, 2022

    @github-actions
    github-actionsBot
    on Mar 22, 2022
    Contributor

    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.

  7. github-actions
    added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Mar 22, 2022
  8. targos
    added this to Node.js feature requestson Mar 22, 2022
  9. targos
    moved this to Stale in Node.js feature requestson Mar 22, 2022

  10. github-actions commented on Apr 22, 2022

    @github-actions
    github-actionsBot
    on Apr 22, 2022
    Contributor

    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.

  11. github-actions
    closed this as completedon Apr 22, 2022
  12. avivkeller
    removed this from Node.js feature requestson Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature requestIssues requesting new Node.js features.moduleIssues and PRs related to the module subsystem.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions