Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 23 08:49
    cospin commented #554
  • Sep 09 14:17
    qroac commented #1182
  • Sep 08 20:05
    OsamaKhan220 opened #1209
  • Aug 11 17:44

    dependabot[bot] on npm_and_yarn

    (compare)

  • Aug 11 17:44
    dependabot[bot] closed #1167
  • Aug 11 17:44
    dependabot[bot] commented #1167
  • Aug 11 17:44
    dependabot[bot] labeled #1208
  • Aug 11 17:44
    dependabot[bot] opened #1208
  • Aug 11 17:44

    dependabot[bot] on npm_and_yarn

    Bump serialize-javascript from … (compare)

  • Aug 07 06:32

    larixer on java-server

    (compare)

  • Aug 07 06:32

    larixer on change-sign-in-flow

    (compare)

  • Aug 07 06:32

    larixer on expo-google-authorization

    (compare)

  • Aug 07 06:32

    larixer on add-material-ui

    (compare)

  • Aug 07 06:31

    dependabot[bot] on npm_and_yarn

    (compare)

  • Aug 07 06:31
    dependabot[bot] commented #1205
  • Aug 07 06:31
    larixer closed #1205
  • Aug 07 06:30

    larixer on docker-upgrade

    (compare)

  • Aug 07 06:30

    larixer on eslint-for-typescript

    (compare)

  • Aug 07 06:30

    larixer on expo-35

    (compare)

  • Aug 06 17:07

    larixer on yarn-plugins

    (compare)

bmoffitt1990
@bmoffitt1990
How would I know if its fixed though if it is supposed to happen on dev
Victor Vlasenko
@larixer
You fix it in dev mode first and then you check the prod
On dev the CSS styles are flickering - its another problem
styles flickering is not related to your problem
bmoffitt1990
@bmoffitt1990
ohhhh i see what you mean
okay I have it working on yarn start again
Victor Vlasenko
@larixer
I suspect you have a problem with your components not rendering on the server
bmoffitt1990
@bmoffitt1990
jus needed to run yarn watch and then re-do the build
Victor Vlasenko
@larixer
well, some of them
bmoffitt1990
@bmoffitt1990
so now the flickering component is back while in yarn start
Victor Vlasenko
@larixer
do not mix yarn watch and yarn build
if you do yarn watch, do not do yarn build
bmoffitt1990
@bmoffitt1990
well i did yarn watch first to remove the build, then I did yarn build & yarn start
Victor Vlasenko
@larixer
yarn build is needed only to check how it will work in prod

well i did yarn watch first to remove the build, then I did yarn build & yarn start

okay, but yarn watch is not needed, yarn build will clear build folder itself

bmoffitt1990
@bmoffitt1990
ahhhh okay
So now that its loading, you want me to disable JS through the console?
Victor Vlasenko
@larixer
yes
after you disable JS and refresh the page, does your page looks right?
bmoffitt1990
@bmoffitt1990
no
actually wait
Ignore the 404, that was intended behavior
I am on a route that is set up, I dont get a 404, but the page does not look right
no warnings in the console
bmoffitt1990
@bmoffitt1990
Okay so I think im getting closer to the problem
I had added a bunch of state to the PageLayout component (mostly due to the hack I had put together). When I comment out all the state, it loads just fine and I can click all the links and the flickering does not occur
Victor Vlasenko
@larixer
Now you know how to debug that :)
Just turn off JavaScript! :)
bmoffitt1990
@bmoffitt1990
So what exactly does this tell me?
all of the state I had was the problem?
I guess I dont understand the implications of turning off JS
Victor Vlasenko
@larixer
Your page is rendered twice
bmoffitt1990
@bmoffitt1990
I am a materials engineer by trade, forgive me lol
Victor Vlasenko
@larixer
The first time it is rendered on the server
The second time it is render in the users browser
If during the first render on the server your component will not be rendered - user will see it as blank first and then when JS kicks-in it will render it properly, but the user will see it as flickering
If you don’t want server to render anything at all, turn off server-side rendering
The kit supports both working with SSR and without SSR
bmoffitt1990
@bmoffitt1990
ahhhh okay. By disabling JS, and running from yarn start, I am testing the SSR?
Victor Vlasenko
@larixer
yes!
bmoffitt1990
@bmoffitt1990
which renders the component completely fine right now
I guess what I dont understand is that with the component rendering right now from yarn start, it would seem that the SSR is working just fine.
Victor Vlasenko
@larixer

. By disabling JS, and running from yarn start, I am testing the SSR

yarn start is unelated, yarn start just launches production server (which need to be built first)
you can disable JS with yarn watch, e.g. dev mode

bmoffitt1990
@bmoffitt1990
gotcha
okay so when i had SSR enabled, and was running with yarn start, the flickering still happened occasionally. I disabled SRR and re-built and havent seen it happen yet
nvm just saw it happen again lol
definitely not as much though
bmoffitt1990
@bmoffitt1990
It shouldn't happen at all though, right? Or will there always be edge cases
Victor Vlasenko
@larixer
ideally it shouldn’t happen, but you need to write code very carefully in order to achieve that