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.

Sign up for GitHub

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

Jump to bottom

Support serverless environments #594

Open
tunnckoCore opened this issue Mar 27, 2020 · 8 comments
Open

Support serverless environments #594

tunnckoCore opened this issue Mar 27, 2020 · 8 comments
Labels
Area: APIs Things related to external and internal APIs Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Proposal A feature request or another suggestion. Type: Enhancement Most issues will probably be for additions or changes. Expected that this will result in a PR.

Comments

@tunnckoCore
Copy link
Member

The existence of formidable-serverless is because serverless env is preprocessing the body.

Today I received one more report (in twitter) because of that. The #285 is related to that too.

We need to integrate that.
@auto-comment
Copy link

auto-comment bot commented Mar 27, 2020

Thank you for raising this issue! We will try and get back to you as soon as possible. Please make sure you format it properly, followed our code of conduct and have given us as much context as possible.
/cc @tunnckoCore @GrosSacASac

@tunnckoCore tunnckoCore mentioned this issue Mar 27, 2020
Closed
@tunnckoCore tunnckoCore pinned this issue Apr 20, 2020
@tunnckoCore tunnckoCore mentioned this issue May 14, 2020
Closed
@tunnckoCore tunnckoCore mentioned this issue Jun 22, 2020
Open
@CatalanCabbage
Copy link

Hi @tunnckoCore! Is there an easy way to reproduce this issue?

@tunnckoCore
Copy link
Member Author

Hi. I'm not sure. Maybe try deploying some of the examples in AWS, GCP, or Vercel. I think it currently works in Vercel.

@leonardovillela
Copy link
Contributor

leonardovillela commented Dec 13, 2020 •
edited

@tunnckoCore can I take this issue?

@tunnckoCore
Copy link
Member Author

sure, take the master as base

@tunnckoCore tunnckoCore mentioned this issue Dec 29, 2020
Open
@tunnckoCore tunnckoCore mentioned this issue Jan 7, 2021
Closed
@tunnckoCore tunnckoCore added Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Proposal A feature request or another suggestion. Type: Enhancement Most issues will probably be for additions or changes. Expected that this will result in a PR. Area: APIs Things related to external and internal APIs and removed feature request labels Apr 2, 2022
@GrosSacASac GrosSacASac mentioned this issue Jul 16, 2023
Closed
@prvashisht
Copy link

@tunnckoCore can I take this issue?

@leonardovillela did you manage to work on this?

@leonardovillela
Copy link
Contributor

@tunnckoCore can I take this issue?

@leonardovillela did you manage to work on this?

Nope, I didn't. Feel free to grab this issue.

@tunnckoCore
Copy link
Member Author

@leonardovillela @prvashisht

yeah, we are open for that, cuz i don't think formidable-serverless will work for the latest v3 version. Its package json asks for ^v1 so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area: APIs Things related to external and internal APIs Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Proposal A feature request or another suggestion. Type: Enhancement Most issues will probably be for additions or changes. Expected that this will result in a PR.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@prvashisht @tunnckoCore @leonardovillela @CatalanCabbage