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

vsce package, Extension entrypoint(s) missing #675

Closed
yzhang-gh opened this issue Jan 1, 2022 · 5 comments · Fixed by #676
Closed

vsce package, Extension entrypoint(s) missing #675

yzhang-gh opened this issue Jan 1, 2022 · 5 comments · Fixed by #676
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug help wanted Issues identified as good community contribution opportunities released
Milestone

Comments

@yzhang-gh
Copy link

(Happy New Year!)

The GitHub CI of my vscode extension has been working very well for a long time (vsce v1.x). However, it doesn't seem to work with vsce v2.x and says

 ERROR  Extension entrypoint(s) missing. Make sure these files exist and aren't ignored by '.vscodeignore':
  extension/out/src/extension

I'm a little confused. Is there any API change? Guess it may be related to the VS Code Web but I haven't got time to take a closer look.


Additional information

the package.json
https://github.com/yzhang-gh/vscode-dic-completion/blob/master/package.json

the ci file
https://github.com/yzhang-gh/vscode-dic-completion/blob/master/.github/workflows/main.yml

the failed ci log
https://github.com/yzhang-gh/vscode-dic-completion/runs/4679563201?check_suite_focus=true

+ [email protected]

Run vsce package
Executing prepublish script 'npm run vscode:prepublish'...

> [email protected] vscode:prepublish /home/runner/work/vscode-dic-completion/vscode-dic-completion
> tsc -p ./

 ERROR  Extension entrypoint(s) missing. Make sure these files exist and aren't ignored by '.vscodeignore':
  extension/out/src/extension

the past passed ci log
https://github.com/yzhang-gh/vscode-dic-completion/runs/3868473421?check_suite_focus=true

+ [email protected]

Run vsce package
Executing prepublish script 'npm run vscode:prepublish'...

> [email protected] vscode:prepublish /home/runner/work/vscode-dic-completion/vscode-dic-completion
> tsc -p ./

 DONE  Packaged: /home/runner/work/vscode-dic-completion/vscode-dic-completion/dictionary-completion-1.1.1.vsix (13 files, 79.63KB)
@haneefdm
Copy link

haneefdm commented Jan 1, 2022

+1

Same issue. I can package (and use the VSIX file successfully) but cannot publish with 2.6.0. I rolled back to version 2.5.3 and I can publish again.

My package.json hasn't changed in a long time in this aspect and I know that the entry point file does exist

@paulhocker
Copy link

+1

This needs to be addressed immediately. Kind of disappointed that a new version was dropped on New Years Eve when there is little available for support.

@ritwickdey
Copy link
Contributor

ritwickdey commented Jan 1, 2022

Quick Fix: Append the .js extension at main field of package.json

image

@joaomoreno joaomoreno added this to the January 2022 milestone Jan 3, 2022
@joaomoreno joaomoreno self-assigned this Jan 3, 2022
@joaomoreno joaomoreno added bug Issue identified by VS Code Team member as probable bug help wanted Issues identified as good community contribution opportunities labels Jan 3, 2022
@github-actions
Copy link

github-actions bot commented Jan 3, 2022

🎉 This issue has been resolved in version 2.6.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

jameswilddev added a commit to skitscript/extension-vscode that referenced this issue Jan 3, 2022
jameswilddev added a commit to skitscript/extension-vscode that referenced this issue Jan 3, 2022
@mohanraj-r
Copy link

I notice the same error with the latest vsce 2.7.0

Even the quick fix suggestion didn't help

Quick Fix: Append the .js extension at main field of package.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug help wanted Issues identified as good community contribution opportunities released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants