Details

    • Type: Story
    • Status: Closed
    • Priority: Minor
    • Resolution: Completed
    • Affects Version/s: None
    • Fix Version/s: Master
    • Labels:
      None

      Description

      Currently, metal dependencies are used freely throughout portal without too much care of which versions are installed and which versions are actually used.

      The goal of this story is to consolidate:

      • Fixed versions of all dependencies in `frontend-js-metal-web`
      • Same versions of all dependencies used in different bundles
      • SF rule to enforce no other versions are used in the future

      In general, because of how we assemble our frontend code, only one version of some modules will be running at the same time in runtime and it will usually be (and should be) shared among all modules. These dependencies are:

      • clay and all clay-*
      • metal and all metal-*
      • senna

      So, to start, we'd need a rule to check that:

      1. In a package.json
      2. In the dependencies block
      3. The versions of some dependencies match those in a given list:
        1. `clay` and `clay-*` package versions should match those specified in frontend-taglib-clay/package.json
        2. `metal` and `metal-*` package versions should match those specified in frontend-js-metal-web/package.json
        3. `senna` package versions should match that specified in frontend-js-spa-web/package.json

      In the future, we might extend that list to other modules.

        Attachments

          Activity

            People

            • Assignee:
              jose.balsas Chema Balsas
              Reporter:
              jose.balsas Chema Balsas
              Recent user:
              Chema Balsas
              Participants of an Issue:
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: