Looking for maintainer

[zaro]

The company that sponsored this fork originally is not interested for quite some time in it and I myself don't have the time/need to maintain the library as I have moved to projects that don't use it.

[danyalutsevich]

May be you could write your ideas on what could be implemented

I asked the developer of the original library and his advice was to
get rid of yarn, lerna and use pnpm, turbo, changesets instead

I had my own ideas but they seems to be solved by @eicrud/eicrud

[zaro]

@danyalutsevich Well, I would say i's mostly bugfixes and releasing to NPM.

As you pointed out, for new projects probably there are better options and this eicrud looks quite interesting.

get rid of yarn, lerna and use pnpm, turbo, changesets instead

I don't think the biggest problem of the library is the tooling around it, so while this will have some effect probably won't do much in terms of adoption. Also the underlying TypeORM library seems is rapidly falling out of favour which isn't helping either.

The library while doing a really good job, need quite some re-factoring to be easier to add new features.

[rjpkuyper]

The company I work with is at least adding some new features to this package and also fixed some outdated maintenance issues. It's forked here.

Currently what is done:

• fix pipelines
• Increased all dependencies to latest both for NPM as the docker dependencies
• migrate to faker and decouple coupled seeds to tests
• Add (opinionated) REST-based policy feature. Multiple clients are using this in production. Though, we haven't added any documentation about it yet.
• They are also willing to invest in some adapters for Prisma, sequelize and others.

Regarding problems around the framework; I agree that the original code base need some refactoring to make it easier. However, this will be something we will work on in the upcoming year. For now, our biggest focus will be long term maintenance and adding some most wanted features our clients want. In general, the framework is actually still doing a quite good job.

[jkaos92]

@rjpkuyper Thanks. Hopefully the library doesn't die, it is not perfect but i really like it and i have used it in many projects from the initial nestjsx/crud and didn't found any viable alternative for now.

Something is better than nothing so i really appreciate your and your company work toward this.
The library was stable for me for all the DBMS i used. Not having companies sponsoring/people mantaining it is the only downside for me. Dependencies update is what is really needed and takes time and again i really appreciate new people stepping in. Thanks again.
Also, if people will start to switch to your version, please invest into documentation update a bit.

[abdokouta]

@zaro @rjpkuyper , we’re interested in sponsoring this project to support ongoing updates and maintenance. Please let us know what would be required from our side and any clear milestones and timelines for core code refactoring. Additionally, we’d like to understand the key features and improvements planned. We’re open to community input and would love to discuss this further.

[iamjoeker]

I'm also interested in contributing. I'm looking into the possibility of sponsorship from my company.

[zaro]

@abdokouta @iamjoeker Can you reach out over email (zarrro [AT] gmail [DOT] com) so we can talk about your needs . I might be willing to do more maintenance and feature development if there is enough interest and support.

[afilp]

@rjpkuyper @zaro Is it possible that you add an "Issues" tab on your fork? So that we can have adjustments there too, as it seems that your fork is many commits/changes ahead of this repo? (unless you want your changes to be merged here, and so on).

From Gemini:

Can you enable issues on a fork?

Yes, you can! It's a setting you can change. If you want your fork to have its own issue tracking system (for example, if you're developing a significantly different version of the project, or using your fork for personal development where you want to track your own tasks), you can enable issues in your fork's settings.

[afilp]

Also, another fork that has some improvements:
https://github.com/4Digital-LLC/dataui-nestjs-crud/pulls?q=is%3Apr+is%3Aclosed

[rjpkuyper]

@afilp I enabled the issue tracking on the fork.