Uploaded image for project: 'HAL'
  1. HAL
  2. HAL-1478

Migrate from Bower to Yarn

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 3.0.3.Final
    • Component/s: None
    • Labels:
      None

      Description

      Bower is deprecated since last year and there's also official recommendation to migrate to Yarn [1]. Bower also doesn't support 'shrinkwrap' feature to lock dependencies [2]. Currently, there is no plan to add Bower support into PNC (Project NewCastle - internal Red Hat build system for Middleware, future replacement of MEAD). From the product perspective, we should migrate from deprecated or barely supported tools and dependencies to fully supported and perspective ones.

      Most of packages which are available via Bower registry should be also available via NPM registry. If there's a package which is available only via Bower registry and not via NPM registry, it's probably not going to be better maintained (or developed) in future. So it's better to find another one and migrate to it. If it's a Red Hat project we should recommend them to publish their bits to NPM registry.

      [1] https://bower.io/blog/2017/how-to-migrate-away-from-bower/
      [2] https://github.com/bower/bower/issues/505

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              harald.pehl Harald Pehl
              Reporter:
              harald.pehl Harald Pehl
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: