Dependencies cache issue on the server

[oliviertassinari]

🐛 bug report

Description of the problem

I believe there is a caching issue with the server-side containers. Running the following url https://codesandbox.io/s/github/mui-org/material-ui/tree/master/examples/nextjs should start a project with the latest version of the dependencies. It seems that it's not the case for Material-UI. From what I can observe, it pulls our v3 instead of v4.

How has this issue affected you?

The problem was reported by one of our users in mui/material-ui#16979.

Link to sandbox

• buggy: https://codesandbox.io/s/github/mui-org/material-ui/tree/master/examples/nextjs
• After forcing a fresh install of the dependencies: https://codesandbox.io/s/nextjs-6j8u7

[lbogdan]

Hey @oliviertassinari ,

I think this #2075 (comment) should maybe address your issue?

[oliviertassinari]

Ok, I think that we can try "post-update": "yarn upgrade" to workaround the limitation. Thanks

[lbogdan]

Nice! Closing this for now, please reopen if you encounter further issues. Also, for more general questions, you can open a thread on Spectrum.

[oliviertassinari]

We went for not applying this patch. The example is optimized for people starting a new project. They copy and paste the source, we shouldn't mix the concerns.

[oliviertassinari]

Is there a way to solve this problem without leaking the concern outside codesandbox?

[lbogdan]

We're always open to suggestions. 🙂

[oliviertassinari]

I was wondering, maybe we could use an env variable to conditionally apply the command?

 "scripts": {
    "dev": "next",
    "build": "next build",
-   "start": "next start"
+   "start": "next start",
+   "post-update": "[[ -n $CODESANDBOX ]] && yarn upgrade --latest"
  }
}

But then, what about Windows 🙃 cc @garethx

[lbogdan]

But post-update has no meaning outside CodeSandbox, anyway?

[oliviertassinari]

@lbogdan I didn't know that. I thought it was a npm command I wasn't aware of. I think that if it were prefixed with codesandbox-post-update, it would have been trivial to figure it out, as well for our users to feel confident removing the line once they clone the examples :).

[lbogdan]

Yeah, we modeled it after post-install, which is a npm thing, and named it post-update because it's supposed to run whenever the git repo updates. Whether we should have namespaced it with the codesandbox- prefix I think it's up for debate. 🙂

[oliviertassinari]

@garethx what do you think about reopening the pull request, for all our demos with this approach?

 "scripts": {
    "dev": "next",
    "build": "next build",
-   "start": "next start"
+   "start": "next start",
+   "post-update": "echo \"codesandbox preview only, need an update\" && yarn upgrade --latest"
  }
}

@lbogdan Thanks for the help.