Does Angular Cli 6 support @import ~ anymore?

I just create a brand new app with angular cli 6. I tried use do

@import '~styles/variables';

But I got file not found error.

Here is my code:

https://stackblitz.com/github/dereklin/myng6app?file=src%2Fapp%2Fapp.component.scss

Is @import ~ no longer supported?

Rename the file from "/src/styles/_variables.scss" to "/src/styles/variables.scss"

"import" is part of typescript and angular 6 implements typescript

That's interesting. While stackblitz appears to work, running ng serve locally still produces the same error after change the file name:

ERROR in ./src/app/app.component.scss
Module build failed: 
@import '~styles/variables';
^
      File to import not found or unreadable: ~styles/variables.
      in /Users/delin/sandbox/myng6app/src/app/app.component.scss (line 1, column 1)
ℹ ｢wdm｣: Failed to compile.

Here is my repo: https://github.com/dereklin/myng6app

On another note, stackblitz seems to cache my old app. When I do https://stackblitz.com/github/dereklin/myng6app, I can still see _variables.scss instead of the newly named variable.scss.

But I really think _variables.scss is the right file name since they are partials and I don't want sass to compile them: https://kolosek.com/sass-import/

Change the app.component.scss to

@import '../../styles/variables

and name the variables file as "_variables.scss"

But that's relative import. My original question is regarding the support of @import ~. It used to work before my upgrading to Angular 6. Some claim it's still working (storybookjs/storybook#3814). I want to find out if it's indeed supported still.

Did you find the way how to solve the issue?

The usage of the tilde was/is not officially supported and is actual an artifact of the internal implementation of the build system. While it may currently work in certain situations, it is not guaranteed to continue to function in the future. In the style use cases outlined above, a relative path or the use of the includePaths option (more details) is recommended.

@clydin

@clydin Is this a change of stance? On #9166 and #9184 (back in January), you noted that this syntax being unsupported was a defect. It also appears that there are unit tests in 6.0.x that check if tilde imports work.

Has something changed in policy?

EDIT: For what it's worth, I'm seeing the same behavior in a fresh v6 project using LESS, so the symptom isn't unique to SCSS.

The Angular Material documentation contained a usage of the tilde and to prevent wide spread breakage a set of tests for a limited usage of the tilde were added at that time. These tests were carried over into 6.x to attempt to ease transition. However, there is currently not a guarantee that the tilde will continue to function (even in the tested limited capacity) moving into the future.

@clydin

@clydin I see. Given that this functionality happens to work sometimes (despite not being intentionally supported), what sort of work do you think it would take to make it intentionally supported? I'd be interested in taking a stab at it if it's not too hairy. It's quite a handy thing to have, after all.

@NickLanam

@NickLanam I've proposed an idea that may solve this issue in #12573. Let me know if that would handle your use-case, especially if @clydin is unwilling to commit to supporting ~ this may be a feasible alternative.

@damienwebdev

@damienwebdev That proposal would add a fair bit of flexibility, but I'm not sure that it achieves the same use case. In the issue here, a working implementation avoids the need for manually specifying where to find each thing. It defaults to finding node_modules (no matter how deep in the tree the file you're working on might be).

In my case (Angular 7):

angular.json

"projects": {
    "MyProject": {
      "sourceRoot": "src"
}}

styles.scss
@import "assets/css/variables.scss";

What about server side applications?

In my angular.json file, adding:

"stylePreprocessorOptions": {
							"includePaths": [
								"src/styles"
							]
						},

to the architect.build.options seems to work, but it fails with ng run myapplication:server:dev.

Do I have to add it also in architect.server.options?

In my case ~src label doesn't work only for SSR, because I can't define assets in options of the server scheme:

"assets": [
   "src/assets"
]

When I try to do so I get an error:

Schema validation failed with the following errors:
  Data path "" should NOT have additional properties(assets).

stylePreprocessorOptions > includePaths working though...

"@angular-devkit/build-angular": "^0.13.9"
"@angular/cli": "^7.3.9"

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.}

Navigation Menu

Repository navigation

Does Angular Cli 6 support @import ~ anymore? #11435

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Does Angular Cli 6 support @import ~ anymore? #11435

Description

Activity

LeoUrzua commented on Jul 3, 2018

dereklin commented on Jul 3, 2018

LeoUrzua commented on Jul 3, 2018

dereklin commented on Jul 3, 2018

VitalDoVilmate commented on Jul 3, 2018

clydin commented on Jul 3, 2018

NickLanam commented on Jul 9, 2018

clydin commented on Jul 9, 2018

NickLanam commented on Jul 9, 2018

damienwebdev commented on Oct 12, 2018

NickLanam commented on Oct 12, 2018

Albejr commented on Dec 8, 2018

rtyx commented on May 23, 2019

ViieeS commented on Jun 7, 2019

angular-automatic-lock-bot commented on Sep 9, 2019

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions