I haven't done an npm publish from it yet, but in theory it would work. The thing that's most notable and least intuitive (needs documentation) is the browserify plugin shipping with annotator now. Using `browserify -p annotator` causes any require calls for "annotator" will resolve to a namespace shim that will find annotator in AMD, CommonJS, or the global scope.
See the Makefile in annotator-annotateit for a complete command line which builds the plugin bundle the same way the core plugins are built, which results in a UMD module that should work in any environment. On Apr 22, 2014 10:27 PM, "Randall Leeds" <[email protected]> wrote: > openannotation/annotator-annotateit > On Apr 22, 2014 8:42 PM, "Kristof Csillag" <[email protected]> wrote: > >> Hi, >> >> Is there an example project somewhere which showcases how to properly >> package a plugin for Annotator, which lives in an independent >> repository, and is released via npm / browserify independently of the >> upstream project? >> >> I am talking about an example that showcases the required settings for >> the whole toolchain. >> >> Thank you: >> >> Kristof >> >> _______________________________________________ >> annotator-dev mailing list >> [email protected] >> https://lists.okfn.org/mailman/listinfo/annotator-dev >> Unsubscribe: https://lists.okfn.org/mailman/options/annotator-dev >> >
_______________________________________________ annotator-dev mailing list [email protected] https://lists.okfn.org/mailman/listinfo/annotator-dev Unsubscribe: https://lists.okfn.org/mailman/options/annotator-dev
