You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 1, 2019. It is now read-only.
Looks like there is a pretty major issue for windows environment: awesome-typescript-loader skips output emitted by typescript. This occured due to incorrect behavior of isFileEmit function in helpers.ts. I see the following code there
In my case fileName is C:\MyFolder\MyFile while sourceFileName is c:\MyFolder\MyFile. As consequence awesome loader thinks that there was no emit for this file. Probably here should be case insensetive comparison for windows environment.
I used v3.0.0-beta.17 version
The text was updated successfully, but these errors were encountered:
@kkovalevskiy what the version of nodejs do you use? there was an issue on Windows for node 6.3 and lower. (see nodejs/node#6624 for details). If I am not mistaken it was fixed in 6.4
I checked the latest version of node and looks like all work fine on 6.9.4. Maybe this should be added to docs (that loader is working on specific versions of nodejs on Windows)? Or maybe it's better to make it work on versions before 6.9.4 (or 6.4)?
Hello!
Looks like there is a pretty major issue for windows environment: awesome-typescript-loader skips output emitted by typescript. This occured due to incorrect behavior of
isFileEmit
function inhelpers.ts
. I see the following code thereIn my case
fileName
isC:\MyFolder\MyFile
whilesourceFileName
isc:\MyFolder\MyFile
. As consequence awesome loader thinks that there was no emit for this file. Probably here should be case insensetive comparison for windows environment.I used v3.0.0-beta.17 version
The text was updated successfully, but these errors were encountered: