Observer pattern for decoupling of data and visualisation in purely client-based javascript?

I want to learn about best practices / patterns of data visualisation in the context of a purely client-/browser-based javascript program (i.e. the data resides in the browser so there is no communication with the server after page load).

In particular, I wonder if decoupling of the data and the corresponding visualisation (e.g. in three.js) with the Observer pattern is good design. The data may change, and is visualised only in one way (so that would mean only one Observer).

Is this a good approach in general and in particular regarding the particular circumstances or is another approach better suited for the task?