Preview error

[fullerpault]

I've been wanting to try out Quire for some time and I've finally gotten around to it (yay!). Unfortunately, I'm running into issues getting the preview command to work. Here's the output I've been getting:

Any suggestions for troubleshooting?

[Erin-Cecele]

Hi @fullerpault, did you receive this error message when you previewed for the first time? Or have you made changes to your project? If it's the latter, what kind of changes have you made?

[Erin-Cecele]

@fullerpault disregard my last message, I see you have made updates and changes, including adding IIIF images to your project. I think the issuse may be the the image id. Per our documentation, "the id can be anything as long as it starts with a letter, is all lowercase, and uses dashes instead of spaces." It looks like your id starts with a number. Can you double-check and try amending it so it starts with a letter instead? For example, fig-789-iiif.

If that doesn't work, can you please run the command quire info --debug and let us know what the output is? That will help us do some testing on our end.

Thank you!

[fullerpault]

Thanks @Erin-Cecele! Missed that part of the documentation, apologies! Unfortunately, I renamed the figure id but ran into an error again. Here's that output:

Here's the output from quire info --debug:

[Erin-Cecele]

Hi @fullerpault, you are running an outdated version of Quire. Try updating your project by following these instructions: https://quire.getty.edu/docs-v1/install-uninstall/#update-an-existing-project. You can also try installing a slightly older version of Node. Either 18.20.8 or 20.19.4 should work.

[fullerpault]

Hey @Erin-Cecele, that's super weird! I downloaded Quire earlier this week. Trying to update didn't work, and I also even just tried to uninstall with npm uninstall --global @thegetty/quire-cli and reinstall entirely. Still got the same error, and running quire info --debug shows the same output as before.

Is there a chance I'm somehow downloading an older version unintentionally? I'm on a Windows 11 machine and have tried using both Powershell and Git Bash (in VS Code terminal).

[Erin-Cecele]

We have been working on a number of improvements for Windows users. There is a new version of Quire that has not been officially released, as we are still doing testing. But you can give it a try. Install with this command: npm install -g @thegetty/quire-cli@1.0.0-rc.32

[fullerpault]

Bummer - even when uninstalling and running that I'm not able to get things going. I'm sure it's mostly on my end, but I'm not entirely sure what I'd have to do to make it work. I'm happy to keep testing things out for you if that's helpful, but I can also just keep an eye out for a new release (while seeing if I can find a Mac I can use in the meantime). Thanks for all of your help!

[Erin-Cecele]

My apologies, @fullerpault, I provided the wrong install command. Here is the correct one: quire new my-project --quire-version 1.0.0-rc.32. This will start a new project that incorporates the aforementioned latest updates (including Windows-specific fixes). You can then move content from your original project into this one. I recommend making small batches of changes and then re-previewing. This will help narrow down the source, just in case the break is caused by something other than the file names not starting with a letter.

If, after trying the latest version, you continue to encounter errors/issues, please share the complete terminal output.

[fullerpault]

Hi @Erin-Cecele, here's the terminal output after trying that command. Let me know if there's anything else I should try (happy to also chat elsewhere if that's easier).

[Erin-Cecele]

Hi @fullerpault Let's try one last thing. I just encountered this error message in a project I was working on yesterday. I resolved it by running the command npm install and then previewing again. If that still doesn't work, let us know if you would like to hop on a call to troubleshoot in real-time.

[fullerpault]

Thanks @Erin-Cecele! Unfortunately, that didn't seem to work either - here's the output. I'm super appreciative of all of your help so far. Thanks for offering to hop on a call, that'd be great! Let me know the best way to schedule that.