Mjml: -bash: mjml: command not found

[ssosina]

So I'm following the MJML documentation for basic installation. I successfully install. I run npm list in my project folder and MJML appears there.

However, when I run mjml -v the following error appears
-bash: mjml: command not found

Terminal output for when I run which Node
/usr/local/bin/node

Content of my .bashrc is empty at the moment. I previously added export PATH="$PATH:./node_modules/.bin" but this made no difference.

Using a Macbook air, High Sierra and Terminal.

[iRyusa]

Hi @ssosina

Weird, looks like a path issue. If you do a ./node_modules/.bin/mjml -V what does it return ?

edited: typos

[ssosina]

Thanks for the quick reply.

This is what I get
-bash: ./node_modules/.bin: No such file or directory

I uninstalled and attempted to reinstall. It doesn't load the node module files into the folder :/

[iRyusa]

Well did you done a folder like workspace and npm init inside it ?

Then you can do an npm install mjml and it should work in this folder.

(I think in recent npm release, you no longer need to npm init)

[ssosina]

Thats the first thing I usally do @iRyusa

Steps:

1. Created new folder on desktop test-email
2. Ran npm init
3. Ran npm install mjml
4. Ran npm list – I can see mjml and all it dependencies.
5. I can node modules folder now
6. Ran mjml -v result is -bash: mjml: command not found
7. Ran ./node_modules/.bin mjml -V result is -bash: ./node_modules/.bin: is a directory

Do I create .bash_profile or .bashrc on my platform?

[iRyusa]

You're missing a / in /node_modules/.bin/mjml

Can you echo $PATH too to check if the PATH is ok ?

Edit: my bad, i did a typo in my original reply fixed it

[ssosina]

I should have picked up on that.

Right it shows the version now –

Locals-MacBook-Air:test-email user$ ./node_modules/.bin/mjml -V
3.3.5

This is what I get when i get echo the path:

Locals-MacBook-Air:test-email user$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin

[iRyusa]

I think it's a .bash_profile in OSX but I'm not 100% sure about it

[ssosina]

@iRyusa Hmm. I added it to a bash_profile instead. even tried with bashr yet no difference.

check this out.

Locals-MacBook-Air:test-email user$ mjml -v
-bash: mjml: command not found
Locals-MacBook-Air:test-email user$ ./node_modules/.bin/mjml -V
3.3.5
Locals-MacBook-Air:test-email user$ 

[iRyusa]

Can you echo $PATH again to see if the path is ok

I now advise to follow the npm-exec path like this https://stackoverflow.com/questions/9679932/how-to-use-package-installed-locally-in-node-modules to avoid some kind of nasty package that could replace a common cmd line

[ssosina]

Sure, see below.

Locals-Air:test-email user$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:./node_modules/.bin

[iRyusa]

So

$ pwd
$ ls
$ echo $PATH 
$ mjml -V

In order to double check everything ? :)

[ssosina]

Locals-Air:~ user$ cd desktop
Locals-Air:desktop user$ cd fs-email
Locals-Air:test-email user$ pwd
/Users/user/desktop/test-email
Locals-Air:test-email user$ ls
test.html       index.html  node_modules
test.mjml       index.mjml  package.json
Locals-Air:test-email user$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
Locals-Air:test-email user$ mjml -v
-bash: mjml: command not found
Locals-Air:test-email user$ 

[iRyusa]

Yeah so your $PATH isn't updated, I don't know why it doesn't read your bashrc/bashprofile and there's not really much we can do about this :/

Sorry, but I'm closing the issue.

[TidyIQ]

Same issue here. Did you ever get this fixed?

[iRyusa]

If you've installed it locally just use npm-exec mjml or yarn mjml it's
now the safest way to use cli binary

On Wed, May 29, 2019 at 2:47 AM TidyIQ [e-mail] wrote:

Same issue here. Did you ever get this fixed?

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/mjmlio/mjml/issues/885?email_source=notifications&email_token=AAELHTOVDUORW7YJU775FRTPXXHCBA5CNFSM4EDYV6AKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWN22PA#issuecomment-496741692,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAELHTOR26JOOJZVKKY7AP3PXXHCBANCNFSM4EDYV6AA
.

[kostimarko]

I too had this issue. Running mjml input.mjml -o output.html doesn't work.

However, in my package.json adding a command like "compile":"mjml input.mjml -o output.html" works

[e10a]

However, in my package.json adding a command like "compile":"mjml input.mjml -o output.html" works

@kostimarko this worked for me, thanks for this!

[sasha150187]

I too had this issue. Running mjml input.mjml -o output.html doesn't work.

However, in my package.json adding a command like "compile":"mjml input.mjml -o output.html" works

Hello, Kosti. Can you tell where exactly you put this command in package.jason ?

[probablyabear]

@sasha150187 From what it sounds like, I have a similar setup to @kostimarko. Put the script in the scripts section of package.json.

It'd look something like this:

// package.json
...
"scripts": {
    "start": // some other script,
    "compile": mjml input.mjml -o output.html
}
...

[iRyusa]

Newer npm comes with npx, so you should be able to do npx mjml too

[kostimarko]

@sasha150187 From what it sounds like, I have a similar setup to @kostimarko. Put the script in the scripts section of package.json.

It'd look something like this:

// package.json
...
"scripts": {
    "start": // some other script,
    "compile": mjml input.mjml -o output.html
}
...

@probablyabear you got to it before me :)