Support Vitest #4145

birkskyum · 2023-08-13T21:01:55Z

Vitest - website - github

What version of Bun is running?

0.8.1

What platform is your computer?

Darwin 22.5.0 arm64 arm

What steps can reproduce the bug?

bun --bun x vitest

What is the expected behavior?

No error

What do you see instead?

SyntaxError: Import named 'Console' not found in module 'node:console'.

Additional information

Related to:

The text was updated successfully, but these errors were encountered:

birkskyum · 2023-08-13T22:05:57Z

It seems like the console.ts / console.js that contains:

export default console

Might also have to export the named Console in order to be node compatible.

paperdave · 2023-08-15T00:25:55Z

Console issue you are seeing is #3625. It's a constructor that returns a console object that has stdout/stderr redirected

mnik01 · 2023-09-09T13:43:22Z

Any workarounds?

ghiscoding · 2023-09-15T18:58:36Z

might also be worth to know that Vitest itself also have a PR, in draft, to support Bun by using ShadowRealm with this description

Currently, all jsdom tests are failing because bun doesn't seem to correctly support VM module.

paperdave · 2023-09-19T01:50:04Z

console.console is implemented in the next release
that might fix vitest

birkskyum · 2023-09-19T14:29:13Z

It's progress, but I get this:

vitest on  main [!?] 
➜ bun --bun x vitest

 DEV  v0.34.4 /Users/admin/repos/vitest

[bun] Warning: worker_threads.Worker option "argv" is not implemented.
[bun] Warning: worker_threads.Worker option "execArgv" is not implemented.
[bun] Warning: worker_threads.Worker option "resourceLimits" is not implemented.

AriPerkkio · 2023-09-19T15:39:32Z

Those warning can be ignored, see https://github.com/tinylibs/tinypool/pull/70/files#diff-478191b8d0c43c3d24bfda206ff15909923b8b5a89eec9c967376feded4edfa7R9

nyxb · 2023-09-23T21:35:30Z

have the same:

[bun] Warning: worker_threads.Worker option "argv" is not implemented.
[bun] Warning: worker_threads.Worker option "execArgv" is not implemented.
[bun] Warning: worker_threads.Worker option "resourceLimits" is not implemented.

and cant ignore tests doesnt finish

and get this if i want cancel need to do it 1000 times before exit:

RangeError: exitCode must be between 0 and 127
      at /Users/nyxb/projects/github_packages/eslint-config/node_modules/vitest/dist/vendor-node.81dd929c.js:17951:8
      at _keypressHandler (/Users/nyxb/projects/github_packages/eslint-config/node_modules/vitest/dist/vendor-node.81dd929c.js:17946:34)
      at /Users/nyxb/projects/github_packages/eslint-config/node_modules/vitest/dist/vendor-node.81dd929c.js:17990:10
      at keypressHandler (/Users/nyxb/projects/github_packages/eslint-config/node_modules/vitest/dist/vendor-node.81dd929c.js:17989:33)
      at node:readline:114:54
      at onData (node:readline:476:34)
      at addChunk (node:stream:1940:42)
      at readableAddChunk (node:stream:1894:58)
Cancelling test run. Press CTRL+c again to exit forcefully.

17946 |   async function _keypressHandler(str, key) {
17947 |     if (str === "" || str === "\x1B" || key && key.ctrl && key.name === "c") {
17948 |       if (!ctx.isCancelling) {
17949 |         ctx.logger.logUpdate.clear();
17950 |         ctx.logger.log(c.red("Cancelling test run. Press CTRL+c again to exit forcefully.\n"));
17951 |         process.exitCode = 130;
            ^
RangeError: exitCode must be between 0 and 127
      at /Users/nyxb/projects/github_packages/eslint-config/node_modules/vitest/dist/vendor-node.81dd929c.js:17951:8
      at _keypressHandler (/Users/nyxb/projects/github_packages/eslint-config/node_modules/vitest/dist/vendor-node.81dd929c.js:17946:34)
      at /Users/nyxb/projects/github_packages/eslint-config/node_modules/vitest/dist/vendor-node.81dd929c.js:17990:10
      at keypressHandler (/Users/nyxb/projects/github_packages/eslint-config/node_modules/vitest/dist/vendor-node.81dd929c.js:17989:33)
      at node:readline:114:54
      at onData (node:readline:476:34)
      at addChunk (node:stream:1940:42)
      at readableAddChunk (node:stream:1894:58)

IndranilKhedkar · 2023-10-09T16:36:48Z

Same here - error: "vitest" exited with code 9 (SIGKILL)

pafeltowicz · 2023-10-13T14:01:09Z

I have same problem

birkskyum · 2024-01-04T15:07:33Z

Hmm... if I now make a small test file like this , and run, it seems to just freeze:

➜ bun --bun x vitest

 DEV  v1.1.1 /Users/admin/repos/histoire-vue3-starter

MkSavin · 2024-01-10T14:19:09Z

The argument implementation warning was removed in version 1.0.22, but vitest still doesn't work.
It turns out that we need to wait for the implementation of bun's virtualization or the integration of shadowrealm api in vitest

Rhymmor · 2024-03-28T05:18:16Z

Getting this error while running bun x -b vitest run.

OS: Darwin 23.1.0 arm64 arm

Bun v1.0.35, Vitest v1.4.0

> bun x -b vitest run  

82 |                                    `You can download it from ${msvcDownloadLink}`,
83 |                            { cause: error }
84 |                    );
85 |            }
86 | 
87 |            throw new Error(
             ^
error: Cannot find module @rollup/rollup-darwin-arm64. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory.
 cause: {
  "name": "ResolveMessage",
  "position": null,
  "message": "Cannot find module \"@rollup/rollup-darwin-arm64\" from \"***/rollup/dist/native.js\"",
  "level": "error",
  "specifier": "@rollup/rollup-darwin-arm64",
  "importKind": "require-call",
  "referrer": "***/rollup/dist/native.js"
}

      at requireWithFriendlyError (***/node_modules/rollup/dist/native.js:87:9)
      at ***/node_modules/rollup/dist/native.js:96:48

redbit86k · 2024-06-19T15:33:32Z

Maybe interesting fact:

if you take the node:20 docker image and install bun there, then our
bun run vitest --coverage --run --watch false
completes without problems.

if we use the oven:bun image it just hangs.
Hope this fact maybe helps someone as a workaround if possible...

birkskyum · 2024-06-19T15:48:00Z

With the node one, does it pass with the '--bun' flag?

redbit86k · 2024-06-20T08:58:14Z

Sadly
bun run --bun vitest --coverage --run
does not finish.
Also does not work on my local dev machine (ubuntu24lts), just hangs

birkskyum · 2024-06-30T22:19:42Z

I know bun has a competing bun test, but as of writing vitest is quickly becoming a staple, so it would be great if bun could support it as well. If people can adopt bun in their projects, and then consider swapping the test runner, that would give a much nicer migration story towards bun.

https://2023.stateofjs.com/en-US/libraries/#tools_arrows

✅ Closes: oven-sh/bun#4145

birkskyum · 2024-08-06T00:31:13Z

Still issue with vitest 2.x / bun 1.1.22-canary.85+cacbaba52

➜ bun --bun x vitest

 DEV  v2.0.5

marviobezerra · 2024-08-13T19:54:09Z

+1

JarekToro · 2024-09-04T15:22:45Z

+1

birkskyum · 2024-09-10T13:20:46Z

Tried with latest stabe bun 1.1.27 - it hangs, and also makes these weird symbols instead of interrupting why I try to escape it

birkskyum added the bug Something isn't working label Aug 13, 2023

birkskyum mentioned this issue Aug 13, 2023

Support Astro #3746

Closed

paperdave mentioned this issue Sep 15, 2023

feat(runtime): Implement console.Console #5448

Merged

3 tasks

jasongitmail mentioned this issue Nov 7, 2023

Tests not found after using bun install, but found using npm install, on Github Actions #6971

Open

Applelo mentioned this issue Nov 8, 2023

Add Bun test support SpiriitLabs/vite-plugin-svg-spritemap#23

Closed

Mimikkk mentioned this issue Jan 22, 2024

[TypeScript] full support ✨🤖 EvanZhouDev/gemini-ai#6

Closed

holgerd77 mentioned this issue Feb 14, 2024

Generalized Runtime Docs / (First round) Bun Support ethereumjs/ethereumjs-monorepo#3219

Open

dylanlangston mentioned this issue Mar 4, 2024

Can't use Bun to test dylanlangston/dylanlangston.com#73

Open

Electroid mentioned this issue Mar 4, 2024

bunx vitest hangs #9170

Closed

birkskyum mentioned this issue May 22, 2024

vitest hangs #11268

Open

fubhy mentioned this issue Jul 16, 2024

disable bun test suite Effect-TS/effect#3264

Merged

ianzone added a commit to ianzone/react-template that referenced this issue Jul 23, 2024

chore: 🤖 use node as runtime

9d217a5

✅ Closes: oven-sh/bun#4145

fubhy mentioned this issue Aug 3, 2024

Using Bun with @effect/vitest, tests fail to run Effect-TS/effect#3406

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Support Vitest #4145

Support Vitest #4145

birkskyum commented Aug 13, 2023 •

edited

Loading

birkskyum commented Aug 13, 2023

paperdave commented Aug 15, 2023 •

edited

Loading

mnik01 commented Sep 9, 2023

ghiscoding commented Sep 15, 2023

paperdave commented Sep 19, 2023 •

edited

Loading

birkskyum commented Sep 19, 2023 •

edited

Loading

AriPerkkio commented Sep 19, 2023

nyxb commented Sep 23, 2023 •

edited

Loading

IndranilKhedkar commented Oct 9, 2023

pafeltowicz commented Oct 13, 2023

birkskyum commented Jan 4, 2024

MkSavin commented Jan 10, 2024

Rhymmor commented Mar 28, 2024 •

edited

Loading

redbit86k commented Jun 19, 2024

birkskyum commented Jun 19, 2024

redbit86k commented Jun 20, 2024

birkskyum commented Jun 30, 2024

birkskyum commented Aug 6, 2024

marviobezerra commented Aug 13, 2024

JarekToro commented Sep 4, 2024

birkskyum commented Sep 10, 2024

Support Vitest #4145

Support Vitest #4145

Comments

birkskyum commented Aug 13, 2023 • edited Loading

What version of Bun is running?

What platform is your computer?

What steps can reproduce the bug?

What is the expected behavior?

What do you see instead?

Additional information

birkskyum commented Aug 13, 2023

paperdave commented Aug 15, 2023 • edited Loading

mnik01 commented Sep 9, 2023

ghiscoding commented Sep 15, 2023

paperdave commented Sep 19, 2023 • edited Loading

birkskyum commented Sep 19, 2023 • edited Loading

AriPerkkio commented Sep 19, 2023

nyxb commented Sep 23, 2023 • edited Loading

IndranilKhedkar commented Oct 9, 2023

pafeltowicz commented Oct 13, 2023

birkskyum commented Jan 4, 2024

MkSavin commented Jan 10, 2024

Rhymmor commented Mar 28, 2024 • edited Loading

redbit86k commented Jun 19, 2024

birkskyum commented Jun 19, 2024

redbit86k commented Jun 20, 2024

birkskyum commented Jun 30, 2024

birkskyum commented Aug 6, 2024

marviobezerra commented Aug 13, 2024

JarekToro commented Sep 4, 2024

birkskyum commented Sep 10, 2024

birkskyum commented Aug 13, 2023 •

edited

Loading

paperdave commented Aug 15, 2023 •

edited

Loading

paperdave commented Sep 19, 2023 •

edited

Loading

birkskyum commented Sep 19, 2023 •

edited

Loading

nyxb commented Sep 23, 2023 •

edited

Loading

Rhymmor commented Mar 28, 2024 •

edited

Loading