Skip to content

Conversation

hansl
Copy link
Contributor

@hansl hansl commented Dec 8, 2017

Previously we filtered our path mapping resolver to only be used on typescript.
The correct behaviour is unclear; tsc does not resolve JS files, only TS. But
there is a lot of value to use path mapping to resolve JavaScript files, and
it replaces the webpack alias configuration option. Because of that value it
was decided to fix this.

Fixes #8117.

Previously we filtered our path mapping resolver to only be used on typescript.
The correct behaviour is unclear; tsc does not resolve JS files, only TS. But
there is a lot of value to use path mapping to resolve JavaScript files, and
it replaces the webpack alias configuration option. Because of that value it
was decided to fix this.

Fixes angular#8117.
@Brocco Brocco merged commit eb4c9e7 into angular:master Dec 13, 2017
@hansl hansl deleted the fix-path-mapping-again branch November 28, 2018 23:35
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

tsconfig paths not respected
4 participants