Feature: @transpile block

[nicholaides]

Works like this:

@transpile
  const { compile } = require('@danielx/civet')

  // return a function that will be used to transpile handler functions
  return (code, filename) => compile(
    // puts the handler code inside a `return do ...` block then compiles it
    `return do\\n${code.replace(/^/gm, '  ')}`,
    { sync: true, filename }
  )

Rule
  /.+/ ->
    // use your pre-transpiled language
    $0 |> .toUpperCase()

Currently does not support async. In Node.js that will be ok because require is sync. Civet and esbuild both have sync versions of compile/transform.

TODO:

• support transpilation "target" so that it can compile to JS or TS depending on the context
• apply the transpile to code blocks (code in triple backticks)

Questions

• What are the security concerns around having the LSP execute arbitrary code when a .hera file is opened?
• The @transpile block can only be synchronous right now. Does that work for the scenarios this needs to support?

[nicholaides]

This fails the should parse decompiled rules round-tripping test. Not sure how to address this.

[edemaine]

Wow! I'm excited to use Civet in Civet's Hera rules!

I know I suggested this API, but maybe we should turn the second argument into an object with filename property so that we can add other properties too? E.g. we talked about js vs ts.

[nicholaides]

maybe we should turn the second argument into an object with filename property so that we can add other properties too? E.g. we talked about js vs ts.

I was thinking the same thing.