I see that there is still some effort needed to bridge jest.
How about instead of bridging jest, providing a mode that builds all the tests in some dir, and then the user is responsible for running jest against that? Jest will automatically update when the output changes.
The one thing that breaks is Jest's detection of files changed vs git, there might be some way to handle that though.
I see that there is still some effort needed to bridge jest.
How about instead of bridging jest, providing a mode that builds all the tests in some dir, and then the user is responsible for running jest against that? Jest will automatically update when the output changes.
The one thing that breaks is Jest's detection of files changed vs git, there might be some way to handle that though.