Meteor pages kills spiderable

[MaazAli]

TypeError: 'undefined' is not a function (evaluating 'args[last].bind(this)')

  http://localhost:3000/packages/alethes_pages.js?880d02062f225bbd69e5852c934f32f79bbaa468:323
  http://localhost:3000/packages/alethes_pages.js?880d02062f225bbd69e5852c934f32f79bbaa468:248
  http://localhost:3000/packages/alethes_pages.js?880d02062f225bbd69e5852c934f32f79bbaa468:234
  http://localhost:3000/packages/alethes_pages.js?880d02062f225bbd69e5852c934f32f79bbaa468:391
  http://localhost:3000/packages/alethes_pages.js?880d02062f225bbd69e5852c934f32f79bbaa468:169 in Pages
  http://localhost:3000/collections/anime.js?7e438b069e082d5588772bbc7d6075190e5aa0a2:295
  http://localhost:3000/collections/anime.js?7e438b069e082d5588772bbc7d6075190e5aa0a2:469

If I remove the package spiderable doesn't throw that error when I go to /?_escaped_fragment_=

[ivankravchenko]

+1

[rantav]

+1, this happens to me too. Is there a workaround?
I don't directly use meteor-pages, but it gets included indirectly by https://github.com/yogiben/meteor-admin which I do use

[alethes]

This is because of ariya/phantomjs#10522. The issue is fixed in PhantomJS 2. In earlier versions, you could use https://github.com/kdimatteo/bind-polyfill.

[GiraffeSlacks]

@alethes Forgive me but what does PhantomJS have to do with this? I don't use PhantomJS that I'm aware of so I can't upgrade it to version 2 (that I'm aware of.)

[alethes]

spiderable is based on PhantomJS. Anyway, I started moving from native bind to _.bind, which works fine with PhantomJS 1.*.

[GiraffeSlacks]

Thanks for the explanation. I'm not using spiderable.

[olivierpascal]

Hi, +1 same error with Spiderable and the last version of meteor-pages

TypeError: 'undefined' is not a function (evaluating 'args[last].bind(this)')

  http://localhost/packages/alethes_pages.js?c34e40f7b75aeda63059eaf986e5f32eddb1b152:333
  http://localhost/packages/alethes_pages.js?c34e40f7b75aeda63059eaf986e5f32eddb1b152:255
  http://localhost/packages/alethes_pages.js?c34e40f7b75aeda63059eaf986e5f32eddb1b152:242
  http://localhost/packages/alethes_pages.js?c34e40f7b75aeda63059eaf986e5f32eddb1b152:401
  http://localhost/packages/alethes_pages.js?c34e40f7b75aeda63059eaf986e5f32eddb1b152:408
  http://localhost/packages/alethes_pages.js?c34e40f7b75aeda63059eaf986e5f32eddb1b152:178 in Pages
  http://localhost/lib/env.coffee.js?7ef3989cd8c6cff155326d8f8fe00938f88dfe0c:43
  http://localhost/lib/env.coffee.js?7ef3989cd8c6cff155326d8f8fe00938f88dfe0c:48

Is this bug supposed to be fixed?