Add _index.scss resolution when using @import on a directory

[mattpilott]

I have hit a point where this would be really useful for myself and the team. Take a look at sass/sass#690

Theres a fair bit of discussion resolving with the addition of this feature, I am wondering if this is on the radar and when it will be available.

Thanks!

[nschonni]

The support has landed in libsass with sass/libsass@3af837c but won't be available here till the next libsass tagged release is brought into node-sass

[mattpilott]

Any timescales on that @nschonni ?

[oqx]

Seconding @matt3224 here. Is there a timeline on this feature?

[nschonni]

Libsass was bumped in 4.9 9d6faf6 so this should be available

[nschonni]

Actually doesn't look like it was https://github.com/sass/node-sass/blob/master/src/libsass/src/file.cpp

[Chlebamaticon]

It still doesn't work. :(

I've generated angular project with @angular/cli@6.0.8 and dependency that's responsible for compiling whole project(@angular-devkit/build-angular@~0.6.8) is using node-sass@4.9.1. As far as I know it's also compiling all the .sass files within application.

To the point, am receving such error after attempting to import file called '_index.scss' from directory 'src/styles'.

@import './styles';
^
      File to import not found or unreadable: ./styles.
      in /Users/<user>/Projects/<name>/src/index.scss (line 2, column 1)

[moraveyo]

Doesn't work for me too. (
And the doc says it's already there: https://sass-lang.com/documentation/file.SASS_REFERENCE.html#index_files

I invented this hack:
Instead of index.scss or _index.scss I make a _.scss.

For exapmle block/_.scss

Then I import like that:
@import "block/";
Everything works fine, although syntax check of my IDE is not very happy.

[mattfelten]

I'm looking for this too. Just tested the current version of node-sass to see if it's updated in 4.11, but it's not yet. https://github.com/mattfelten/node-sass-index-test

[mattfelten]

Just looked into this more. Looks like libsass has the change required in 3.6, but that hasn't been released yet. Looks like we're waiting for 3.6 to be released first.

sass/libsass#2772 (comment) says it'll be released around Xmas, so converting from internet time, we'll have this feature by June.

[PolyPik]

libsass 3.6 got released just under a week ago.

How fast can we release a new version of node-sass that uses libsass 3.6?

[xzyfer]

It'll be a couple weeks..it's a complicated process and I'm off on vacation till the end of June.

…

On Fri., 24 May 2019, 4:34 am PolyPik, ***@***.***> wrote: libsass 3.6 <https://github.com/sass/libsass/releases/tag/3.6.0> got released just under a week ago. How fast can we release a new version of node-sass that uses libsass 3.6? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2339?email_source=notifications&email_token=AAENSWDKVVHQXRGXYBLPF43PW3PSNA5CNFSM4E3WV7XKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWDDI6Q#issuecomment-495334522>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAENSWBDQETGJXL7DMTKUF3PW3PSNANCNFSM4E3WV7XA> .