-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Status of Express #3525
Comments
Hey @jdcauley, absolutely. We're committed to Sails regardless of what happens to any of our dependencies. Specifically re: Express, see #3235 (comment) for more context. |
Thanks for posting, @jdcauley. I'm a repo bot-- nice to meet you! The issue queue in this repo is for verified bugs with documented features. Unfortunately, we can't leave some other types of issues marked as "open". This includes bug reports about undocumented features or unofficial plugins, as well as feature requests, questions, and commentary about the core framework. Please review our contribution guide for details. If you're here looking for help and can't find it, visit StackOverflow, our Google Group or our chat room. But please do not let this disrupt future conversation in this issue! I am only marking it as "closed" to keep organized. Thanks so much for your help!
|
(@jdcauley Going to reopen this for a little while in case that link helps anyone else out who has questions about the future of Express.) |
Will Sails continue to be supported and maintained in the event that Express fails to get back under development?
The text was updated successfully, but these errors were encountered: