Myujth

Thought I had this figured out yesterday, but I apparently did not and after another full day of trying to figure this out I'm asking for help again.

I have a module that is "installed" via npm link which is written in ES6. There is a class that I am exporting called Perishable. I have stripped down the class to the bare minimum are the issue still exists.

export default class Perishable 
 constructor() 

 

I am trying to extend the class, and I am doing so like this:

// Perishable is imported already and IS NOT NULL. 
export default class Apple extends Perishable 
 constructor() 
 super()
 

When calling new Apple() I get the following error: Class constructor Perishable cannot be invoked without 'new'

However, I can directly create a new Perishable class via new Perishable() without any problems.

To add onto this, copy+pasting the class into the same directory and importing it using a relative path allows me to properly call new Apple(). I believe this has to do with the way that webpack/babel is transpiling the symlinked class. This is what I get when inspecting the transpiled code: of the symlinked class

var Apple = function (_Perishable) 
 _inherits(Apple, _Perishable);

 function Apple() 

 return Apple;
(_idleEngine.Perishable);

This is what I get when I inspect the code of the local class (that works properly).

var Apple = function (_Perishable) 
 _inherits(Apple, _Perishable);

 function Apple() 

 return Apple;
(_Perishable3.default);

The only difference between the two generated codes is what's in the curlies at the end, one is (_idleEngine.Perishable) and one is (_Perishable3.default).

console.log(Perishable) returns the same thing for both types of imports, and new Perishable() works fine for both imports.

I should add that the symlinked class is imported via a npm link and the local class I just copy+pasted out of the library to be in the same folder as the Apple class.

EDIT: This seems to only be a problem with syslinked modules as publishing the module "fixed" the issue.