Skip to content
This repository was archived by the owner on Apr 8, 2020. It is now read-only.

[Question/Bug] NodeServices[0] [fail] ts-loader: Using typescript@1.8.10 and c:\**\**\tsconfig.json #231

Closed
baserz opened this issue Jul 31, 2016 · 5 comments

Comments

@baserz
Copy link

baserz commented Jul 31, 2016

Hi folks
I got an issue in an app im building and im unsure exactly what caused it. When running it in Kestrel, the first line that appears is an error: "NodeServices[0] [fail] ts-loader: Using typescript@1.8.10 and c:__\tsconfig.json" and thats it. The application then works fine, both prerender and client render. But i realized that this breaks azure publishing through visual studio for example.

I first assumed it was some of my code, but i couldnt locate anything. So i checkedout an old branch which i previously deployed successfully to azure -> same error. So i created a new empty project and pasted the samplecode from the sampleproject (yo aspnetcore-spa angular2) and got the exact same error. Running the sample project worked however.

Now im starting to suspect if it perhaps is something that is broken after i updated visual studio 2015or something. But i wanted to check if anyone here knows what this error means (it tells me absolutely nothing in regards as to what is wrong). As said everything works perfectly efter that error has passed locally.

@MarkPieszak
Copy link
Contributor

Do you have ts-loader installed in your node_modules? It's the webpack loader used to compile TS files. It's strange that it would work, but still give you an error on the kestrel & azure side.

@frankwallis
Copy link

@Baseless the message 'ts-loader: Using typescript@1.8.10 and /.../tsconfig.json' is just a normal console message which ts-loader always outputs when starting the compilation, it's not an error. Not sure why NodeServices is prefixing it with [fail]

@baserz
Copy link
Author

baserz commented Aug 1, 2016

Thanks for the input. Frank: i see the message in the older generated aspnetcore project as well (but it dont fail there). Mark: Yes i include the exact versions and dependencies specified by the generated yeoman template.

Edit: I tried getting the latest version of the yeoman template, which also gave the same error (which i saw when i removed the silent flag which is set in latest template for the ts-loader) when i added it as part of another project, but was published successfully to azure. I suppose that the reason for this silent flag is to suppress the error message that will otherwise give an exception during publishing? Will try on my initial project.

Tanks for the input sofar guys.

@nil4
Copy link

nil4 commented Aug 1, 2016

TypeStrong/ts-loader#249 explains why Using typescript@ is seen as an error: it is printed to stderrr instead of stdout.

@baserz
Copy link
Author

baserz commented Aug 1, 2016

This is solved. It was enough to add the flag for silent ts-loader (thus avoiding the compile exception) and it seems to work nu. The strange thing is how this worked before without this flag. I know i ran some updates for vs, but strange if that would have affected it.
Summarized: quite illogical to output information messages as errors. A bit confusing to us with limited experience of webpack.

ANYWAY seems like the thread that nil4 provided link with covers this and after adding the silent trigger it works so i thank you for the input and go ahead and close this.

@baserz baserz closed this as completed Aug 1, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants