Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6784947
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T17:03:48+00:00 2026-05-26T17:03:48+00:00

I think I’ve been suffering from a very strange bug. There might be something

  • 0

I think I’ve been suffering from a very strange bug. There might be something systematically broken with EventEmitter. Ever since I started using the once function things seem off.

The following lines of console output demonstrate what’s happening:

var EventEmitter = require('events').EventEmitter;
a = new EventEmitter();
a.on("bla", function() { console.log("perm");});
a.once("bla", function() { console.log("this is temp"); });
a.emit('bla');

You would expect both events to be called, but on my console the output is:

> a.emit("bla")
perm
perm
true

What’s going on??

I’ve also tried using the code in a script and that seemed to work but I’m getting the feeling that the once function is somehow responsible for the weird glitches on my server.

Anyone ever encountered this?

[Tested on versions 0.5.1 and 0.5.3]

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T17:03:48+00:00Added an answer on May 26, 2026 at 5:03 pm

    Works for me on 0.5.10. I’m pretty sure you typed something else than what you posted here – where could the second “perm” come from? Try it again.

    $ node
    > var EventEmitter = require('events').EventEmitter;
    > a = new EventEmitter();
    {}
    > a.on("bla", function() { console.log("perm");});
    { _events: { bla: [Function] } }
    > a.once("bla", function() { console.log("this is temp"); });
    { _events: { bla: [ [Function], [Object] ] } }
    > a.emit('bla');
    perm
    this is temp
    true
    >
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I think that asking this might be kind of silly but I'm still wondering
I think I have found a bug when setting or getting the Me.Top property
I think it will be very hard for you to read the code but
I think this has probably been asked, but after reading a lot, I'm not
I think I'm missing something basic here. Why is the third IF condition true?
Think of a window designed with Qt Designer. Lots of sub-widgets. There is a
I think there is a logical / mathematical solution to this problem and I
I think that I have a quite strange question. I am using a class
I think I'm missing something basic here. Any explanation or pointers to previously asked
I think I've stumbled upon a bug in the .NET (or the native windows

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.