Node.js 中的‘ TypeError: is not a function’

在 Node.js 中运行以下代码时出现错误

var assert = require('assert');
var request = require('request');
var index = require('./index');
it('verify javascript function', function(done) {
var v2 = index.AddNumbers(5, 6);
assert.equal(11, v2);
done();
});

index.js文件包含以下代码:

function AddNumbers(a,b){
return a+b;
}

我做错了什么?

138223 次浏览

With NodeJS modules, to make something public, you have to export it. Add this to the end of index.js:

module.exports.AddNumbers = AddNumbers;

(That's using the old CommonJS modules. For ESM, it would be export AddNumbers;)


Here it is running on my machine:

$ cat index.js
function AddNumbers(a,b){
return a+b;
}


module.exports.AddNumbers = AddNumbers;


$ cat example.js
var index = require('./index');
var v2 = index.AddNumbers(5,6);
console.log(v2);


$ node example.js
11

This happened to me many times because of circular dependency, check if you have 2 classes that are requiring each other, remove one of them from requiring the other and the issue should be solved

If you need to expose a specific component, function or a variable to public. You have to exports those components using JavaScript modules.

let add = (a,b)=>{
return ( a+b);
}
module.exports.add=add;

or if you want to expose multiple functions, you can do as follows.

let add = (a,b)=>{
return (a+b);
}
let subtract = (a, b)=>{
return (a-b);
}
module.exports={
add : add,
subtract : subtract
};

Your "AddNumbers" function in the "index.js" file should be as follows,

function AddNumbers(a,b){
var addition = function(a, b){
return (a + b) ;
};


module.exports = {
additionResult: addition
};
}

And you need to call it in your "Node.js" file as follows

var assert = require('assert');
var request = require('request');
var index = require('./index');
it('verify javascript function', function(done) {
var v2 = index.additionResult(5, 6);
assert.equal(11, v2);
done();
});

This should work. Please note that you call the function by whatever the token name you exported the return value by (I use a different name here just for clarity). Almost everybody uses the same name as the function name so there are no confusion. Also in ES6, if you use the same name you can export as just,

module.exports = {
addition
};

instead of,

module.exports = {
addition: addition
};

since you use the same name. It is an ES6 feature.

I'm fairly a beginner at Node JS so I managed to get this error by importing a function like so:

const { functionName } = require('./function')

instead of like so:

const functionName = require('./function')

Editing my post to add an explanation since I've learned more node since I wrote it. If a module exports an object containing multiple functions functions like so:

module.exports = { functionName, otherFunction }

Then the function has to be deconstructed out of the object during the import, as in the first code snippet. If the module exports a single function or a default function, like so:

 module.exports = functionName

Then tt must be imported directly, as in the second code snippet.

This is happening because two files are referencing each other i.e You are calling function (s) from file A in file B and vice versa which is called Circular Dependency.

One silly mistake I did was while exporting was:

module.exports = [module_name_1, module_name_2, ..., module_name_n]

The right way is:

module.exports = {module_name_1, module_name_2, ..., module_name_n}

I ran into the same problem while trying to follow a Nodejs tutorial by w3schools. I copied the following code from them:

exports.myDateTime = function () {
return Date();
};

That, however, wouldn't work for me. What resolved the problem for me was adding module. before the exports keyword like this:

module.exports.myDateTime = function () {
return Date();
};

A simple way I debugged this (After about 2 days of troubleshooting) was to actually see why 'x' is not a function. Basically, console.log(x) to see the actual object returned. Turned out I was conflicting x with another declared variable (happens especially when you use axios.res and req,res args.

just pass the function as an argument it will solve your Problem

now you can access the sample function without having to require it in sample2 file this solves the problem of typeError

//sample
const sample2 = require('./sample2');
const sample = async (payload) => {
const { value }= payload;
const response = sample2({sample});
}




// sample2
const sample2 = async ({sample}) => {
const response = sample({value});
}
module.exports = sample2;
  

https://medium.com/visual-development/how-to-fix-nasty-circular-dependency-issues-once-and-for-all-in-javascript-typescript-a04c987cf0de

this post visualizes the circular dependency injection like a child or nested file tried to import parent or top-level file

repo.js

service.js

there are 2 files

service.js uses repo.js file by importing it works but check in repo.js that it tried to import service.js file it shows circular dependency injection warning

The most correct answer was from @shimi_tap. I want to reply it as comment, but doesn't have enough reputation, so I am gonna answer it using a simple example, like in this case below:

  1. File A has 3 functions to process database activity: function addDB, updateDB, and delData;
  2. File B has 2 functions to process User activity on smartphone: function addHistory, and editHistory;

Function updateDB in file A is calling function editHis in file B, and function editHistory is calling function updateDB in file A. This is what we called circular-dependency. And we need to prevent it by only giving output of state from editHistory and the rest will be processed inside file A.

//ORIGINAL FUNCTIONS which caused CIRCULAR DEPENDENCY
function updateDB() {
//process update function here
//call function in fileB
const history = require("fileB.js");
await history.editHistory(data).then((output) => {
if(output["message"] === "success"){
response = {
state: 1,
message: "success",
};
}
});
return response;
}


//THIS is the WRONG ONE
function editHistory() {
//process function to edit History here
//call function in fileA
const file = require("fileA.js");
await file.updateDB(data).then((output) => { //You should not call it here
if(output["message"] === "success") {
output = {
state: 1,
message: "success",
};
}
});
return output;
}


//==================================================//
//THE FIX
function updateDB() {
//process function here
const history = require("fileB.js");
await history.editHistory(data).then((output) => {
if(output["message"] === "success"){
await updateDB(data).then((output) => {
response = {
state: 1,
message: "success",
};
});
} else {
log("Error");
}
});
return response;
}


function editHistory() {
//process function to edit History here
// No more calling to function inside the file A
output = {
state: 1,
message: "success",
};
return output;
}