chore: revert back pull request #396

[vitaliy-guliy]

What does this PR do?

It is a temporary solution.
Reverts back #396 as it become not possible to run che-code in the development mode

What issues does this PR fix?

Part of eclipse-che/che#23163

How to test this PR?

• create a PR from che-code repository
• update node dependencies, compile and then run che-code

Does this PR contain changes that override default upstream Code-OSS behavior?

• the PR contains changes in the code folder (you can skip it if your changes are placed in a che extension )
• the corresponding items were added to the CHANGELOG.md file
• rules for automatic git rebase were added to the .rebase folder

[github-actions]

Click here to review and test in web IDE:

[RomanNikitenko]

I propose not revert those changes, but find a way to fix che-in-che development

[vitaliy-guliy]

I propose not revert those changes, but find a way to fix che-in-che development

It is a temporary solution.

There are several higher priority issues that need to be resolved.

It is more than a year Che become my primary development environment. And now my development environment is broken.

[RomanNikitenko]

@vitaliy-guliy
as far as I know:

• Upgrade devfile/api and eclipse-che/che-devworkspace-generator #396 affects only che-in-che development
• it was merged more then a month ago
• at the same time you are going to downgrade devfile/api dependency - it will affect a new release - as you are going to have a vacation

I'm still +1 to find a fix for che-in-che development instead of reverting those changes
As a workaround we could use your changes locally at che-in-che development

===
btw - all jobs failed, so it looks like it's not enough just revert those changes - some adaptation is required

[vitaliy-guliy]

I'm still +1 to find a fix for che-in-che development instead of reverting those changes As a workaround we could use your changes locally at che-in-che development

I will leave the PR opened for some time until we fix the problem

To apply changes from this PR as a temporary workaround I'm using the following command
(just share for someone who needs to run che-code in che)

git show 764f6502330d2f3a509b5fc1da90f6b02f81aa3c > /tmp/my-changes.patch
git apply /tmp/my-changes.patch

[mattgritter]

Just adding context for additional interested parties because I also ran across this problem doing some proof-of-concept work while building for Linux on s390x. The 2.3.0 version of the (at)devfile package is now an ESM module vs a CommonJS module in 2.2.0, so the require statement generated by the transpiler in che-api/impl/k8s-service-impl is no longer valid as show in the pop up notification in the original comment. Least intrusive change to me was to use import("@devfile/api") where needed but honestly not familiar enough with the technologies to know the actual implications of making that change.

[vitaliy-guliy]

Update

git show 5695c8cb9cb085632fbde0beef950421c9b95af0 > /tmp/my-changes.patch
git apply /tmp/my-changes.patch