-
Notifications
You must be signed in to change notification settings - Fork 12
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
Make this module up-to-date and to the Fastify standard #2
Comments
Can somebody please add this repo to @fastify/libraries please? |
Should we remove all the deprecated functions and options? |
Yes |
Done. |
Is refactoring part of this issue? We got already
What left is
|
I'd be ok to cut a v2 without #15, and then work on a v3 for it. |
After #27 we could integrate parseRange and fresh package. |
Imho all relevant pieces are now in the repo. We could start transplanting open PRs from the original repo to our fork. But maybe @climba03003 wants to implement #15 ? |
#15 is super important. |
I think we can close this. |
Should we release v2? |
Yes, #15 would completely change the API. And |
This module was forked due to fastify/fastify-static#352.
Given the status of maintenance of
send()
and how badly out of date it was in its deps, I think we could do some good work here to bring this module up to our standards.The text was updated successfully, but these errors were encountered: