Please consider publishing to OpenVSX registry.

We are running Web version of VS Code in Gitpod. But only MS products like VS Code may use MS Marketplace. So we have to use Open VSX instead. It is a vendor neutral alternative. Products like VSCodium, Theia, code-server and so on are using OpenVSX registry.

Docs are here: https://github.com/eclipse/openvsx/wiki/Publishing-Extensions Technically it should be straightforward. You get a token and call ovsx publish with it, for instance how RedHat is publishing the java extension: https://github.com/redhat-developer/vscode-java/blob/ff51dbffc30dd23190335c929e9f34ccdf511554/Jenkinsfile#L73-L82

In my case when I do "Select workspace folders" It shows me modules from my project's dependencies (from node_module folder).

This doesn't help

  "files.exclude": {
    "**/node_modules": true
  }

This extension is great, but a key feature that it's lacking for me to get the most out of it is the ability to open the corresponding package.json in a new tab, instead of updating the workspace config or opening a window.

It's much faster to open the package.json in a new tab, select the file in the Explorer View and then go from there.

Thank you!

Thanks a lot for this extension, I like it.

I manually sort folders after syncing to better match the organization I prefer. When I sync again, this sorting is reset. I wish for an option, that when I sync, newly discovered packages are only added to the end of the list and existing ones are updated (e.g. the emoji), but existing sorting stays as is.

Thanks a lot in advance.

Hi,
Your extension seems great and i really would like to try it.
Unfortunately it doesn't seems to be working for me.

Here is how it went :

1. Installation went fine
2. Tried To execute a command in a repo (WSL): every command fail with command not found.
3. Tried To execute a command in a repo (local): every command fail with command not found.
   

Environnment:

• Windows 10
• VsCode

Version: 1.56.2 (user setup)
Commit: 054a9295330880ed74ceaedda236253b4f39a335
Date: 2021-05-12T17:13:13.157Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: 8.9.255.24-electron.0
OS: Windows_NT x64 10.0.19042

• Monorepo

Name: Monorepo Workspace
Id: folke.vscode-monorepo-workspace
Description: Manage monorepos with multi-root workspaces. Supports Lerna, Yarn, Pnpm, Rushjs and recursive package directories
Version: 1.3.1
Publisher: Folke Lemaitre
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=folke.vscode-monorepo-workspace

I happened to have seen a similar error recently on another extension (Spell Right) and it might just be related to the fact that VsCode updated their Electron version.
Here is the link to the answer of the owner: bartosz-antosik/vscode-spellright#426 (comment)

Feel free to ask for further information i would be glad to be of help!

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Datasource	Name	Replacement PR?
npm	eslint-plugin-node
npm	rollup-plugin-terser
npm	vscode-test

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency @rollup/plugin-commonjs to v26
• chore(deps): update dependency glob to v11
• chore(deps): update dependency rollup to v4
• chore(deps): update dependency typescript to v5
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): replace dependency eslint-plugin-node with eslint-plugin-n 14.0.0
• chore(deps): replace dependency rollup-plugin-terser with @rollup/plugin-terser 0.1.0
• chore(deps): update all non-major dependencies (@rollup/plugin-node-resolve, @rollup/plugin-typescript, @types/glob, @types/mocha, @types/node, @typescript-eslint/eslint-plugin, @typescript-eslint/parser, devmoji, eslint, eslint-config-prettier, eslint-plugin-import, eslint-plugin-jest, eslint-plugin-prettier, glob, husky, mocha, prettier, rollup, rollup-plugin-typescript2, tslib, typescript)
• chore(deps): update vscode (@types/vscode, vscode-test)
• chore(deps): update definitelytyped (major) (@types/glob, @types/node)
• chore(deps): update dependency @rollup/plugin-node-resolve to v15
• chore(deps): update dependency @rollup/plugin-typescript to v11
• chore(deps): update dependency husky to v9
• chore(deps): update linters (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser, eslint, eslint-config-prettier, eslint-plugin-chai-expect, eslint-plugin-jest, eslint-plugin-prettier, eslint-plugin-promise, eslint-plugin-unicorn, prettier)
• chore(deps): update test packages to v10 (major) (@types/mocha, mocha)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Hey, I've found I could use a bit more differentiation between package types in my workspace. There's definitely value to being able to manage settings through the settings UI, but for cases where more emoji would be useful, how about an array config? E.G. monorepoWorkspace.moreFolders: [{prefix, regex}]

While I was looking around the code, I also found what I think might be a typo. Should it be "prefix.unkown"?

Thanks!

It would be nice if other type of apps were supported.

For example, I have a Python backend in my monorepo.

Either by customizing workspaceContains:

workspaceContains:[**/package.json, **/Pipfile]

Or by manually selecting folders that you want to consider "apps".

Hi! Thanks for a great work. I never wrote VSCode extensions, so I don't know how exactly it could be done, but can we made this field configurable?

https://github.com/folke/vscode-monorepo-workspace/blob/master/src/extension.ts#L51

Right now, when I'm sync my Rush projects with workspace folders, it includes the root as well. I want to get rid of root in workspace because it makes a conflict with types then.

When right clicking on a package name in my monorepo and selecting "Find in Folder", the "files to include" field is populated with a path that uses the extensions package name (complete with emoji) instead of the actual path. This is in vscode 1.50 (first noticed it in 1.49) and monorepo-workspace extension 1.2.0.

Hello. The extension is great, except one thing, which renders the extension unusable to me:

It alters [workspace].code-workspace when switching workspace folders (its okay when it syncs packages). You understand that the purpose of this file is storing project (monorepo) settings to other vs-code users? If it keeps changing for every user individually workspace selection, you have to .gitignore it, which renders the purpose of storing cross-user settings pointless - extension recommendations btw. indicating the point of file is to share, not to ignore - why should I recommend extensions to myself?

Is there any way to prevent or workaround this behavior? TI hope there is a solution because otherwise the extension is great. Thanks in advance.

In a project with more than 50 packages and thousand of dependencies the new version 1.3.0 take long time to launch "Select workspace Folders". I downgraded to 1.2.0 and the process is instantaneous.

Hey, I love the plugin! Just wondering if you could set it to always sync before opening the select GUI. I think this would definitely help streamline the UI.

Hi, to further make it easier to visually scan and group packages, it would be cool if the package folders were bolded.

I work on a Monorepo using nx and yarn workspaces. we have our packages grouped in nested directories. I wanted to try Monorepo Workspace but it only recognises our apps.

like so

./apps/
  app-1/
  app-2/
./packages/
  common/
    pkg-1/
    pkg-2/
    data-access/
      pkg-1/
  app-1/
    pkg-1/

I tried to get you logs but don't know where they would be. Please let me know what you need.

Steps to Reproduce:

1. Have MacBook Air 8 GB M1 model
2. Install VSCode Insider 1.53.0 (sha: 4a875e23d20b64504a818834f3fa4c40adb8d480)

VSCode installed:

Version: 1.53.0-insider
Commit: 4a875e23d20b64504a818834f3fa4c40adb8d480
Date: 2020-12-21T12:34:09.548Z (1 wk ago)
Electron: 11.1.0
Chrome: 87.0.4280.88
Node.js: 12.18.3
V8: 8.7.220.29-electron.0
OS: Darwin arm64 20.1.0

Machine Configuration

MacBook Air (M1, 2020)
Chip: Apple M1
Memory: 8 GB

This is great, and I wonder if I may request to port this extension to vim.coc marketplace?

Heya, so I'm running a mono repository with the following stack, however, whenever I try to use your extension it won't see any of my packages. I'm not very good with regex so that might be the issue (reset it to standard now).

root: smartcloud-dev
./package.json
./packages/public/components/package.json
./packages/public/webfront/package.json
./packages/public/webpanel/package.json
./packages/containers/discord/package.json

VSCode recently added support for add patterns in order to display custom labels for the vscode tabs: https://code.visualstudio.com/docs/getstarted/userinterface#_customize-tab-labels

I think we can take advantage of this new feature and use it to prefix (for example) monorepo app|package|util related to the open file within the tab.

Hi,

I'm noticing that the npm scripts for all of my yarn workspaces are listed, not merely the ones associated with the folders I've configured this to display.

Am I doing something wrong, is this a feature request, or is this a limitation in vscode itself, such as microsoft/vscode#71635 ?

Hi,

I really like this extension except that it appears not to work on windows; the paths to packages are not correct for Windows.

It appears that the path to my package is created as "/Users/Josh/Projects/" but that doesn't resolve correctly; it should instead of "C:/Users/Josh/Projects/".

Thank you!

like the title

vscode.commands.executeCommand('extension.select', param1, params2); 

commands.registerCommand("extension.select", (...params) => select(...params))

when use terminal command, WorkspaceFolderItem is null

What I'm looking for is simply to exclude the org name that's used in the package.json name from the displayed label.

For example in our repo all of our package names are prefixed @foo/ but it becomes very redundant when that's used as workspace name.

Maybe some combination of regexp/template would allow users to configure package names.