issues
search
k-g-a
/
jest-node-exports-resolver
MIT License
25
stars
7
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Get `Cannot find module` error after upgrade to Jest 29.0.0+
#19
hunterdes
closed
11 months ago
3
findMainPackageJson() doesn't work properly on Windows
#18
kasperpawlowski
opened
2 years ago
1
Doesn't work for older versions of Jest
#17
franklin-ross
opened
2 years ago
3
Doesn't seem to work with @firebase/auth
#16
tettoffensive
opened
2 years ago
0
Fix handling absolute paths on Windows
#15
grpawel
closed
2 years ago
3
"setupFiles" and "setupFilesAfterEnv" Jest options do not work properly when using jest-node-exports-resolver
#14
Maikel-Nait
closed
2 years ago
2
Throwing an error doesn't work for monorepos
#13
gigaSproule
opened
2 years ago
5
fix: failed on pnpm
#12
JiangWeixian
opened
2 years ago
6
Doesn't Appear to work with Top level node Exports
#11
dairyisscary
closed
2 years ago
6
Remove extra logs for optional modules
#10
exarus
closed
2 years ago
1
Since 1.1.3 'Cannot use import statement outside a module'
#9
yaakovfeldman
opened
2 years ago
10
Respect conditions if present
#8
vpzomtrrfrt
closed
2 years ago
3
Add support for subpath patterns
#7
ezzatron
closed
3 years ago
3
Add support for string and nested exports & self-referencing packages
#6
piranna
closed
3 years ago
9
Doesn't work with `ws` module
#5
piranna
opened
3 years ago
3
Don't work with `exports` as string
#4
piranna
closed
3 years ago
1
Don't ignore if `submoduleName` has an extension
#3
piranna
closed
3 years ago
4
Not working accessing files in scoped packages
#2
piranna
closed
3 years ago
3
Don't require export of `package.json` file
#1
piranna
closed
3 years ago
13