You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
@dakaraphi Sorry for hijacking this thread. I have a related situation - an extension depending on another extension. However, I don't even get the code compiled when defining a dependency from one extension to another extension. Thus, I was wondering if you could share your setup to reproduce the issue you are seeing. It sounds like you figured out a way of compiling the code.
From microsoft/vscode#35458 cc @dakaraphi
The text was updated successfully, but these errors were encountered: