-
Notifications
You must be signed in to change notification settings - Fork 25.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ngc's flatModuleOutFile does not emit metadata on windows #15192
Comments
File name needed to be normalized before comparison when using synthetic file names. Fixes angular#15192
I reproduced the error and have a fix PR out to fix the Windows issue. I also sent a PR for changes I would recommend to your library setup. The attached repository doesn't quite work as you are obscuring the |
…ar#15215) File name needed to be normalized before comparison when using synthetic file names. Fixes angular#15192 PR Close angular#15215
…ar#15215) File name needed to be normalized before comparison when using synthetic file names. Fixes angular#15192 PR Close angular#15215
…ar#15215) File name needed to be normalized before comparison when using synthetic file names. Fixes angular#15192 PR Close angular#15215
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
I'm submitting a ... (check one with "x")
Current behavior
Compiling using
ngc
and withflatModuleOutFile
does not produce a*.metadata.json
file on Windows.Expected behavior
*.metadata.json
file should be produced on all platforms.Minimal reproduction of the problem with instructions
On a OSX machine, there will be a
out-tsc/index.metadata.json
. On Windows, this file will not be present.What is the motivation / use case for changing the behavior?
ngc
should work on Windows.Please tell us about your environment:
Windows 10, VS Code, npm@4.0.5, node@7.4.0, typescript@2.2.1
Language: [ TypeScript 2.2 ]
Node (for AoT issues):
node --version
= 7.4.0The text was updated successfully, but these errors were encountered: