JavaScript Error for NodeBB V1.0.0 on Chrome browser latest version 55.



  • Hi ,
    @baris @julian @psychobunny
    For NodeBB V1.0.0 getting following JS error.
    Uncaught SyntaxError: Unexpected token function
    at /nodebb.min.js?bd1f194e-00b7-48d1-83ce-af6df8a63699:10
    at /nodebb.min.js?bd1f194e-00b7-48d1-83ce-af6df8a63699:10
    /src/modules/sounds.js?bd1f194e-00b7-48d1-83ce-af6df8a63699:11 Uncaught TypeError: Cannot read property 'on' of undefined
    at /src/modules/sounds.js?bd1f194e-00b7-48d1-83ce-af6df8a63699:11
    at Object.execCb (/nodebb.min.js?bd1f194e-00b7-48d1-83ce-af6df8a63699:9)
    at w.check (/nodebb.min.js?bd1f194e-00b7-48d1-83ce-af6df8a63699:9)
    at w.<anonymous> (/nodebb.min.js?bd1f194e-00b7-48d1-83ce-af6df8a63699:9)
    at /nodebb.min.js?bd1f194e-00b7-48d1-83ce-af6df8a63699:8
    at /nodebb.min.js?bd1f194e-00b7-48d1-83ce-af6df8a63699:9
    at z (/nodebb.min.js?bd1f194e-00b7-48d1-83ce-af6df8a63699:8)
    at w.emit (/nodebb.min.js?bd1f194e-00b7-48d1-83ce-af6df8a63699:9)
    at w.check (/nodebb.min.js?bd1f194e-00b7-48d1-83ce-af6df8a63699:9)
    at w.enable (/nodebb.min.js?bd1f194e-00b7-48d1-83ce-af6df8a63699:9)

    Please see this screenshot : http://screencast.com/t/vjlH6lL7

    On latest Chrome browser version 55 Js file under public/src loading seperately.
    Please refer screenshot : http://screencast.com/t/O0tlRSmJU

    Is there idea why these errors are getting introduced on latest version of Chrome only?
    Any help is appreciated!!


  • Admin

    NodeBB v1.0.0...? Is there possibly any chance you can upgrade to a newer version? 😟



  • @julian Thanks for the reply!

    Yes! We are using NodeBB v1.0.0.

    Is there any way to avoid loading JS file under public/src separately on chrome 55?


  • Community Rep

    @akumbhare the latest is 1.4.2. Can you upgrade?


  • Global Moderator

    On latest Chrome browser version 55 Js file under public/src loading seperately.

    This is not a bug AFAIK.



  • Thanks for the support!!
    @julian @Bri @PitaJ

    I have upgraded Nodejs version to v4.7.0 and It solved the problem.


Log in to reply
 


Star

Looks like your connection to NodeBB was lost, please wait while we try to reconnect.