Skip to content
  • NodeBB 3.6.0 minimum NodeJS version.

    NodeBB Development
    11
    3 Votes
    11 Posts
    1k Views
    barisB
    Will downgrade sharp to 0.32.6 and release a new patch version since we received other reports of the sharp error.
  • Dropping support for nodejs 14 in NodeBB 3.x

    NodeBB Development
    1
    4 Votes
    1 Posts
    248 Views
    barisB
    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
  • Can't start after update nodejs/npm

    Solved Technical Support
    4
    0 Votes
    4 Posts
    3k Views
    AntosikA
    @mroczny No, in the previous update, a redis package was replaced via ioredis package. And that change is broke your configuration. Related PR: https://github.com/NodeBB/NodeBB/pull/9545
  • 0 Votes
    2 Posts
    462 Views
    PitaJP
    This isn't a forum for node.js help. It's the community forum for NodeBB, a node.js based forum software.
  • What version of NodeJS is now supported?

    General Discussion
    11
    0 Votes
    11 Posts
    4k Views
    julianJ
    Always best to, just in case I believe socket.io will need to rebuild its binaries.
  • 0 Votes
    6 Posts
    3k Views
    TelokisT
    @Bri Yes there are solutions like Microsoft's vcpkg or even cppan. But my tool would be more like a deployment complement: you would generate your binaries for the end user to download them but also an amalgamated version in case they want to use the quick n easy way. One thing I'd like to setup if this happens to be successful would be a cloud service which would allow to easily amalgamate your project.
  • Anybody using ES6 yet?

    General Discussion
    13
    1 Votes
    13 Posts
    6k Views
    SuperMikeS
    Just using function syntactic sugar var hello = (name) => {....} And this makes code clear in async flow async.waterfall([ (next) => { next(err, 'name') }, (name, next) => { next(err, 'final') } ], callback)
  • Learn Nodejs

    NodeBB Development
    5
    1 Votes
    5 Posts
    2k Views
    julianJ
    Just practice -- just build things. I have my coisin-in-law (is that a real term?) learning Node.js via Tessel, even though: It's kind of expensive They don't use NodeBB to power their forums Try nodeschool. If you respond well to it, then keep using it. The key is to find programming fun and gain that sense of accomplishment.
  • 0 Votes
    5 Posts
    3k Views
    frissdiegurkeF
    You know (one of) the main difference(s) between TCP and UDP, don't you? TCP is connection-oriented, UDP isn't. So there is no UDP core-functionality to check whether the receiver is alive (/has the port opened). You'd either need to create server-side code or know the server-behavior (e.g. responses to specific datagrams) to achieve an UDP port-scanner. If you're able to write server-side code the best is to ask for UDP port status via TCP since it has reliable data-transfer implemented.
  • 0 Votes
    1 Posts
    2k Views
    K
    Well, I have this issue that I need to do following things: 1.Mongo Find 2. Foreach 3. MongoFind 4 one more Foreach. because of asynchronaus mongo calls it is difficult to get proper result, however process.nextTick should handle this problem and still I have problem: function find(dbComm) { dbComm.forEach(function (current) { id= parseFloat(current.ID); db.anotherCollection.find({ ID: id}, function (error, result) { result.forEach(function (rank) { if (parseFloat(result.ID) == parseFloat(current.ID)) { rank.rank = 'Some calculations'; } }); }); }); } app.get('/someparams', function (req, res) { db.collection.find().sort({ "rank": order }).skip(pagenumber).limit(5, function (err, result) { process.nextTick(function () { find(result, function () { }) }); process.nextTick(function () { res.send(result); }); }); And on client side I should recive an array where the rank equals 'Some Calculations' but unfortunetly it is not... However...! If I add setTimeout(function(){}) before res.send(result) (and res.send(result) will be placed inside setTimeout) it actually does work and on client side I recive data with "Some Calculations" but it is just timeout and it fails sometimes and client dont recive "Some Calculations" if I put process.nextTick instead of setTimeout it doesnt work and "Some calc..." are not sent. Something is beeing done eralier then it should (probably in forEach in find() function) and my question is how to deal with it? maybe I should put process.nextTick in different function ?
  • NodeJS Help [Anyone that could help me]

    General Discussion
    4
    0 Votes
    4 Posts
    2k Views
    debianmasterD
    test tst test
  • Installation steps on Debian.

    General Discussion
    1
    1 Votes
    1 Posts
    1k Views
    A
    The current steps outline how to compile the package yourself, however, they do now have a version for the raspberry pi, well, up to 0.10.26 anyway. So might be worth changing the Debian NodeJS section with wget http://nodejs.org/dist/v0.10.26/node-v0.10.26-linux-arm-pi.tar.gz tar -xvzf node-v0.10.26-linux-arm-pi.tar.gz node-v0.10.26-linux-arm-pi/bin/node --version You should see: v0.10.26 NODE_JS_HOME=/home/pi/node-v0.10.26-linux-arm-pi PATH=$PATH:$NODE_JS_HOME/bin npm —version You should see: 1.4.3 Not sure if this helps or not..