One of the most common questions I have been asked over the years (and still am today) about extending model-driven PowerApps / Dynamics 365 CE with html and JavaScript is:
“What’s the most productive way to develop and debug Dynamics 365 (and now model-driven PowerApps) web resources?”
The answer to that question will certainly be different depending on who you ask. Any answer to this question is subjective. There are lots of code editors out there that allow you to edit the various file types supported by web resources (html and JavaScript being the most common). There are lots of helpful tools available that could be leveraged in different ways to answer this question (some from Microsoft, many created by members of the community). I’ve tried lots of approaches over the years. If you’ve come across any of my older blog posts or videos on the topic, then you’ve probably seen some of them. When I show people my current preferred approach, most generally agree that it is more productive than what they are currently doing. The video below is a comprehensive walkthrough of my my current approach. As you will see in the video, at the time of this post, my toolchain is Visual Studio 2017, a must have (in my opinion) Visual Studio extension from Jason Lattimer called D365 Developer Extensions, and Fiddler.
HTH