Open cderv opened 1 month ago
And it seems we also have another copy of the dependency in .quarto
project hidden folder
❯ grep -2 "revealjs[.]com" .\.quarto\_freeze\site_libs\revealjs\dist\reveal.js
/*!
* reveal.js 4.3.1
* https://revealjs.com
* MIT licensed
*
Not sure how it behave when new updated quarto with new revealjs update is used. 🤔
I'll try to build an easier example to investigate all this...
I'll try to build an easier example to investigate all this...
right now I can't reproduce on a simple website... It happens only inside quarto-web
I wouldn't touch the freeze implementation without a longer discussion with @jjallaire and @dragonstyle; there's a lot of corner cases involved.
Observed behavior
I was testing
revealjs/update-v5
branch in dev quarto-cli to render our demo slides at https://quarto.org/docs/presentations/revealjs/demo/This new branch is using revealjs 5.1.0 and I would have expected this to be used.
Dependency in
site_libs
was updatedBut freezer is still using old version
which implies that with
freeze: true
in our quarto-web project when doingthe freezer is used for site_libs it seems, and the old revealjs is used... After
quarto render
I getback to old one.
If I delete the file, then the new version is put in freezer.
So I believe this is a conflict similar to our "different themes in websites", but when using freeze. All the revealjs presentation in the website are using same file in
site_libs/
.It seems
site_libs
in the freezer will always win. So it needs to be updated somehow.I need to understand this, and see what is the recommended way : Manuel invalidation or a fix in our site_libs handling...