Using the Quick Start, there is an infinite reload with browsersync
60 views
Skip to first unread message
Raymond Camden
unread,
Dec 30, 2015, 5:02:46 PM12/30/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to AngularJS
I'm following the guide here (https://angular.io/docs/ts/latest/quickstart.html), and after I did npm start, it opened up the app in a new tab and then began a cycle of infinite reloading. In my terminal, I see messages like this:
It helped me wrap my head around many of the angular 2 concepts
Raymond Camden
unread,
Jan 1, 2016, 4:33:17 PM1/1/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to AngularJS
Ok, as a follow up, I'm seeing the issue again while working on the Tutorial. I made sure I did not npm start in app folder. As before, I'm seeing multiple "File changed" messages for stuff inside node_modules. Things worked fine for a while, but now the tab is constantly reloading.
On Wednesday, December 30, 2015 at 4:02:46 PM UTC-6, Raymond Camden wrote:
Raymond Camden
unread,
Jan 1, 2016, 4:41:55 PM1/1/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to AngularJS
Ok, looks like - maybe - it was Dropbox. Telling it to pause syncing seems to have helped. Oddly - last mod values for the files weren't changing so I don't think Dropbox was 'updating' them, but, whatevs. :)
On Wednesday, December 30, 2015 at 4:02:46 PM UTC-6, Raymond Camden wrote: