Print warning when .vsceignore is missing or misconfigured about vscode-vsce HOT 4 CLOSED

I agree we should do something to make sure the user is aware of .vscodeignore. I think we should print a warning when we do not detect a .vscodeignore file. We could also request the user to confirm that he wants to proceed without .vscodeignore file, however I fear we would break some pipelines with that.

Also printing what is being packaged is a great idea as mentioned here #995 and we could even provide a command to just print what would be packaged if the user runs vsce package or vsce publish so the user can see it without actually having to package the extension.

from vscode-vsce.

Good ideas. I suggest to discuss with Joao in your next sync, since he also has thoughts on this topic.

from vscode-vsce.

Building on the work completed in #995, we have added a warning for users who are not using either a .vscodeignore file or the "files" property in package.json. Additionally, we have made several minor enhancements to improve the overall experience for users packaging their extensions. These changes aim to ensure that extensions are packaged as expected.

from vscode-vsce.

Works great -> verified
For a missing license file we ask the user to confirm with a Y. But for a missing .vscodeignore we just print a warning, and do not prompt the user. Should we prompt?

from vscode-vsce.