You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if I could composer require wp-less from a plugin or theme folder as a way of installing wp-less.
Currently due to the "type": "wordpress-plugin" if you try this wp-less will end up in /wp-content/themes/{yourtheme}/wp-content/plugins/wp-less and wp-less' dependencies will be put in /wp-content/themes/{yourtheme}/vendor. wp-less.php is not designed for this structure as it expects that either it's a plugin or that the vendor folder is relative to it.
The text was updated successfully, but these errors were encountered:
The problem here is that you would need to make changes that would break things for everybody else.
To use an analogy, what you're requesting is like saying a car wheel requires a sunroof assembly to function when assembling just the wheel. When assembling a full WP stack, you're assembling a car, but we're thinking about it from the wrong way round here with just the wheel.
Instead require wp-less from your theme and plugin, then require your theme/plugin from the main WordPress project, wp-less will be pulled in and installed in the appropriate location. Such a composer.json would go in the WP root ( it needn't manage every plugin and every theme, and WP Core itself though ).
The alternative is to specify a parent folder, but that would change the composer.json and break things for everyone else.
It would be nice if I could
composer require wp-less
from a plugin or theme folder as a way of installing wp-less.Currently due to the
"type": "wordpress-plugin"
if you try this wp-less will end up in/wp-content/themes/{yourtheme}/wp-content/plugins/wp-less
and wp-less' dependencies will be put in/wp-content/themes/{yourtheme}/vendor
. wp-less.php is not designed for this structure as it expects that either it's a plugin or that the vendor folder is relative to it.The text was updated successfully, but these errors were encountered: