Joe Pea

Whatever they do, I'm guessing the `yield` is for the same reason as I described: take the end of the output wire, then return it to be used as input...

@paldepind Is that a good way to think about it? Or is there a another way?

Ah, looks like we can basically just use `element()` like shown here: https://github.com/funkia/turbine/blob/master/src/elements.ts#L29. So ```js element('some-element')({class: 'foo'}, [...children]) ``` That should cover most cases, but there might still be special...

@paldepind I suppose that works. I'm also looking at Vue+Nuxt.js, which abstracts that part away.

They do it very very declaratively. But so do you!! I think the functional-to-HTML approach you have is nice.

Let me also follow the tutorial, that might help...

Yeah, there are a few CLI tools with subcommands features, but they are all written plain JS: - [yargs](https://www.npmjs.com/package/yargs) - example with folder hierarchy: https://github.com/yargs/yargs/blob/master/docs/advanced.md#example-command-hierarchy-using-commanddir - example with nested functions:...

:thinking: Hmmmm, maybe after the [sub-module issues](https://github.com/microsoft/rushstack/issues/1711) get worked out, then we could make a command that could accept a remote project URL and clone it into the specified path...

The file is not ignored by `.gitignore`, and in `/.rush/temp/package-deps_build.json` I see: ```json { "files": {}, "arguments": "tsc -p ./tsconfig.json " } ``` Should it be listed there? How does...

Ooooooh. I think I see the issue: My ``s are git sub modules. The "umbrella repo" that contains them, where I run `rush build` can not see what files changed...