Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent behavior with module.exports and callback function in documentation example #202

Open
SebastianAviles opened this issue Sep 26, 2024 · 0 comments

Comments

@SebastianAviles
Copy link

I tried running a file as described in the documentation. Originally, my file looked like this:

module.exports = (callback, message) => {
    ...
    callback(null, message);
};

But when I ran it, it threw the error "module.exports is empty." I had to change my code like this:

function myfunction(callback, message) {
    ...
    callback(null, message);
}
exports { myfunction }

This worked, but now it throws an error saying that callback is not a function. So, I had to make the following change:

function myfunction(callback, message) {
    ...
    return message;
}
exports { myfunction }

This works, but it's completely different from the approach shown in the documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant