Open andreek opened 1 month ago
You may also want to consider other node resolution algorithms like PNPM and Yarn, both of which use symlinks that may result in not having a node_modules
folder. For example, including .yarn
or .pnpm
.
You may also want to consider other node resolution algorithms like PNPM and Yarn, both of which use symlinks that may result in not having a
node_modules
folder. For example, including.yarn
or.pnpm
.
Thanks for the hint but I don't see a problem if I'm not missing something. I've used PNPM to develop this PR and every symbolic link includes /node_modules/
as suffix. I'm not that familiar with yarn, but I don't run into a problem with it either.
I can confirm that this PR makes quibble work with Node22. I'm using PNPM, so no troubles on that side. @searls any chance of getting this merged and released?
In Node.js >= v21.0.0 quibble adds 3rd party libs with
?__quibble=0
suffix as key to the quibbled modules. When Node.js is resolving the real module quibble does not find the mock, because this url does not include?__quibble=0
.I think it's related to these API changes: https://github.com/testdouble/quibble/pull/96
This PR fixes this problem by excluding urls with
node_modules
from being resolved withquibbledUrl
.Fixes: https://github.com/testdouble/testdouble.js/issues/530