Rob Bearman

@rbox-risk Here is what I'm doing that is successful against the current `core` branch. In `next.config.js` ``` const remarkMath = require('remark-math'); const rehypeKatex = require('rehype-katex'); const withNextra = require('nextra')({ theme:...

Confirmed the same on the latest `core`.

> does this work with yarn? @Subham-Maity I have not built with yarn, only pnpm, but if the project has otherwise been working for you with yarn, I don't see...

> I think for this to land, we need to find a way to inject the KaTeX CSS dynamically instead of relying on a CDN. @shuding I replaced the CDN...

> Someone is attempting to deploy a commit to a Personal Account owned by @shuding on [Vercel](https://vercel.com/). @shuding first needs to [authorize it](https://vercel.com/git/authorize?type=github&job=%7B%22headInfo%22%3A%7B%22sha%22%3A%226e6c90b7c5bbeb09402b207a7558621ccdad3271%22%7D%2C%22id%22%3A%22QmXpdk5BjsfeShmE3uPmj6FNNrrkvcZBoimbpMGp4ZywMu%22%2C%22org%22%3A%22shuding%22%2C%22prId%22%3A978%2C%22repo%22%3A%22nextra%22%7D). This sounds scary, and was most likely...

@imranbarbhuiya I'm curious - if you manually redeploy and choose to ignore the build cache, does your deployment succeed? This is assuming your local builds succeed on a fresh clone.

> disabling caching worked That's what I suspected. Vercel's build cache has been a problem for our deployments, too, with problems ranging from build failures as you've observed, to changes...