-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Unknown file extension .svelte still happening #6529
Comments
Hello @webJose. Please provide a minimal reproduction using a GitHub repository or StackBlitz (you can also use examples). Issues marked with |
Please provide a minimal reproduction. Asking maintainers to create component libraries with specific framework is too much. |
No problem. But really? You can do I could not follow the recommendation of Being the stubborn person that I sometimes am, I still typed "inline", and to my surprise it showed up in Intellisense, where I could read that there was a I think this should be documented as a minimum, as I bet it happens to others. If I may be so bold, I'd like to ask if this is a workaround or is it expected to always be like this? My updated import { sveltekit } from '@sveltejs/kit/vite';
import { svelteTesting } from '@testing-library/svelte/vite';
import { defineConfig } from 'vitest/config';
export default function () {
return defineConfig({
plugins: [sveltekit(), svelteTesting()],
test: {
include: ['src/**/*.{test,spec}.{js,ts}', 'src/**/*.{test,spec}.svelte.{js,ts}'],
environment: 'jsdom',
globals: true,
server: {
deps: {
inline: [/@scope\/name/]
}
}
},
});
}; Thank you very much for the time taken to give me some attention. I appreciate it. Cheers! |
UpdateThe workaround fails when 2 regular expressions are added to import { sveltekit } from '@sveltejs/kit/vite';
import { svelteTesting } from '@testing-library/svelte/vite';
import { defineConfig } from 'vitest/config';
export default function () {
return defineConfig({
plugins: [sveltekit(), svelteTesting()],
test: {
include: ['src/**/*.{test,spec}.{js,ts}', 'src/**/*.{test,spec}.svelte.{js,ts}'],
environment: 'jsdom',
globals: true,
server: {
deps: {
inline: [/@scope1\/name1/, /@scope2\/name2/]
}
}
},
});
}; Preliminary testing seems to indicate that only the first one is honored. |
Without seeing some code and being able to run a minimal reproduction there's not much we can do. Those configuration files look just fine to me. |
Describe the bug
I am creating a new bug report since this one got closed and limited, therefore I cannot comment on it.
This problem is still present. The original issue states that "dist" folders are not being given special treatment anymore, and this is why the issue was allegedly closed (as far as I can tell). I am in Vitest 2.1.1 and this still happens.
Reproduction
The error should appear. Current
vite.config.ts
configuration:System Info
Used Package Manager
npm
Validations
The text was updated successfully, but these errors were encountered: