And when we build the app, this still stays the same, although the content.ejs file is built into production.js. So my question is, what should we do so that when we build the app, these references point to ejs files inside of production.js?
When the production.js file is created, your views are included and get preloaded when the script runs. When you reference: '//app/views/content.ejs', view first checks if the view file you are requesting has been preloaded and if it has, will use that instead of making a request for the .ejs file.
Leave a comment on Curtis Cummings's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic