Skip to content
  • NodeBB 3.12.0

    NodeBB Development
    3
    +2
    4 Votes
    3 Posts
    127 Views
    DownPWD
    Very good ^^ Thank you all
  • 3.12.0 Upgrade Support

    Pinned Technical Support
    6
    0 Votes
    6 Posts
    98 Views
    codenamejessicaC
    Hey Guys, (sorry, cross posted, I will delete the other) I have installed NodeBB several times on different servers. Although since the 3.12 update, it seems there is something odd going on. ./nodebb setup Dependencies outdated or not yet installed. Installing them now... npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/config-array instead npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/object-schema instead npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported npm warn deprecated [email protected]: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. npm warn deprecated npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp) npm warn deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm warn deprecated [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options. added 883 packages, and audited 884 packages in 2m 110 packages are looking for funding run `npm fund` for details 1 moderate severity vulnerability Some issues need review, and may require choosing a different dependency. Run `npm audit` for details. OK 2024-12-20T17:11:03.298Z [5747] - info: NodeBB Setup Triggered via Command Line Welcome to NodeBB v3.12.0! This looks like a new installation, so you'll have to answer a few questions about your environment before we can proceed. Press enter to accept the default setting (shown in brackets). URL used to access this NodeBB (http://localhost:4567) https://jbrowns.com Please enter a NodeBB secret (b3008965-ca64-412b-803c-b63bcb7a99ec) Would you like to submit anonymous plugin usage to nbbpm? (yes) Which database to use (mongo) 2024-12-20T17:11:19.813Z [5747] - info: Now configuring mongo database: MongoDB connection URI: (leave blank if you wish to specify host, port, username/password and database individually) Format: mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]] Host IP or address of your MongoDB instance (127.0.0.1) localhost Host port of your MongoDB instance (27017) MongoDB username NodeBBDB Password of your MongoDB database MongoDB database name (nodebb) 2024-12-20T17:11:52.598Z [5747] - warn: NodeBB Setup Aborted. TypeError: Cannot read properties of undefined (reading 'hasOwnProperty') at completeConfigSetup (/opt/nodebb/src/install.js:203:21) at setupConfig (/opt/nodebb/src/install.js:189:8) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async install.setup (/opt/nodebb/src/install.js:583:3) at async Object.setup (/opt/nodebb/src/cli/setup.js:30:15) So, I thought I would switch to v3.11.1 by using with a success install: git clone -b v3.11.1 https://github.com/NodeBB/NodeBB.git . Something you may want to look into. Once I get this up and running, I may have a look as well. *EDIT: Forgot to mention, this was a clean install on an Ubuntu 24.04 VPS. Using a non-sudo user. *EDIT AGAIN: I think I found the issue. Line number 46 of setup.js in (src/cli) *EDIT AGAIN AGAIN: Ignore the last EDIT, that is coming after you setup an admin account. *EDIT AGAIN AGAIN AGAIN: I think it is here: const data = await install.setup(); I think the data is returning undefined. But I cannot be sure.