docs(ct): add brief information about CSS modules into FAQ (#34677)
This commit is contained in:
parent
081031f50e
commit
741a7079fe
|
@ -853,6 +853,14 @@ export default defineConfig({
|
|||
});
|
||||
```
|
||||
|
||||
### How do I use CSS imports?
|
||||
|
||||
If you have a component that imports CSS, Vite will handle it automatically. You can also use CSS pre-processors such as Sass, Less, or Stylus, and Vite will handle them as well without any additional configuration. However, corresponding CSS pre-processor needs to be installed.
|
||||
|
||||
Vite has a hard requirement that all CSS Modules are named `*.module.[css extension]`. If you have a custom build config for your project normally and have imports of the form `import styles from 'styles.css'` you must rename your files to properly indicate they are to be treated as modules. You could also write a Vite plugin to handle this for you.
|
||||
|
||||
Check [Vite documentation](https://vite.dev/guide/features#css) for more details.
|
||||
|
||||
### How can I test components that uses Pinia?
|
||||
|
||||
Pinia needs to be initialized in `playwright/index.{js,ts,jsx,tsx}`. If you do this inside a `beforeMount` hook, the `initialState` can be overwritten on a per-test basis:
|
||||
|
|
Loading…
Reference in New Issue