The migration process replaces mj-includes with the actual content

[splitt3r]

Simple demo files from https://mjml.io/documentation/#mj-include.

Reproduction Steps:
The header.mjml file:

<mj-section>
  <mj-column>
    <mj-text>This is a header</mj-text>
  </mj-column>
</mj-section>

The index.mjml file:

<mjml>
  <mj-body>
    <mj-include path="header.mjml" />
  </mj-body>
</mjml>

Migrating the files via (PowerShell):
mjml -m .\index.mjml -o .\index.mjml

Observed behavior:
The index.mjml becomes:

<mjml>
  <mj-body>
    <mj-column>
      <mj-text>This is a header</mj-text>
    </mj-column>
  </mj-body>
</mjml>

MJML version:

4.0.3

Is there any way to force the correct behaviour of not replacing the include with its content?

[iRyusa]

Thanks for reporting this one @splitt3r !

Mhh, we might be able to add an option into the parser to skip include for 4.1 @kmcb777 ?

[brianespinosa]

Phew! I was going crazy trying to figure out what was going on trying to convert for v3 to v4. Glad to see there's already a PR open for this one.

[kmcb777]

Hi @splitt3r @brianespinosa we released a new beta for mjml 4.1, which you can install with npm install mjml@next, could you check if it resolves this migration problem ?

[brianespinosa]

Thanks, @kmcb777

I will try to take a look early next week when I get a free cycle and report back.