Download the PHP package userfrosting/vite-php-twig without Composer
On this page you can find all versions of the php package userfrosting/vite-php-twig. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download userfrosting/vite-php-twig
More information about userfrosting/vite-php-twig
Files in userfrosting/vite-php-twig
Package vite-php-twig
Short Description Vite function for Twig templates
License MIT
Homepage https://github.com/userfrosting/vite-php-twig
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package vite-php-twig
Vite Manifest Support for PHP & Twig
Vite Manifest function for PHP & Twig Templates. Allows Vite manifest integration in PHP & Twig Templates without Symfony. Optimized for PHP-DI style containers.
Inspired by kellerkinderDE/vite-encore-bundle & PHP-Vite.
Installation
Documentation & Usage
Using standalone
[!TIP]
ViteManifestimplements\UserFrosting\ViteTwig\ViteManifestInterfaceif you prefer to type-hint against interfaces, for use with dependency injection.
Using with Twig
[!IMPORTANT] Requires Twig 3 or newer
Vite writes a manifest.json file that contains all of the files needed for each Rollup 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.
Now, to render all of the script and link tags for a specific "entry" (e.g. views/foo.js), you can:
If you have multiple entry point scripts on the same page, you should pass them in a single call to avoid duplicates - for example:
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.
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 and server.port:
For more information on how to configure Vite, see the official documentation.
ViteManifest Options
manifestPath- string: Points to the Vitemanifest.jsonfile 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 theoutDirin 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
- License
