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

Use in custom Node runtimes #268

Open
dougmoscrop opened this issue Apr 1, 2022 · 0 comments · May be fixed by #269
Open

Use in custom Node runtimes #268

dougmoscrop opened this issue Apr 1, 2022 · 0 comments · May be fixed by #269
Labels
enhancement New feature or request

Comments

@dougmoscrop
Copy link

What would you like to have implemented?

Running Node 16 in a Custom Runtime on Lambda, requires this workarond:

process.env.AWS_EXECUTION_ENV = 'AWS_Lambda_nodejs14.x'
const { default: chromium } = await import('chrome-aws-lambda')

Given the deprecation of older Lambda runtimes, perhaps the check could just be if AWS_EXECUTION_ENV starts with AWS_Lambda_?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

More flexible runtime execution check to support custom runtimes dougmoscrop/chrome-aws-lambda
1 participant
@dougmoscrop