Description
Summary
A contributor on Discord has encountered issues setting up their development environment using Gitpod. After looking into it I have noticed that Gitpod have updated the default base image to use Node.js 20.
The repository is still using Node.js 18 for development and hasn't yet been tested on the newer version, which went LTS about a week ago. We are planning on upgrading our development environment to the newer version but we haven't gotten to it yet.
This issue has evidenced that the current setup commands that are supposed to install a specific Node.js version are not working. We should fix this asap to unlock contributors.
Why is this needed?
So that new contributors can onboard easily and have a working environment when they start.
Which area does this relate to?
Other
Solution
Review the .gitpod.yml
file and make sure it initializes the environment correctly.
Acknowledgment
- This request meets Powertools for AWS Lambda (TypeScript) Tenets
- Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status