Closed spickermann closed 6 months ago
Dear @spickermann ,
i am seeing the same issues, although not running mrml
but the "plain" mjml
.
I think, this issue is related to yarn
. If you install mjml
via npm
instead of yarn
, this works perfectly fine for me. However, this is kind of wonky, because the entire pipeline uses yarn
.
I have described my finding in #108 so far.
Maybe you can provide additional information if you find something?
i ended up running a
npm install -g mjml
in my Dockerfile
that creates the image for my server to get rid of the issue.
However, obviously, i am looking for a better solution ;)
@spickermann I'm having trouble replicating it in my project. Would you be able to submit a PR for the fix?
@spickermann Does this branch solve the warning for you? https://github.com/sighmon/mjml-rails/pull/118
@sighmon I am sorry for not responding to your questions. Yes, the current master
branch is fixing the issue. Thank you!
Hey there,
I updated
mjml-rails
to4.10.0
and enabled usingmrml
, an option that was added in https://github.com/sighmon/mjml-rails/pull/114. At the same time, I removed the dependency onmjml
frompackage.json
.My
Gemfile
includes these lines:And my
config/initializers/mjml.rb
looks like this:I ran my test suite and
mjml-rails
seems to work as expected and renders emails usingmrml
just fine.But when starting the application or running the specs, this warning in put out to the console:
I wouldn't expect this warning when
mjml-rails
is configured to usemrml
andmrml
is installed.