-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Update recommended workaround for inlining a package #6237
Closed
6 tasks done
IAmLuisJ opened this issue
Jul 29, 2024
· 0 comments
· Fixed by IAmLuisJ/vitest#1 or IAmLuisJ/vitest#2 · May be fixed by #6238
Closed
6 tasks done
Update recommended workaround for inlining a package #6237
IAmLuisJ opened this issue
Jul 29, 2024
· 0 comments
· Fixed by IAmLuisJ/vitest#1 or IAmLuisJ/vitest#2 · May be fixed by #6238
Labels
Comments
IAmLuisJ
added a commit
to IAmLuisJ/vitest
that referenced
this issue
Jul 29, 2024
Update recommended workaround for inlining a package that has a syntax error when resolving a bundled dependency, since the current workaround uses deprecated config options close vitest-dev#6237
IAmLuisJ
added a commit
to IAmLuisJ/vitest
that referenced
this issue
Jul 29, 2024
Update recommended workaround for inlining a package that has a syntax error when resolving a bundled dependency, since the current workaround uses deprecated config options close vitest-dev#6237
IAmLuisJ
added a commit
to IAmLuisJ/vitest
that referenced
this issue
Jul 29, 2024
Update recommended workaround for inlining a package that has a syntax error when resolving a bundled dependency, since the current workaround uses deprecated config options close vitest-dev#6237
6 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
When Vitest runs into
SyntaxError: Cannot use import statement outside a module
it recommends the following workaroundserver.deps.inline is deprecated and the suggestion should be updated to
Reproduction
Any project that requires deeply nested alias configs in dependencies
System Info
Used Package Manager
npm
Validations
The text was updated successfully, but these errors were encountered: