Skip to content

[Feature/Bug Report] Discourage/disable "./" as one of the "moduleDirectories" #10498

Closed

Description

@davidroeca

🐛 Bug Report

This is a bug report pertaining to the use of "./" as one of the moduleDirectories. In particular, I was using a scoped package that had the same subdirectory name as a non-scoped package (e.g. @my-scope/my-package relies on my-package as an external/peer dependency). This prevented @my-scope/my-package from having access to my-package.

To Reproduce

See this repo

Expected behavior

Ideally, this behavior is not allowed. We should instead encourage people to use moduleNameMapper.

Link to repl or repo (highly encouraged)

Again see https://github.com/davidroeca/jest-shadowing-issue

envinfo

  System:
    OS: Linux 5.4 Linux Mint 20 (Ulyana)
    CPU: (8) x64 Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz
  Binaries:
    Node: 14.9.0 - ~/.asdf/installs/nodejs/14.9.0/bin/node
    Yarn: 1.22.4 - ~/.asdf/shims/yarn
    npm: 6.14.8 - ~/.asdf/installs/nodejs/14.9.0/bin/npm
  npmPackages:
    jest: ^26.4.2 => 26.4.2

Activity

  1. changed the title [-][Feature] Discourage/disable "./" as one of the "moduleDirectories"[/-] [+][Feature/Bug Report] Discourage/disable "./" as one of the "moduleDirectories"[/+] on Sep 10, 2020
  2. davidroeca commented on Sep 10, 2020

    @davidroeca
    ContributorAuthor

    Apologies, hit enter too soon. Edited the issue with the correct info.

  3. geritol commented on Apr 4, 2021

    @geritol

    I have also run into this issue (@emotion/react having react as a dependency).
    @davidroeca I think the Needs Repro label can be removed as there seems to be a reproduction.

  4. geritol commented on Apr 4, 2021

    @geritol

    for the record:

    // jest.config.js
    module.exports = {
      // ...
    -  moduleDirectories: ["node_modules", "."]
    +  moduleDirectories: ["node_modules", "<rootDir>"],
    };

    solves the issue

  5. github-actions commented on Feb 17, 2023

    @github-actions

    This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days.

  6. davidroeca commented on Feb 17, 2023

    @davidroeca
    ContributorAuthor

    I see no mentions/cautions here. I believe it is still at the very least worth discouraging somewhere in the docs.

  7. github-actions commented on Feb 17, 2024

    @github-actions

    This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days.

  8. added a commit that references this issue on Feb 21, 2024
    7be4e56
  9. github-actions commented on Mar 18, 2024

    @github-actions

    This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

  10. github-actions commented on Apr 18, 2024

    @github-actions

    This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
    Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

  11. locked as resolved and limited conversation to collaborators on Apr 18, 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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions