Uploaded image for project: 'Stripes'
  1. Stripes
  2. STRIPES-679

SPIKE: investigate yarn v2 vs npm v7

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Priority: P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Template:
    • Development Team:
      Stripes Force

      Description

      yarn v1.0 is effectively abandon-ware. Migrating to v2.0 might be easy, the docs note:

      The best way to migrate is just to upgrade Yarn and see whether everything works. If it doesn't, go back to this guide and look for more context on the error you got. Most steps here aren't needed for most projects - we just tried to document all the tips that you could find handy if something breaks!

      Even if it is easy, it should still be a deliberate decision and we should at least investigate alternatives such as npm 7. We lean heavily on yarn features such as workspaces, but yarn may no longer hold a monopoly on such features. Some of our tooling used to (and may still) rely on finding things in node_modules directories, which may go away in yarn v2, but maybe that tooling itself was based on old yarn alias handling which itself could be ripped out now that we have reliable workspaces.

      The point is just this: we can't stay on yarn v1 forever and we should do some research.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                zburke Zak_Burke
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases