René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Cannot link tns-core-modules in Angular app","articleBody":"**Environment**\r\nProvide version numbers for the following components (information can be retrieved by running `tns info` in your project folder or by inspecting the `package.json` of the project):\r\n - CLI: 6.1.2\r\n - Cross-platform modules: 6.1.1\r\n - Android Runtime: 6.1.2\r\n - iOS Runtime: 6.1.1\r\n\r\n**Describe the bug**\r\nWhen trying to contribute to `tns-core-modules` and using an external NS Angular app to develop / test these contributions, the compile step fails when following the instructions currently outlined in [DevelopmentWorkflow.md](https://github.com/NativeScript/NativeScript/blob/master/DevelopmentWorkflow.md#running-another-app) (Running Another App).\r\n\r\n**To Reproduce**\r\n``` bash\r\ngit clone git@github.com:NativeScript/NativeScript.git\r\ncd NativeScript\r\ntns create blank-ng --template tns-template-blank-ng\r\ncd blank ng\r\nnpm install ../tns-core-modules --save\r\ntns run ios # or tns run android\r\n```\r\n\r\n**Expected behavior**\r\nApplication should run successfully but instead generates the following log https://gist.github.com/rynop/5156d00932b17937cc8889f2a0581f03\r\n\r\n**Additional context**\r\n@bundyo discovered a [workaround](https://github.com/NativeScript/nativescript-dev-webpack/issues/1044#issuecomment-533397897):\r\n\r\n\u003e The problem with linking is that Angular/TS project tend to grab the linked TS files in core modules and try to compile them without the references needed. I've only managed to run it by compiling the core modules with outDir and linking that (.d.ts, package.json and other files, except TS ones should be copied over too). Maybe the team can consider moving to an outDir compilation. Another way would be dev-webpack to forbid Angular/ts-loader for traversing node_modules.\r\n\r\nBut as noted by @MartoYankov [here](https://github.com/NativeScript/NativeScript/pull/7861#issuecomment-535801655):\r\n\u003e @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.\r\n\u003e \r\n\u003e 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.\r\n\r\nSo addressing this issue is two-fold:\r\n- Update dev workflow to require `tns-platform-declarations` as a dev dependency in the Angular app in this scenario (alongside with a references.d.ts in the app root)\r\n- Address the remaining errors that the Angular compiler produces with types and exports\r\n\r\n","author":{"url":"https://github.com/manoldonev","@type":"Person","name":"manoldonev"},"datePublished":"2019-10-04T14:57:50.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/7905/NativeScript/issues/7905"}