Skip to content
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

module: NODE_PRIORITIZED_PATH didn't precede relative node_modules #551

Open
legendecas opened this issue Aug 7, 2019 · 1 comment
Open

Comments

@legendecas
Copy link
Contributor

  • Version: v0.11.x
  • Platform: all
  • Subsystem: module

Suppose we have following structure:

-- /
 |- /vendor
 |  |- /lru-cache
 |
 |- /workspace
    |- /node_modules
    |  |- /lru-cache
    |
    | index.js

While we run index.js in directory /workspace with NODE_PRIORITIZED_PATH set to /vendor, /workspace/node_modules/lru-cache would still be used but not /vendor/lru-cache. This behavior is not as aligned with document, in which NODE_PRIORITIZED_PATH is preceding node_modules folder under current working directory.

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.64. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot issue-label-bot bot added the bug label Aug 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant