Skip to content

Commit

Permalink
chore: run install as part of vscode:prepublish
Browse files Browse the repository at this point in the history
I believe the reason the patch release failed last time was that vsce
validates that package.json matches node_modules (good thing to have!)
so you ship what you think you ship. When the version of the language
server package is bumped by semantic-release it only updates the package.json,
since it's designed for publishing packages, not publishing built and bundled
assets necessarily. At least that's my theory. We'll see next time I guess.
No harm in manually bumping the version should it be something else.
  • Loading branch information
wkillerud committed Mar 2, 2024
1 parent 4ccd392 commit 9304572
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion vscode-extension/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -118,7 +118,7 @@
"shx": "0.3.4"
},
"scripts": {
"vscode:prepublish": "npm run build",
"vscode:prepublish": "npm install && npm run build",
"clean": "shx rm -rf dist",
"build": "npm run clean && webpack --mode production",
"dev": "npm run clean && webpack --mode development",
Expand Down

0 comments on commit 9304572

Please sign in to comment.