Spike: investigate best way to handle optional 3rd party dependencies

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • 3
    • Not Needed
    • None
    • Not Needed
    • None
    • None
    • None
    • None
    • None
    • None

      We should investigate how optional vs peer dependencies are handled in the different package managers (npm, yarn, deno).

      We need to outline the pros/cons of each way of specifying the dependency alongside a plug-in approach (more like we do with our own add-on packages, such as kerberos), and pick a consistent way to move forward for our credential auth.

            Assignee:
            Neal Beeken
            Reporter:
            Daria Pardue
            Daria Pardue
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: