Update Changelog and Readme

Author: lcharette

CHANGELOG.md

@@ -4,6 +4,10 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
 
+## 1.1.0
+- Support CSS standalone file by [@imagoiq](https://github.com/imagoiq) in [#1](https://github.com/userfrosting/vite-php-twig/pull/1)
+- Add PHP 8.4 Tests
+
 ## 1.0.2
 - Apply `basePath` to server URL
 

README.md

@@ -26,27 +26,30 @@ $manifest = new ViteManifest('.vite/manifest.json');
 
 // Get files for `views/foo.js` entry
 $manifest->getScripts('views/foo.js'); // Scripts
-$manifest->getStyles('views/foo.js'); // Style
-$manifest->getImports('views/foo.js'); // Preload
+$manifest->getStyles('views/foo.js'); // Styles
+$manifest->getImports('views/foo.js'); // Preloads
 
 // Render HTML tags for `views/foo.js` entry
 $manifest->renderScripts('views/foo.js'); // Scripts
-$manifest->renderStyles('views/foo.js'); // Style
-$manifest->renderPreloads('views/foo.js'); // Preload
+$manifest->renderStyles('views/foo.js'); // Styles
+$manifest->renderPreloads('views/foo.js'); // Preloads
 
 // If you have multiple entry point scripts on the same page, you should pass them in a single call to avoid duplicates - for example:
 $manifest->getScripts('views/foo.js', 'views/bar.js');
 ```
 
+> [!TIP]
 > `ViteManifest` implements `\UserFrosting\ViteTwig\ViteManifestInterface` if you prefer to type-hint against interfaces, for use with dependency injection.
 
 ### Using with Twig
+> [!IMPORTANT]
 > Requires Twig 3 or newer
 
-Vite writes an `manifest.json` file that contains all of the files needed for each "entry". To reference entries in Twig, you need to add the `ViteTwigExtension` extension to the Twig Environment. This accept a `ViteManifest`, which itself accept the path to the `manifest.json`, 
+Vite writes a `manifest.json` file that contains all of the files needed for each [Rollup Input](https://rollupjs.org/configuration-options/#input) or "entry". To reference entries in Twig, you need to add the `ViteTwigExtension` extension to the Twig Environment. This accepts a `ViteManifest`, which itself accepts the path to the `manifest.json`.
 
 ```php
 use UserFrosting\ViteTwig\ViteManifest;
+use UserFrosting\ViteTwig\ViteTwigExtension;
 use Twig\Environment;
 use Twig\Loader\FilesystemLoader;
 
@@ -59,7 +62,7 @@ $twig = new Environment($loader);
 $twig->addExtension($extension);
 ```
 
-Now, to render all of the `script` and `link` tags for a specific "entry" (e.g. `entry1`), you can:
+Now, to render all of the `script` and `link` tags for a specific "entry" (e.g. `views/foo.js`), you can:
 
 ```twig
 {{ vite_js('views/foo.js') }}
@@ -72,8 +75,13 @@ If you have multiple entry point scripts on the same page, you should pass them
 {{ vite_js('views/foo.js', 'views/bar.js') }}
 ```
 
-### Vite default port
-By default, vite will use port `5173`. However, if the port is already being used, Vite will automatically try the next available port so this may not be the actual port the server ends up listening on. Since a PHP application doesn't know which port is being used by vite, the port can be forced in the `vite.config.js` file inside your project's root directory using [`server.strictPort`](https://vitejs.dev/config/server-options#server-strictport) and [`server.port`](https://vitejs.dev/config/server-options#server-port) :  
+Standalone CSS, SCSS, SASS, and LESS files can also be rendered directly, as long as they are defined in your Vite config as a rollup input.
+```twig
+{{ vite_css('my_theme.less') }}
+```
+
+### Vite Default Port
+By default, Vite will use port `5173`. However, if the port is already being used, Vite will automatically try the next available port so this may not be the actual port the server ends up listening on. Since a PHP application doesn't know which port is being used by Vite, the port can be forced in the `vite.config.js` file inside your project's root directory using [`server.strictPort`](https://vitejs.dev/config/server-options#server-strictport) and [`server.port`](https://vitejs.dev/config/server-options#server-port):
 ```js
 server: {
     strictPort: true,
@@ -90,24 +98,13 @@ $manifest = new ViteManifest(
     basePath: 'dist/',
     serverUrl: 'http://[::1]:5173/',
     devEnabled: true,
-)
+);
 ```
 
-`manifestPath` - string
-
-Points to the Vite `manifest.json` file created for the production build.. Optional if you're using the dev server
-
-`basePath` - string 
-
-Public base path from which Vite's published assets are served. The assets paths will be relative to the `outDir` in your vite configuration. It could also point to a CDN or other asset server, if you are serving assets from a different domain.
-
-``serverUrl`` - string 
-
-The vite server url, including port. Can be used to specify a non-default port if used.
-
-``devEnabled`` - bool
-
-Indicates whether the application is running in development mode (i.e. using vite server). Defaults to false.
+- `manifestPath` - string: Points to the Vite `manifest.json` file created for the production build. Optional if you're using the dev server.
+- `basePath` - string: Public base path from which Vite's published assets are served. The assets paths will be relative to the `outDir` in your Vite configuration. It could also point to a CDN or other asset server if you are serving assets from a different domain.
+- `serverUrl` - string: The Vite server URL, including port. Can be used to specify a non-default port if used.
+- `devEnabled` - bool: Indicates whether the application is running in development mode (i.e. using Vite server). Defaults to false.
 
 ## See Also
 - [Changelog](CHANGELOG.md)