[question] how to develop vscode extensions locally with inter dependencies

[d-akara]

I'm attempting to develop extensions which have a common dependency.
I use npm link to satisfy the dependency locally.

The problem is that I can't package the extension because vsce will fail due to npm saying there are extraneous modules. This is due to both modules requiring vscode.

The annoying work around is to uninstall the vscode from the common module before I package/publish. But this is an annoying workflow.

Is there a way to make this work properly?

[joaomoreno]

Can you show me the log from vsce?

[d-akara]

@joaomoreno
Error: Command failed: npm list --production --parseable --depth=99999 npm ERR! extraneous: [email protected] /Users/chadmeadows/development/vscode-extensions/dakaraphi/vscode-extension-space-jumper/node_modules/vscode-extension-common/node_modules/vscode

vscode-extension-space-jumper is the extension I'm attempting to package.
vscode-extension-common is the module I've included via npm link

[joaomoreno]

Is vscode listed in the dependencies object of vscode-extension-common/package.json?

[d-akara]

yes

[joaomoreno]

As a regular dependency? And the version matches what's on disk? Because that's what npm is complaining about.

[d-akara]

hmm, ok. So I actually had it listed as devDependency.
So vsce does not complain if I move it to dependency; however, doesn't my package then unnecessarily include the vscode libraries?

[joaomoreno]

Hm devDependency should actually work... Interesting.. that might be the issue here.

[joaomoreno]

Moved to microsoft/vscode-vsce#207