Support module paths outside of Magento root #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In my Magento environment, I'm using local composer repositories that are outside of the Magento root. In other words, if Magento lives in `/var/www/html`, a Magento module could actually be living in `/data/extensions/`. Unfortunately, this JS util is expecting the module path to be part of the Magento root, and because of that, it fails to detect a custom Tailwind file. This PR adds support for module paths outside of Magento, simply by seeing if the delivered (absolute) path exists.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In my Magento environment, I'm using local composer repositories that are outside of the Magento root. In other words, if Magento lives in
/var/www/html, a Magento module could actually be living in/data/extensions/. Unfortunately, this JS util is expecting the module path to be part of the Magento root, and because of that, it fails to detect a custom Tailwind file. This PR adds support for module paths outside of Magento, simply by seeing if the delivered (absolute) path exists.