Skip to content

Use vsce 1.x since 2.x is not compatible with Node 12.x#2195

Merged
rgrunber merged 1 commit intoredhat-developer:masterfrom
rgrunber:vsce-1
Nov 5, 2021
Merged

Use vsce 1.x since 2.x is not compatible with Node 12.x#2195
rgrunber merged 1 commit intoredhat-developer:masterfrom
rgrunber:vsce-1

Conversation

@rgrunber
Copy link
Copy Markdown
Member

@rgrunber rgrunber commented Nov 4, 2021

+npm WARN notsup Unsupported engine for vsce@2.1.0: wanted: {"node":">= 14"} (current: {"node":"12.13.1","npm":"6.12.1"})
+npm WARN notsup Not compatible with your version of node/npm: vsce@2.1.0
+
++ vsce@2.1.0

Signed-off-by: Roland Grunberg rgrunber@redhat.com

Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
Comment thread Jenkinsfile
env.PATH="${env.PATH}:${nodeHome}/bin"
sh "npm install -g typescript"
sh "npm install -g vsce"
sh 'npm install -g "vsce@<2"'
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, vsce@2.0 is just published 10 hours ago. We can keep 1.x first before we catch up 2.0 gap.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, the <2 is just so that we can continue getting 1.x updates without having to manually touch the build files every time.

@rgrunber rgrunber added this to the Early November milestone Nov 5, 2021
@rgrunber rgrunber merged commit dd6f006 into redhat-developer:master Nov 5, 2021
@rgrunber rgrunber deleted the vsce-1 branch November 5, 2021 03:34
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

Successfully merging this pull request may close these issues.

2 participants