Analyze js-dataverse module and decide whether to build on top of it or redo it from scratch

[GPortas]

Overview of the Feature Request

Since the early discussions about modularity in the Dataverse SPA, we suggested the idea of creating a Dataverse API Client module / library, which would encapsulate the Dataverse API access logic so that it can be reused by other applications other than the Dataverse SPA.

Currently there is already an npm module for this: https://www.npmjs.com/package/js-dataverse.
Actually, this module is not heavily used and is a bit old. We need to analyze it in more detail to decide whether to build on top of it and continue its evolution, or redo it from scratch considering the design and functionality that the module already provides.

What kind of user is the feature intended for?

Dataverse frontend developers

What inspired the request?

• MVP Strategy document: link
• New potential issues requiring connectivity to the Dataverse API

What existing behavior do you want changed?

N/A

Any brand new behavior do you want to add to Dataverse Frontend?

• API Client / Data Access Layer

Any related open or closed issues to this feature request?

• Add version number to bottom right of each page (e.g. v. 5.13 build 1244-79d6e57) #12

[GPortas]

After analyzing the js-dataverse package, the final decision is to reimplement the package from scratch. For more information, see: Analysis document