Preview error related to index.md

[Erin-Cecele]

Thank you @Erin-Cecele That worked! I can create a new project and run a preview. However, once I start working on my project, I edit all the info and I run a preview again to see the changes, I get this error:

[CLI] running eleventy using lib/11ty cli
[CLI:11ty] running eleventy serve
[quire] DEBUG Figures:ImageProcessor
inputRoot: /Users/v-federici/parasoleprintmaking/content/_assets/images
outputRoot: /Users/v-federici/parasoleprintmaking/_site

[quire] INFO Figures Processing complete
WARNING: mixed-decls deprecation is obsolete. If you were previously silencing it, your code may now behave in unexpected ways.

WARNING: mixed-decls deprecation is obsolete. If you were previously silencing it, your code may now behave in unexpected ways.

WARNING: mixed-decls deprecation is obsolete. If you were previously silencing it, your code may now behave in unexpected ways.

[11ty] Problem writing Eleventy templates:
[11ty] 1. Having trouble writing to "./_site/index.html" from "./content/index.md" (via EleventyTemplateError)
[11ty] 2. Transform pdf encountered an error when transforming ./content/index.md. (via EleventyTransformError)
[11ty] 3. Cannot read properties of null (reading '1') (via TypeError)
[11ty]
[11ty] Original error stack trace: TypeError: Cannot read properties of null (reading '1')
[11ty] at file:///Users/v-federici/parasoleprintmaking/_plugins/transforms/outputs/pdf/transform.js:145:83
[11ty] at Proxy.forEach ()
[11ty] at trimLeadingSeparator (file:///Users/v-federici/parasoleprintmaking/_plugins/transforms/outputs/pdf/transform.js:144:62)
[11ty] at Object.default (file:///Users/v-federici/parasoleprintmaking/_plugins/transforms/outputs/pdf/transform.js:257:3)
[11ty] at Object. (file:///Users/v-federici/parasoleprintmaking/_plugins/transforms/outputs/index.js:24:16)
[11ty] at Object.fn (file:///Users/v-federici/parasoleprintmaking/node_modules/@11ty/eleventy/src/Benchmark/BenchmarkGroup.js:37:23)
[11ty] at TransformsUtil.runAll (file:///Users/v-federici/parasoleprintmaking/node_modules/@11ty/eleventy/src/Util/TransformsUtil.js:37:30)
[11ty] at async #renderPageEntryWithLayoutsAndTransforms (file:///Users/v-federici/parasoleprintmaking/node_modules/@11ty/eleventy/src/Template.js:927:13)
[11ty] at async Template.generateMapEntry (file:///Users/v-federici/parasoleprintmaking/node_modules/@11ty/eleventy/src/Template.js:959:15)
[11ty] at async Promise.all (index 10)
[11ty] Benchmark 137ms 11% 8× (Configuration) "epub" Transform
[11ty] Copied 7 Wrote 4 files in 1.21 seconds (303.6ms each, v3.1.0)
[11ty] Eleventy Fatal Error (CLI):
[11ty] 1. Having trouble writing to "./_site/index.html" from "./content/index.md" (via EleventyTemplateError)
[11ty] 2. Transform pdf encountered an error when transforming ./content/index.md. (via EleventyTransformError)
[11ty] 3. Cannot read properties of null (reading '1') (via TypeError)
[11ty]
[11ty] Original error stack trace: TypeError: Cannot read properties of null (reading '1')
[11ty] at file:///Users/v-federici/parasoleprintmaking/_plugins/transforms/outputs/pdf/transform.js:145:83
[11ty] at Proxy.forEach ()
[11ty] at trimLeadingSeparator (file:///Users/v-federici/parasoleprintmaking/_plugins/transforms/outputs/pdf/transform.js:144:62)
[11ty] at Object.default (file:///Users/v-federici/parasoleprintmaking/_plugins/transforms/outputs/pdf/transform.js:257:3)
[11ty] at Object. (file:///Users/v-federici/parasoleprintmaking/_plugins/transforms/outputs/index.js:24:16)
[11ty] at Object.fn (file:///Users/v-federici/parasoleprintmaking/node_modules/@11ty/eleventy/src/Benchmark/BenchmarkGroup.js:37:23)
[11ty] at TransformsUtil.runAll (file:///Users/v-federici/parasoleprintmaking/node_modules/@11ty/eleventy/src/Util/TransformsUtil.js:37:30)
[11ty] at async #renderPageEntryWithLayoutsAndTransforms (file:///Users/v-federici/parasoleprintmaking/node_modules/@11ty/eleventy/src/Template.js:927:13)
[11ty] at async Template.generateMapEntry (file:///Users/v-federici/parasoleprintmaking/node_modules/@11ty/eleventy/src/Template.js:959:15)
[11ty] at async Promise.all (index 10)

---

I can see in Visual Studio Code that once Quire creates index.html, the file does not contain the info that I entered in index.md...

Not sure what to do, by all the index related files show some differences with previous projects'.
For instance, in the image attached, on the left, you have the new project's (just created) index.js in the markdown (plugins) section, where all the initial lines start with "import"(and then the plugins' names); on the right, you see the same file from another project, created before this whole issue started, and the plugins lines start with "const".

Originally posted by @MultimedialitySummerSchool in #1049 (reply in thread)

[Erin-Cecele]

Hi @MultimedialitySummerSchool - reading this error message, it appears there is an issue with your index.md file that may be related to images. Did you make recent changes to either the images or that file? Is there a shortcode or a reference to an image in the index.md file?

[Erin-Cecele]

One "best practice" that I like to recommend is only making a handful of changes before previewing. That will help narrow down the particular change that may have broken the preview. The more work you do before previewing, the harder it can be to pinpoint the breaking point. Preview often is my advice.

[MultimedialitySummerSchool]

Thank you Erin for following up on this and for creating a new discussion for this issue.

The error appears even when I only change the title of the publication in the publication.yaml file, right after creating a new project and launching a preview to make sure everything works.

The main issue seems to be that when Quire creates a new project, it generates a different cmd file in the eleventy directory. Unlike all the previously working projects, which use a cmd.js file, the new project has a cmd.cjs file. See screenshot:

I'm not sure how the cmd.cjs file relates to the failure to generate the index-related files in a newly created project, but I came to this conclusion by reading the error message and comparing the eleventy directory to those in working projects.

As a workaround, I've been duplicating a working project and using that as the basis for a new one (for now).

[Erin-Cecele]

@MultimedialitySummerSchool Thanks for doing such a deep dive into the code. We really appreciate that level of detail. That said, sometimes the Terminal output provides more information than is necessary to diagnose the issue and turns out to be a distraction. It's possible that the inconsistency in file names is indicative of a larger issue, but we should start troubleshooting at a higher level and rule out other potential causes first.

Unfortunately, I am not able to recreate your issue. When I start a new project on rc-33/node 22 and change the title in the publication.yaml, I am still able to preview just fine, which leaves me a bit in the dark as to what could be going wrong.

I just want to double-check, did you make any changes to the page YAML (see below) in the index.md file (especially to the image field)? Or did you possibly delete the spiral-overlay.png image from the _assets/images folder?

---
title: Cover
layout: cover
order: 1
menu: false
toc: false
image: spiral-overlay.png
---

If the answers to the above inquiries are no, can you create an organizational account in GitHub, add your repo to it, and add both Greg and me as collaborators? Here is more information: https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/about-organizations. If I am added as a collaborator, then I can clone (copy) your project and take a look around at what might be breaking the preview. Let me know if that is possible. Otherwise, I suggest hopping on a call and screensharing!

[Erin-Cecele]

Hi @MultimedialitySummerSchool Thank you for sharing your project repo notaries with me. I'm able to preview with no issues. It's looking fantastic!

[Erin-Cecele]

Similar to discussion #1058, we chalked this up to permissions errors related to @MultimedialitySummerSchool's system, which is why I was able to preview without an issue.