Closed probablyabear closed 4 years ago
If you reinstall it, it should grab the latest version available already
Thanks @iRyusa. I reinstalled it, and double checked its package.json. Looks like it's setup to pull in the latest minor version since 4.0.0:
"dependencies": {
"mjml": "^4.0.0",
"plugin-error": "^1.0.1",
"replace-ext": "^1.0.0",
"through2": "^3.0.1"
},
Just want to be sure I can take advantage of the newer releases of mjml while using this in my gulp workflow.
Carret on npm will match latest non major version, so it shouldn’t be an issue check if you have any lock filE in your project
On 28 Apr 2020, at 02:24, Stephen Rust notifications@github.com wrote:
Thanks @iRyusa. I reinstalled it, and double checked its package.json. Looks like it's setup to pull in the latest minor version since 4.0.0:
"dependencies": { "mjml": "^4.0.0", "plugin-error": "^1.0.1", "replace-ext": "^1.0.0", "through2": "^3.0.1" }, Just want to be sure I can take advantage of the newer releases of mjml while using this in my gulp workflow.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
You're right, thanks for the sanity check!
Would it be possible to bump the version of MJML used in this to the latest release?