Skip to content

Conversation

bhorai-atl
Copy link
Collaborator

@bhorai-atl bhorai-atl commented Sep 24, 2025

What Is This Change?

Migrated the project from npm to Yarn v4 (Berry) for improved dependency management, better performance, and enhanced developer experience.

  • Replaced package-lock.json with yarn.lock
  • Added .yarnrc.yml configuration
  • Set packageManager: "yarn@4.10.3" in package.json
  • Configured nodeLinker: node-modules for VS Code extension compatibility
  • Updated all npm commands to yarn equivalents (package.json, pre-commit hook, Dockerfile, GitHub actions workflows)

How Has This Been Tested?

Basic checks:

  • All unit tests passing
  • Build compiles successfully without warnings
  • Extension packaging works correctly

Recommendations:

  • Update the CHANGELOG if making a user facing change

@bhorai-atl bhorai-atl force-pushed the AXON-1209-move-to-yarn branch from c38a936 to 50ca720 Compare September 24, 2025 12:11
@bhorai-atl bhorai-atl force-pushed the AXON-1209-move-to-yarn branch 2 times, most recently from fdd8586 to 0b2971f Compare October 3, 2025 09:35
@bhorai-atl bhorai-atl self-assigned this Oct 3, 2025
@bhorai-atl bhorai-atl changed the title AXON-1209 move to yarn AXON-1209: Migration: npm → yarn v4 (Berry) Oct 3, 2025
@bhorai-atl bhorai-atl changed the title AXON-1209: Migration: npm → yarn v4 (Berry) AXON-1209: Migration: npm → Yarn v4 (Berry) Oct 3, 2025
@bhorai-atl bhorai-atl force-pushed the AXON-1209-move-to-yarn branch from 325c1a6 to 15a2f41 Compare October 3, 2025 14:46
@bhorai-atl bhorai-atl marked this pull request as ready for review October 3, 2025 14:47
om-ukr
om-ukr previously approved these changes Oct 3, 2025
@bhorai-atl bhorai-atl force-pushed the AXON-1209-move-to-yarn branch from 15a2f41 to 04cca9a Compare October 3, 2025 16:31
@sdzh-atlassian
Copy link
Member

As a fellow yarn lover, I wholeheartedly welcome the change - but I would suggest that we not merge this for the next week, given the TEAM-related code freezes and the general caution advisory

@marcomura
Copy link
Collaborator

I'm not able to run the extension in debug mode with yarn:
image

Errors:

 *  Executing task: yarn run devcompile 

error This project's package.json defines "packageManager": "yarn@4.10.3". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.

 *  The terminal process "/bin/zsh '-l', '-c', 'yarn run devcompile'" terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it. 

@bhorai-atl
Copy link
Collaborator Author

bhorai-atl commented Oct 6, 2025

@marcomura Looks like you have Yarn 1.22.22 locally. Please enable Corepack and switch to Yarn 4.10.3 to run the "yarn run devcompile"

  1. npm i -g corepack
  2. corepack enable
  3. corepack prepare yarn@4.10.3 --activate
  4. yarn run devcompile

@bhorai-atl bhorai-atl changed the title AXON-1209: Migration: npm → Yarn v4 (Berry) [On Hold] AXON-1209: Migration: npm → Yarn v4 (Berry) Oct 6, 2025
@bhorai-atl bhorai-atl force-pushed the AXON-1209-move-to-yarn branch from e5f7cfc to 3ca2b3f Compare October 8, 2025 15:46
@bhorai-atl bhorai-atl changed the title [On Hold] AXON-1209: Migration: npm → Yarn v4 (Berry) AXON-1209: Migration: npm → Yarn v4 (Berry) Oct 8, 2025
@bhorai-atl bhorai-atl force-pushed the AXON-1209-move-to-yarn branch from 73368d5 to f52059e Compare October 8, 2025 20:15
@bhorai-atl bhorai-atl force-pushed the AXON-1209-move-to-yarn branch from 0be59db to 13310e2 Compare October 21, 2025 15:30
@bhorai-atl
Copy link
Collaborator Author

Hey @sdzh-atlassian, could you please take another look at this code?

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.

4 participants