docs: note chromium workaround (#213)

Author: bluwy

CONTRIBUTING.md

@@ -87,6 +87,13 @@ All pull requests should be opened against the `main` branch.
 Integration tests for new features or regression tests as part of a bug fix are very welcome.
 Add them to projects in `packages/e2e-tests`.
 
+If tests aren't running properly locally, open [scripts/jestGlobalSetup.js](./scripts/jestGlobalSetup.js) and update `chromium.launchServer` to use the default bundled chromium version:
+
+```js
+// don't pass any options to use bundled chromium
+return chromium.launchServer();
+```
+
 #### Documentation
 
 If you've changed APIs, update the documentation.

docs/config.md

@@ -202,9 +202,9 @@ export default defineConfig({
 
   Setting this option to `true` will directly pre-bundle Svelte libraries, which should improve initial page load performance. However, please note some caveats:
 
-  1.  Deeply importing Svelte components is not supported. Either import all components from one entrypoint, or always stick to deep imports, otherwise it could cause multiple instance of the Svelte library running.
+  1. Deeply importing Svelte components is not supported. Either import all components from one entrypoint, or always stick to deep imports, otherwise it could cause multiple instance of the Svelte library running.
 
-  2.  When updating the Svelte compiler options in `svelte.config.js` or `vite.config.js`, delete the `node_modules/.vite` folder to trigger pre-bundling in Vite again.
+  2. When updating the Svelte compiler options in `svelte.config.js` or `vite.config.js`, delete the `node_modules/.vite` folder to trigger pre-bundling in Vite again.
 
 ### generateMissingPreprocessorSourcemaps
 

docs/faq.md

@@ -97,6 +97,6 @@ Pre-bundling dependencies is an [optimization in Vite](https://vitejs.dev/guide/
 
 Historically, Svelte components had issues being pre-bundled, causing [deduplication issues](https://github.com/vitejs/vite/issues/3910) and [CJS interoperability issues](https://github.com/vitejs/vite/issues/3024). Since Vite 2.5.2, [a new API in Vite](https://github.com/vitejs/vite/pull/4634) allowed us to [automatically handle Svelte library pre-bundling](https://github.com/sveltejs/vite-plugin-svelte/pull/157) for you.
 
-Today, this feature had served us well, however a caveat remained that large Svelte component libraries often slows down the initial page load. If this affects you, try setting [experimental.prebundleSvelteLibraries](./config.md#prebundleSvelteLibraries) option to `true` to speed things up. (Note that it's an experimental option that may not always work)
+This feature had served us well, however a caveat remained that large Svelte component libraries often slows down the initial page load. If this affects you, try setting [experimental.prebundleSvelteLibraries](./config.md#prebundleSvelteLibraries) option to `true` to speed things up. (Note that it's an experimental option)
 
 In case you still run into errors like `The requested module 'xxx' does not provide an export named 'yyy'`, please check our [open issues](https://github.com/sveltejs/vite-plugin-svelte/issues).