[Request] Publish Extension on open-vsx.org

[oxy]

Hi there!

I'm reaching out to you because we currently have your extension manually added to our extension gallery at Coder for code-server, and we're currently working on a migration to open-vsx, which is also used by other community VSCode forks (including, but not limited to Arch Linux's Code-OSS builds and VSCodium).

We (and other open source VSCode forks) cannot use Microsoft's extension gallery, as MS' terms of service allows only the proprietary MS products to interact with the official gallery.

We'd really appreciate it if you can add your extension to open-vsx! A simple guide on publishing extensions to Open-VSX is available here.

[filiptronicek]

@yairhaimo could you help here please 🙏? The extension is auto-published [1] via a repository called https://github.com/open-vsx/publish-extensions. This would mean before Wix decides to publish the extension there, it could be published by us, but a problem has appeared, which is that the script fails to package up the extension.

Could you please share any docs or the steps for packaging the extension into a .vsix file?

[yairhaimo]

@shahata can help with this

[filiptronicek]

Friendly ping @shahata :), can provide any details if required and would love to assist with either publishing to Open VSX or setting up some of the releasing workflows with assets.

[shahata]

@filiptronicek did you try to package the latest version? any packaging issue should be resolved in v3 and up

[filiptronicek]

I tried packaging the latest version (https://github.com/wix/import-cost/tree/master) by installing dependencies (npm i) and then executing vsce package inside of vscode-import-cost but I get an error message that the entrypoint is missing:

gitpod /workspace/import-cost/packages/vscode-import-cost (master) $ vsce package
 ERROR  Extension entrypoint(s) missing. Make sure these files exist and aren't ignored by '.vscodeignore':
  extension/dist/extension.electron.js,
  extension/dist/extension.browser.js

@shahata should I be running the command somewhere else? Or are there any steps I'm missing?

[shahata]

You also need to run npm test

[filiptronicek]

So these are the commands in order that I executed:

1. npm i in root
2. npm run pretest in packages/vscode-import-cost to compile the js
3. vsce package in packages/vscode-import-cost

Now I'm getting this from vsce 🤔:

 ERROR  invalid relative path: extension/../../.eslintignore

[shahata]

Try vsce package --no-dependencies

[shahata]

I added a build command to make this process easier, all you need to do is clone the repo and then run:

$ npm install
$ npm run build

Then you can just collect the extension from packages/vscode-import-cost/vscode-import-cost-${version}.vsix

[filiptronicek]

Thanks a lot for the guidance here 🙏, I was able to build a .vsix correctly. Sadly, the auto-publishing CI seems to be a bit stuck and running in an infinite loop, but I think I can make it work and will comment here again once the latest version is published :).

[filiptronicek]

v3.3.0 has been published 🎉! [open-vsx.org]

So glad I can use the extension again, thanks a lot @shahata 🧡