-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
process.chdir is not available in workers #566
Comments
Then you might want to mock it, or use |
@antfu Would it be a good idea to have a comment that disables workers just for one file? |
mocking isn't really an option because I need to do more file operations (not in my repo, but in external monorepos). I'll have to tried --threads 🤔 |
It is |
aight, I'm happy with that -- things seem to be moving along now :D |
…r`. (vitest-dev#567) Adds a few feature to allow users to configure error handling if they so choose. Without this feature, any error from the source observable would be treated as "unhandled" by RxJS, and thrown in a new call stack. Resolves vitest-dev#566
Describe the bug
if you're testing node utilities, maybe ones that help interact with the file system, and you need to call
chdir
, there is no way to test that behavior because all tests run in node workers, which aren't allowed to callprocess.chdir
Reproduction
raises:
Is there a way to opt certain tests to not run in a worker?
otherwise I'd need to test anything that uses chdir, in mocha or something.
System Info
The text was updated successfully, but these errors were encountered: