front: switch from yarn to npm

[Yohh]

close #9143

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.14%. Comparing base (83fbe09) to head (d443e01).
Report is 13 commits behind head on dev.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@             Coverage Diff             @@
##              dev    #9169       +/-   ##
===========================================
+ Coverage   37.82%   91.14%   +53.32%     
===========================================
  Files         994      773      -221     
  Lines       91103    82300     -8803     
  Branches     1176     1168        -8     
===========================================
+ Hits        34459    75015    +40556     
+ Misses      56190     7248    -48942     
+ Partials      454       37      -417     

Flag	Coverage Δ
editoast	?
front	99.18% <ø> (+79.06%)	⬆️
gateway	2.18% <ø> (ø)
osrdyne	3.28% <ø> (ø)
railjson_generator	87.49% <ø> (ø)
tests	86.74% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[emersion]

I had success running https://github.com/imsnif/synp

I think we'd be less likely to run into issues if we can use this tool instead of crossing fingers.

[emersion]

• Running npm install before renaming resolutions to overrides in package.json makes npm use @rtk-query/oazapfts-patched instead of our fork.
• Running npm install after renaming resolutions to overrides in package.json makes npm die with ".git can't be found" in husky install.
• Trying to upgrade oazapfts to the latest version won't work because it uses a monorepo and Git repo dependencies can't target a subdir.

[shenriotpro]

Thanks for the README update

[emersion]

Hm, why did the version constraints in package.json change? I'd expect the package.json to stay as-is except for the overrides rename.

[Yohh]

done

[emersion]

Hm, unless I'm missing something, I still see these package.json changes?

[Yohh]

are you sure your branch is up to date? I don"t see it anymore...

edit: ok I missed some packages

[Yohh]

done

[Khoyo]

[khoyo@odin osrd-hotfix]$ git grep yarn
front/README.md:- Install playwright dependencies `cd ./front/ && yarn playwright install --with-deps`
front/README.md:this script as you would to `yarn e2e-tests` or `yarn playwright test`.
front/docker/Dockerfile.playwright:COPY front/package.json front/yarn.lock /app/front/
front/docker/Dockerfile.playwright:RUN yarn install --frozen-lockfile
front/package-lock.json:        "yarn": "^1.7.0"
front/package-lock.json:        "yarn": ">=1"
front/package-lock.json:        "yarn": ">=1"
front/package-lock.json:        "yarn": "*"
front/package-lock.json:    "node_modules/yarn": {
front/package-lock.json:      "resolved": "https://registry.npmjs.org/yarn/-/yarn-1.22.22.tgz",
front/package-lock.json:        "yarn": "bin/yarn.js",
front/package-lock.json:        "yarnpkg": "bin/yarn.js"
scripts/run-front-playwright-container.sh:VERSION=$(yarn list --pattern playwright --json | jq -r '.data.trees[].name | split("@")[-1]' | sort -u)
scripts/run-front-playwright-container.sh:    osrd-playwright:latest yarn playwright test "${args[@]}"

The dependency in the lockfile is probably valid, the rest probably isn't.

[Yohh]

[khoyo@odin osrd-hotfix]$ git grep yarn
front/README.md:- Install playwright dependencies `cd ./front/ && yarn playwright install --with-deps`
front/README.md:this script as you would to `yarn e2e-tests` or `yarn playwright test`.
front/docker/Dockerfile.playwright:COPY front/package.json front/yarn.lock /app/front/
front/docker/Dockerfile.playwright:RUN yarn install --frozen-lockfile
front/package-lock.json:        "yarn": "^1.7.0"
front/package-lock.json:        "yarn": ">=1"
front/package-lock.json:        "yarn": ">=1"
front/package-lock.json:        "yarn": "*"
front/package-lock.json:    "node_modules/yarn": {
front/package-lock.json:      "resolved": "https://registry.npmjs.org/yarn/-/yarn-1.22.22.tgz",
front/package-lock.json:        "yarn": "bin/yarn.js",
front/package-lock.json:        "yarnpkg": "bin/yarn.js"
scripts/run-front-playwright-container.sh:VERSION=$(yarn list --pattern playwright --json | jq -r '.data.trees[].name | split("@")[-1]' | sort -u)
scripts/run-front-playwright-container.sh:    osrd-playwright:latest yarn playwright test "${args[@]}"

The dependency in the lockfile is probably valid, the rest probably isn't.

you're right, I removed the useless mentions in package-lock.json and updated the playwright script, thank you

[emersion]

The package-lock.json references should be retained. In general this file shouldn't be edited by hand. It has "yarn" references because some of our dependencies depend on yarn.