Question: checking for all `[deps]` in `docs/Project.toml` about literate.jl HOT 5 CLOSED

Do you have a link to an example CI run where you had this failure?

from literate.jl.

This happens to me very often so it was easy to make an example:
JeffFessler/book-la-demo#12
github says it "passes" but the actual build is full of errors due to the missing package.

from literate.jl.

The build on that PR was a success though? It does have heaps of warnings in the logs, but they're warnings, not errors. If you want them to be errors, you need to set strict = true in makedocs.

from literate.jl.

Interesting. I had not noticed that those were mere warnings because they are filled with serious sounding words like failed and ArgumentError and UndefVarError.
I guess I expected that an omitted deps would be an actual error, not just a warning.

I had studied the Literate docs pretty carefully, but I had overlooked the (apparently experimental) keyword option strict = true in the Documenter docs for makedocs.
Thanks for letting me know about that!
I added it and now things fail/work as expected. I'll close this issue.
Hopefully the dialogue here will help someone else in the future.
Thanks much!

from literate.jl.

Is there a way to make my local test more faithful to the cloud environment so that if I am missing a deps entry then it will fail locally? I've tried JULIA_LOAD_PATH=docs/Project.toml:@StdLib but that just caused many seemingly unrelated errors.

Setting the load path should work, if you make sure the only entry is the docs/Project.toml environment. What unrelated errors did you see?

from literate.jl.