vite:css and postcss creating errors on SSR ?

10:56:50 PM [vite] Internal server error: Attempted to assign to readonly property.
Plugin: vite:css
File: /workspaces/motu/node_modules/@solidjs/start/shared/dev-overlay/styles.css
at <anonymous> (/workspaces/motu/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:38958:18)
at processTicksAndRejections (:13:78)
38953 | }
38954 | catch (e) {
38955 | e.message = `[postcss] ${e.message}`;
38956 | e.code = code;
38957 | e.loc = {
38958 | column: e.column,
^
TypeError: Attempted to assign to readonly property.
10:56:50 PM [vite] Internal server error: Attempted to assign to readonly property.
Plugin: vite:css
File: /workspaces/motu/node_modules/@solidjs/start/shared/dev-overlay/styles.css
at <anonymous> (/workspaces/motu/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:38958:18)
at processTicksAndRejections (:13:78)
38953 | }
38954 | catch (e) {
38955 | e.message = `[postcss] ${e.message}`;
38956 | e.code = code;
38957 | e.loc = {
38958 | column: e.column,
^
TypeError: Attempted to assign to readonly property.
Hi, I'm trying to start my solid-start project on another compute but I can't get it to work. I get this weird postcss error during SSR. And I'm using Devcontainers to reproduce my development environment, so I'm even more dazzled that it works on one compute and not on the other lol. Anyone has ever seen this error ?
1 Reply
Cyber Grandma
Cyber GrandmaOP10mo ago
Okay, I've forcefully removed all node_modules on my "working" computer and reinstalled all deps, and now it doesn't there either lol. So some dependency update caused this.
Want results from more Discord servers?
Add your server