Closed kuniss closed 3 years ago
Packaging is done with vsce
internally. We updated the vsce
dependency and released a new version 0.2.1 (#326). Does that fix the issue?
@spoenemann, it's hard for me to retry this as I have corrected my build logic (the main reason for the original problem) and this issue is not relevant anymore for my project.
To check whether the problem is solve dwith 0.2.1, I would need to re-package the .vsix file with npx ovsx without publishing it. How can I do this with ovsx?
That's currently not possible. I'll close this then, and we can reopen if we encounter it again.
Due to an build script issue my extension get re-packaged by the ovsx CLT after having already packaged by vsce CLT. The ovsx re-packaging, however, left the node modules out as one can conclude from the following build log:
The differently packaged VSIX file can be downloaded from
For me it is not an issue anymore, however, as I just reuse the vsce created VSIX file in my build now. But it may be an issue for some one, who is publishing to OpenVSX only...