Package Details: theia-electron 1.61.0-2

Git Clone URL: https://aur.archlinux.org/theia-electron.git (read-only, click to copy)
Package Base: theia-electron
Description: Cloud & Desktop IDE Platform
Upstream URL: https://www.theia-ide.org/
Keywords: eclipse electron ide theia
Licenses: EPL2
Submitter: bence.hornak
Maintainer: ccorn
Last Packager: ccorn
Votes: 19
Popularity: 0.001705
First Submitted: 2020-04-18 15:55 (UTC)
Last Updated: 2025-05-07 11:38 (UTC)

Latest Comments

1 2 3 4 5 6 Next › Last »

oech3 commented on 2025-05-09 17:53 (UTC) (edited on 2025-05-11 19:34 (UTC) by oech3)

@ccorn Do you know how to build theia with system-wide libffmpeg.so containing proprietary codecs? Because updating of one of a theia-based app in offcial repo is blocked by electron issue, and it may related with it.

[Edit]Solved, and this package may able to use electron31 or 34.

oech3 commented on 2025-05-08 12:12 (UTC)

Why make-package-json.sh instead of package{,-lock}.json from https://github.com/eclipse-theia/theia/tree/v${pkgver} ?

oech3 commented on 2025-05-07 12:57 (UTC) (edited on 2025-05-07 12:57 (UTC) by oech3)

(as opposed to the browser build)

OK. (There is a no rule about naming for packages with replaced runtimes. It sometimes confuses me.) If upstream include major ver to package*.json, and extracting at build process is allowed, constant maintenance may unneeded.

ccorn commented on 2025-05-07 12:36 (UTC)

@oech3: Oh, another issue to watch. Thanks for that.

The package name theia-electron refers to the electron build (as opposed to the browser build) of Theia. At least that is how I understand it.

As long as Theia remains conservative in their electron version upgrades, I consider it best to keep Theia's bundled electron version.

However, if Theia begins to closely follow electron updates, then we can consider replacing the bundled electron.

oech3 commented on 2025-05-07 12:01 (UTC)

So this package has invalid name until https://github.com/eclipse-theia/theia/issues/15059 is solved?

ccorn commented on 2025-05-07 11:51 (UTC)

@oech3: ripgrep hack incorporated.

Regarding electron: Theia seems to be quite sensitive about electron versions. Upstream's current favorite seems to be electron30, but Arch has already left that behind (relegated to AUR, that is). In any case, that kind of hack would require constant maintenance, so I am reluctant to even try that.

oech3 commented on 2025-05-07 10:42 (UTC) (edited on 2025-05-07 10:45 (UTC) by oech3)

This is done at https://gitlab.archlinux.org/archlinux/packaging/packages/code/-/blob/main/PKGBUILD?ref_type=heads .

if rg --help shows superset, it should be just save about 10MB, and increase performance for people using optimized repository.

Note: We already ignoring bundled electron...

ccorn commented on 2025-05-07 10:19 (UTC)

@oech3: Nice idea. It is a hack, but it has its upsides. Thinking about it.

Currently there seem to be two (identical) rg binaries in theia-electron:

/usr/lib/theia-electron/lib/backend/native/rg
/usr/lib/theia-electron/node_modules/@vscode/ripgrep/bin/rg

Those are version 13.0.0 whereas Arch's ripgrep package is up-to-date (14.1.1).

oech3 commented on 2025-05-06 09:12 (UTC)

Would you depends=(ripgrep);ln -sf /usr/bin/rg /pathto/app/lib/backend/native/rg ?

ccorn commented on 2025-04-10 08:23 (UTC) (edited on 2025-05-05 15:26 (UTC) by ccorn)

The recent upstream updates to 1.60.0 .. 1.61.0 currently fail in the webpack phase:

Error: webpack exited with an unexpected code: 1.
    at ChildProcess.<anonymous> (/build/theia-electron/src/node_modules/@theia/application-manager/lib/application-process.js:86:28)
    at ChildProcess.emit (node:events:524:28)
    at maybeClose (node:internal/child_process:1104:16)
    at ChildProcess._handle.onexit (node:internal/child_process:304:5)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
==> ERROR: A failure occurred in build().

Update: Workaround found, cf. Theia #15545.

1 2 3 4 5 6 Next › Last »