Tagged template literals and wizardry

Here is a totally crazy idea. I am posting it here because I don’t have time to work on it right now.

If this is just too crazy for fly, I can accept it (I can already see it might be too crazy indeed). A new module would do just fine in that case.

const source = ["src/**/*.js", "!src/ignore/**/*.js"]
const target = ["dist/app.js"]

module.exports = `
    watch ${source} >
        eslint {no-extra-semi: 0}
        babel {es2015, state-0}
    > concat > target > ${target}
`

[lukeed]

Lol you can call it an abstraction if it makes you feel more comfortable that way.

But right now, as you have it, it still uses template literals, injecting source and using api methods. You can regex this down and perform some behind the scenes magic so that Fly gets what it wants, and that’s what defines an abstraction/decorator pattern.

It’s up to you and how far you want to take this syntax. Obviously, at some point, it becomes its own thing (or more like a Make clone). You’ll have to decide if it still should compile down to fly-compatible exports, or becomes its own runner.

Worth exploring if you’re interested.

[jorgebucaran]

When does it stop being a decorator and becomes its own language? Or is JavaScript a decorator of C++?