Inconsistent "Relative imports outside of src/" restriction ?

[hugomallet]

Is this a bug report?

Maybe not

Which terms did you search for in User Guide?

This is related to my previous answer : #1333 (comment)

Steps to Reproduce

I have a projet which imports an other "private" package. I am using sass in both packages. The private package is passed to babel only (not node-sass).

I have something like the following in the private module :

// src/component/module.js

import '../styles/module.scss';

// src/styles/module.scss

.module {
    background: url('../images/module.jpg');
}

Then in the main project, if i do this :

// src/index.js

import '@my/module/dist/component/module.js';

everything works fine, but if i do "the same thing" from my sass file :

// src/main.scss

@import '@my/module/dist/styles/module.scss';

i obtain the following error :

Module not found: You attempted to import ../images/module.jpg which falls outside of the project src/ directory. Relative imports outside of src/ are not supported.

Expected Behavior

Both import should fail or success ?

To be able to split my project, i would like to be able to import other packages components and sass files.

Actual Behavior

Importing from sass from sass fails but importing sass from js works.

[hugomallet]

Ok finally the issue is different.

The problem is :

• if imported from javascript, "url()" in sass file are relative to the imported module
• if imported directly from sass, "url()" in sass file are relative to the main package

Both pass through webpack so the behaviour should be the same ?

[Timer]

One is detecting the symlink and the other is not, we'll need to look into this.

[bugzpodder]

Do you need the tilda, ie
@import '~@my/module/dist/styles/module.scss';

[hugomallet]

@bugzpodder, It does not seem to work.

[stale]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

[stale]

This issue has been automatically closed because it has not had any recent activity. If you have a question or comment, please open a new issue.

[jackwilsdon]

It looks like this is a case of "Problems with url(...)", as sass-loader does not resolve paths in urls. It appears that #5829 may fix this, however it seems to have some other issues at the moment when resolving paths.