TypeError: resolver is not a function

Question

I am attempting to create a basic post on click in my NextJS app to a MongoDB database. The issue i am getting is TypeError: resolver is not a function. I understand it might be a syncronicity issue but for the life of me I cannot figure out where.

Stack used: NextJS, Axios, Mongoose.

Component code snippet calling axios:

i know the states are updating so i am putting only the snippet that handles the request

  handleSubmit = async (e: any) => {
    e.preventDefault();

    await axios
      .post('/api/roomSession', {
        roomName: this.state.roomName,
        teamName: this.state.teamName
      })
      .then((response: any) => console.log('axios call reached', response))
      .catch((error: any) => console.log('---- error! ----', error));
  };

[...]
<button onClick={this.handleSubmit}>Create</button>
[...]

NextJS API file:

import { newSession } from '../../packages/backend/mongo/connection';

const apiNewSession = async (roomName, teamName) => {
  await newSession(teamName, roomName);
};

export default apiNewSession();

Mongoose file:

const mongoose = require('mongoose');

mongoose
  .connect(
    'mongodbconnection',
    { useNewUrlParser: true, useUnifiedTopology: true }
  )
  .then(() => {
    console.log('connected to mongoDB');
  })
  .catch(err => console.error('Connection failed: ', err));

  const sessionSchema = new mongoose.Schema({
    teamName: String,
    roomName: String
  });

const Session = mongoose.model.tests || mongoose.model('tests', sessionSchema);

export const newSession = async (teamName, roomName) => {
  const session = new Session({
    teamName,
    roomName
  });
  const result = await session.save();
  mongoose.connection.close();
};

Some extra info on the strange behaviour: When first time called, the code throws the aformentioned error but manages to reach the mongoDB connection and creates an EMPTY entry inside the collection (only _id, and _v). Upon second attempt, only the error is thrown.

Alan W. Smith · Accepted Answer · 2022-08-08 00:05:21Z

92

I was exporting the function incorrectly from the NextJS API file.

Correct method: export default apiNewSession;

Not sure why it still happened when when i was exporting the function by default.

edited Aug 8, 2022 at 0:05

Alan W. Smith

25.6k5 gold badges73 silver badges101 bronze badges

answered Feb 16, 2020 at 15:36

Valentin

1,5111 gold badge12 silver badges15 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

sudhee_bsp Over a year ago

You can also try - export default async function apiNewSession; It works in case you wanted to export async function.

Mohsen Over a year ago

+2 so far... ;)

Patrick Michaelsen Over a year ago

Man, they really could have written a better error message for that.

Ben Winding · Accepted Answer · 2022-07-13 11:03:21Z

5

My problem was that I was defining a middleware function incorrectly...

This is okay

/* pages/api/endpoint.js */
export default MiddleWare(handler)

But middleware functions shouldn't be async...

async function MiddleWare(handler) {
// ^ remove this!
  return async function (req, res) {
    // some async stuff
    next(req, res);
  }
}

answered Jul 13, 2022 at 11:03

Ben Winding

12k5 gold badges93 silver badges80 bronze badges

Collectives™ on Stack Overflow

TypeError: resolver is not a function

2 Answers 2

3 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

3 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related