Open Readf0x opened 1 year ago
:wave: Thanks for the report, this looks like a bug on our side. I've now added it to our internal tracker.
:wave: Thanks for the report, this looks like a bug on our side. I've now added it to our internal tracker.
Sorry about the lack of professionalism, I was extremely annoyed at the time of posting :P
The issue still happens. For me, it happens basically whenever I do anything with Sveltekit on StackBlitz at some point, and from then on it's impossible to get it to work again.
Reproduction page: https://stackblitz.com/edit/sveltejs-kit-template-default-36pavj?file=package.json
@jrvidal any news about the internal issue?
Describe the bug
Very often when I'm using stackblitz, I'll make a change to my code that will create an error. Oh well, no biggie, vite will let me just undo the change and, wait what do you mean vite crashed? That's not supposed to happen. So I check the error log and I see:
Right now, I'm encountering this error whenever I edit a specific css file. Since I'm currently working on the slowest laptop known to man, it can take upwards of 20s to restart the vite server, and css is something I have to edit quite frequently.
I really couldn't tell you why this happens, but it is a frequent occurrence. It also occurs when you go to a route that doesn't exist without a dynamic route error handler.
Link to the blitz that caused the error
https://stackblitz.com/github/Readf0x/site-rewrite/tree/d0bc67bf20e7ecafb65b320965cdf20bc36ebdf2?file=src%2Flib%2Fprism%2Fcatppuccin.css
Steps to reproduce
In the preview, navigate to the "/about" route (accessible navbar, hamburger menu if preview has small width, or direct url) Edit css file Upon attempt to reload page, vite will crash with
Error: `line` must be greater than 0 (lines start at line 1)
Expected behavior
Vite should not crash in this instance, it should at worst return with a 500 internal server error.
Parity with Local
Screenshots
No response
Platform
Additional context
The exact line I'm editing is line 35. There is a 100% chance of this error occurring when changing the rule name from "overflow-x" to "overflow".