You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been setting up jest.el for my projects and noticed that the default value of jest-executable (npm test) is not that general.
In my case, the default breaks because we work in a monorepository where the toplevel test is not directly invoking jest.
Proposed solution
I would propose to change it to npx --no-install jest, which should work in a larger number of cases.
The downside is you need a bit more modern version of npm. But it was introduced a while back.
Alternative solution
Alternatively, finding "jest" in the path would also work and the user could rely on add-node-modules-path. Related discussion: #2. But my proposed default value should work in most installations.
The text was updated successfully, but these errors were encountered:
I have been setting up jest.el for my projects and noticed that the default value of
jest-executable
(npm test
) is not that general.In my case, the default breaks because we work in a monorepository where the toplevel
test
is not directly invoking jest.Proposed solution
I would propose to change it to
npx --no-install jest
, which should work in a larger number of cases.The downside is you need a bit more modern version of npm. But it was introduced a while back.
Alternative solution
Alternatively, finding "jest" in the path would also work and the user could rely on add-node-modules-path. Related discussion: #2. But my proposed default value should work in most installations.
The text was updated successfully, but these errors were encountered: