Digest cycle

Last reviewed May 28, 2026 Content v20260528

Track mode

client_angularjs

Means

In-browser AngularJS 1.x

Reading

~1 min

Level

advanced

This lesson

This lesson teaches Digest cycle: the concepts, APIs, and habits you need before advancing in AngularJS.

The digest cycle drives updates in 1.x—watchers and manual $apply mistakes cause “binding not updating” bugs.

You will apply Digest cycle in contexts like: Long-lived intranet apps, government portals, and codebases not yet moved to Angular, React, or Vue.

Write JavaScript for AngularJS 1.8, click Run—register modules/controllers, then mountApp(moduleName, templateHtml) in #ng-app; printOutput feeds the terminal.

When hooks, state, and effects from intermediate lessons are familiar.

$digest and $apply propagate scope changes; manual $apply fixes third-party callbacks outside Angular.

Third-party callbacks outside Angular must call $scope.$apply() or use $timeout so bindings update.

Important interview questions and answers

Q: Why does this matter?
A: $digest and $apply propagate scope changes; manual $apply fixes third-party callbacks outside Angular.

Self-check

Summarize Digest cycle in one sentence.
What would you try next in the playground?

Challenge

Digest cycle hands-on

Edit the default code.
Click Run in browser.
Confirm preview or terminal output.

Done when: preview or terminal matches the lesson goal.

Pitfall: Third-party callbacks (maps, websocket) must call $scope.$apply or bindings look frozen.

Interview prep

When is $digest needed?: Angular schedules digests after DOM events; call $apply when code outside Angular mutates scope.

Playground

Runs in your browser in a sandboxed frame. Backend runners appear when this track’s profile allows them.

Discussion

Past discussion is visible to everyone. Only logged-in users can post comments and replies.

Starter discussion topics

$apply when?
Infinite digest cause?

No discussion yet. Be the first to ask a question.