Kindly asking... is this still maintained? about hygen

[svallory]

Hey @jondot I'm kind of on a cross-roads here. I'm continuing the development of hypergen, I recently added an Indexed store implementation to speed up generator loading and conflict resolution.

The reason I did that is because my goal is to have at least dozens of templates with multiple overrides. I'll also add automatic template package discovery by reading package.json dependencies.

I'm telling you all this because it is becoming increasingly harder to send PRs back to hypergen (especially because I don't want to impose "my way").

Also, I feel your pain about the state of the node ecosystem. So I'm thinking of migrating the codebase to ESM and Deno which supports cross-compilation of binaries to all platforms. And that would be a total departure.

So I wanted to check with you what you think about this. If you want, this could become hygen v7, we merge the projects and maybe even create an organization. If not, it's okay too. I just wanted to be mindful of the work you did (I'm standing on the shoulder of giants here hehehe)

When you can, let me know what you think, ok? Thanks!

[jondot]

Hi yes, this is still maintained.

The reason I'm taking more time to interact is the huge pain that is the Node.js ecosystem. Projects break out of no reason, and Javascript fatigue is a real thing.

Hygen at its current featureset works really well, and I always hesitate before trying to update dependencies and the codebase (because of the Node ecosystem).

I've started rrgen which will turn into Hygen's big brother (faster, easier, simpler, better), and rrgen is used in production and in high profile context already.

I'll try to review the PRs and see what should go into Hygen, but my main pain point is the ecosystem (ability to produce binaries, releases in a reliable manner in Node)

[svallory]

Hi yes, this is still maintained.

The reason I'm taking more time to interact is the huge pain that is the Node.js ecosystem. Projects break out of no reason, and Javascript fatigue is a real thing.

Hygen at its current featureset works really well, and I always hesitate before trying to update dependencies and the codebase (because of the Node ecosystem).

I've started rrgen which will turn into Hygen's big brother (faster, easier, simpler, better), and rrgen is used in production and in high profile context already.

I'll try to review the PRs and see what should go into Hygen, but my main pain point is the ecosystem (ability to produce binaries, releases in a reliable manner in Node)

Thank you for taking the time to reply! I'm creating a set of templates for monorepo and projects setup using moon, and I was kind of stuck needing some features to deal with the combinatorial explosion of the options.

Hygen had most of them, so I ended up implementing the one I required most (multiple templates directories) and since I'm in rush, I published it as hypergen.

I'm happy to continue making PRs for whatever makes sense to you, and even merge the projects back together in the future if you want

This first rc version is not a 100% backwards compatible but very close. I changed how missing directories is treated in some cases, so an error may be thrown in some cases. But that shouldn't really be an issue. Because if you are setting HYGEN_TMPLS, for example, you probably think that path exists, right?

Side note: Not sure if you are aware of Marko JS and their new tags api, but I think their language is perfect for templates and I want to make a translator for it so I can use marko instead ejs or whatever