We're going to revert the fix for production so your doc is correct, but this change should have been made backwards compatible in view of live production services that it ended up breaking.
The test app also fails deployment in the same way:
> @cerc-io/test-progressive-web-app@0.1.43 cerc_compile
> next experimental-compile
⨯ Invalid project directory provided, no such…One problem is that the test app we used to verify this fix is not using the right version of next:
$ npm list next
@cerc-io/test-progressive-web-app@0.1.42 /home/david/projects/cerc/test-…Investigating this a bit, I noticed that the test-pwa project specifies "latest" for next, and yarn why reports the version used as 14.2.5.
When that project is deployed the deployer runs the…
Re-test fails:
Request ID:bafyreick3n5eqqd5aa7r4tn52nnvbal6on2p6gfcmqu36xpoxwhsevs2oe
Application:crn://snowballtools/applications/pwa-nextjs-app-router@0.0.1
Last Update:2024-07-26T23:07…Thanks. I suspect the current display is not handling multi-host-name scenarios.
Hi, can you expand a bit on what the bug is? E.g. expected 'this' but got 'this' ? Thanks.
This turns out to only affect web app config (environment variables). The app code itself is not stale. The cause is a bug in nextjs -- it has a scheme for generating file names from the hash of…
Expected outcome:
I deploy a new version of my webapp -> users of that webapp get the new version without needing to do anything unusual like open an incognito window.
Actual outcome:
That…