chore: update the vite readme.md

Author: Sébastien Henau

packages/vite/README.md

@@ -1,64 +1,36 @@
-# Vite plugin for sending sourcemaps to Flare
+# @flareapp/vite
 
-The Flare Vite plugin helps you send sourcemaps of your compiled JavaScript code to Flare. This way, reports sent using the `@flareapp/js` will be formatted correctly.
+Vite build plugin for [Flare](https://flareapp.io) that uploads sourcemaps after each build. With sourcemaps, error reports sent by `@flareapp/js` will show the original source code instead of minified output.
 
-Additionally, it automatically passes the Flare API key to `@flareapp/js`. This way, `flare.light()` works without any additional configuration.
-
-Check the JavaScript error tracking section in [the Flare documentation](https://flareapp.io/docs/javascript-error-tracking/installation) for more information.
+The plugin also injects the Flare API key and a sourcemap version identifier into your build, so `flare.light()` works without any additional configuration.
 
 ## Installation
 
-Install the plugin using NPM or Yarn:
-
 ```bash
-yarn add @flareapp/vite
-# or
 npm install @flareapp/vite
 ```
-Next, add the plugin to your `vite.config.js` file:
 
-```js
+## Quick start
+
+Add the plugin to your `vite.config.ts`:
+
+```ts
 import { defineConfig } from 'vite';
 import flareSourcemapUploader from '@flareapp/vite';
 
 export default defineConfig({
     plugins: [
         flareSourcemapUploader({
-            key: 'YOUR API KEY HERE'
+            key: 'YOUR_FLARE_API_KEY',
         }),
     ],
 });
 ```
 
-Run the `vite build` command to make sure the sourcemaps are generated. You should see the following lines in the output:
-
-```bash
-@flareapp/flare-vite-plugin-sourcemaps: Uploading 12 sourcemap files to Flare.
-@flareapp/flare-vite-plugin-sourcemaps: Successfully uploaded sourcemaps to Flare.
-```
-
-## Configuration
-
-- `key: string` **(required)**: the Flare API key 
-- `base: string`: the base path of built output (defaults to Vite's base path)
-- `runInDevelopment: boolean`: whether to upload sourcemaps when `NODE_ENV=development` or when running the dev server (defaults to `false`)
-- `version: string`: the sourcemap version (defaults to a fresh `uuid` per build)
-- `removeSourcemaps: boolean`: whether to remove the sourcemaps after uploading them (defaults to `false`). Comes in handy when you want to upload sourcemaps to Flare but don't want them published in your build.
-
-## development
-
-Publish a new release: 
-
-```bash
-npm version patch
-npm publish
-```
+## Documentation
 
-Tag the release:
+Full documentation on configuration options, sourcemap resolution, and more is available at [flareapp.io/docs/javascript/general/resolving-bundled-code](https://flareapp.io/docs/javascript/general/resolving-bundled-code).
 
-<pre>
-git tag <var>VERSION</var>
-git push origin <var>VERSION</var>
-</pre>
+## License
 
-Replace <var>VERSION</var> with `v` + the version from `package.json` — for example, `v1.0.2` 
+The MIT License (MIT). Please see [License File](../../LICENSE.md) for more information.