[
https://issues.apache.org/jira/browse/FLAGON-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Poore reassigned FLAGON-398:
-----------------------------------
Assignee: (was: Rob Foley)
> Update NPM release via registry
> -------------------------------
>
> Key: FLAGON-398
> URL: https://issues.apache.org/jira/browse/FLAGON-398
> Project: Flagon
> Issue Type: Task
> Components: release_scripts, UserALE.js
> Affects Versions: Flagon 1.0
> Reporter: Joshua Poore
> Priority: Blocker
> Fix For: Flagon 1.0
>
>
> NOTE: belongs in
> [https://github.com/apache/incubator-flagon/tree/FLAGON-344/release]
> Our NPM distro on registry is poor:
> # distribution doesn't contain pre-build userale scripts (+min) in /build
> dir or as 'files': [https://docs.npmjs.com/files/package.json]
> #
> [https://github.com/apache/incubator-flagon-useralejs/blob/master/build/userale-1.0.0.js]
> (not-minified script) has a function (exports) flag, however, unclear if
> this exposes functions in prebuilt useralejs script via npm. Would be
> convenient if we could package this file, so that npm users could invoke
> functions from a single 'require' call, rather than having to require
> different src files to find the functions they want exposed. See
> [https://docs.npmjs.com/files/package.json] for examples of different include
> strategies for npm modules including single vs. multiple src files.
> # We have no examples for usage. Generally, our API is great and users of
> npm distro don't need to invoke important functions via npm (e.g., .filter,
> .map, attachHandler). Even so, it would be good to have at least an
> attachHandler example for userale usage via npm.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
