It probably depends on your data. For example, if none of the values will ever contain commas, you could just make it a comma-separated list and then split on a comma (e.g. starting your app with FOO=bar,baz,quux node myapp.js then doing var foo = process.env.FOO.split(',') in myapp.js).
Otherwise if your input values can be more complex, JSON will probably be the easiest to work with.
In this scenario, it doesn't sound like an env var is the way to go.
Usually, you'll want to use environment variables to give your application information about its environment or to customize its behavior: which database to connect to, which auth tokens to use, how many workers to fork, whether or not to cache rendered views, etc.
Your example looks more like a model, so something like a database is probably a better fit.
That said, there's no context around what your app does or how it uses festivals, so if it does turn out that you should use an env var, then you have several options. The simplest is probably to just use a space or comma-delimited string: