Closed scarf005 closed 2 months ago
Yes, sorry for the trouble. This is a breaking change in Lume 2.2.0, that changed the way to import LumeCMS. It's explained here: https://lume.land/blog/posts/lume-2.2.0-luisa-villalta/#cms-import-changes
The solution is to add the lume/cms/
entry to your import maps:
{
"imports": {
"lume/": "https://deno.land/x/lume@v2.2.1/",
"lume/cms/": "https://cdn.jsdelivr.net/gh/lumeland/cms@0.5.1/"
}
}
Version
2.2.1
Platform
linux
What steps will reproduce the bug?
https://github.com/lumeland/lume/assets/54838975/3797ecda-a412-4f79-a98e-722a7f86f1d0
initialize lume with default options. or:
deno cache https://deno.land/x/lume@v2.2.1/cms/adapters/lume.ts
How often does it reproduce? Is there a required condition?
always happens.
What is the expected behavior?
What do you see instead?
output.log
Additional information
No response