Server/browser state transfer not working

[that70schris]

here's a page as an example: https://staging.stilt.com/about

here's some package.json:

    "@angular-builders/custom-webpack": "8.4.1",
    "@angular-devkit/build-angular": "0.803.25",
    "@angular/animations": "8.2.14",
    "@angular/cdk": "8.2.3",
    "@angular/cli": "8.3.25",
    "@angular/common": "8.2.14",
    "@angular/compiler": "8.2.14",
    "@angular/compiler-cli": "8.2.14",
    "@angular/core": "8.2.14",
    "@angular/forms": "8.2.14",
    "@angular/material": "8.2.3",
    "@angular/platform-browser": "8.2.14",
    "@angular/platform-browser-dynamic": "8.2.14",
    "@angular/platform-server": "8.2.14",
    "@angular/router": "8.2.14",
    "@builder.io/angular": "1.0.82",
    "@nguniversal/express-engine": "8.2.6",
    "@nguniversal/module-map-ngfactory-loader": "8.2.6",
    "@sentry/browser": "5.12.1",
    "@types/node": "13.7.0",
    "@types/segment-analytics": "0.0.32",
    "angular2-text-mask": "9.0.0",
    "core-js": "3.6.4",
    "crypto-js": "3.1.9-1",
    "express": "4.17.1",
    "fs-extra": "8.1.0",
    "hammerjs": "2.0.8",
    "lodash.mergewith": "4.6.2",
    "lodash.pick": "4.4.0",
    "mock-express-request": "0.2.2",
    "mock-express-response": "0.2.2",
    "newrelic": "6.3.0",
    "nginx-conf": "1.5.0",
    "ngx-cookie": "4.1.2",
    "ngx-uploader": "8.0.0",
    "node-sass": "4.13.1",
    "numeral": "2.0.6",
    "request-promise": "4.2.5",
    "robotstxt-webpack-plugin": "7.0.0",
    "rxjs": "6.5.4",
    "sitemap": "5.1.0",
    "text-mask-addons": "3.8.0",
    "tlds": "1.207.0",
    "ts-md5": "1.2.7",
    "ts-node": "8.6.2",
    "typescript": "<3.5",
    "typescript-require": "0.2.10",
    "webpack-merge": "4.2.2",
    "zone.js": "0.10.2"

let me know if you need anything else

[steve8708]

@that70schris we're having trouble reproducing, can you add any other info?

also note there is one Builder content API request that always happens on the client and hydrates the DOM in the latest versions. this is to enrich for anything dynamic like interactivity, lazy loaded images, etc (in case that is what you are seeing and expecting that to not be there)

[that70schris]

oh, maybe that's what's causing the flash of content. If you try visiting the example page, you should see it do a full refresh

[steve8708]

oh a flash of content is definitely no good. I'm not seeing a flash on that link tho, but I do see images pop in when they load

[that70schris]

hmm, you're right, seems like it might've be fixed

[steve8708]

ah yes - flashing was definitely an issue at one point, so may have just been that one version but you are passed it now. will close out, and thanks for reporting @that70schris !