chromedriver executable in not available after pixi environment activation on Windows

[carlodri]

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

Mostly what the title says. I have checked that chromedriver.exe indeed exists but it is not available as executable after pixi environment activation.

Installed packages

...

Environment info

❯ pixi info
System
------------
       Pixi version: 0.54.2
           Platform: win-64
   Virtual packages: __win=10.0.19045=0
                   : __cuda=12.4=0
                   : __archspec=1=skylake
          Cache dir: D:\.pixi\cache
       Auth storage: C:\Users\...\.rattler\credentials.json
   Config locations: No config files found

Global
------------
            Bin dir: D:\.pixi\bin
    Environment dir: D:\.pixi\envs
       Manifest dir: D:\.pixi\manifests\pixi-global.toml

Workspace
------------
               Name: ...
            Version: 0.1.0
      Manifest file: D:\...\pixi.toml
       Last updated: 12-09-2025 15:14:28

Environments
------------
        Environment: default
           Features: default
           Channels: conda-forge, ...
   Dependency count: 18
       Dependencies: python, ipykernel, holoviews, numpy, scipy, scikit-image, ipywidgets, rich, nbstripout, joblib, lmfit, opencv, scikit-learn, findpeaks, polars, fang_line_scan_undistortion, selenium, python-chromedriver-binary
   Target platforms: win-64
    Prefix location: D:\...\.pixi\envs\default

[bollwyvl]

Yeah, the upstream package doesn't claim to do that, rather it offers a command which provides a path to the executable, as shown in the API/CLI examples. Indeed, it would make sense to package chromedriver directly, but that would be another feedstock, ideally built from source...

[carlodri]

But the executable is in the package, right? so maybe it should be made accessible?