Adds a module doc and code block to help satisfy JSR's scoring.Suggestions for alternatives or improvements very welcome.Part of#3597

The example for the CSP middleware looks a bit broken currently on JSR,due to the `@example` markdown is not wrapped in a code block.<img width="1136" height="247" alt="image"src="https://github.com/user-attachments/assets/57888033-aa9e-4701-87dc-4f4810365177"/>## Changes- Improves formatting a bit, to be less compact- Wraps the example in a code block ` ```ts `- Adds a title to the `@example` - "Basic usage" - To avoid the examplebeing labeled as "Example1" on JSR

Improves documentation of `@fresh/plugin-vite` related to public API,and exports missing symbols/types that are part of public API(`FreshViteConfig`).- Adds `@module` JSDoc for the `@fresh/plugin-vite/client` entrypoint  - Internal only, used for browser HMR- Exports types `ImportCheck` & `ImportCheckDiagnostic`, as they arepart of the public API via `FreshViteConfig`- Should make [`ImportCheck` link to correcttype](https://jsr.io/@fresh/plugin-vite/doc/~/FreshViteConfig#property_checkimports):<img width="1053" height="285" alt="image"src="https://github.com/user-attachments/assets/766c29f7-7f39-429e-bd81-234fed6b0820"/>- Adds JSDoc descriptions for all public exports; `fresh`,`FreshViteConfig`, `ImportCheck` & `ImportCheckDiagnostic`- Adds description for `FreshViteConfig.checkImports`Part of#3597 &#3596

…ts (#3603)Addresses scoring of `@fresh/examples` of JSR for several metrics:- ✅ Adds module doc for all entrypoints- ✅ Adds descriptions to all public exports for `@fresh/examples` (0% ->100%)I could not find if `@fresh/examples` are part of any E2E tests to testusing JSR package as mounted app or Island, or if this is just a smalldemo for users. So I just added small generic drescriptions.Part of#3597

Improves clarity of CORS JSDoc example for JSR:<img width="1088" height="706" alt="image"src="https://github.com/user-attachments/assets/8ea3b6f9-a5ee-41cc-9512-a3a0fb87a4c0"/>## Changes- Split the example into two: Basic & Advances- Uncomment "Advanced" example

This PR just fills out the `README.md` with minimal usage example, suchthat they can get a small taste of how the framework can be used. Thisalso helps improve the score in JSR.Part of#3597

Played around with Hono in the past days and the`.text()/.json()/.html()` helpers are kinda neat, even if you can alwaysconstruct that yourself manually. Also added a `.stream()` helper tocreate streams without having to deal with `ReadableStream` andencodings yourself.

| Before| After || :---: | :---: ||![before](https://github.com/user-attachments/assets/6d485c89-79ec-485d-9897-de9db0a9b044)|![after](https://github.com/user-attachments/assets/5c134ea1-6dec-4da5-8a84-e7e7b7e062a7)|The appearance on dark mode doesn't change.Co-authored-by: Ayaka <KiritaniAyaka@users.noreply.github.com>

The recommended way to configure custom directives from Tailwind is touse `files.associations`.Check recommended settings from Tailwind CSS IntelliSense Extension:https://github.com/tailwindlabs/tailwindcss-intellisense#recommended-vs-code-settingsThis allows us to stop maintaining future changes to custom directivesfrom TailwindCSS, instead letting the TailwindCSS extension decide howto handle them.Co-authored-by: Ayaka <KiritaniAyaka@users.noreply.github.com>

Mappings were wrong for a few reasons:- Missing source map generation in one babel transform- setting `compact: false` causes vite to generate incorrect mappings in`vite:import-analysis`- stack traces need to be mapped by viteFixes#3609

This change was accidentally included in:#3624

- `@fresh/core@2.2.0`- `@fresh/update@2.2.0`- `@fresh/init@2.3.0`- `@fresh/plugin-vite@1.0.8`