Publish to NPM

[pacarvalho]

Duplicate of #43

Can you please publish this package to NPM?

1. Many client side applications have pipelines that are not designed to have ENVs in the HTML.
2. It makes for better code for the developers using your product to be able to yarn add your module and have a class instantiated that we can access.

Currently we rely on packages maintained by third parties for this purpose which increases the chances of having lagged versions.

You could even create a package that fetches the source code within it to solve the problem of breaking changes on your package stopping client applications from functioning.

[david-sharer]

Workaround for those willing to welcome cthulhu into their code base:

function evaluateAndExport<T>(code: string, exportedValue: string): T {
  return Function(`${code};\n\n;return ${exportedValue};`)();
}

// this gets the file in angular2+, adapt as needed
const fileText = await this.http.get('https://...../2.0/zaf_sdk.js', { responseType: 'text' }).toPromise();
const exportedValue = evaluateAndExport<ExportedZafClient>(fileText, 'ZAFClient');
const client = exportedValue.init();

[tyteen4a03]

Bump - we would like to be able to type hint in our code.

[kyleyee23]

+1

[devinmatte]

Any update on an NPM publish? There's https://www.npmjs.com/package/zendesk_app_framework_sdk which is a publishing an old version from a fork

[bkw]

2024 on still nobody cares. How sad.