Dependencies?

[srl295]

(Disclaimer is that I understand dependency challenges, I can show you my own list.)

When following https://theia-ide.org/docs/composing_applications in evaluating the platform, installing dependencies gives this with npm i:

npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs
npm warn deprecated npmlog@6.0.2: This package is no longer supported.
npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
npm warn deprecated abab@2.0.6: Use your platform's native atob() and btoa() methods instead
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.
npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated gauge@4.0.4: This package is no longer supported.
npm warn deprecated fstream@1.0.12: This package is no longer supported.
npm warn deprecated xterm-addon-fit@0.8.0: This package is now deprecated. Move to @xterm/addon-fit instead.
npm warn deprecated @types/highlight.js@10.1.0: This is a stub types definition. highlight.js provides its own type definitions, so you do not need this installed.
npm warn deprecated xterm-addon-search@0.13.0: This package is now deprecated. Move to @xterm/addon-search instead.
npm warn deprecated xterm@5.3.0: This package is now deprecated. Move to @xterm/xterm instead.
npm warn deprecated electron-rebuild@3.2.9: Please use @electron/rebuild moving forward.  There is no API change, just a package name change
npm warn deprecated puppeteer@19.7.2: < 22.8.2 is no longer supported
npm warn deprecated gauge@2.7.4: This package is no longer supported.
npm warn deprecated are-we-there-yet@1.1.7: This package is no longer supported.
npm warn deprecated npmlog@4.1.2: This package is no longer supported.
npm warn deprecated xterm-addon-fit@0.5.0: This package is now deprecated. Move to @xterm/addon-fit instead.
npm warn deprecated are-we-there-yet@1.1.7: This package is no longer supported.
npm warn deprecated npmlog@4.1.2: This package is no longer supported.
npm warn deprecated gauge@2.7.4: This package is no longer supported.
npm warn deprecated rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported
npm warn deprecated xterm@4.19.0: This package is now deprecated. Move to @xterm/xterm instead.

OK, i'll try yarn instead, which gives:

yarn install v1.22.17
info No lockfile found.
[1/4] 🔍  Resolving packages...
warning @theia/callhierarchy > @theia/core > keytar > prebuild-install > npmlog@4.1.2: This package is no longer supported.
warning @theia/callhierarchy > @theia/core > drivelist > prebuild-install > npmlog@4.1.2: This package is no longer supported.
warning @theia/callhierarchy > @theia/core > keytar > prebuild-install > npmlog > are-we-there-yet@1.1.7: This package is no longer supported.
warning @theia/callhierarchy > @theia/core > keytar > prebuild-install > npmlog > gauge@2.7.4: This package is no longer supported.
warning @theia/file-search > @theia/filesystem > rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
warning @theia/file-search > @theia/filesystem > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning @theia/file-search > @theia/filesystem > rimraf > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning @theia/file-search > @theia/filesystem > trash > globby > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning @theia/plugin-ext-vscode > @theia/terminal > xterm-addon-fit@0.8.0: This package is now deprecated. Move to @xterm/addon-fit instead.
warning @theia/plugin-ext-vscode > @theia/terminal > xterm-addon-search@0.13.0: This package is now deprecated. Move to @xterm/addon-search instead.
warning @theia/plugin-ext-vscode > @theia/terminal > xterm@5.3.0: This package is now deprecated. Move to @xterm/xterm instead.
warning @theia/plugin-ext-vscode > @theia/plugin-ext > @theia/test > xterm@4.19.0: This package is now deprecated. Move to @xterm/xterm instead.
warning @theia/plugin-ext-vscode > @theia/plugin-ext > @theia/test > xterm-addon-fit@0.5.0: This package is now deprecated. Move to @xterm/addon-fit instead.
warning @theia/preview > @types/highlight.js@10.1.0: This is a stub types definition. highlight.js provides its own type definitions, so you do not need this installed.
warning @theia/terminal > xterm@5.3.0: This package is now deprecated. Move to @xterm/xterm instead.
warning @theia/terminal > xterm-addon-fit@0.8.0: This package is now deprecated. Move to @xterm/addon-fit instead.
warning @theia/terminal > xterm-addon-search@0.13.0: This package is now deprecated. Move to @xterm/addon-search instead.
warning @theia/cli > glob@8.1.0: Glob versions prior to v9 are no longer supported
warning @theia/cli > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning @theia/cli > mocha > glob@8.1.0: Glob versions prior to v9 are no longer supported
warning @theia/cli > temp > rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported
warning @theia/cli > temp > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning @theia/cli > patch-package > rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
warning @theia/cli > puppeteer-core > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning @theia/cli > puppeteer-core > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning @theia/cli > puppeteer@19.7.2: < 22.8.2 is no longer supported
warning @theia/cli > @theia/localization-manager > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning @theia/cli > @theia/application-manager > electron-rebuild@3.2.9: Please use @electron/rebuild moving forward.  There is no API change, just a package name change
warning @theia/cli > @theia/ffmpeg > unzipper > fstream@1.0.12: This package is no longer supported.
warning @theia/cli > @theia/ffmpeg > unzipper > fstream > rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
warning @theia/cli > @theia/application-manager > source-map-loader > abab@2.0.6: Use your platform's native atob() and btoa() methods instead
warning @theia/cli > @theia/application-manager > electron-rebuild > node-gyp > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning @theia/cli > @theia/application-manager > electron-rebuild > node-gyp > npmlog@6.0.2: This package is no longer supported.
warning @theia/cli > @theia/application-manager > electron-rebuild > node-gyp > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning @theia/cli > @theia/application-manager > electron-rebuild > node-gyp > npmlog > gauge@4.0.4: This package is no longer supported.
warning @theia/cli > @theia/application-manager > electron-rebuild > node-gyp > npmlog > are-we-there-yet@3.0.1: This package is no longer supported.
warning @theia/cli > @theia/application-manager > electron-rebuild > node-gyp > make-fetch-happen > cacache > glob@8.1.0: Glob versions prior to v9 are no longer supported
warning @theia/cli > @theia/application-manager > electron-rebuild > node-gyp > make-fetch-happen > cacache > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning @theia/cli > @theia/application-manager > electron-rebuild > node-gyp > make-fetch-happen > cacache > @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs
warning @theia/cli > @theia/application-manager > electron-rebuild > node-gyp > make-fetch-happen > cacache > @npmcli/move-file > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
…
warning "@theia/search-in-workspace > react-autosize-textarea@7.1.0" has unmet peer dependency "react@^0.14.0 || ^15.0.0 || ^16.0.0".
warning "@theia/search-in-workspace > react-autosize-textarea@7.1.0" has unmet peer dependency "react-dom@^0.14.0 || ^15.0.0 || ^16.0.0".
warning "@theia/messages > react-perfect-scrollbar@1.5.8" has unmet peer dependency "react@>=16.3.3".
warning "@theia/messages > react-perfect-scrollbar@1.5.8" has unmet peer dependency "react-dom@>=16.3.3".
warning "@theia/preview > markdown-it-anchor@5.0.2" has unmet peer dependency "markdown-it@^8.4.1".

I know for example rimraf 4.0 was published 2 years ago (despite that node builtin now has a recursive delete).

Anyway, when then trying to build I get:

$ theia clean && theia build
Failed to resolve module: @theia/electron

I'm on Node 18.20.4.

It does start (yay!), but the dependency warnings are a little concerning, and some of them seem like low hanging fruit (such as rimraf).

Yes, I searched your issues and discussions for similar. I found a couple of discussions of specific dependencies and one about yarn v1 but did not find something about the unsupported dependencies.

I'm evaluating theia as the foundation for a new project, so trying to see if this situation is something I should be concerned about or not.

[JonasHelming]

How did you compose your application, did you use the Yeoman generator?

[JonasHelming]

And to directly answer your question: Yes, we are actively working on keeping the dependencies up-to-date. This is crucial for the adopting projects.

[srl295]

• No, i used the package.json in https://theia-ide.org/docs/composing_applications#setup - I've since been pointed at the generator in Build Your own vs. Extending IDE #14244

[JonasHelming]

Reason I am asking is that we recently decided to get rid of the path with the manual package.json.
It is constantly confusing new adopters and also harder to maintain.
About the dependency warnings, I added an item to our next dev call: https://github.com/eclipse-theia/theia/wiki/Dev-Meetings

[JonasHelming]

For additional information, besides the regular yarn upgrades we do every release, we decided to do an explicit dependency review for every community release to identify deprecated dependencies, next will be beginning of Nov. Rimraf is upgraded in the meantime

[JonasHelming]

Where did you get the information to use theia clean && theia build?

[srl295]

https://theia-ide.org/docs/composing_applications/#consuming-vs-code-extensions just below there.