There's a package from GitHub I want to use in my filament project, but it is badly maintained and not compatible anymore.

I would like to upgrade it myself, but how do I do this? Do I have to create a fork?

What is the recommendation on this situation?

fork, edit and then pull request.
But i would always check the license, if there's one.

@thebiochemic there is a pull request already, but the author has probably left for a walk since 2022.

@Wombat what you can do, if the original author is not active anymore, you can mention in the PR, that your fork is an upgraded version of that package, to notify future users, who might stumble over that github repo

@jestdotty even if most of the code is replaced, the base of it at some point wasn't yours (that also includes the chosen tech stack and architecture decisions, artwork, name, etc.). I feel it's just good practice to keep the original names and stuff in place and add yourself as a contributor (albeit a massive one).

Entirely rewriting something from scratch is a different story. And even then it's also good practice to atleast mention the source of inspiration.

Unless the author in question doesn't want attribution, then i guess it doesn't matter really.

author never looked at it again cuz they may consider it complete. Or, in the worse case scenario, the project's been architectured in a way that's really hard to maintain. Either way, I've 2 suggestions.

1. If the first case is true. Make an extension for that project. Don't add that feature directly.

2. If the second case's true. Make an extension for that project. Don't add that feature directly.

@kobenz actually a package dependency is also not maintained anymore and therefore installation fails. So I will go the way of my own package creation which kinda is a fork but actually I am rewriting it a lot.

@Wombat good idea, remember to paste the original license whenever you copypasta so you don't get fucked later on