dependencies.rst 4.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100
  1. .. raw:: html
  2. <div id="banner"><a href="https://github.com/jcbrand/converse.js/blob/master/docs/source/theming.rst">Edit me on GitHub</a></div>
  3. ============
  4. Dependencies
  5. ============
  6. Installing the 3rd party dependencies
  7. =====================================
  8. We use development tools which depend on Node.js and npm (the Node package manager).
  9. If you don't have Node.js installed, you can download and install the latest
  10. version `here <https://nodejs.org/download>`_.
  11. Alternatively you can `use your operating system's package manager to install
  12. Node.js <https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions>`_.
  13. Also make sure you have ``Git`` installed. `See here <http://git-scm.com/book/en/Getting-Started-Installing-Git>`_.
  14. Now use ``git`` to check out the Converse repository:
  15. ::
  16. git clone https://github.com/conversejs/converse.js.git
  17. Now go into the repository checkout and run ``make dev`` in order to set up the
  18. development environment.
  19. ::
  20. cd converse.js
  21. make dev
  22. If you're using Windows, or don't have GNU Make installed, you can run the
  23. following:
  24. ::
  25. cd converse.js
  26. npm install
  27. npm run lerna
  28. This will install the Node.js development tools and Converse's dependencies.
  29. The front-end dependencies are those JavaScript files on which
  30. Converse directly depends and which will be loaded in the browser as part of
  31. the bundle in ``dist/converse.js`` (or ``dist/converse.min.js``).
  32. To see the 3rd party dependencies (not just the front-end dependencies, but
  33. also ones necessary for development tasks like making builds), take a look at
  34. the list under the ``devDependencies`` in `package.json <https://github.com/jcbrand/converse.js/blob/master/package.json>`_.
  35. .. note::
  36. After running ```make dev```, you should now have a new *node_modules* directory
  37. which contains all the external dependencies of Converse.
  38. If this directory does NOT exist, something must have gone wrong.
  39. Double-check the output of ```make dev``` to see if there are any errors
  40. listed. For support, you can ask in our chatroom: `dicuss@conference.conversejs.org <xmpp:discuss@conference.conversejs.org>`_.
  41. If you don't have an XMPP client installed, follow this link to
  42. `conversejs.org <https://conversejs.org/fullscreen#converse/room?jid=discuss@conference.conversejs.org>`_
  43. where you can log in and be taken directly to the chatroom.
  44. Brief description of Converse's dependencies
  45. ===============================================
  46. Converse relies on the following dependencies:
  47. * `DayJS <https://github.com/iamkun/dayjs>`_ provides a better API for handling dates and times.
  48. * `Strophe.js <http://strophe.im/>`_ maintains the XMPP session, is used to
  49. build XMPP stanzas, to send them, and to register handlers for received stanzas.
  50. * `lodash <https://lodash.com/>`_ provides very useful utility functions.
  51. * `Skeletor <https://github.com/skeletorjs/skeletor/>`_, a `Backbone <http://backbonejs.org/>`_ fork
  52. which is used to model the data as Models and Collections and to create Views that render the UI.
  53. * `pluggable.js <https://github.com/jcbrand/pluggable.js>`_ provides the plugin
  54. architecture for Converse. It registers and initializes plugins and
  55. allows existing attributes, functions and objects on Converse to be
  56. overridden inside plugins.
  57. .. _`dependency-libsignal`:
  58. Libsignal
  59. ---------
  60. If you want OMEMO encryption, you need to load `libsignal
  61. <https://github.com/signalapp/libsignal-protocol-javascript>`_ separately in
  62. your page.
  63. For example::
  64. <script src="3rdparty/libsignal-protocol-javascript/dist/libsignal-protocol.js"></script>
  65. The reason libsignal needs to be loaded separately is because it's released
  66. under the `GPLv3 <https://github.com/signalapp/libsignal-protocol-javascript/blob/master/LICENSE>`_
  67. which requires all other dependent JavaScript code to also be open sourced under the same
  68. license. You might not be willing to adhere to those terms, which is why you
  69. need to decide for yourself whether you're going to load libsignal or not.