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
This project is currently lacking an active lead maintainer. I no longer have an active use case for local S3 development and do not have the time to keep this library up-to-date with a level of quality I'd be happy with.
In its current state, this project is already pretty useful and handles many of S3's edge cases with grace. Though with the deprecation of Node 8, AWS Signature Version 2, and path-style bucket access, it's embarrassingly fallen a bit behind and isn't an accessible way for developers to create S3 test environments right now.
More accessible simulation of subdomain and vhost-style buckets (since path-style buckets are going away Fall 2020)Add guideline for dev DNS server #635
Support creating buckets without Signature Version 2 support**
Support creating buckets without path-style access**
Hi all!
This project is currently lacking an active lead maintainer. I no longer have an active use case for local S3 development and do not have the time to keep this library up-to-date with a level of quality I'd be happy with.
In its current state, this project is already pretty useful and handles many of S3's edge cases with grace. Though with the deprecation of Node 8, AWS Signature Version 2, and path-style bucket access, it's embarrassingly fallen a bit behind and isn't an accessible way for developers to create S3 test environments right now.
Current v4.x plans:
(since path-style buckets are going away Fall 2020)Add guideline for dev DNS server #635** AWS doesn't yet document how buckets will behave once these restrictions are in place, initial support will be experimental
My v4.x wishlist (v4.1 and beyond)
The text was updated successfully, but these errors were encountered: