-
Notifications
You must be signed in to change notification settings - Fork 12k
@ngtools/webpack fails when using "*" as tsconfig paths alias #3441
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
Comments
Just ran into this and was having issues all day with it. Ended up getting things working by changing my |
Closing as outdated. If this still happens, please let me know. |
Hey filipesilva, this still does occur and there's an open pull request that should fix the issue, but hasn't been reviewed yet. |
@chrisfitz thanks for letting me know, that Pr is still awaiting review. I'll reopen this. |
I'm having the same issue with the EDIT: just saw the 1.3.0 release. It fixes the issue on my side... sorry 😊 |
Fixed by #7250. |
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. |
Uh oh!
There was an error while loading. Please reload this page.
OS?
macOS Sierra
Versions.
angular-cli: 1.0.0-beta.22-1
node: 6.6.0
os: darwin x64
@ngtools/webpack: 1.1.9
Repro steps.
ng new project
src/tsconfig.json
and add the following tocompilerOptions
:The log given by the failure.
Mention any other details that might be useful.
node_modules
directory as an alternative, theng serve
command will hang and become unresponsive.Using this:
Results with webpack hanging with this output:
However, occasionally I'll get a memory error:
@ngtools/webpack
in a custom webpack configuration with the same results.tsc
to compile the project works as expected.The text was updated successfully, but these errors were encountered: