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

question: is this package still maintained? #1488

Open
sudharsan-selvaraj opened this issue Feb 12, 2025 · 6 comments
Open

question: is this package still maintained? #1488

sudharsan-selvaraj opened this issue Feb 12, 2025 · 6 comments
Labels
type: question Questions about the usage of the library.

Comments

@sudharsan-selvaraj
Copy link

First of all, thank you for building and maintaining routing-controllers! It’s a great project, and I truly appreciate the effort that has gone into it.

I'm currently evaluating routing-controllers for a new project I'm about to start and would like to understand if the project is still actively maintained. I noticed that the last release was made about two years ago, and I couldn't find recent updates or activity in the repository.

Could you please clarify the current maintenance status of the project? Are there any plans for future updates or active contributions?

@sudharsan-selvaraj sudharsan-selvaraj added the type: question Questions about the usage of the library. label Feb 12, 2025
@OskarLebuda
Copy link

There are couple of PR and issues that doesnt' even have an response from author.
Here is statement of the author (in other typestack repo) - typestack/class-validator#1775

I'm currently working on routing-controller replacement called vercube. If u're interested - just contact with me and I'll give u an erly access

@attilaorosz
Copy link
Member

I wouldn't call it dead, but the priorities are a bit elsewhere at the moment.

Unfortunately I've seen countless iterations of replacements of this package but usually they end up abandoned after a couple of months, but let's hope @OskarLebuda version will be different. I would also love to just use a library and not have to maintain one :).

On the other hand, we usually keep this up to date as much as possible because it's used in production.

If someone has cool ideas which are not just bloat, I'm always open for discussion, especially when not just requests but contributions are also present.

@OskarLebuda
Copy link

I wouldn't call it dead, but the priorities are a bit elsewhere at the moment.

Unfortunately I've seen countless iterations of replacements of this package but usually they end up abandoned after a couple of months, but let's hope @OskarLebuda version will be different. I would also love to just use a library and not have to maintain one :).

On the other hand, we usually keep this up to date as much as possible because it's used in production.

If someone has cool ideas which are not just bloat, I'm always open for discussion, especially when not just requests but contributions are also present.

@attilaorosz I've never called it "dead". I have productions projects that uses routing-controllers.

I've also never said that my "version" will be better than this project. But we have to do something to keep our projects up to date. For example moving them to ESM.

I love to use routing-controlles, but as you maintain - there are other priorities than this project.

@attilaorosz
Copy link
Member

@OskarLebuda it might have sounded different compared to what I meant. What I wanted to emphasise is that I hope your version will be better so we all can move to a better version.

I have my problems with routing-controllers mostly due to some design choices made in the early days that are now hard to remove. I also don't want to use the bloated alternatives like nest.js or ts.ed because they introduce so much clutter and force you into their way of thinking. But until that lean alternative arrives, we have to live with this and I have to find the time to generate a release (which takes almost an hour because I still don't have correct push rights and also have to gather each change for the changelog manually) each time a meaningful or necessary update set is available.

@OskarLebuda
Copy link

OskarLebuda commented Feb 14, 2025

@OskarLebuda it might have sounded different compared to what I meant. What I wanted to emphasise is that I hope your version will be better so we all can move to a better version.

I have my problems with routing-controllers mostly due to some design choices made in the early days that are now hard to remove. I also don't want to use the bloated alternatives like nest.js or ts.ed because they introduce so much clutter and force you into their way of thinking. But until that lean alternative arrives, we have to live with this and I have to find the time to generate a release (which takes almost an hour because I still don't have correct push rights and also have to gather each change for the changelog manually) each time a meaningful or necessary update set is available.

@attilaorosz Maybe you would like to collaborate with my projects and solve your problems with routing-controlles? Let me know if you're interested. Love to see your point ☺️

@attilaorosz
Copy link
Member

Sent you an email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: question Questions about the usage of the library.
Development

No branches or pull requests

3 participants