The suggested action here is to create a JavaScript package, installable via npm, that would be parallel to firefly_client for Python - that is, a refactoring of only the APIs for invoking actions on a remote Firefly session into a separate package.  The installation and use of this package would not load the whole of Firefly and would not result in a Firefly application or any of the visual elements of Firefly appearing in the browser in which the APIs were called.

The purpose of this package is to facilitate writing an interface from JupyterLab to a Firefly session running in a separate browser window.

Note that it is related to the project in DM-11528 of making the whole of Firefly npm-installable to facilitate the use of the Firefly visual components in the JupyterLab environment.  It may be more efficient to address both tickets simultaneously; Trey Roby may want to chime in on that.

Both ways of working ("next to" JupyterLab and "in" JupyterLab) may be desirable.