Expose SLPJS completely

[jcramer]

Some applications may need to access additional methods that are not wrapped by SLP-SDK. For these use cases, it would be useful to expose the whole SLPJS.

I've seen other users have this same request, and I've come across this in consuming SLP-SDK myself.

[christroutner]

What is the pro/con of including slpjs with SLP-SDK vs the developer requireing the slpjs separately in their application?

[jcramer]

Pros:

• Same version of SLPJS can be accessed, don't have to worry about type/feature mismatch with whatever version SLP-SDK is using
• SLP-SDK is a Software Developers Kit and therefore should be the one stop shop for gaining access to all SLP related code (and recommended libraries associated with SLP)

Cons:

• ?

[Ekliptor]

I'm also for exposing SLPJS completely.

A possible con is that WebPack Tree Shaking will have less code to eliminate https://webpack.js.org/guides/tree-shaking/
But seeing that a minified bundle.js of slp-sdk v4.4.0 which just exposed the SDK is already 1.28 MB (see code below), it seems to me there is little code to eliminate either way.

import * as SLP from "slp-sdk";
window.SLP = SLP;