-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve message for error "Nesting selectors can only be used inside a rule" #12208
Comments
Which bundler are you using where this error appears like this? Using Vite I get the info where things are (rather; I got them until recently, there's a pending issue where v-p-s adjusts the stack in a way that makes it impossible for Vite to do the right thing; update: it's a bug in vite-plugin-inspect, so unrelated) |
Hello, sir! Indeed, this is (or was, I suppose) with Vite v5. I didn't get the culprit in the message. :-( Could it be because of the pending thing you mentioned? |
I realized that this is a bug in |
I understand. Not sure about what to tell you. I'm not using I guess I can try to reproduce again. Let me locate the commit that fixes this and see if I can revert. |
@dummdidumm I reverted the CSS change and tested with next.166, which is the one I was using when I reported this. It is showing up now. Unsure what was going on back then. This part was missing when I reported:
Since then, newer Svelte's show even a preview of the code, so I guess we can forget about this one. I'm closing. Thanks for looking into it. |
Describe the problem
The problem is the current state of the error. I just started a Svelte v5 branch for a large component library. I installed Svelte v5 and compiled. The error that I get is this:
And what's the problem? That it doesn't say which file is the one with the problem. The stack trace doesn't contain it because logically, the file is not being executed. It is therefore a needed piece of information in the error message.
Describe the proposed solution
Include the problematic file in the error message:
Importance
would make my life easier
UPDATE
Since I have dozens of files and zero clue about the one error'ing out, I'm very tempted to say that I the importance of this could be upgrated to "cannot use Svelte without this".
The text was updated successfully, but these errors were encountered: