Skip to content
This repository has been archived by the owner on Feb 4, 2020. It is now read-only.

Question: How to update to use latest MJML #52

Open
sinklair opened this issue Dec 12, 2018 · 5 comments
Open

Question: How to update to use latest MJML #52

sinklair opened this issue Dec 12, 2018 · 5 comments

Comments

@sinklair
Copy link

Is there a simple way to upgrade the MJML support behind the extension? I would like to use a change in 4.2.1 that is causing linting errors in this version.

@sinklair
Copy link
Author

Bump

@dalefish
Copy link

Bump, but to go the other way. I'd like it to use a custom version (3.3.5) globally available on the CMD line.

Not holding my breath but would be nice for backwards compatibility with older code bases

@keberox
Copy link

keberox commented Feb 22, 2019

It would be great to allow the engine version to be configurable, even point to a local npm global installed version, at least within a major version line 4.*

@TheWebTech
Copy link

bump.

Would help contribute to update the MJML version included if a wiki or something explained the process or how mjml is being loaded a little. (and if it's not completely over my head)

@dnuanes
Copy link

dnuanes commented Jun 4, 2019

Same. I think the features work well, if we can just get an update to the latest version of MJML, that would be great.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants