Cannot find module 'jibo'


#1

I’ve got a small (Hopefully) issue.

I went to atom to install the jibo SDK and it gave me some errors. Errors like “Cannot find module ‘pixi’”. I was ok with that I just had to execute ‘npm install “module name” --save’ almost 20 times, ‘npm install’. Then it gave me an error saying “Cannot find module ‘Jibo’”, I did ‘npm install “Jibo” --save’, opened atom and the error was still there. Idk what to do!

Operating System: macOS Sierra 10.12.6
Node Version: 8.5.0
Atom version: 1.20.1

I am not great at English so I don’t understand ram and those kind of things if you want the log here it is:

Error: Cannot find module 'jibo’
at Module._resolveFilename (module.js:470:15)
at Module._resolveFilename (/private/var/folders/48/8v_z5kqj17b2_1lh79sgv_2w0000gn/T/AppTranslocation/2054C453-A943-48A5-9912-B6E14F843333/d/Atom.app/Contents/Resources/electron.asar/common/reset-search-paths.js:35:12)
at Function.get_Module._resolveFilename (/private/var/folders/48/8v_z5kqj17b2_1lh79sgv_2w0000gn/T/AppTranslocation/2054C453-A943-48A5-9912-B6E14F843333/d/Atom.app/Contents/Resources/app/src/module-cache.js:354:58)
at Module.require (file:///private/var/folders/48/8v_z5kqj17b2_1lh79sgv_2w0000gn/T/AppTranslocation/2054C453-A943-48A5-9912-B6E14F843333/d/Atom.app/Contents/Resources/app/static/index.js:40:43)
at require (/private/var/folders/48/8v_z5kqj17b2_1lh79sgv_2w0000gn/T/AppTranslocation/2054C453-A943-48A5-9912-B6E14F843333/d/Atom.app/Contents/Resources/app/src/native-compile-cache.js:66:33)
at o (/Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:9:410)
at /Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:9:601
at Object.a.24…/face/mode-select (/Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:12:18321)
at o (/Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:9:550)
at /Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:9:601
at Object.a.11…/…/atom-react/core/react-editor (/Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:10:27313)
at o (/Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:9:550)
at /Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:9:601
at Object.a.1…/atom-react/core/react-editor (/Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:9:2018)
at o (/Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:9:550)
at /Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:9:601
at Object.a.120…/animation-editor/animation-editor (/Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:19:29613)
at o (/Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:9:550)
at e (/Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:9:717)
at /Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:9:734
at l (/Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:9:85)
at Object. (/Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:9:279)
at Object. (/Users/isangedal/.atom/packages/jibo-sdk-1.7.1/lib/jibo-sdk.js:21:3)
at Module.get_Module._compile (/private/var/folders/48/8v_z5kqj17b2_1lh79sgv_2w0000gn/T/AppTranslocation/2054C453-A943-48A5-9912-B6E14F843333/d/Atom.app/Contents/Resources/app/src/native-compile-cache.js:106:36)
at Object.value [as .js] (/private/var/folders/48/8v_z5kqj17b2_1lh79sgv_2w0000gn/T/AppTranslocation/2054C453-A943-48A5-9912-B6E14F843333/d/Atom.app/Contents/Resources/app/src/compile-cache.js:239:29)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (file:///private/var/folders/48/8v_z5kqj17b2_1lh79sgv_2w0000gn/T/AppTranslocation/2054C453-A943-48A5-9912-B6E14F843333/d/Atom.app/Contents/Resources/app/static/index.js:47:45)
at require (/private/var/folders/48/8v_z5kqj17b2_1lh79sgv_2w0000gn/T/AppTranslocation/2054C453-A943-48A5-9912-B6E14F843333/d/Atom.app/Contents/Resources/app/src/native-compile-cache.js:66:33)


#2

Hi @Isangedal

Thank you for your interest in the SDK and developing for Jibo.

We recently posted a blog post here and a post in this forum providing an update on our SDK development efforts letting the community know that we will be taking down the current publicly available SDK. I apologize for any inconvenience this causes.

We are doing this to allow us to focus our internal resources on bringing the new toolkit to you and other interested developers.

We have not finalized the date for the re-launch of our developer tools but we will be sure to keep the community up-to-date on this via our developer newsletter and blog. If you have not already signed up for those updates I recommend going to our developer website here and singing up via the form on that page.

That will make sure that you are notified with updates as we work towards the next version of our developer tools.


New SDK on the way?
#3

This topic was automatically closed after 25 hours. New replies are no longer allowed.