While this works it requires lots of manual work, which is not ideal. Imho, it should work the same for Angular and TS project. Here are my thoughts:

1. The Angular compiler seems to ignore or fail to resolve the references.d.ts in the tns-core-modules folder. If you add tns-platform-declarations and a references.d.ts to your app, the required references will be there. We can add this to the steps.
2. It seems that even when you do 1. the Angular compiler still doesn't like the typescript in the core modules. We should perhaps investigate these errors. They seem to be connected to the interface exports in the d.ts files.

I'll make some tests where the problem is, since it is happening only in Angular (though I might have seen it in Vue+TS) and then we can address it in dev-webpack or, if not possible - create an automated script to deploy to another folder.

@bundyo I followed the steps from "running another app" plus one additional step - adding the tns-platform-declarations packages to the app. The errors that the ng compiler producers are with types and exports. I suspect these still happen in the regular ts-loader, but as warnings. The ng compiler is producing them as errors.

The reason why we don't want to promote alternative dev setups is because we can't support them. We adhere to the dev setup in the nativescript plugin seed to make sure the tns-core-modules have a similar setup to all plugins. What I mean is, we should fix the current setup or if not possible - change the dev setup in the plugin seed first.

@rynop as elaborated by @MartoYankov I have logged a separate issue #7905 that we will need to address to fix the dev workflow in this scenario. I will close this PR for the time being.