How to completely remove pre-rendering code from Angular template #667

Closed
opened 2025-08-09 17:17:10 +00:00 by fergalmoran · 0 comments
Owner

Originally created by @danobri on 6/12/2017

I am working on an intranet application based on the latest Angular (v4) template, and have disabled pre-rendering due to the fact that API calls return 401 errors, as described in issue #971. I do not have a specific requirement for pre-rendering and it adds quite a bit of complexity to the template, so would like to completely remove all the pre-rendering code from the project. There was a similar question in issue #928, but the solution appears to be specific to the older ng2 version of the template, and does not directly apply to the current ng4 version. Can anyone provide a similar list of steps for what needs to be removed? It would be great if pre-rendering could be included/excluded via a switch on the dotnet new command for this template so users could choose whether to include. My hunch is that it's not commonly needed, and adds unnecessary complexity for most users.

*Originally created by @danobri on 6/12/2017* I am working on an intranet application based on the latest Angular (v4) template, and have disabled pre-rendering due to the fact that API calls return 401 errors, as described in issue [#971](https://github.com/aspnet/JavaScriptServices/issues/971). I do not have a specific requirement for pre-rendering and it adds quite a bit of complexity to the template, so would like to completely remove all the pre-rendering code from the project. There was a similar question in issue [#928](https://github.com/aspnet/JavaScriptServices/issues/938), but the solution appears to be specific to the older ng2 version of the template, and does not directly apply to the current ng4 version. Can anyone provide a similar list of steps for what needs to be removed? It would be great if pre-rendering could be included/excluded via a switch on the dotnet new command for this template so users could choose whether to include. My hunch is that it's not commonly needed, and adds unnecessary complexity for most users.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/JavaScriptServices#667
No description provided.