We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm pretty sure this is the right place to create this issue, but if not let me know.
I'm trying to use vscode to debug some of my unit tests. One of my test files uses the relatively new inline type imports feature to condense imports:
import fs from 'node:fs'; import path from 'node:path'; import assert from 'node:assert'; import { EOL } from 'node:os'; import { isNativeError } from 'node:util/types'; import { declare } from '@babel/helper-plugin-utils'; import { asMockedFunction, type AnyFunction } from '@xunnamius/jest-types'; import babel from '@babel/core';
However, the Jest plugin for vscode crashes, giving me the following error as all IDE UI decorations disappear:
/repos/babel-plugin-tester/test/plugin-tester.test.ts: failed to parse test results: SyntaxError: Unexpected token, expected "," (7:32)
Removing the inline type annotation fixes it. Is this expected behavior (that is: am I missing a babel plugin or something)?
Thanks for reading!
The text was updated successfully, but these errors were encountered:
ok, I was able to reproduce this error. We need to upgrade the dependency of this library.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
I'm pretty sure this is the right place to create this issue, but if not let me know.
I'm trying to use vscode to debug some of my unit tests. One of my test files uses the relatively new inline type imports feature to condense imports:
However, the Jest plugin for vscode crashes, giving me the following error as all IDE UI decorations disappear:
Removing the inline type annotation fixes it. Is this expected behavior (that is: am I missing a babel plugin or something)?
Thanks for reading!
The text was updated successfully, but these errors were encountered: