Gotcha -- tell me a bit more about your objective -- just trying to get an ng1.x app running?
-
-
Replying to @joshmobley
Correct :) I'm looking to press CMD+S and see the magic happen where all my changes appear in the Browsers automatically.
2 replies 0 retweets 0 likes -
Replying to @decahub
lolol you're gonna be so pissed when you see my pull request to show what was wrong...
1 reply 0 retweets 1 like -
Replying to @joshmobley
This is a historic moment for me because it will be my first pull request from someone who is not my mom :D Exciting! Thanks!
1 reply 0 retweets 0 likes -
Replying to @decahub
So I think your trouble is that html-watch runs a reload as well as js-watch - so js-watch injects, which causes html-watch to fire
5 replies 0 retweets 0 likes -
Replying to @joshmobley
lastly, b4 heading 2 bed. I should have mentioned that I am using
@WebStormIDE :( There seems to be a memory problem with the it1 reply 0 retweets 0 likes -
Replying to @decahub
hi, what kind of memory problem? Can you please tell us more? Thanks!
@joshmobley4 replies 0 retweets 0 likes -
Replying to @WebStormIDE
When that starts happening the whole projects behaves erratically: changes on files or file system don't show, for example.
1 reply 0 retweets 0 likes -
Replying to @decahub
do you have any tool that changes the files, e.g. build tool such as Gulp, Grunt, npm or Webpack?
1 reply 0 retweets 1 like -
Replying to @WebStormIDE
I do. This is while developing a Gulp workflow :)
2 replies 0 retweets 0 likes
and you're editing the same files, right? Usually with Gulp the output goes to a dist/built folder and it's recommended... 1/2
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.