-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build theme without changing directories #14
base: master
Are you sure you want to change the base?
Conversation
…git root and the theme dir all the time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bdimaggio - I wish I could've saved you some trouble ahead of time! Here's a one-liner for your drupal site's theme dir that makes no assumptions about where it's located (drush 9):
drush dd $(drush st --field=theme)
Actually take this just one step further, this seems to work for me... does this work for you? npm run start --prefix=$(drush dd $(drush st --field=theme)) |
ohhh this is brilliant ⭐️ I'm just gonna make aliases for this and its |
I think it's fine for this to live in this repo. The more I think about this though, the more it makes me feel like maybe we should consider adding something like this to https://github.com/thinkshout/robo-drupal Like what if we could do
|
We could even have a special keyword for |
@bdimaggio and @wxactly - adding a script for this sounds like a valuable addition to I usually end up with two terminal screens and keep the watcher running on one of them to see live updates. Since I haven't tried playing around with these solutions yet, I'm not sure how my flow might differ from the one(s) being proposed. Any insights here? The idea of getting to build the theme from the same directory we do work sounds like a great benefit. Let me know if I can be assistance! |
Heck yes! Awesome ideas all. I'll do that.
…On Mon, Mar 9, 2020 at 12:18 PM Jaymz Rhime ***@***.***> wrote:
We could even have a special keyword for install (robo theme install)
that did npm install instead.... still brainstorming ;)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14?email_source=notifications&email_token=ABPAY3P5NYHP2RK62VHFAUTRGUQGXA5CNFSM4LCS7G72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOH5JEI#issuecomment-596628625>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPAY3MOITRE72FYOLRAST3RGUQGXANCNFSM4LCS7G7Q>
.
|
Enforcing this lets us do dynamic theme compilation per thinkshout/ts_recipes#14 Note that this is waiting on pantheon-systems/example-drops-8-composer#334 and km_collaborative to switch to that release.
Just wrote this to save me having to jump back and forth between the git root and the theme dir all the time. I'm a very novice shell scripter--feedback very welcome.