-
-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot call method 'toJSON' of undefined #414
Comments
I'm having the exact same problem when working through the Beginner's Guide. Also tried downloading the reveal.js skeleton and I get these errors:
And a little later:
|
Please provide the source of the project that is causing the error. @ alexraasch Does the html5 boilerplate skeleton work? I think the reveal.js skeleton may need some configuration - not sure as that skeleton is a user contributed one - not a core team one. |
I think I'm having a similar error that may be related. Then when I create a new docpad project to test say the KitchenSink Skeleton it gives the error after installing :
One thing to note is I am receiving an error when installing a new project using docpad run on a clean directory. The same error was given with the Boilerplate Skeleton:
I have tried installing socket.io and node-gyp independently. node-gyp installs fine but socket.io gives me the same error. I have also tried installing node-gyp globally as well, which was suggested on another github thread. But no joy there either. :) |
I have the same issue as @alexraasch, but ONLY on reveal.js. I'll report a bug there and see what gets done. |
The problem in reveal.js seems to be the call to
It should be (note the tags and slideOrder properties):
--Edit |
Unfortunately I don't have access to the reveal.js skeleton to fix it, but I can delete it from the official listing. Are people okay with that? |
I'm not all that keen - its quite a nice skeleton and it seems the problem is quite simple. |
@balupton Ok - I get what you mean. The skeleton is read only on github (doh!) |
Closing due to age. Ecosystem has likely fixed this. Try again with v6.80 or later. |
Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: