Not working on macOS #44
Labels
p3-minor-bug
An edge case that only affects very specific usage (priority)
Comments
searene
added
the
p3-minor-bug
|
+1 |
1 similar comment
|
+1 |
zxch3n
added a commit
that referenced
this issue
Jun 18, 2022
|
Could you switch to the pre-release version and check whether it acts the same? If so, please attach the output log from Vitest to help me locate the issue.
I'm also using macOS, but I cannot reproduce this error. I need you guys' help, thanks. |
|
Hi, how to switch to the pre-release version? Are there any guidelines? |
|
@searene You can do it in the extension homepage |
|
@zxch3n Hi, After I started the
I got the following output: Seems like the test is skipped. By the way, when I ran the test manually outside of VSCode using the following command: ./node_modules/.bin/vitest /Users/joey/WebstormProjects/vitest-ext-basic-example/add.test.ts -t add 1 + 1The test is passed as expected: |
|
Same problem on m1-osx with a solid-project :/ |
kodiakhq bot
pushed a commit
to recipeyak/recipeyak
that referenced
this issue
Aug 1, 2022
Basically: - Replace web pack setup with vite and upgrade various dependencies and cull unnecessary ones. - Also remove TSLint. Will replace with typescript-eslint rules eventually. - Got rid of the hacky landing page static generation. Various road bumps along the way: - https://javascript.plainenglish.io/how-to-set-up-path-resolving-in-vite-ad284e0d9eae - fix sass imports vitejs/vite#5764 (comment) - Then needed to rewrite the alias for typescript again to match the types - Replace `process`. With the `import.meta.env` thing - https://stackoverflow.com/questions/64677212/how-to-configure-proxy-in-vite - Fix imports for static files from `requires()` - Had to fix proxying for `/avatar` and `/api` in dev - Ran into remarkjs/react-markdown#339 (comment) - Upgrade markdown react to fix - Migrate from `react-helmet` to fix some deprecation warnings - Vite has a different jsx config, so no need to import React - microsoft/TypeScript#41882 - Vitest issue: - https://github.com/vitest-dev/vitest/blob/57c2367196b3fd978a04fa38ebdac7a5b6ef9b16/packages/vite-node/src/client.ts#L178-L179 - Couldn’t import react-dnd, upgraded - react-dnd/react-dnd#3368 - `import { isUndefined } from "util"` didn’t work - Favicon via https://github.com/darkobits/vite-plugin-favicons to replace web pack equivalent - Issue with React router browser history in vitest, it exploded until jsdom was setup - Question: https://stackoverflow.com/questions/71703933/what-is-the-difference-between-vite-and-vite-preview - Vitest vscode integration broken :/ - vitest-dev/vscode#44 - Tried happy-dom but it doesn’t work, lots of issues, supposed to be faster - Took a while to get MSW in a good place, had to write some stuff so missing endpoint mocks fail the test - I think there's room for improvement here in terms of developer experience - Test with react testing library and API calls - https://www.npmjs.com/package/nock - Doesn’t fail test on unknown mock - https://stackoverflow.com/questions/69430232/jest-nock-how-to-fail-a-test-if-a-non-mocked-request-is-made - MSW - Doesn’t fail test on unknown mock - mswjs/msw#946 - Relay’s mockEnvironment - couldn't easily find thorough examples - Apollo mock provider - Doesn’t fail test on unknown mock - Added a visualize plugin similar to a web pack analyzer thing, but it’s slightly off with the numbers it gives for sizes: - btd/rollup-plugin-visualizer#96 - TODO: - ESLINT rules, replace what tslint provided, eslint-cake anyone? - https://typescript-eslint.io/rules/no-floating-promises/ - And more!!! - Replace lodash with lodash-es - Or maybe: https://github.com/onebay/vite-plugin-imp - Although lodash-es seems cleaner - SSR for landing page?
|
Works for me, following the steps to reproduce on an M1 Mac Mini, using the pre-release version of the plugin. Node 18.4.0 (and npm, not yarn, if that makes a difference). I am having problems getting it to work in a svelte project (even a newly initialized one) though. |
|
m1 Mac, svelte-kit project, it can see all the tests, but can't run them:
Changed to |
|
Same issue for me on linux, it looks like the websocket never connects (no WS Open message). I can confirm downgrading |
|
version 0.2.15 works for me as the last one |
|
This issue should be fixed now. If it's still wrong, let me know |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
Maybe I didn't use the addon in the correct way? But simply put, the addon is not working at all. After installing it, I saw the testing tab, I saw the little error beside the test, but no matter where I click, the test is not running.
To Reproduce
https://github.com/zxch3n/vitest-ext-basic-examplenode setup.mjs.Expected behavior
It should start testing.
Screenshots
Environment
{ "System": { "OS": "macOS 12.4" }, "Binaries": { "Node": { "version": "18.2.0", "path": "~/.nvm/versions/node/v18.2.0/bin/node" }, "Yarn": { "version": "1.22.18", "path": "/usr/local/bin/yarn" }, "npm": { "version": "8.9.0", "path": "~/.nvm/versions/node/v18.2.0/bin/npm" } }, "IDEs": { "VSCode": { "version": "1.67.2", "path": "/usr/local/bin/code" } }, "npmPackages": { "vite": { "installed": "2.9.9", "wanted": "^2.9.9" }, "vitest": { "installed": "0.12.10", "wanted": "^0.12.6" } } }The text was updated successfully, but these errors were encountered: