conversejs / converse.js

Web-based XMPP/Jabber chat client written in JavaScript
http://conversejs.org
Mozilla Public License 2.0
3.04k stars 763 forks source link

Cannot blacklist modules when in dev.html #3388

Open fenix011 opened 2 months ago

fenix011 commented 2 months ago

Describe the bug

while in the dev.html file / environment, i just change the websockets defaults, XMPP now being served via BOSH. And 'fullscreen' to 'overlay' view_mode too. This works fine so far. Then i just add a blacklisted_plugins section :

    converse.plugins.add('converse-debug', {
        initialize () {
            const { _converse } = this;
            window._converse = _converse;
        }
    });

    converse.initialize({
        i18n: 'af',
        theme: 'dracula',
        auto_away: 300,
        enable_smacks: true,
        loglevel: 'debug',
        prune_messages_above: 100,
        message_archiving: 'always',
        muc_respect_autojoin: true,
        muc_show_logs_before_join: true,
        view_mode: 'overlay',
        whitelisted_plugins: ['converse-debug'],
        // connection_options: { worker: '/dist/shared-connection-worker.js' }
    bosh_service_url: 'https://myxmppserver.info:5281/http-bind',

    blacklisted_plugins: [
         'converse-controlbox',
         'converse-rosterview'
     ]

    });

and the web browser goes 'blank page' but the Converse logo.

To Reproduce Steps to reproduce the behavior:

  1. just add the mentioned 'blacklisted_plugins' section con converse.initialize in dev.html
  2. launch 'make serve && make watch'
  3. go the web browser
  4. See Screenshot below

Expected behavior I would expect Converse dev.html render in the browser

Screenshots

converse-issue

Environment (please complete the following information):

Additional context

Adding this particular 'blacklisted_plugins' section is not causing problems when not in dev. environment but applied in 'production' and getting Converse.js from the CDN