This repository was archived by the owner on Dec 16, 2025. It is now read-only.
This repository was archived by the owner on Dec 16, 2025. It is now read-only.
Limitations #4
Description
Various limitations and accommodations must be made to use this package.
- This package assumes that Vite will be used alongside its installation directory. It also assumes the exact location of the Vite manifest file.
- This package is of type "wordpress-themecore". The intention here is that Composer must be configured to install packages of this type within the site's main theme directory. This means that this infrastructure can only be used for a single theme. I.e. it could not be used within both a parent and child theme at the same time.
- The assumed Vite architecture also requires that all Sass files exist within an src directory. We are currently looking to move block-specific Sass files within block-specific directories, which also contain the block registration PHP classes and template files. The Vite architecture could be adapted to treat a whole theme directory (which contains individual block directories) as a Vite source directory. This would allow Vite to compile from any file descending from a theme root directory, regardless of specific location.
To resolve some of these issues, I suggest that this package be engineered as an MU Plugin. This plugin could register a WP CLI command to install a standardised Vite architecture, plus any other standard files, to any theme directory.
This could also register a WP CLI command to act as a wrapper for the Vite compilation process. This process could compile all assets in all themes using a single command. This would also mitigate the need for any site-specific or theme-specific compilation commands.