Introducing the NodeBB 0.7.0 Persona preview

Moved NodeBB Development

Suggested Topics


  • 4 Votes
    1 Posts
    94 Views

    We will be dropping support for nodejs 14.x in nodebb 3.x.

    Nodejs 14 will be out of maintenance in april 2023 and some of our dependencies no longer support it.

    You can see nodejs release schedule here https://github.com/nodejs/release#release-schedule

  • 0 Votes
    4 Posts
    230 Views

    More specifically, the issue is that it defines a static directory in plugin.json:

    "staticDirs": { "s3": "public" },

    But doesn't have it.

    It seems to be an artifact of people forking and updating it without fully understanding what exactly it was doing - looking back at some history at some point someone moved the templates from public/templates to just templates/ and apparently NodeBB wasn't enforcing that directories have to exist at that point, so it wasn't noticed and all future forks inherited this bug.

    NodeBB is IMO doing fine here - a lack of directory a plugin declared to have might suggest some issue with the installation or the plugin itself (for example a typo in a path). A plugin incorrectly declaring something it doesn't use can't really be distinguished from these issues.

    Also, @julian while .gitignore works, I feel like it's a bit of abuse of that feature and the name is misleading (upon seeing a directory with .gitignore my first thought would be that something is supposed to go there but will be ignored. And I feel without knowing much about git I might've assumed it meant the whole directory would be ignored by git - the opposite of what it actually does). I personally prefer the convention of using an empty file named .gitkeep (or just .keep), since it more obviously refers to keeping the directory and wouldn't have any other potential impact on files included by git.

    EDIT: TL;DR of the issue:
    why would nodebb do this

  • 0 Votes
    6 Posts
    1k Views

    @pitaj said in Setting up a nodebb development environment:

    grunt isn't installed globally by default, so run npm i -g grunt then it will work

    Thank you. Once I installed it I could just run grunt and it worked.

    It still takes almost 30 seconds to build, but at least it's automatic.

    This is probably something seasoned nodejs devs know, n00bs like me not so much.

    Would someone mind updating the documentation since nodebb watch doesn't work anymore?

  • 13 Votes
    34 Posts
    18k Views

    @Ribesg said:

    That's because there are far too many bugs.

    Where's my banhammer... :trollface: