Skip to content

Conversation

@vrubezhny
Copy link
Contributor

@vrubezhny vrubezhny commented Feb 3, 2026

@vrubezhny vrubezhny marked this pull request as draft February 3, 2026 18:51
@vrubezhny vrubezhny force-pushed the fix-move-to-yarn-v4 branch 26 times, most recently from adf265b to 3b1472c Compare February 6, 2026 19:04
@vrubezhny vrubezhny force-pushed the fix-move-to-yarn-v4 branch 19 times, most recently from 74477a4 to fbdfa04 Compare February 11, 2026 15:20
Fixes: https://issues.redhat.com/browse/CRW-10005

Signed-off-by: Victor Rubezhny <vrubezhny@redhat.com>
@vrubezhny
Copy link
Contributor Author

What's done:

  • Cloud-shell is converted to use yarn v4,
  • Dockerfile is updated to use node 22 (alpine) image (v16 was too outdated and had no support for yarn v4)
  • Devfile has converted from v1 to v2.3.0 outdated images replaced with the modern ones for Go and Node.js containers
  • Recommended extensions setup has moved to .vscode/extensions.json
  • Creating "Remote Debug" launch has moved to .vscode/launch.json out of the devfile

Using Devfile commands to compile che-machine-exec go-project and cloud-shell Front End:

move-to-yarn-v4_spedup.mp4

Running che-machine-exec in debugger (vscode launch):

launch-debug-after-move-to-yarn-v4.mp4

@vrubezhny vrubezhny self-assigned this Feb 11, 2026
@vrubezhny vrubezhny marked this pull request as ready for review February 11, 2026 20:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants