Skip to content
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

node-debug: extension is not properly packaged #28

Closed
vince-fugnitto opened this issue Apr 27, 2020 · 4 comments
Closed

node-debug: extension is not properly packaged #28

vince-fugnitto opened this issue Apr 27, 2020 · 4 comments

Comments

@vince-fugnitto
Copy link
Contributor

Description

The vscode-node-debug is not properly packaged meaning that the extension does not work correctly when consumed. As a consequence, users are not able to successfully debug (including running mocha tests).

From downloading the extension, it is clear that something went wrong as the entire dist folder is missing:

Error: Cannot find module '/Users/vincentfugnitto/workspace/theia/plugins/vscode-builtin-node-debug/extension/dist/nodeDebug.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:582:15)
    at Function.Module._load (internal/modules/cjs/loader.js:508:25)
    at Function.Module.runMain (internal/modules/cjs/loader.js:754:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
root ERROR [hosted-plugin: 92007] internal/modules/cjs/loader.js:584
    throw err;
    ^
Screen Shot 2020-04-27 at 10 09 24 AM
@akosyakov
Copy link
Collaborator

akosyakov commented Apr 27, 2020

@vince-fugnitto this extension namespace was claimed by MS, you will need to file an issue in vscode-node-debug and vscode-node-debug2 to ask them to release for Open VSX as well, since they are owner now

How to publish: https://github.com/eclipse/openvsx/wiki/Publishing-Extensions

@vince-fugnitto
Copy link
Contributor Author

@vince-fugnitto this extension namespace was claimed by MS, you will need to file an issue in vscode-node-debug and vscode-node-debug2 to ask them to release for Open VSX as well, since they are owner now

How to publish: https://github.com/eclipse/openvsx/wiki/Publishing-Extensions

@akosyakov I wasn't aware that they had claimed the namespace and were interested in publishing to open-vsx :) I thought that since the extensions were builtins (and not usually published on the marketplace) we'd want to take care of publishing them ourselves, they are required for other plugins to work correctly.

Is there a standard way forward when requesting that they publish to open-vsx?

@akosyakov
Copy link
Collaborator

@akosyakov
Copy link
Collaborator

Is there a standard way forward when requesting that they publish to open-vsx?

Not yet, we wait till the registry is transfered to Eclipse Foundation.

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

No branches or pull requests

3 participants