How to remove internal package from blueprint

#1

Hi,
I build a desktop application based on theia blueprint, I want to remove some of the internal packages because I do not need them, like source control and extensions. for now I just remove the dependency from package.json, but the container is still in, where can I remove it completely
image

#2

I believe the extension view is contributed by the @theia/vsx-registry package, the source control view by @theia/scm. I’m not sure it’s possible to remove the @theia/scm package, since the @theia/plugin-ext package (required for plugin support) depends on it. You can run yarn why <package> to find out why a package is imported even though it’s not in the package.json.

To remove it the scm view, you’ll likely need to override the ScmContribution yourself.

#3

Hi,
I try to implement a EmptyScmContribution, but has a problem,
image
you know super constructor has code
image
this create the option to add scm to left bar. and it is readonly, seem can not be changed

#4

In theia, almost all codes can be changed through ‘rebind’

#5

I’m not sure it’s possible to remove the @theia/scm package, since the @theia/plugin-ext package (required for plugin support) depends on it.

Does that dependency really make scm removal impossible? Or simply make scm removal require plugin-ext removal?

#6

@chrisjj Yes, if you were to remove @theia/plugin-ext, you can easily remove the @theia/scm dependency. Note that you lose support for all vscode extensions in that case. In theory you can build an application purely on the @theia/core package, but it doesn’t do anything, since it doesn’t contain any features, only building blocks to contribute features to Theia.

#7

Yes, if you were to remove @theia/plugin-ext , you can easily remove the @theia/scm dependency.

Thanks.

Note that you lose support for all vscode extensions in that case.

No problem, given the OP specified “I do not need them, like source control and extensions.”

Regardless it sounds like plugin-ext’s dependency on scm might deserve review.

#8

@wss you can use what is known as a FilterContribution to remove contributions in the framework such as the ones contributed by @theia/scm. You can follow a similar approach to this question where the debug-view was filtered out: I need to remove "Debug" functionality - #2 by vince-fugnitto.

registerContributionFilters(registry: ContributionFilterRegistry): void {
    registry.addFilters('*', [
        filterClassName(name => name !== 'ScmContribution')
    ]);
}

You may need to run the command reset workbench layout in the application once you filter out for the first time to clean up any local storage that may still be referencing the view. By default you’ll end up without the scm-view present (among other contributions like commands, statusbar items):

image
image1181×746 23 KB

#9

hi,
Get it,thanks great