experimentalJustInTimeCompile is not shown as enabled under cy open > settings

[muratkeremozcan]

Current behavior

Trying out #29244, we add experimentalJustInTimeCompile under component property, but under app settings the feature is not shown as enabled. There is also no title or description under the experiment.

Desired behavior

The experimentalJustInTimeCompile shows as enabled under app settings, so we can confirm that things are working and an i18n description is present

Test code to reproduce

git clone git@github.com:muratkeremozcan/react-cypress-ts-vite-template.git
cd react-cypress-ts-vite-template.
yarn 

yarn cy:open-e2e # or ct

View Settings, and experimentalJustInTimeCompile.

Cypress Version

13.14.0

Node version

20

Operating System

macOS 14.6.1

Debug Logs

No response

Other

We can log out the object in console and see it there, but not in the app itself.

[jennifer-shehane]

@muratkeremozcan Thanks for reporting. Seems adding this to this view was overlooked. We'll get a fix out for it in the next release.

Let us know your feedback on the actual feature in this github discussion. I know you've been asking for help around this for a while.

[muratkeremozcan]

@muratkeremozcan Thanks for reporting. Seems adding this to this view was overlooked. We'll get a fix out for it in the next release.

Let us know your feedback on the actual feature in this github discussion. I know you've been asking for help around this for a while.

I am all over it, will report soon.

[muratkeremozcan]

@jennifer-shehane @AtofStryker

I tried this out locally in our app with 1.5k component tests.

Without the flag, the startup time was 2:10.
With it, down to 30 seconds. Fantastic improvement. This will save plenty time in CI.

I have to get the PR in to prove out CI is fine, but that should be fine.

[AtofStryker]

@jennifer-shehane @AtofStryker

I tried this out locally in our app with 1.5k component tests.

Without the flag, the startup time was 2:10. With it, down to 30 seconds. Fantastic improvement. This will save plenty time in CI.

I have to get the PR in to prove out CI is fine, but that should be fine.

CI might take a bit longer to run since we need to compile each spec before running, but there shouldn't be any chunk load errors present. If CI is more reliable, but ultimately takes longer to run, smart orchestration should be more effective here and throwing more parallel workers at the problem should ultimately reduce times as well as an option.

[muratkeremozcan]

@jennifer-shehane @AtofStryker
I tried this out locally in our app with 1.5k component tests.
Without the flag, the startup time was 2:10. With it, down to 30 seconds. Fantastic improvement. This will save plenty time in CI.
I have to get the PR in to prove out CI is fine, but that should be fine.

CI might take a bit longer to run since we need to compile each spec before running, but there shouldn't be any chunk load errors present. If CI is more reliable, but ultimately takes longer to run, smart orchestration should be more effective here and throwing more parallel workers at the problem should ultimately reduce times as well as an option.

Makes sense. Previously because of the set startup time, parallelization had diminishing returns.
Ex: Startup 2.5 mins, tests take 5 mins.

If we parallelized more, the 5 minutes would not reduce further.

Now the startup is 30 secs, but tests take about 8. So we can benefit more from parallelization.

[AtofStryker]

@muratkeremozcan Does the experiment show as enabled when you open via cy:open-ct? The experiment shows an enabled under CT but not under e2e since it is a CT only config when I run the reproduction.

[muratkeremozcan]

@muratkeremozcan Does the experiment show as enabled when you open via cy:open-ct? The experiment shows an enabled under CT but not under e2e since it is a CT only config when I run the reproduction.

You are correct. The focused scripts I have are actually doing a good job of isolating the flags per the test type, and I neglected actually checking the CT mode when enabling the CT-only relevant flag.
This flag is different to other experimental flags where you cannot enable it at base level.

Closing the issue. I will see myself out.

[cypress-bot]

Released in 13.14.1.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v13.14.1, please open a new issue.