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

[obsolete] [email protected] #40101

Closed
alexdima opened this issue Dec 12, 2017 · 0 comments · May be fixed by maxemiliang/vscode-ext#31 or stefanonepa/vscode-chrome-debug#5
Closed

[obsolete] [email protected] #40101

alexdima opened this issue Dec 12, 2017 · 0 comments · May be fixed by maxemiliang/vscode-ext#31 or stefanonepa/vscode-chrome-debug#5
Assignees
Labels
debt Code quality issues
Milestone

Comments

@alexdima
Copy link
Member

alexdima commented Dec 12, 2017

This comes in all the way from here. Please update to be on par with the rest of the product.

The javascript lock could easily move to 0.2.1.

[trace] [obsolete] Backtrace for [email protected]:
		/Users/alex/src/vscode/extensions/ms-vscode.node-debug2/package-lock.json
[trace] [obsolete] Backtrace for [email protected]:
		/Users/alex/src/vscode/extensions/javascript/yarn.lock
[trace] Backtrace for [email protected]:
		/Users/alex/src/vscode/extensions/json/server/yarn.lock
		/Users/alex/src/vscode/extensions/ms-vscode.node-debug/package-lock.json

The idea of this issue is that we stop shipping N times the same module at different versions and that we keep up-to-date with our dependencies.

@alexdima alexdima added the debt Code quality issues label Dec 12, 2017
@alexdima alexdima added this to the December 2017/January 2018 milestone Dec 12, 2017
mjbvz added a commit that referenced this issue Dec 12, 2017
@mjbvz mjbvz removed their assignment Dec 12, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.