-
-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@golevelup/ts-vitest #613
Comments
@sschneider-ihre-pvs It is possible but |
Sorry, but I don't understand what the issue is. I copied the contents of the mocks.ts file, replaced all occurrences of It's a single file, so it's not an issue for us to simply copy it to our codebases, but it would definitely be an improvement to have a separate package for this. |
Hi, we just did the same thing. It should be easy enough to add in a vitest file. |
Copied over the ts-jest files and adapted them to work with Vitest, so now you can use these testing utils with Vitest. fix golevelup#613
Copied over the ts-jest files and adapted them to work with Vitest, so now you can use these testing utils with Vitest. fix golevelup#613
Copied over the ts-jest files and adapted them to work with Vitest, so now you can use these testing utils with Vitest. fix golevelup#613
Opened up a PR that adds support for Vitest: #702 |
…ils (#702) * feat(ts-vitest): added a new package to support vitest for testing utils Copied over the ts-jest files and adapted them to work with Vitest, so now you can use these testing utils with Vitest. fix #613 * fix(ts-vitest): set type to module * ci(ts-vitest): exclude from jest and add vite config * ci(ts-vitest): add coverage * ci(ts-vitest): add missing deps * ci(ts-vitest): only run vitest on Node 18 * ci(ts-vitest): move vitest to optional dependencies * ci(ts-vitest): only build on Node 18 * ci(ts-vitest): fix build commands
ts-vitest is meant to be imported by vitest as such it needs to be a proper ESM module. The package.json already defined it as "type": "module", but the typescript build was still generating a CommonJS build. This fix updates the typescript configuration to output an ESM module. re golevelup#613
ts-vitest is meant to be imported by vitest as such it needs to be a proper ESM module. The package.json already defined it as "type": "module", but the typescript build was still generating a CommonJS build. This fix updates the typescript configuration to output an ESM module. re #613
ts-vitest is meant to be imported by vitest as such it needs to be a proper ESM module. The package.json already defined it as "type": "module", but the typescript build was still generating a CommonJS build. This fix updates the typescript configuration to output an ESM module. re #613
ts-vitest is meant to be imported by vitest as such it needs to be a proper ESM module. The package.json already defined it as "type": "module", but the typescript build was still generating a CommonJS build. This fix updates the typescript configuration to output an ESM module. re #613
would it be possible to make a similar
createMock
for vitest like in @golevelup/ts-jest? I guess it would be something like%s/jest/vi/g
or something.The text was updated successfully, but these errors were encountered: