Open fsecada01 opened 4 years ago
As I'm digging through this more, it seems like there are three issues:
1) the subprocess
run command needs the shell=True
argument to run the list of line command components.
2) The NPM modules are out of date/non-existent
3) Foundation Email requires Node v10; newer versions (like 12) are not compatible with the CLI.
Is it possible to build nvm or anything into this module?
The workaround I have right now is to install and work with Foundation Email via the Sass and node.js method directly. I had to utilize npx
to run Node as v10. These were the commands that ultimately worked for me.
npm install -g foundation-cli
npx -p node@10 foundation new --framework emails
ren at the prompt, write in the name of the project. For this demo, I chose Emails
cd Emails
npx -p node@10 foundation watch
Trying to install foundation emails directly w/o Node v.10 causes issues with certain previously-native packages like primordial
. This seems like the best workaround.
It seems likely that one of the requirements via the identified command list from
DEF_NODE_PACKAGES_REQUIRED
is faulty. I got the following printout when trying to run npm directly from my chosen node modules directory.