Model inheritance chain causes associations to throw an error

What you are doing?

class MyBaseModel extends Model {
  ...
}

class MyActualModel extends MyBaseModel {
  ...
}

class MyOtherModel extends MyBaseModel {
  ...
}

MyActualModel.hasMany(MyOtherModel)

What do you expect to happen?

I expected this to not throw an error.

What is actually happening?

MyActualModel.hasMany called with something that's not a subclass of Sequelize.Model

It looks like the instanceof check on line 12 of mixin.js is a little too strict and should just be !(target instanceof this.sequelize.Model). Right now it’s checking target.prototype instead of just target.

Dialect: any Database version: N/A Sequelize version: 4.8.0

[jimsimon]

@jawadakram20 I didn’t fix the issue and I ended up not using Sequelize.

[nbkhope]

@peabnuts123 I have a project that defines some models as a separate npm package. When I import those models in my project and start my application, I get an error when it calls .associate:

Error: ModelNameGoesHere.hasMany called with something that's not a subclass of Sequelize.Model

ModelNameGoesHere is a model that is defined in a separate npm package. That is, it comes from

import ModelNameGoesHere from 'some-separate-npm-package'

When I copy the code from the package into my application, the problem goes away.

Is there any solution to this?