JS API tests for loading multiple nested paths with renderSync

[Goodwine]

Issue: sass/dart-sass#1962

[skip sass-embedded]

See: sass/embedded-host-node#226

[nex3]

What parameters are actually passed to the importer in plain Dart Sass versus the embedded host?

[Goodwine]

What parameters are actually passed to the importer in plain Dart Sass versus the embedded host?

I'm not 100% sure if this is what you're referring to, but:

dart-sass importer

console.log
  ## DEBUG: url= ./foo/_a.scss - prev: /home/goodwine/repos/sass-spec/spec/sandbox/9067981249289676/src/index.scss
console.log
  ## DEBUG: url= ./foo/_a.scss - prev: /home/goodwine/repos/sass-spec/spec/sandbox/9067981249289676/src/_includes.scss
console.log
  ## DEBUG: url= ./foo/_b.scss - prev: /home/goodwine/repos/sass-spec/spec/sandbox/9067981249289676/src/_includes.scss

embedded importer

console.log
  ## DEBUG: url= foo/_a.scss - prev: /home/goodwine/repos/sass-spec/spec/sandbox/308212682427188/src/index.scss
console.log
  ## DEBUG: url= file:///home/goodwine/repos/sass-spec/spec/sandbox/308212682427188/src/foo/_b.scss - prev: /home/goodwine/repos/sass-spec/spec/sandbox/308212682427188/src/_includes.scss
<crash>

I looked at the implementations, and dart-sass seems to just call the importer without trying to do much wrapping, but embedded-host-node has some fancier wrapping and I think that's where it goes "wrong"

Like if I implement a "modern" importer using compile() instead of renderSync() I would have to implement a correct canonalize() and I would realize that the input Sass is kinda wrong 🤔