Quire Commands Not Recognized

[aebancroft]

Hello! I'm trying to run Quire commands in Windows command prompt from the project directory and am getting an error:

'quire' is not recognized as an internal or external command,
operable program or batch file.

Any suggestions are much appreciated!

Thank you ---Alex

[geealbers]

Hi Alex, that's strange. You'd previously able to run Quire commands before right? Did anything change in your system recently? And if you try a Quire command (say quire --version) from a different directory, I assume you get the same message?

[aebancroft]

Correct, same error message. I've actually never run Quire commands before, but have been publishing projects successfully. Nothing has changed on my system. Should I try re-cloning the project from Git?

[geealbers]

When you say you've "been publishing projects successfully", you mean you're making changes to the Markdown and YAML files in your text editor and pushing them to GitHub, but you've never previewed them on your machine before with the quire preview command, correct? If so, the project itself should still be fine and no need to re-clone, but you need to run a fresh install of Quire itself, which is separate from the project. Instructions are here but let me know if it doesn't work or if I misunderstood something: https://quire.getty.edu/documentation/install-uninstall/.

[aebancroft]

Thanks, Greg! You were right - looks like Quire needed a fresh install. I can now run Quire commands.

Now I'm running the quire preview --verbose command and get the following:

C:\Users\ABancroft\museum-essays>quire preview --verbose
Launching preview server
i Navigate to http://localhost:1313 to see your changes.
i Press Control+C or type "quire stop" to stop the preview.
events.js:292
throw er; // Unhandled 'error' event
^

Error: spawn node_modules.bin\webpack.cmd ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
at onErrorNT (internal/child_process.js:469:16)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
Emitted 'error' event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:273:12)
at onErrorNT (internal/child_process.js:469:16)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
errno: 'ENOENT',
code: 'ENOENT',
syscall: 'spawn node_modules\.bin\webpack.cmd',
path: 'node_modules\.bin\webpack.cmd',
spawnargs: [
'--watch',
'-d',
'--progress',
'--color',
'--config',
'webpack\webpack.config.dev.js'
]
}

And http://localhost:1313/ site cannot be reached/refused to connect. Any ideas? Would it be better if I start a separate discussion topic for this?

Thanks, Greg!

[aebancroft]

Thanks, Greg! Those URL constructs are good to know. I was able to view all our essays at http://localhost:1313/contents/ except for the one we're trying to troubleshoot. Should be http://localhost:1313/paintings/sbondini-pino/. The essay is pushed to Github - https://github.com/thegetty/museum-essays/blob/stage/content/paintings/sbondini-pino.md. I've checked objects.yml, publication.yml, sbondini-pino.md header; all look ok. Any ideas?

[aebancroft]

Jen and I are both working on this essay and have both committed changes to it. We also both recently had to regenerate our Git personal access tokens. Could this have affected our ability to push changes to the museum-essays repo?

[geealbers]

I’m afraid I’m out this week so not going to be able to troubleshoot, but can look on Monday. Or if it’s something more urgent, @workergnome could maybe take a look?

[aebancroft]

I appreciate you taking a look, Greg. I'm around Monday if it's easier to have a quick Zoom call. Thank you!

[geealbers]

The answer to the original query is marked above, but just to close the loop on these other issues here for posterity, and anyone who stumbles onto this post. There were two issues at play, the first was that this particular Quire project was using the draft flag on pages, which is a Hugo feature that's not supported in Quire preview, and on the projects deploy system set up through Netlify, automated builds had been stopped unbeknownst to the project editors.