Meta errors when rendering multiple times concurrently

[BenMansley]

Meta errors when rendering multiple times concurrently

[GemN]

Hello,
Got exactly the same problems when rendering emails to send to different customers in AWS lambda

[GemN]

I found a workaround.
I actually build with a script all my folder heml, into a folder html. Push both folders and in the code I directly load from the html folder (and for variables i use Mustache)

Script to build:

#!/bin/bash
type heml >/dev/null 2>&1 || { echo >&2 "Require heml. Please install (yarn global add heml)."; exit 1; }

for entry in "heml"/*
do
  if [ -f "$entry" ];then
    echo "-- Building $entry to html"
    filename=${entry##*/}
    heml build $entry --output html/${filename%.*}.html
  fi
done

Load html email:

const htmlEmail = fs.readFileSync(`${__dirname}/../emails/templates/html/myemail.html`, {
  encoding: 'utf-8',
});

Build the emails with dynamic variables:

const htmlEmailWithValues = Mustache.render(htmlEmail, emailData);
const form = new FormData();
form.append('from', 'App <[email protected]>');
form.append('to', `${firstname} <${email}>`);
form.append('subject', subject);
form.append('html', htmlEmailWithValues);

[robmcfeely]

@BenMansley @GemN or anyone find a solution to this? Same problem. It pretty much renders this project useless for service type activity :(

[Devessier]

I'm getting the same error.
Has anybody found a solution or a workaround 😄 ? @BenMansley @GemN @robmcfeely

[robmcfeely]

Nope. We dropped the library

…

On Mon 10 Feb 2020, 18:46 Devessier, ***@***.***> wrote: I'm getting the same error. Has anybody found a solution or a workaround 😄 ? @BenMansley <https://github.com/BenMansley> @GemN <https://github.com/GemN> @robmcfeely <https://github.com/robmcfeely> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#91?email_source=notifications&email_token=AAZTJCSYPPHJGCHNOV45FNTRCGOJDA5CNFSM4G7H7LA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELJY5RI#issuecomment-584289989>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZTJCSU4EP72DRMT2UI77DRCGOJDANCNFSM4G7H7LAQ> .

[Devessier]

@robmcfeely Okay, thank your for your reply ! 👍

[Devessier]

@GemN Great workaround !

I think I would have used your solution if I wouldn't must dynamically generate content using loops or conditions.
I created a small class that spawns 4 Node.js thread workers, each of them executing the heml function while waiting for the previous execution to be completed in order to prevent race conditions we encountered.
Like that I don't need to rely on HEML CLI.

The Gist containing the code : https://gist.github.com/Devessier/f17c3bf4e7f9a799059d1fec110ba841