nodebb-theme-custom is not in the npm registry

  • Here's a message from the output of ./nodebb upgrade.

    npm http 404
    npm ERR! 404 'nodebb-theme-custom' is not in the npm registry.
    npm ERR! 404 You should bug the author to publish it
    npm ERR! 404 It was specified as a dependency of 'nodebb'
    npm ERR! 404 
    npm ERR! 404 Note that you can also install from a
    npm ERR! 404 tarball, folder, or http url, or git url.

    So who's the author of nodebb-theme-custom that we should be bugging?

  • GNU/Linux Admin

    I don't know... but it sounds like you might have a folder in your node_modules called nodebb-theme-custom... so in essence, that'd be you as the author 😉

  • @julian

    Gawd, I hope not! How can I bug me?

  • GNU/Linux Admin

    In all honesty, though -- that's the kind of error you'd get if you "fork" a theme by copying an existing package to another folder... is that what happened? Because it is not published in the registry, npm can't get any info on it, and complains loudly. (I've never heard npm complain softly... 😞 )

  • @julian

    Most likely. But if that's what it is, I'm not going to bother about it. I don't have time to mess with templates at this time.

    Btw, I like the sound notifications. Does it work on mobiles as well?

  • GNU/Linux Admin

    Here is the documentation from the HTML5 audio library I use:

    NOTE: In order to save bandwidth, mobile devices don't load/play sounds without user intervention (no autoplay). iPhone and iPad can only play one sound at a time and don't allow to change the volume dynamically. iPad has some issues with multiple sounds on the same page.

    ... and I use .wav files, which the Android stock browser may not be so hot at parsing -- but Chrome should be fine.

Suggested Topics

| | | |