ERROR TypeError: sp is not a constructor

[kkotak]

ERROR TypeError: sp is not a constructor

[lathonez]

Hi Ketan, Please confirm you are using 2.4.0. Thanks, Stephen

…

On Fri, 7 Apr 2017 at 02:33, Ketan Kotak ***@***.***> wrote: Using with Angular4.x non AOT compile. Here's the stack trace myComponent.html:2843 ERROR TypeError: sp is not a constructor at SignaturePad.ngAfterContentInit (signature-pad.js:20) at callProviderLifecycles (core.es5.js:11046) at callElementProvidersLifecycles (core.es5.js:11027) at callLifecycleHooksChildrenFirst (core.es5.js:11011) at checkAndUpdateView (core.es5.js:12028) at callViewAction (core.es5.js:12340) at execEmbeddedViewsAction (core.es5.js:12312) at checkAndUpdateView (core.es5.js:12026) at callViewAction (core.es5.js:12340) at execEmbeddedViewsAction (core.es5.js:12312) at checkAndUpdateView (core.es5.js:12026) at callViewAction (core.es5.js:12340) at execComponentViewsAction (core.es5.js:12286) at checkAndUpdateView (core.es5.js:12031) at callViewAction (core.es5.js:12340) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#33>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AG5tSOEFX-UkXR3S-T2PwuK04jVgTxxtks5rtRPBgaJpZM4M12eO> .

[kkotak]

Yes. I'm using 2.4.0.

[lathonez]

Can you link to your repository or provide some other kind of repro?

…

On Sat, 8 Apr 2017 at 03:46, Ketan Kotak ***@***.***> wrote: Yes. I'm using 2.4.0. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#33 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AG5tSKYqKvcTG7Rq0qx0bElNCCDIQzy2ks5rtnZsgaJpZM4M12eO> .

[anhiliate]

Same issue reproduced by me too. Version is also 2.4.0. Code worked fine 3 days ago

[lathonez]

Hi, Could you link to your repository or provide some other kind of repro? The demo app is working fine on this version. What is the difference with your setup? Thanks

…

On Sun, 9 Apr 2017 at 08:31, Gonzo the Great ***@***.***> wrote: Same issue reproduced by me too. Version is also 2.4.0. Code worked fine 3 days ago — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#33 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AG5tSB13maN8Yx2bJGKh6ViA_0rn20ufks5ruAqrgaJpZM4M12eO> .

[anhiliate]

Hi Stephen,

thanks for your help and sorry for my stupid question.
I had my dependencies outdated. Clearing the node modules and 'npm install' get it working again.

Cheers,
Anh

[lathonez]

No worries, glad you got it sorted.

…

On Sun, 9 Apr 2017 at 10:39, Gonzo the Great ***@***.***> wrote: Hi Stephen, thanks for your help and sorry for my stupid question. I had my dependencies outdated. Clearing the node modules and 'npm install' get it working again. Cheers, Anh — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#33 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AG5tSPA5GCEJeeX-cr9NIUEtksBM7UrPks5ruCiygaJpZM4M12eO> .

[teresahoes]

Also clearing node_modules and doing npm install worked for me.. thanks!