CRAN litedown + plus me being a fool + general confusion

[TimTaylor]

I updated some of the documentation in one of my packages today and there seems to be an issue with the rendering of its vignette on CRAN (e.g. odd data frame rendering and ggplot plot internals being displayed) . Initially I thought it was due to an error on my part where I managed to modify the VignetteBuilder entry to read

`VignetteBuilder: litedown, knitr

instead of

`VignetteBuilder: litedown`

However upon inspecting the resulting source I noticed that the generator tag says

<meta name="generator" content="litedown 0.4">

This is the CRAN rendered vignette:
https://cran.r-project.org/web/packages/grates/vignettes/grates.html

and this is how it looks on the litedown generated site using litedown 0.61:
https://www.reconverse.org/grates/doc/grates.html

So I tried installing litedown 0.4 to see if I could recreate the rendering issues. Whilst I could see the js assets were missing I was unable to create the odd display of the evaluated R code (both data frames and plots).

Do you have any idea what could be going on here?

I've emailed CRAN to see if they would allow me to submit a hotfix but that was when I thought the issue was my VignetteBuilder entry but now I'm not so sure.

In case relevant here's the vignette source https://github.com/reconverse/grates/blob/main/pkg/vignettes/grates.Rmd.

Apologies for the rambling nature of the post I'm just at a loss 😕

[yihui]

Hmm, that's very odd. The VignetteBuilder entry should be irrelevant. I'm not sure about the reason for the weird output, but the generator tag should be correct about the litedown version at the time of R CMD build. The only possibility I could think of is the chunk option print = NA. It was probably used against xfun < v0.50.

Anyway, if the latest CRAN versions of litedown and xfun work fine for the vignette, I don't know if it's still worth the time to investigate the reason (it may not be easy to figure out which old version of litedown and which old version of xfun can reproduce the problem).

[TimTaylor]

Oh - I think this is my fault 🤦 I've been able to recreate. I ran Rdevel CMD build with an old xfun/litedown combo. Annoyingly I have a script that keeps my Rdevel build up to date but forgot to update the installed packages afterwards 😢 . Will add that to the update script now it's bitten me.

Sorry for the noise.

[yihui]

No worries!