-
Notifications
You must be signed in to change notification settings - Fork 193
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
[Question] vsce prepublish before version bump ? #834
Comments
Maybe we need a new lifecycle script?
Would this help? |
What about add the backup logic? |
The problem with the backup solution is that |
Well, it's really tricky. |
Given you have a functional workaround at the moment, we'll close this request for now. Thanks! |
Hi team, you build a nice tool for VS Code.
But I get some confusion in the process of using it recently.
vsce package 2.0.1
will get a VSIX with version 2.0.1, although it is possible that the version number in package.json was 2.0.0.The vscode-vsce help to do versionBump after prepublish which executes "vscode:prepublish" script.
Take our project as an example, the package.json file is referenced in the source code, we need to get the package's name, version to collect BI data. so the package will run prepublish to build or compile the source code, so the version of package.json which is 2.0.0 will be hardcoded.
Then vsce will leverage the compiled result to generate visx.
Finally, the verison of visx is 2.0.1, however, the code gets the version number 2.0.0 at runtime.
So I would like to know what is your consideration for this design.
Is there any solution to resolve my problem?
The text was updated successfully, but these errors were encountered: