Skip to content
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.

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

chore: Upgrade msw to 2.7.0 (and Node.js to 22.13.1) in /ui #4995

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

peruukki
Copy link
Contributor

What this PR does / why we need it:

The main purpose was to upgrade msw from 0.36.8 to 2.7.0, to get rid of the security alerts of the old version. The upgrade turned out to be quite difficult, and in the end I also had to upgrade Node.js from 20 to 22, see more below.

Which issue(s) this PR fixes:

No specific issue for this, but the idea for the upgrade originated from #4451.

Misc

I only got the tests to pass with this combination of other dependencies:

  • test running environment: @happy-dom/jest-environment
    • jsdom (the default) or jest-fixed-jsdom (suggested in many places around the internet) neither worked due to various different errors.
  • Node.js version: 22
    • I don't have an explanation, but with Node 20 the tests often fail to navigate to other pages, without visible errors, though sometimes the tests do pass. I saw the same failing behavior in other running environments than @happy-dom/jest-environment too, but in those there were also some visible errors. With Node 22, the tests seem to run notably faster, which might be related.
    • Version 22 has been in long-term support for quite a while now, so it's good to move to it anyway.

The main purpose was to upgrade msw from 0.36.8 to 2.7.0, to get rid of
the security alerts of the old version. The upgrade turned out to be
quite difficult, and in the end I only got the tests to pass with this
combination of other dependencies:

- test running environment: @happy-dom/jest-environment

    - jsdom (the default) or jest-fixed-jsdom (suggested in many places
      around the internet) neither worked due to various different
      errors.

- Node.js version: 22

    - I don't have an explanation, but with Node 20 the tests often fail
      to navigate to other pages, without visible errors, though
      sometimes the tests do pass. I saw the same failing behavior in
      other running environments than @happy-dom/jest-environment
      too, but in those there were also some visible errors. With Node
      22, the tests seem to run notably faster, which might be related.

    - Version 22 has been in long-term support for quite a while now, so
      it's good to move to it anyway.

Signed-off-by: Harri Lehtola <[email protected]>
@peruukki peruukki requested a review from a team as a code owner January 31, 2025 07:26
@franciscojavierarceo
Copy link
Member

Hey @peruukki have you had issues loading project configs? We had someone report issues with the UI since the 0.40 release: #4981

@peruukki
Copy link
Contributor Author

peruukki commented Feb 1, 2025

Hey @peruukki have you had issues loading project configs? We had someone report issues with the UI since the 0.40 release: #4981

I have only used the sample projects in the repository, and actually the Empty Registry there fails to load. But as far as I remember, it has always been like that for me, and I assumed it was expected since the project is indeed totally empty. 😄

empty-project-fails-to-load

@tchughesiv
Copy link
Contributor

@franciscojavierarceo @peruukki that issue has been resolved for dev builds and will be fully resolved with the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants