Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`require('./')` broken if parent directory has file with the same name

See original GitHub issue

🐛 Bug Report

Suppose you have a file dir/fn.js that requires the current directory using const x = require('./'), and the parent directory has a file dir.js. In Node.js 8, x will contain the exported value from dir/index.js. In Jest, x will contain the exported value from dir.js

To Reproduce

Steps to reproduce the behavior:

https://github.com/vkarpov15/jest-bug

Expected behavior

require() in Jest should behave the same as require() in vanilla Node.js, especially if using the Node test environment.

Link to repl or repo (highly encouraged)

https://github.com/vkarpov15/jest-bug

envinfo

$ npx envinfo --preset jest
npx: installed 1 in 1.063s

  System:
    OS: Linux 4.15 Ubuntu 16.04.3 LTS (Xenial Xerus)
    CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
  Binaries:
    Node: 8.9.4 - /usr/bin/node
    npm: 5.6.0 - /usr/bin/npm
  npmPackages:
    jest: 24.9.0 => 24.9.0 

$

Re: https://github.com/Automattic/mongoose/issues/8053

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:5

Top GitHub Comments

1reaction

vkarpov15commented, Sep 4, 2019

I don’t think I have the time to put in a PR. I already worked around this in Mongoose so nothing more to do on my end.

Why does Jest monkey patch require() anyway? Seems very dubious

0reactions

github-actions[bot]commented, May 11, 2021

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.