Skip to content

Maintenance: update Gitpod config #1781

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
Closed
1 of 2 tasks
dreamorosi opened this issue Nov 2, 2023 · 1 comment · Fixed by #1782
Closed
1 of 2 tasks

Maintenance: update Gitpod config #1781

dreamorosi opened this issue Nov 2, 2023 · 1 comment · Fixed by #1782
Assignees
@dreamorosi
Labels
completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)

Comments

@dreamorosi
Copy link
Contributor

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

Future readers

Please react with 👍 and your use case to help us understand customer demand.
@dreamorosi dreamorosi added internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) confirmed The scope is clear, ready for implementation labels Nov 2, 2023
@dreamorosi dreamorosi self-assigned this Nov 2, 2023
@dreamorosi dreamorosi mentioned this issue Nov 2, 2023
Merged
9 tasks
@dreamorosi dreamorosi linked a pull request Nov 2, 2023 that will close this issue
chore(maintenance): improve Gitpod config #1782
Merged
9 tasks
@github-project-automation github-project-automation bot moved this from Working on it to Coming soon in Powertools for AWS Lambda (TypeScript) Nov 2, 2023
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Nov 2, 2023

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@dreamorosi dreamorosi moved this from Coming soon to Shipped in Powertools for AWS Lambda (TypeScript) Nov 2, 2023
@dreamorosi dreamorosi added completed This item is complete and has been merged/shipped and removed confirmed The scope is clear, ready for implementation labels Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dreamorosi dreamorosi

Labels
completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Projects
Powertools for AWS Lambda (TypeScript)
Status: Shipped
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore(maintenance): improve Gitpod config aws-powertools/powertools-lambda-typescript
1 participant
@dreamorosi