Commands not found. Ubuntu 17

[matthewkoon]

Just installed vs code and the git extension both seemingly working fine. When I install SPGo and look to run > SPGo: configure workspace

command 'spgo.configureWorkspace' not found

Debug info says about the same: /usr/share/code/resources/app/out/vs/workbench/workbench.main.js:2255 command 'spgo.configureWorkspace' not found

Any known issues in this environment?

[sg-chrishasz]

Hello @matthewkoon!

I built an Ubuntu system today and was able to reproduce this issue. Fortunately it is simply a case of a few import statements mismanaging their camel casing. I'm going to run a set of user tests and will publish fixes as version 1.2.5 in the next few days.

[matthewkoon]

Thanks for the quick response Chris, I'll watch for it and help test.

On Thu, May 17, 2018 at 6:42 PM, Chris Hasz notifications@github.com wrote:

Hello @matthewkoon https://github.com/matthewkoon!

I built an Ubuntu system today and was able to reproduce this issue. Fortunately it is simply a case of a few import statements mismanaging their camel casing. I'm going to run a set of user tests and will publish fixes as version 1.2.5 in the next few days.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/readysitego/spgo/issues/42#issuecomment-390047698, or mute the thread https://github.com/notifications/unsubscribe-auth/AGOXUn8YxLBPpIIoYV-mumQU7cmjzKj1ks5tzgrrgaJpZM4UDn4f .

-- Matthew Koon *CEO*, zooma http://zooma.io/ mobile: 540.303.2071 4147 North Ravenswood Avenue, Suite 300, Chicago, IL 60613 matthew.koon@zooma.io

[sg-chrishasz]

I just released 1.2.5 to the VSCode App Store, which should have full support for Unix/Linux environments. Thanks for helping test out Ubuntu support!

[s-KaiNet]

@sg-chrishasz just a small hint - you can add "forceConsistentCasingInFileNames": true in your tsconfig to prevent such errors in future. In this case, TS will throw an error if imports have a different casing.

[matthewkoon]

Just updated and still the same result. Tried removing Code and it's settings, reinstalled fresh and same.

[sg-chrishasz]

I just pushed build 1.2.6, which resolves a deploy-time error with package management. Can you try this latest package once it is available for you? I will leave this bug open for you to close when you can confirm proper functionality.

[matthewkoon]

Getting there, slightly different message this time.

[sg-chrishasz]

I'm able to build and run from VSCode in Ubuntu, but packaging commands are still failing. I'm sure this is the root of the error. I'm going to work on getting this built, but I'm noticing major differences between package-lock.json files in Ubuntu and Windows/OSX, even though I'm using the same version of npm (5.6.0).

I'll post updates as I have them. In the meantime, if you want to test along, you can do the following:

1. globally install the vsce tools: sudo npm install -g vsce
2. get latest from 1.2.7 branch: git clone https://github.com/readysitego/spgo
git checkout 1.2.7 git pull
3. get packages: npm install
4. Build and install package manually: vsce package code --install-extension <package>.vsix where <package> is the name of the package generated in the step above.

In my environment, I'm seeing a number of Cannot find module 'vscode' errors at the vsce package step.

[sg-chrishasz]

Update: I believe I've solved the problem. Turns out the vscode package has been a dev dependency this whole time (why did this not break the package before ¯\_(ツ)_/¯ ).

Can you follow the steps above with the latest on the 1.2.7 branch and see if this resolves your issues as well? Thanks for the help!

[matthewkoon]

That did it!