This repository has been archived by the owner. It is now read-only.

JS Uncaught TypeError #21

Closed
paulkeogh opened this Issue Dec 18, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@paulkeogh

paulkeogh commented Dec 18, 2015

Built from github.

I see the following error in the browser console;

Uncaught TypeError: (0 , u.default) is not a function (typeof.js:11)

and there is no diagram displayed.

@javallone

This comment has been minimized.

Show comment
Hide comment
@javallone

javallone Dec 18, 2015

Owner

What browser are you running?

Owner

javallone commented Dec 18, 2015

What browser are you running?

@paulkeogh

This comment has been minimized.

Show comment
Hide comment
@paulkeogh

paulkeogh Dec 21, 2015

Hi,

I am running Google Chrome 47.0.2526.106 (64 bit) on CentOS 6.5

Let me know if you want any more testing done.

Thanks,

On 18 December 2015 at 18:49, Jeff Avallone notifications@github.com
wrote:

What browser are you running?


Reply to this email directly or view it on GitHub
#21 (comment)
.

paulkeogh commented Dec 21, 2015

Hi,

I am running Google Chrome 47.0.2526.106 (64 bit) on CentOS 6.5

Let me know if you want any more testing done.

Thanks,

On 18 December 2015 at 18:49, Jeff Avallone notifications@github.com
wrote:

What browser are you running?


Reply to this email directly or view it on GitHub
#21 (comment)
.

@paulkeogh

This comment has been minimized.

Show comment
Hide comment
@paulkeogh

paulkeogh Dec 21, 2015

Same result on Firefox - Mozilla/5.0 (X11; Linux x86_64; rv:38.0)
Gecko/20100101 Firefox/38.0

On 18 December 2015 at 18:49, Jeff Avallone notifications@github.com
wrote:

What browser are you running?


Reply to this email directly or view it on GitHub
#21 (comment)
.

paulkeogh commented Dec 21, 2015

Same result on Firefox - Mozilla/5.0 (X11; Linux x86_64; rv:38.0)
Gecko/20100101 Firefox/38.0

On 18 December 2015 at 18:49, Jeff Avallone notifications@github.com
wrote:

What browser are you running?


Reply to this email directly or view it on GitHub
#21 (comment)
.

@javallone

This comment has been minimized.

Show comment
Hide comment
@javallone

javallone Dec 21, 2015

Owner

Thank you, I am seeing the same problem. It looks like it only happens when running the site locally (regexper.com isn't exhibiting the error). It may be due to some bad interaction between NPM deps that have seen updates since the last deployment. I'll be pushing a change to update versions shortly.

Owner

javallone commented Dec 21, 2015

Thank you, I am seeing the same problem. It looks like it only happens when running the site locally (regexper.com isn't exhibiting the error). It may be due to some bad interaction between NPM deps that have seen updates since the last deployment. I'll be pushing a change to update versions shortly.

@javallone javallone closed this in cff494a Dec 21, 2015

javallone added a commit that referenced this issue Dec 21, 2015

Removing babel-plugin-transform-runtime
It appears to be involved somehow with the JS errors from Issue #21.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.