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
I'd like to run astrum through my gulp browser sync config rather than on mamp. I am able to add new components and view files in my current setup, however Astrum does not "Compile" unless I add/edit a component.
What behaviour would you expect?
I'd like for Astrum to compile whenever I edit a file without having to run this project in my mamp local server.
Perhaps there can be some sort of watch task that updates the files when they're changed. I just don't know how the current system works other than it just "works" when it's in mamp lol.
How can this issue be replicated?
spin up a localhost env with gulp and astrum
Platform: Mac
OS Version: 10.12.4
Node Version: 4.4.7
NPM Version: 2.15.8
Astrum Version: 1.9.3
The text was updated successfully, but these errors were encountered:
Hi @WhatsNewSaes. Apologies for the delay in responding to this! I'm hesitant to enforce a specific config on Astrum as everyones local environments are different. I for example run everything through a Homestead/Vagrant...
With regards to "compiling" Astrum wouldn't a project level gulp watcher that watches for changes to Astrum components and my compiled project stylesheets and then uses browser sync to update Astrum be a workable approach?
Tell us about the issue you are experiencing
I'd like to run astrum through my gulp browser sync config rather than on mamp. I am able to add new components and view files in my current setup, however Astrum does not "Compile" unless I add/edit a component.
What behaviour would you expect?
I'd like for Astrum to compile whenever I edit a file without having to run this project in my mamp local server.
Perhaps there can be some sort of watch task that updates the files when they're changed. I just don't know how the current system works other than it just "works" when it's in mamp lol.
How can this issue be replicated?
spin up a localhost env with gulp and astrum
Platform: Mac
OS Version: 10.12.4
Node Version: 4.4.7
NPM Version: 2.15.8
Astrum Version: 1.9.3
The text was updated successfully, but these errors were encountered: