Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Looking for maintainer #66

Open
zaro opened this issue Oct 11, 2024 · 2 comments
Open

Looking for maintainer #66

zaro opened this issue Oct 11, 2024 · 2 comments

Comments

@zaro
Copy link
Member

zaro commented Oct 11, 2024

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.

@zaro zaro pinned this issue Oct 11, 2024
@danyalutsevich
Copy link

danyalutsevich commented Oct 11, 2024

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
Copy link
Member Author

zaro commented Oct 11, 2024

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants