You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Ryan, Nikhil, and everyone else who's been putting in the amazing work into solid start (and the web at large haha)! 👋
When importing static assets, for example, import Img from "~/test.png";, the default export of this appears to be incorrect when server rendering this string, resulting in a 404 for the browser.
Client side rendering (with { start: { ssr: false } }) appears to get this src attribute correct with a /_build/@fs prefixed url that does not 404. I didn't try client side navigation within an SSRed app, but my suspicion is that it works since the client bundles are probably working the same in that case.
Also note that using hand-crafted, "public" urls from the vite /public directory appears to be work in both modes, unsurprisingly.
Expected behavior 🤔
Both server and client bundles should have same default export strings.
Steps to reproduce 🕹
Minimal reproduction (this is my app.jsx file in a "bare" start setup) and { start: { ssr: true } } in vite.config.js
Duplicates
Latest version
Current behavior 😯
Hi Ryan, Nikhil, and everyone else who's been putting in the amazing work into solid start (and the web at large haha)! 👋
When importing static assets, for example,
import Img from "~/test.png";
, the default export of this appears to be incorrect when server rendering this string, resulting in a 404 for the browser.Example server output:
Client side rendering (with
{ start: { ssr: false } }
) appears to get thissrc
attribute correct with a/_build/@fs
prefixed url that does not 404. I didn't try client side navigation within an SSRed app, but my suspicion is that it works since the client bundles are probably working the same in that case.Also note that using hand-crafted, "public" urls from the vite
/public
directory appears to be work in both modes, unsurprisingly.Expected behavior 🤔
Both server and client bundles should have same default export strings.
Steps to reproduce 🕹
Minimal reproduction (this is my
app.jsx
file in a "bare" start setup) and{ start: { ssr: true } }
invite.config.js
Context 🔦
No response
Your environment 🌎
The text was updated successfully, but these errors were encountered: