faressoft / faressoft/terminalizer
[Bug] Installation doesn't add `terminalizer` to `$PATH`.
- Dominant language
- JavaScript
- Stars
- 16.2k
- Forks
- 520
- PR merge metrics
- No merged PRs in 30d
Description
#### What The Problem Is
Upon installation, `terminalizer` isn't added to `$Env:PATH`:
~~~MA
RokeJulianLockhart@Beedell:~$ sudo dnf5 install yarnpkg
Updating and loading repositories:
Repositories loaded.
Package Arch Version Repository Size
Installing:
yarnpkg x86_64 1.22.22-14.fc43 updates 106.4 MiBTransaction Summary:
Installing: 1 packageTotal size of inbound packages is 22 MiB. Need to download 22 MiB.
After this operation, 106 MiB extra will be used (install 106 MiB, remove 0 B).
Is this ok [y/N]: y
[1/1] yarnpkg-0:1.22.22-14.fc43.x86_64 100% | 2.8 MiB/s | 22.2 MiB | 00m08s
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[1/1] Total 100% | 2.6 MiB/s | 22.2 MiB | 00m09s
Running transaction
[1/3] Verify package files 100% | 21.0 B/s | 1.0 B | 00m00s
[2/3] Prepare transaction 100% | 1.0 B/s | 1.0 B | 00m01s
[3/3] Installing yarnpkg-0:1.22.22-14.fc43.x86_64 100% | 33.7 MiB/s | 111.1 MiB | 00m03s
Complete!
RokeJulianLockhart@Beedell:~$ yarn global add terminalizer
yarn global v1.22.22
[1/4] Resolving packages...
warning terminalizer > electron > @electron/get > global-agent > boolean@3.2.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
warning terminalizer > electron > @electron/get > global-agent > roarr > boolean@3.2.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Installed "terminalizer@0.12.0" with binaries:
- terminalizer
Done in 48.68s.
RokeJulianLockhart@Beedell:~$ terminalizer record demo
bash: terminalizer: command not found...
~~~
#### What My Environment Is
~~~YAML
RokeJulianLockhart@Beedell:~$ rpm -qi $(rpm -qf $(command -v $0))
Name : bash
Version : 5.3.0
Release : 2.fc43
Architecture: x86_64
Install Date: Thu 30 Oct 2025 20:48:08 GMT
Size : 8820142
Signature :
RSA/SHA256, Wed 23 Jul 2025 23:14:17 BST, Key ID 829b606631645531
Source RPM : bash-5.3.0-2.fc43.src.rpm
Build Date : Wed 23 Jul 2025 20:33:15 BST
Build Host : buildvm-x86-20.rdu3.fedoraproject.org
Packager : Fedora Project
Vendor : Fedora Project
URL : https://www.gnu.org/software/bash
Bug URL : https://bugz.fedoraproject.org/bash
RokeJulianLockhart@Beedell:~$ rpm -qi yarnpkg
Name : yarnpkg
Version : 1.22.22
Release : 14.fc43
Architecture: x86_64
Install Date: Fri 02 Jan 2026 23:38:42 GMT
Size : 111612757
Signature :
RSA/SHA256, Wed 03 Dec 2025 14:21:41 GMT, Key ID 829b606631645531
Source RPM : yarnpkg-1.22.22-14.fc43.src.rpm
Build Date : Wed 03 Dec 2025 13:24:32 GMT
Build Host : buildhw-x86-08.rdu3.fedoraproject.org
Packager : Fedora Project
Vendor : Fedora Project
URL : https://github.com/yarnpkg/yarn
Bug URL : https://bugz.fedoraproject.org/yarnpkg
RokeJulianLockhart@Beedell:~$ yarn info terminalizer
yarn info v1.22.22
{
name: 'terminalizer',
version: '0.12.0',
main: 'bin/app.js',
bin: {
terminalizer: 'bin/app.js'
},
scripts: {
dev: 'NODE_ENV=development webpack --watch',
build: 'NODE_ENV=production webpack --progress',
prepublish: 'npm run build'
},
dependencies: {
'@homebridge/node-pty-prebuilt-multiarch': '^0.11.14',
async: '^2.6.3',
'async-promises': '^0.2.2',
axios: '^1.7.5',
chalk: '^2.4.2',
death: '^1.1.0',
deepmerge: '^2.2.1',
electron: '^25.2.0',
'fs-extra': '^5.0.0',
'gif-encoder': '^0.6.1',
inquirer: '^6.5.2',
'js-yaml': '^3.13.1',
lodash: '^4.17.15',
'performance-now': '^2.1.0',
pngjs: '^3.4.0',
progress: '^2.0.3',
'require-dir': '^1.1.0',
'string-argv': '0.0.2',
tmp: '^0.2.1',
uuid: '^10.0.0',
yargs: '^17.7.2'
},
devDependencies: {
ajv: '^6.12.6',
'clean-webpack-plugin': '^4.0.0',
'css-loader': '^4.3.0',
jquery: '^3.4.1',
'mini-css-extract-plugin': '^2.7.6',
'terminalizer-player': '^0.4.1',
webpack: '^5.88.1',
'webpack-cli': '^4.10.0',
xterm: '^v3.14.5'
},
gitHead: '4e3dc19fb22d8cae973a43e84bf3476e17324eb5',
dist: {
integrity: 'sha512-eDi+ezFetag//7/0Y6C/XlxVPBjMkM3pvYUr1gV6CJy8hEx2vjNWqubiw87psdrMnXSOTDthDWSvpArECuM9cA==',
shasum: '34902a4ba501590ef9c424402ad041d3da95c374',
tarball: 'https://registry.npmjs.org/terminalizer/-/terminalizer-0.12.0.tgz',
fileCount: 37,
unpackedSize: 3056377,
signatures: [
{
keyid: 'SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA',
sig: 'MEYCIQC8jjOg0DNdqA7HYVjGpBlFjUHb4ecynEYj8+xBVVDYYwIhALa2t0LNJgzgzaQIxF0h+HzYJfCoaXZ7/oZKoJ7t0/SQ'
}
]
},
directories: {}
}
Done in 0.45s.
~~~
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the global installation with Yarn and inspect the package entry point shown as bin/app.js, along with the installation metadata that declares the terminalizer binary. Verify how the global binary directory is exposed to the shell, then confirm that a fresh installation makes the terminalizer command discoverable on PATH.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100