You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well... kind of official from the community standpoint, but if you're reading this you probably know the original asset-rack has been somewhat abandoned. I guess this thread should be used to discuss who should inherit the project and which new fork we should all go use, support, contribute to and etc.
It looks like @Alex-Cheng has some enthusiasm to maintain a fork. I think the spiritual successor should probably be a group of people with relevant experience or maybe an organization to prevent stagnation or reliance on one maintainer.
There's a lot of big issues like express 4.x support and a huge backlog of issues and PRs that render a pretty built-out asset pipeline library to currently useless. It wouldn't be a lot of work to fix it and revive a lot of previous work as well.
The other alternative and possibly better argument is to jump to a comparable or more well-built project and integrate some of the key differentiating features like S3 deploy integration (imo the most unique one).
Thoughts?
The text was updated successfully, but these errors were encountered:
Well... kind of official from the community standpoint, but if you're reading this you probably know the original asset-rack has been somewhat abandoned. I guess this thread should be used to discuss who should inherit the project and which new fork we should all go use, support, contribute to and etc.
It looks like @Alex-Cheng has some enthusiasm to maintain a fork. I think the spiritual successor should probably be a group of people with relevant experience or maybe an organization to prevent stagnation or reliance on one maintainer.
There's a lot of big issues like express 4.x support and a huge backlog of issues and PRs that render a pretty built-out asset pipeline library to currently useless. It wouldn't be a lot of work to fix it and revive a lot of previous work as well.
The other alternative and possibly better argument is to jump to a comparable or more well-built project and integrate some of the key differentiating features like S3 deploy integration (imo the most unique one).
Thoughts?
The text was updated successfully, but these errors were encountered: