Any forbidden dependencies in server side plugin?

I have plugin that just imports “web-push” npm library and it reports error when i try to trigger it in workflow:

Sorry, we have encountered an unexpected error. Please file a bug report (Help -> Report a bug), including error code 1583343372189x577332493403640300 and a step-by-step explanation of how to reproduce this issue.

Just including this library in dependencies makes error in workflow, i don’t even “require” it in plugins code.

On plugin’s page i get green “Deployment is up to date”.

Tried with “got” library and same result.

Are there some dependencies that are forbidden on server side plugin?

Not that I’m aware of, the environment is AWS Lambda with standardized memory and processing capabilities, so you might be better off by both emailing bubble support for this and searching the web about such limitations in AWS Lambda.

1 Like

Ok thanks, i’m looking into that.

EDIT:
Lambda in fact has limits (AWS Lambda Limits: Exploring Deployment | Dashbird). I’m not sure which of those i might be hitting.

1 Like

This topic was automatically closed after 14 days. New replies are no longer allowed.