Here is my TsConfig.tns.json file:
{ "extends": "./tsconfig.json", "compilerOptions": { "outDir": "./out-tsc/app", "paths": { "@src/*": [ "src/*.tns.ts", "src/*.ts", "src/*.prod.ts" ] } }, "files": [ "./src/main.tns.ts", "./src/polyfills.tns.ts" ], "include": [ "./src/**/*.tns.ts", "./src/**/*.d.ts", "src/environments/environment.prod.ts" ], }
here is my tsconfig.app.json file:
{ "extends": "./tsconfig.json", "compilerOptions": { "outDir": "./out-tsc/app", "paths": { "@src/*": [ "src/*.web", "src/*" ] } }, "files": [ "./src/main.ts", "./src/polyfills.ts" ], "include": [ "./src/**/*.d.ts" ], }

interesting to note it does show me that it's using... tsconfig-paths-webpack-plugin: Using config file at ./tsconfig.tns.json

Seems this was unanswered here: NativeScript/nativescript-dev-webpack#1154

@bufke do you have any insight?

You would be better served by someone on the NativeScript team. However, to my best understanding, you will never succeed in trying to use a NS shared project using the .tns. method. The previously shared approach was done by the telerek team and the current maintainers do not agree with it nor have time to support it. I can understand the position the current maintainers are in is tough and find no blame on them.

The current recommended approach is to rewrite your app using something like NX. I started doing this for a smaller app I have and found it to really be on the level of rewrite. For me, it resulted in about 50% more lines of code. My app and web code are really intended to have feature parity, making the .tns.* method highly effective for me. If your web/app code are not tightly coupled, then it may not be such a big deal for you. NX makes it easy to share packages between projects but it does not work well if you only want to replace html with nativescript templates. You may want to consider other options like Flutter which make it much easier to reuse app/web presentation code.

@bufke I figured they put the tsconfig plugin inside @nativescript/webpack to showcase how you can dynamically use a different tsconfig file. However, show cases tsConfigPath that we need to be able to edit.

Literally adding the lines from nativescript-dev-webpack (4 or before) checking if a path resolves to tsconfig.tns.json

Could we edit our webpack.config file to

function getAngularCompilerPlugin(): any {
	const { AngularCompilerPlugin } = require('@ngtools/webpack');
	return AngularCompilerPlugin;
}

and pass in the tns config file?

https://github.com/NativeScript/NativeScript/blob/master/packages/webpack5/src/configuration/angular.ts

Show cases they hardcode tsconfig.app.json :(

Okay, even when I edit that.... to tns.json I run into polyfills.ts vs polyfills.tns.ts.

Lower down that file, I can edit polyfills to tns as well - but still have tons of build issues

Closed based off the response from core team:NativeScript/angular#28