All of which seem to allow for that Node version 6.9.4 as they should. Can anyone shed some light on what might be at issue here? I’m not too familiar with this process so any advice is appreciated.
Hey @Chris_H - it looks like the version it’s trying to use is actually 6.9.2, not 6.9.4, which is why it doesn’t meet the requirement specified. Perhaps their container only installs 6.9.2? In that case, you would need to modify your container setup to install a newer version of node.
You’d do that by adding this to your container’s build commands:
If that doesn’t fetch a new enough version of the 6.x branch for some reason, you can hop up to 8.x by changing the 6 in the URL above to an 8 (that’s what I have for my Sage 8 and Sage 9 containers).
Correct me if I’m wrong, but don’t these commands perform the same function? I’m curious why you’ve got the overhead of installing and running yarn if you’re going to use npm.
Yeah, I really don’t know. Someone else actually wrote these commands and I don’t know enough to change them. My understanding is that they are similar but not exactly the same so I didn’t want to mess with them. Are they likely doing the same thing?
As for the Node version, I added those lines directly above the npm i and the script ran successfully. Thanks again @mmirus!
So far as I know they’re identical: They install dependencies from your package.json. I’ve used them interchangeably many times. I’m not an expert on the differences between yarn and npm, but for what your script appears to be doing (install dependencies, run two scripts) I don’t think you’d even need yarn; npm can do both of those things.