mkg0 jest-webpack-resolver issues - Githubissues

mkg0 / jest-webpack-resolver

path resolver for jest through the webpack.config. Auto detect webpack's resolve properties like aliases, plugins and more

44 stars 6 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Any chance of reviving this for webpack 5

#18 ScriptedAlchemy opened 3 years ago
1
Unknown option "jestWebpackResolver"

#17 lucasriondel opened 5 years ago
6
Please support the case where the webpack config exports a promise!

#16 benalman-toast opened 6 years ago
0
Fix the possibility of an absolute path.

#15 Mechtecs opened 6 years ago
2
add cache

#14 mkg0 closed 6 years ago
0
Cache resolved paths

#13 evanc closed 6 years ago
1
Performance issues

#12 MarcoNicolodi closed 6 years ago
5
Jest module mocks do not work with this resolver

#11 mlippens opened 6 years ago
2
Ci integration

#10 mkg0 closed 6 years ago
0
feat: Add silent option

#9 guilhermelimak closed 6 years ago
0
Add silent option

#8 guilhermelimak closed 6 years ago
3
! get webpack config only once, instead of calling it everytime during resolve

#7 pedi closed 6 years ago
2
publish v0.1.2 to npm

#6 chrismatix closed 6 years ago
1
Import statements won't work

#5 mgoldwater-nisum-com opened 6 years ago
2
Watch flag won't work

#4 mgoldwater-nisum-com closed 6 years ago
1
Support package.json as configuration source

#3 kompot opened 7 years ago
0
Support jest.config.js as for config.

#2 DzoQiEuoi closed 6 years ago
2
Doesn't work if the webpack config exports a function.

#1 DzoQiEuoi closed 7 years ago
1