osapi fails to build (depends on noda)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 9.8k
- Forks
- 326
- PR merge metrics
- No merged PRs in 30d
Description
Hello, I cannot deploy my backend lambda function because of strange error and I want to ask for your help if it's possible.
General issue is I'm using osapi for my s3 connections and stuff and this package works well while I'm working locally but since it's deployed backend sends 502 on any lambda where piece of code with requiring osapi is present.
I created a public deployment: https://zeit.co/kkz-zae/express/g081kykjq
and also GitHub repository to reproduce this:
https://github.com/reetou/now-reproduce-express
As far as I understand it cannot find some dependencies of osapi for some reason.
Hope you will help me or feed my interest why it happened at least.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked now-reproduce-express repository and compare its local behavior with the public deployment. Trace the require of osapi and its dependencies during the ncc build, then verify that the resulting Lambda deployment no longer returns 502.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript, node.js
- Domain
- backend, build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100