vsce-workspace-bug-1

see : microsoft/vscode-vsce#777

Using vsce ls because it illustrates the bug without needing to actually run vsce publish. There is a slim chance that these are two separate bugs.

Fails with workspaces :

cd .vscode/extensions/a
npm install
npm run vsce ls

...
../node_modules/vsce/node_modules/ansi-styles/index.js
../node_modules/vsce/node_modules/ansi-styles/license
../node_modules/vsce/node_modules/ansi-styles/package.json
../node_modules/vsce/node_modules/ansi-styles/readme.md
../node_modules/vsce/node_modules/chalk/index.js
...

Works without workspaces :

cd .vscode-no-workspaces/extensions/a
npm install
npm run vsce ls

dist/extension.js
package.json

The only difference between .vscode/extensions and .vscode-no-workspaces/extensions is that ./vscode/extensions has a package.json file to make it a workspace root :

{
	"name": "@mrhenry/vscode-extensions",
	"private": true,
	"description": "",
	"workspaces": [
		"./*"
	],
	"scripts": {
		"compile": "npm run compile --workspaces --if-present",
		"lint": "npm run lint --workspaces --if-present",
		"publish": "npm run publish --workspaces",
		"version:minor": "npm --workspaces version minor --no-git-tag-version",
		"version:patch": "npm --workspaces version patch --no-git-tag-version"
	}
}