maizzle build production not always resolve nested <component>

• Maizzle Version: Framework v3.7.3
• Maizzle Version: CLI v1.4.0
• Node.js Version: v16.13.

I’m unable to reproduce it constantly, but it seems that sometimes (without changing anything from the code) Maizle is having problems to resolve nested components like this (see the teaser component nested to content component)

<extends src="src/layouts/main.html">
  <block name="template">
    <!-- HEADER -->
    <component
      src="src/components/header.html"
      locals='{"url": "{{social.website}}"}'
    >
      <img
        class="w-[274px] sm:w-[188px]"
        src="https://s3.com/images/email.png"
        alt="Website"
      />
    </component>
    <!-- CONTENT -->
    <component
      src="src/components/content.html"
      locals='{"contentCtaUrl": "https://www.example.com", "contentCtaText": "Cta text"}'
    >
      <!-- EXAMPLE OF CUSTOM CONTENT ADDED UNDER BODY -->
      <component
        src="src/components/teaser.html"
        locals='{"teaserUrl": "https://www.example.com", "teaserText": "Teaser text"}'
      >
      </component>
    </component>
    <!-- FOOTER -->
    <component src="src/components/footer.html">
      <img
        class="w-[274px] sm:w-[188px]"
        src="https://s3.com/images/email.png"
        alt="Website"
      />
    </component>
  </block>
</extends>

do you know any problem similar to this? I’m saying that is not rendering because if I go to see the produced output in build_poduction I see that inside the code I have a <component>

Also, I have another question: if we have nested components, is it a problem if I use the same name for the locals? I would expect that they respect the scope/hierarchy but just to be sure that it was not the problem (of the not rendering properly) I changed it back to have unique names (it’s less clean and scalable)

[cossssmin]

Only if you plan on using them 😃

[cossssmin]

Not doing anything in that sense, yarn has probably cached your dependencies.