-
Notifications
You must be signed in to change notification settings - Fork 15
BC-9973 - Migrate to Vitest #3761
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
base: BC-8695-vite-upgrade
Are you sure you want to change the base?
Conversation
"types": ["node"], | ||
"typeRoots": ["./node_modules/@types", "./types"], | ||
"types": ["node", "vitest/globals"], | ||
"typeRoots": ["./node_modules/@types", "./types", "./node_modules"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should avoid adding the whole node_modules
path here.
vite.config.ts
Outdated
find: /^@@\/(.*)$/, | ||
replacement: fileURLToPath(new URL("$1", import.meta.url)), | ||
}, | ||
], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The additional resolve aliases are only used when running the tests. We should remove them from the configuration for build
and serve
commands.
vite.config.ts
Outdated
@@ -1,3 +1,4 @@ | |||
/// <reference types="vitest" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What exactly is this for and is this still needed? As well as should we separate vite and vitest configs?
Short Description
Links to Ticket and related Pull-Requests
Changes
Data-security
Deployment
New Repos, NPM packages or vendor scripts
Screenshots of UI changes
Checklist before merging