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
The reason for that one is because the one of the transitive dependencies needed to compile native code and required more than 1GB of RAM to do so, causing install failures on AWS micro instances. I agree that it's a better model to have the dependencies be opt-in, but thats also a breaking change and I'm not sure if the benefit of the breaking change justifies the cost to everyone else, like it did with the GCS adapter.
Hey, noticed that the GCS file adapter was moved to devDependencies in this commit 1eb2a87
I like the opt-in approach to these dependencies for production parse servers, any similar plans for S3 / ParseFS adapters?
The text was updated successfully, but these errors were encountered: