Cosmin Popovici

> I would prefer to move the logic into the method Of course, my examples were very basic, users would be free to choose how they handle it. I came...

**EDIT**: fixed by running `nuxt generate` instead. Having this same issue, with both `` and `` when running `nuxt build`, can be seen on the homepage here for the code...

Having a similar issue with `[email protected]` on `[email protected]`:  Downgrading to `0.2.4` works as a temporary solution 👍

Additional context: It's common when coding HTML emails to use 'ghost tables' for Outlook - this is markup written inside conditional comments that target Outlook on Windows, so that it...

> should follow the specs as much as possible Agree 100%. Not sure how this would be done exactly, but basically what this needs is the unparsed contents of a...

I would definitely not want to force the user into defining opening/closing tags through `type` attributes. This is an implementation detail that they shouldn’t have to care about. At point...

Based on your previous comment - if we can still tackle this, my bad 😬

Getting back to this after a while, this seems to do it for opening tags: ```js node.content = `` return node ``` ... however it doesn't work on something like...

Looks like you're using this in Maizzle? Any reason you can't use single quotes around `subject`? This works fine without even having to change the delimiters - just [ignore the...

@Scrum now that we have attributes as locals, would it be possible to evaluate them with `expressions` so that a user could do something like this? #### parent.html ```html ```...