Describe the bug
npm install mjml fails with this error
npm ERR! code ETARGET
npm ERR! notarget No matching version found for [email protected]
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'mjml'
npm ERR! notarget
To Reproduce
npm install mjml
Expected behavior
It should install with no error as the previous days
MJML environment (please complete the following information):
- OS: all system affected
- MJML Version 4.4.1
matteocrippa
All 7 comments
I got the same error
on Ubuntu and Macbook
but I can't wait for the bug fix
I will use 4.4.0 for now
npm install [email protected]
heart
on 30 Jul 2019
Hi, 4.4.1 has just been released so i guess the problem is npm cache, it should be ok in a few hours.
For now you can still use 4.4.0 👍 (4.4.1 is just a minor fix for a very specific use case)
kmcb777
on 30 Jul 2019
@kmcb777 publishing to npm should be immediate and not prone to caching issues. Especially since all other packages seem to have a 4.4.1 version already.
Are you sure / could you verify that the publishing of mjml-button worked as intended?
ctavan
on 30 Jul 2019
It’s not the first time that we have a cache issue on npm release. Even 4.4.0 release had the same issue.
On 30 Jul 2019, at 14:52, Christoph Tavan notifications@github.com wrote:
@kmcb777 publishing to npm should be immediate and not prone to caching issues. Especially since all other packages seem to have a 4.4.1 version already.
Are you sure / could you verify that the publishing of mjml-button worked as intended?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
iRyusa
on 30 Jul 2019
NPM shows that mjml-button is still in version 4.4.0
mjml-validator is also in version 4.4.0
all other dependencies are in version 4.4.1
kaniansky
on 30 Jul 2019
Yes, we're aware of that we're looking to force a re-publish on button & validator. Stick to 4.4.0 for now
iRyusa
on 30 Jul 2019
It's now ok !
Thanks for reporting this, at first we thought it was the usual delay (maybe it's not cache, but several times we had to wait a few hours until all new sub-packages versions are correctly found by npm when trying to install).
Anyway we republished mjml-button and mjml-validator 👍
kmcb777
on 30 Jul 2019
Related issues
iwanaga-sakura
·
4Comments
plaisted
·
4Comments
theVannu
·
3Comments
liminspace
·
3Comments
valstu
·
3Comments
Most helpful comment
I got the same error
on Ubuntu and Macbook
but I can't wait for the bug fix
I will use 4.4.0 for now
npm install [email protected]