Skip to content
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

Expose the Express app on S3rver instances #59

Closed
wants to merge 1 commit into from

Conversation

kherock
Copy link
Collaborator

@kherock kherock commented Mar 5, 2017

The fs option added in #54 wasn't documented and was a breaking change, so I was pretty confused what was wrong for a bit. Using fs-extra by default makes it non breaking : ).

@kherock
Copy link
Collaborator Author

kherock commented Mar 19, 2017

@jamhall Any comment on this?

edit: I just noticed that my issue is only present when using it as a mountable express app. The command line version already has fs-extra set as a default.

This also reduces redundant code by dynamically creating the setter methods for the S3rver class.
@kherock kherock changed the title Use fs-extra as default fs backend Expose the Express app on S3rver instances Mar 19, 2017
@kherock
Copy link
Collaborator Author

kherock commented Mar 19, 2017

OK, I've figured out a better solution since the problem was just that certain default options aren't set when you try to use the Express app via require('s3rver/lib/app'). Instead, I've opted to make it accessible so something like new S3rver(options).app is possible. The app prop just gets recreated every time the options are updated.

@kherock
Copy link
Collaborator Author

kherock commented Jan 24, 2018

Closing since I'll include these changes in a less intrusive manner in #63.

@kherock kherock closed this Jan 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant