Why is my deployed project ui different to my local ui?
When i deploy to railway for some reason one of the components width is reduced? its smaller than it is when doing wasp start locally
14 Replies
Hi @ArDev. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Hmm, I don't know enough to give you a confident answer yet. The issue you're experiencing could be due to a variety of factors, such as differences in environment configurations between your local setup and the deployment environment, or specific CSS that behaves differently in different environments.
However, without more specific information, it's hard to provide a definitive answer. I would recommend checking your environment configurations and also reviewing your CSS to see if there might be any environment-specific styles that could be causing this issue.
For more information on deploying with Wasp, you can check out the Wasp deployment documentation (https://wasp-lang.dev/docs/advanced/deployment/manually#updates--redeploying).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @ArDev, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
Hmmm, so the difference is that your app goes through the build process, and something must have changed there. I believe we had sometihng about this in the past, with the stitches. I tihnk @miho or @matijash might remember what was it and have idea about this also?
In the meantime @ArDev , can you provide more info? Wasp version, and which component is it?
i am on the latest wasp version (although not the latest opensaas version) and the component is the landingpage component
it seems to work fine on mobile though
and wasp start works fine (on pc) but deploying does not
i have modified the landingpage styling slightly though, but it seems to work fine when doing wasp start like i said
actually i think it seems everything is kinda zoomed out?
i zoomed in (on brave) and then it shows expected behaviour
from 100% to 150%
Hey @ArDev, can you maybe share your app (or a part of it that reproduces the error) and we can check it out
the full app?
Ideally only a subset that successfully reproduces an error. If you can't find that, then the full app.
its not an error, its just every single component is zoomed out
would it be to do with my css file?
like i said it only does this when deploying to railway
Please share some code we can use to reproduce it
@ArDev Just to rule it out: Most browsers safe your zoom level per host. So maybe you are zoomed in on localhost or zoomed out on the production environment? hit cmd+0 (ctrl+0 on windows) to make sure you are on 100% on both devices. And did you check whether the issue occurs on different browsers and devices (different pc) as you said on mobile its working just fine.
yes this is zoomed out on different browsers
@sodic @miho this issue is universal wherever i deploy
just did it on railway & netlify
is there any hacky solutions i could do?
@ArDev can you share the code with us? You said you changed the landing page slightly. Can you tell us which changes os we can replicate them? Or send us over the code files.
should i send app.tsx? because its affecting every component which app.tsx renders everything
ok ill try find the changes that replicates the issue
Hard for me to say, if you think app.tsx is the cause then yes!
That would be perfect.
Hey @ArDev, like I said here: without the code, we can't do much