-
Notifications
You must be signed in to change notification settings - Fork 12k
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
No support for Webpack resolve.alias #5287
Comments
Seems it has nothing to do with #5031. The issue definitely with WebPack config. I've looked through the sources, cli doesn't add resolve.alias in Webpack config. See here, it adds node_modules path only. Seems we need to expand angular-cli config for aliases. WDYT guys? |
There was already discussion(#1465) regarding expending of angular-cli config and implementing this feature. |
Dupe of #5031, I will followup to your question there. |
Could we reopen this for support for Sass? There doesn't seem to currently be a way to alias CSS... |
As @thomaswmanion said, the alias for sass is not working. This is how my path looks like now when I try to import the global |
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. |
Hello,
It's a copy of issue #5031, it was closed as already implemented but I couldn't manage to make it work.
Steps to reproduce:
I've added this to my tsconfig.json:
Path to the constants file:
src/app/shared/constants/index.ts
When I import it as usual
import { testConst } from './shared/constants/index';
, it works fine:But when I use absolute path, it crashes:
import { testConst } from 'shared/constants/index';
Webpack error:
Could someone confirm that this feature works? Does it need additional config?
The text was updated successfully, but these errors were encountered: