No node in conda environment

[brian-rose]

Potentially closes #593 and gets builds working again

[github-actions]

👋 Thanks for opening this PR! The Cookbook will be automatically built with GitHub Actions. To see the status of your deployment, click below.
🔍 Git commit SHA: 683ce98
✅ Deployment Preview URL: https://ProjectPythia.github.io/pythia-foundations/_preview/594

[kafitzgerald]

Seems to be working again with this change.

Did you figure out what was causing the older version of node to get installed? Just curious in case this needs to be updated elsewhere.

For instance, I think we have this specified in all or most of the cookbook envs. Though interestingly at least this one seems fine: https://github.com/ProjectPythia/advanced-viz-cookbook/actions/workflows/nightly-build.yaml

[brian-rose]

@kafitzgerald I'm not sure. I checked the Cookbook Template repo. nodejs is not listed in its environment file, but does get installed (presumably as a conda-forge-defined dependency of mystmd, e.g. here in this build log.

[brian-rose]

In this most recent failed build log for Foundations, a much older version of nodejs was installed (12.4.0)

Different versions of nodejs and mystmd seem to be installed in different cookbook builds, and I'm currently very confused about it.

[brian-rose]

I'll merge this now so the broken builds aren't holding up other work on Foundations, but it would be good to understand the issue better.

[kafitzgerald]

Yeah, I'm not quite sure what is going on either w/ the builds on this repo (the specification of nodejs isn't needed anymore, but also shouldn't have been breaking anything).

This seems like a reasonable change though and I did verify that mystmd does have an explicit nodejs dependency on conda-forge.