Skip to content
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

documentation router invocation error #7

Closed
yogeshVU opened this issue Jun 26, 2020 · 6 comments
Closed

documentation router invocation error #7

yogeshVU opened this issue Jun 26, 2020 · 6 comments

Comments

@yogeshVU
Copy link
Contributor

In the Getting started readme:

When trying to execute the

webgme import router BindingsDocs webgme-bindings

One get's following error

vagrant@linux:~/webgme-tut/MyNewProject$ webgme import router BindingDocs webgme-bindings
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN mynewproject@1.0.0 No repository field.
npm WARN mynewproject@1.0.0 No license field.

+ webgme-bindings@1.2.0
updated 1 package in 3.857s
/home/vagrant/.nvm/versions/node/v8.9.0/lib/node_modules/webgme-cli/src/ComponentManager.js:255
        componentPath = utils.getPathContaining(otherConfig[this._webgmeName].basePaths.map(
                                                                              ^

TypeError: Cannot read property 'basePaths' of undefined
    at RouterManager.ComponentManager._getPathFromGME (/home/vagrant/.nvm/versions/node/v8.9.0/lib/node_modules/webgme-cli/src/ComponentManager.js:255:79)
    at RouterManager.ComponentManager._getPathFromDependency (/home/vagrant/.nvm/versions/node/v8.9.0/lib/node_modules/webgme-cli/src/ComponentManager.js:222:73)
    at RouterManager.ComponentManager._getJsonForConfig (/home/vagrant/.nvm/versions/node/v8.9.0/lib/node_modules/webgme-cli/src/ComponentManager.js:184:10)
    at RouterManager._getJsonForConfig (/home/vagrant/.nvm/versions/node/v8.9.0/lib/node_modules/webgme-cli/src/RouterManager.js:111:50)
    at RouterManager.ComponentManager._addComponentFromProject (/home/vagrant/.nvm/versions/node/v8.9.0/lib/node_modules/webgme-cli/src/ComponentManager.js:164:17)
    at utils.installProject (/home/vagrant/.nvm/versions/node/v8.9.0/lib/node_modules/webgme-cli/src/ComponentManager.js:153:18)
    at ChildProcess.job.on.code (/home/vagrant/.nvm/versions/node/v8.9.0/lib/node_modules/webgme-cli/src/utils.js:443:20)
    at emitTwo (events.js:131:20)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:925:16)

@brollb
Copy link

brollb commented Jun 26, 2020

This actually looks like a bug in http://github.com/webgme/webgme-cli :)

@brollb
Copy link

brollb commented Jun 27, 2020

It looks like there was a typo in your import command. Can you try:

webgme import router BindingsDocs webgme-bindings

(It looks like you accidentally tried to import "BindingDocs" in the one with the error.)

@brollb
Copy link

brollb commented Jun 30, 2020

@yogeshVU - Does the above command work (using "BindingsDocs" rather than "BindingDocs")?

@kecso
Copy link
Member

kecso commented Jun 30, 2020

I can confirm it works.

@kecso kecso closed this as completed Jun 30, 2020
@yogeshVU
Copy link
Contributor Author

@brollb : somehow I missed this issue and was following on the webgme-cli repo.
Yes using the above new command I am able to access the docs at /bindings-docs/python/index.html
Good to close

@brollb
Copy link

brollb commented Jun 30, 2020

Great - thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants