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.

Sign up for GitHub

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

Jump to bottom

(Spike) Investigate switching from yarn v1 to npm v8 or yarn v3 #2716

Closed
jpveooys opened this issue Oct 19, 2021 · 3 comments
Closed

(Spike) Investigate switching from yarn v1 to npm v8 or yarn v3 #2716

jpveooys opened this issue Oct 19, 2021 · 3 comments
Assignees
@jpveooys
Labels
Size: Medium Assessed as medium task Type: Dependencies Issues that relate to a dependency Type: Development Related to a design system component

Comments

@jpveooys
Copy link
Collaborator

jpveooys commented Oct 19, 2021 •
edited
Loading

Description

Spike to investigate migrating from yarn v1 to npm v8 or yarn v3

Yarn v1 is now only receiving security fixes and so isn't a good long-term option for us.

npm now has support for workspaces so may be able to migrate to it.
@jpveooys jpveooys added Type: Enhancement New feature or request Type: Dependencies Issues that relate to a dependency Status: Needs discussion Issue requires discussion before it can be progressed Type: Development Related to a design system component and removed Status: Needs discussion Issue requires discussion before it can be progressed labels Oct 19, 2021
@m7kvqbe1 m7kvqbe1 added Size: Medium Assessed as medium task and removed Status: Needs discussion Issue requires discussion before it can be progressed labels Oct 20, 2021
@github-actions
Copy link

This issue has been marked as stale because it has been open for 60 days with no activity

@github-actions github-actions bot added the Status: Stale Issue with no activity for the past 60 days label Dec 20, 2021
@jpveooys jpveooys changed the title (Spike) Investigate switching from yarn v1 to npm v7/v8 (Spike) Investigate switching from yarn v1 to npm v7/v8 or yarn v3 Mar 2, 2022
@jpveooys jpveooys changed the title (Spike) Investigate switching from yarn v1 to npm v7/v8 or yarn v3 (Spike) Investigate switching from yarn v1 to npm v8 or yarn v3 Mar 2, 2022
@jpveooys jpveooys removed the Type: Enhancement New feature or request label Mar 14, 2022
@jpveooys jpveooys self-assigned this Mar 14, 2022
@jpveooys
Copy link
Collaborator Author

I've added notes from the spike here: https://gist.github.com/jpveooys/c6a1ba37395744d92a92df2b888f9532

@jpveooys jpveooys removed the Status: Stale Issue with no activity for the past 60 days label Mar 16, 2022
@jpveooys jpveooys mentioned this issue Mar 17, 2022
Closed
@jpveooys jpveooys mentioned this issue Mar 17, 2022
Merged
5 tasks
@jpveooys
Copy link
Collaborator Author

Closing this – findings outlined in the linked gist. We'll look to migrate to npm once some outstanding problems are resolved.

@jpveooys jpveooys mentioned this issue May 3, 2022
Closed
@m7kvqbe1 m7kvqbe1 moved this to Done in Tactical Board Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jpveooys jpveooys

Labels
Size: Medium Assessed as medium task Type: Dependencies Issues that relate to a dependency Type: Development Related to a design system component
Projects
Tactical Board
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@m7kvqbe1 @jpveooys