Uploaded image for project: 'Compass '
  1. Compass
  2. COMPASS-5080

Should we .gitignore package-lock.json files and only create them when we release?

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • No version
    • Affects Version/s: None
    • Component/s: Tech debt
    • Labels:
      None
    • Not Needed

      We could include the shrinkwrap along with the package we publish to npm and maybe include it with the tag. Or as a release artifact. Not sure what's the best way but micromanaging it along with our PRs is a bit tedious. Especially for libraries. Don't we only really need them when installing top-level dependencies?

            Assignee:
            Unassigned Unassigned
            Reporter:
            leroux.bodenstein@mongodb.com Le Roux Bodenstein
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: