fix(resolver): sass files resolution

[ematipico]

Changes

Closes #15897

I applied a custom resolver solely for CSS files.

Testing

Added a new test

Docs

N/A

[changeset-bot]

🦋 Changeset detected

Latest commit: ff685f2

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[codspeed-hq]

Merging this PR will not alter performance

✅ 18 untouched benchmarks

---

_{Comparing fix/sass-resolverr (ff685f2) with main (07c1002)}

[ematipico]

The CI fails for all runners, but locally this doesn't. I am investigating why

[pkg-pr-new]

astro

npm i https://pkg.pr.new/astro@15899

create-astro

npm i https://pkg.pr.new/create-astro@15899

@astrojs/cloudflare

npm i https://pkg.pr.new/@astrojs/cloudflare@15899

@astrojs/preact

npm i https://pkg.pr.new/@astrojs/preact@15899

@astrojs/check

npm i https://pkg.pr.new/@astrojs/check@15899

@astrojs/language-server

npm i https://pkg.pr.new/@astrojs/language-server@15899

astro-vscode

npm i https://pkg.pr.new/astro-vscode@15899

commit: 217e900

[james-yeoman]

What seems weird is that it seems to pass perfectly fine when using the match option.

cd packages/astro
pnpm test:match tsconfig

passes for both dev and build for the alias-tsconfig test, but

cd packages/astro
pnpm test:integration

passes only on dev, and fails at build for the alias-tsconfig test

tests failing.

[matthewp]

Tests failing are legit, those are testing behavior using tsconfig aliases. Not sure exactly why the change breaks them in CI but not locally.

[james-yeoman]

It failed locally for me though. That was the point of my comment