Projects with the sass-embedded package DO NOT WORK on Stackblitz & bolt.new

[AssetKid]

Describe the bug

NOTE: The sass package works just fine but it is much slower.

---

When you install the sass-embedded package in a project, the preview STOPS WORKING on Stackblitz & bolt.new.

sass-embedded is the recommended package in a Vue + Vite project with scss code. In fact, the error dialog tells you to install it.

Link to the blitz that caused the error

https://stackblitz.com/edit/vue-zmgbb8ai

Steps to reproduce

1. Open linked blitz and start the dev server.
2. Focus on the preview section.

Expected behavior

The preview section should display the page.

Parity with Local

• I have run the project in my local machine and I could not reproduce the issue.

Screenshots

Terminal error related to sass-embedded

Components that use scss (App.vue in this case) are stuck on pending. All other components load just fine.

Platform

Browser name  = Chrome
Full version  = 138.0.0.0
Major version = 138
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 77112809,
  "usedJSHeapSize": 70825793,
  "jsHeapSizeLimit": 4294705152
}
Hash = 96435430

Additional context

I first encountered this issue on bolt.new. The AI installed sass-embedded when I asked it to migrate the styles to scss and the preview section stopped working immediately.

I spent a substantial amount of tokens trying to debug this issue thinking it was a project issue. I am sure so many other people have wasted their bolt.new tokens doing the same.

The sass-embedded package is the recommended package so that is what the AI installs when you ask it to use scss.

[GodLyons]

I've had the same problem

[Kerate]

Yes, I've had the same problem using the default Quasar/CLI project. It works fine on Stackblitz but not on Bolt. I spent hours and a lot of tokens writing prompts, uploading known working projects without success.

Good to know it's not just me, but now finding a workaround is going to be painful.