Strange error printing

[1000camels]

I am now getting this strange error:

[CLI:lib/pdf] generating PDF using Paged.js
[CLI:lib/pdf/pagedjs] printing /Users/darcy/Dev/DAM/tokio-ueyama/_site/pdf.html
ProgressEvent: ProgressEvent
at #evaluate (file:///Users/darcy/.nvm/versions/node/v18.17.1/lib/node_modules/@thegetty/quire-cli/node_modules/puppeteer-core/lib/esm/puppeteer/common/ExecutionContext.js:249:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async ExecutionContext.evaluate (file:///Users/darcy/.nvm/versions/node/v18.17.1/lib/node_modules/@thegetty/quire-cli/node_modules/puppeteer-core/lib/esm/puppeteer/common/ExecutionContext.js:146:16)
at async Printer.render (file:///Users/darcy/.nvm/versions/node/v18.17.1/lib/node_modules/@thegetty/quire-cli/node_modules/pagedjs-cli/src/printer.js:202:4)
at async Printer.pdf (file:///Users/darcy/.nvm/versions/node/v18.17.1/lib/node_modules/@thegetty/quire-cli/node_modules/pagedjs-cli/src/printer.js:270:14)
at async default (file:///Users/darcy/.nvm/versions/node/v18.17.1/lib/node_modules/@thegetty/quire-cli/src/lib/pdf/paged.js:59:18)
at async file:///Users/darcy/.nvm/versions/node/v18.17.1/lib/node_modules/@thegetty/quire-cli/src/lib/pdf/index.js:40:12
at async Command.action (file:///Users/darcy/.nvm/versions/node/v18.17.1/lib/node_modules/@thegetty/quire-cli/src/commands/pdf.js:54:5)

I am not even sure what kind of error it is or how to approach resolving it.

Any help is appreciated.

[1000camels]

Using the same node on another project, I do not encounter the error.

[Erin-Cecele]

Do you receive a similar error if you run quire pdf --lib prince

[Erin-Cecele]

@cbutcosk Is this an error you have come across in your PDF work?

[cbutcosk]

@Erin-Cecele Not specifically, but it looks similar to what I've seen happen when 11ty swallows errors from the PDF css compile, missing figure image assets (#845), and other kinds of build-time errors that aren't yet escalated to a real build error...

@1000camels The quick fix: npm install bulma --save-dev and create an empty file at content/_assets/styles/custom.css.

The long reasoning: Apologies for taking the liberty of cloning your repo and building it locally, but I can reproduce your issue when I do that. If you load _site/pdf.html in your project directory with a browser set to allow file-to-file access (Chrome allows this with the --allow-file-access-from-files flag, Safari with a Developer Flag), you'll see the pdf.css file is not loading (among others, but I suspect that's what matters the most to this issue).

Anyway the PDF manually compiles the SCSS files at content/_assets/fonts/index.scss, content/_assets/styles/application.scss, and appends content/_assets/styles/custom.css to make that pdf.css file -- if you run sass content/_assets/styles/application.scss test.css it's erroring out because bulma isn't in the repo and that custom file is missing (or just point it to your SCSS file by tweaking the lines at the end of _plugins/transform/outputs/write.js.

[cbutcosk]

Forgot to mention -- you'll probably want to manually delete the contents of public/ and .11ty-vite/ in addition to running quire clean after you fix the issues to clear intermediate build products.

[Erin-Cecele]

Greatly appreciate your PDF expertise @cbutcosk! Thank you!

[1000camels]

thank you @cbutcosk
Unfortunately, this does not solve my problem.

To begin with, I am still getting that error after installing bulma and creating the empty styles/custom.css. Interestingly, I do not use styles/custom.css because I have created my own styles/custom.scss so I can use SASS

I also do not have the .11ty-vite/ directory

I am also unable to build getting this error:

[11ty] ENOTEMPTY: directory not empty, rename '/Users/darcy/Dev/DAM/tokio-ueyama/.11ty-vite' -> '_site' (via Error)
2024-06-07T00:32:26.657Z Eleventy:EleventyErrorHandler (error stack): Error: ENOTEMPTY: directory not empty, rename '/Users/darcy/Dev/DAM/tokio-ueyama/.11ty-vite' -> '_site'
at async Object.rename (node:internal/fs/promises:779:10)
at async EleventyVite.runBuild (/Users/darcy/Dev/DAM/tokio-ueyama/node_modules/@11ty/eleventy-plugin-vite/EleventyVite.js:74:7)
at async AsyncEventEmitter. (/Users/darcy/Dev/DAM/tokio-ueyama/node_modules/@11ty/eleventy-plugin-vite/.eleventy.js:55:5)
at async Promise.all (index 1)
at async Eleventy.executeBuild (/Users/darcy/Dev/DAM/tokio-ueyama/node_modules/@11ty/eleventy/src/Eleventy.js:1209:7)

I have tried deleting _site before re-running the build process

The build does finish if i use quire build --debug

[1000camels]

I deleted node_modules and rebuilt everything and I am still getting this error

[cbutcosk]

@1000camels Your publication has other issues causing the builds to break + error but the PDF is successfully generated and has the correct content as far as I can tell in my exceedingly brief look into it.

[1000camels]

I sorted out my issue, and I had many. All related to my scss version of custom. Because I had it loaded from index.js like application.scss, I had to include various includes in the scss.

Thanks for the help

[Erin-Cecele]

Hi, @1000camels, I'm so glad you were able to sort this out!! It might be worth opening an issue to address the lack of clear error messaging output by the Quire CLI.