Nikolas LeBlanc

@GiuseppePiscopo, do any of your other templateUrls have this issue, or is it specific to these two templateUrls, or do you only have two components? It would be good if...

Are you using the latest versions of angular2-template-loader and awesome-typescript-loader? If not, you may need the config settings that were removed in this commit: https://github.com/TheLarkInn/angular2-template-loader/commit/beb5b95b7c8e9e6085ee1b663c63e3548ec52897#diff-04c6e90faac2675aa89e2176d2eec7d8L65

Sure if you've got one handy. Sorry, got swamped.

http://stackoverflow.com/questions/42816079/webpack-is-not-resolving-extensions-from-third-party-libraries/42817176#42817176 Been there, gave you a response in SO.

Wow, really? @TheLarkInn, does that even make sense? :) On Tue, Nov 8, 2016 at 10:33 AM ryan [email protected] wrote: > moving angular2-template-loader before awesome-typescript-loader works > for me when...

To be honest I just put it there based on what my reference had had. Not partial to it. On Sun, Jun 11, 2017, 1:36 AM Binoy, wrote: > *@binoy14*...

Awesome I can fix that up for you tomorrow morning if you like, applying your recommendations. And sure, I'm up for that change about web-watch - we should probably add...

Repositories.js ``` openPage(url) { this.props.navigator.push({ component: WebComponent, title: 'Web view', passProps: { source: { uri: url } } }); } ``` WebComponent.js ``` class WebComponent extends React.Component { render() {...

I had the same issue until I noticed that my GitHub Action extension wasn't logged into my GitHub account. Then it was fine.