KNOWN_ISSUES.md

Lava-in-JS

We do not plan to offer complete support for Lava in JS.

That said, we do offer partial support for it. We support Lava inside JavaScript strings:

{% # 👍 supported, will be reformatted using prettier's own JavaScript formatter %}
<script>
  const mySetting = '{{ some_lava_drop }}';
</script>

{% # 👎 not supported, will only reindent the code %}
<script>
  {% if condition %}
    {% # do stuff %}
  {% endif %}
</script>

If you want to refer to a JSON blob, you can do this "purely" by using a <script type="application/json"> with a Lava JSON dump in it:

{% # dump your JSON in an application/json script tag %}
<script id="my-settings" type="application/json">
  {{ my_settings | json }}
</script>

{% # use your JSON by reading it with JavaScript %}
<script> 
  const myLavaSettings = JSON.parse(
    document.getElementById('my-settings').textContent
  );
</script>

Lava-in-CSS

We do not plan to offer complete support for Lava in CSS (or any support for .css.lava)

Our recommendation is the following:

• Define CSS Custom properties somewhere in your HTML-Lava files.
• Use plain .css files that refer to those custom CSS properties

Example:

theme.lava

<style>
  :root {
    --accent-colour: {{ some_setting }};
  }
</style>

styles.css

button.accent {
  color: var(--accent-colour);
}

You can see this pattern used in the Dawn repo.

• theme.lava
• base.css

Pros of this approach:

• Your CSS files are then true CSS files. This means you can use the official syntax highlighting for CSS, the formatter for CSS, etc. Which are bound to have better support than this plugin can offer.
• You can use build tools independently of Lava that work with CSS files.
• You could even use LESS or SCSS independently if you are so inclined.