Wrong version displayed on mjml --version #371
Comments
|
@yumyo Tried |
|
thank you @detj but it didn't work. I'm using mjml just as a globally installed package. As such, the folder I am working in contains just I've uninstalled it, runned My Node version was This is the output of the above install command which appears to be correct: |
|
Well all of your packages are in 2.3.2 it's ok, i think it's just an output bug |
|
I have the same issue from the It's just an output bug of number of the version or really the wrong version ? D'origine quand j'ai tapé |
|
@mdrick It's weird that you got the 2.1.1 version installed though, can you confirm it was not displaying |
|
@ngarnier I can confirm that I had I forced my update with For I can't use |
|
@mdrick Ok, that's weird for the 2.1.1 version, we'll investigate, thanks for reporting. Regarding |
|
I have same issue. It actually seems being really 2.3.1 as I still get mj-hero bug which was fixed in 2.3.3 according to changelog https://github.com/mjmlio/mjml/releases/tag/2.3.3
|
|
Still get same problem on other servers as well. Cannot update to latest mjml version. It seems this is quite important issue :) |
|
It's just an output bug from the cli. We're aware of it, and working to have a better output from |
|
Updated the title, to reflect the real problem |
|
Can you give me the result of |
|
|
You have the good version cf : |
|
it's copy/paste from your documentation which works well on your site: |
|
Strange, it renders fine for me using the NPM version
Kind Regards, :----------------------------: On 5 October 2016 at 10:37, ipa1981 notifications@github.com wrote:
|
|
I just installed MJML back, and it renders the mj-hero fine too. Maybe cleanup your npm installation ? |
|
You're right. On other server it generates good html after update. I'll clean up my machine. Thanks for help. |
|
Ok. This is really irritating. I've deleted and installed again all Node modules (incl. mjml) local and global on my machine and get the same result - Older version. While on other machines it works well. |
|
There is a global cache which may have old version sat in, try "npm cache Kind Regards, :----------------------------: On 5 October 2016 at 11:32, ipa1981 notifications@github.com wrote:
|
|
Silly me. I was solving problems with mjml on my physical machine, where mjml shouldn't even exist. And forgot that other mjml runs inside vagrant virtual box. :). Now I have the latest version. |
|
I have same issue. npm install --save mjml@2.3.3
└─┬ mjml@2.3.3
├─┬ mjml-button@2.0.10
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ ├── core-js@1.2.7
│ └─┬ isomorphic-fetch@2.2.1
│ ├─┬ node-fetch@1.6.3
│ │ └── encoding@0.1.12
│ └── whatwg-fetch@1.0.0
├─┬ mjml-cli@2.3.2
│ ├─┬ fs-promise@0.5.0
│ │ ├── any-promise@1.3.0
│ │ ├─┬ fs-extra@0.26.7
│ │ │ ├── jsonfile@2.4.0
│ │ │ └── klaw@1.3.0
│ │ ├── mz@2.4.0
│ │ └─┬ thenify-all@1.6.0
│ │ └── thenify@3.2.0
│ └─┬ glob@7.1.1
│ └── minimatch@3.0.3
├─┬ mjml-column@2.0.10
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ └── core-js@1.2.7
├─┬ mjml-container@2.0.10
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ └── core-js@1.2.7
├─┬ mjml-core@2.3.2
│ ├─┬ cheerio@0.20.0
│ │ ├─┬ css-select@1.2.0
│ │ │ ├── boolbase@1.0.0
│ │ │ ├── css-what@2.1.0
│ │ │ ├── domutils@1.5.1
│ │ │ └── nth-check@1.0.1
│ │ ├─┬ dom-serializer@0.1.0
│ │ │ └── domelementtype@1.1.3
│ │ ├── entities@1.1.1
│ │ ├─┬ htmlparser2@3.8.3
│ │ │ ├── domelementtype@1.3.0
│ │ │ ├── domhandler@2.3.0
│ │ │ ├── entities@1.0.0
│ │ │ └─┬ readable-stream@1.1.14
│ │ │ └── isarray@0.0.1
│ │ └─┬ jsdom@7.2.2
│ │ ├── acorn@2.7.0
│ │ ├── webidl-conversions@2.0.1
│ │ └── whatwg-url-compat@0.6.5
│ ├── he@1.1.0
│ ├─┬ html-minifier@3.1.0
│ │ ├─┬ change-case@3.0.0
│ │ │ ├── camel-case@3.0.0
│ │ │ ├── constant-case@2.0.0
│ │ │ ├── dot-case@2.1.0
│ │ │ ├── header-case@1.0.0
│ │ │ ├── is-lower-case@1.1.3
│ │ │ ├── is-upper-case@1.1.2
│ │ │ ├── lower-case@1.1.3
│ │ │ ├── lower-case-first@1.0.2
│ │ │ ├── no-case@2.3.0
│ │ │ ├── param-case@2.1.0
│ │ │ ├── pascal-case@2.0.0
│ │ │ ├── path-case@2.1.0
│ │ │ ├── sentence-case@2.1.0
│ │ │ ├── snake-case@2.1.0
│ │ │ ├── swap-case@1.1.2
│ │ │ ├── title-case@2.1.0
│ │ │ ├── upper-case@1.1.3
│ │ │ └── upper-case-first@1.1.2
│ │ ├─┬ clean-css@3.4.20
│ │ │ ├── commander@2.8.1
│ │ │ └── source-map@0.4.4
│ │ ├─┬ ncname@1.0.0
│ │ │ └── xml-char-classes@1.0.0
│ │ └── relateurl@0.2.7
│ ├── immutable@3.8.1
│ ├── jquery@3.1.1
│ ├─┬ js-beautify@1.6.4
│ │ └─┬ editorconfig@0.13.2
│ │ └─┬ lru-cache@3.2.0
│ │ └── pseudomap@1.0.2
│ ├─┬ react@15.3.2
│ │ └─┬ fbjs@0.8.5
│ │ └── core-js@1.2.7
│ ├── react-dom@15.3.2
│ └── warning@3.0.0
├─┬ mjml-divider@2.0.11
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ └── core-js@1.2.7
├─┬ mjml-group@2.0.4
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ └── core-js@1.2.7
├── mjml-head-attributes@2.0.7
├── mjml-head-font@2.0.1
├── mjml-head-title@2.0.1
├─┬ mjml-hero@2.0.10
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ └── core-js@1.2.7
├─┬ mjml-html@2.0.9
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ └── core-js@1.2.7
├─┬ mjml-image@2.0.10
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ └── core-js@1.2.7
├─┬ mjml-invoice@2.0.11
│ ├── numeral@1.5.3
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ └── core-js@1.2.7
├─┬ mjml-list@2.0.9
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ └── core-js@1.2.7
├─┬ mjml-location@2.0.10
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ └── core-js@1.2.7
├─┬ mjml-navbar@2.0.8
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ └── core-js@1.2.7
├─┬ mjml-raw@2.0.9
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ └── core-js@1.2.7
├─┬ mjml-section@2.0.10
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ └── core-js@1.2.7
├─┬ mjml-social@2.0.10
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ └── core-js@1.2.7
├─┬ mjml-spacer@2.0.8
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ └── core-js@1.2.7
├─┬ mjml-table@2.0.9
│ └─┬ react@15.3.2
│ └─┬ fbjs@0.8.5
│ └── core-js@1.2.7
└─┬ mjml-text@2.0.9
└─┬ react@15.3.2
└─┬ fbjs@0.8.5
└── core-js@1.2.7pacakge.json import { version } from 'mjml';
console.log(version()); // 2.3.1node_modules |
|
Only an output bug don't worry
|
|
Hello, This issue is tied to the fact that MJML CLI is a package of MJML. We'll make sure to update the version of |
Hi,
thank you so much for this beautiful piece of work.
I am trying to upgrade to 2.3.2. Unistalled and reinstalled again using npm but it still showing 2.3.1
The text was updated successfully, but these errors were encountered: