https://github.com/rvxlab/composer-rs
Composer re-imagined in Rust
https://github.com/rvxlab/composer-rs
Last synced: 11 months ago
JSON representation
Composer re-imagined in Rust
- Host: GitHub
- URL: https://github.com/rvxlab/composer-rs
- Owner: RVxLab
- Created: 2023-10-07T12:11:32.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2023-10-21T05:36:45.000Z (over 2 years ago)
- Last Synced: 2025-03-28T03:07:41.499Z (over 1 year ago)
- Language: Rust
- Size: 44.9 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Composer RS
An experimental (and WIP) re-imagining of [Composer](https://github.com/composer/composer) written in Rust.
## (Intended) Features
- Near-full API compatibility with Composer
- Built-in [normalization](https://github.com/ergebnis/composer-normalize) support
- Multiple installation strategies
- Extracting directly to the `vendor/` folder (default)
- Extracting to a store and symlinking to `vendor/` (like pnpm)
## Implemented features
*TODO*
## Differences to Composer
While I strive to be as compatible with Composer as possible, there are a few differences.
### Config
Several configuration options are either unsupported (such as the PHP-specific ones) and some options have different defaults.
#### Unsupported config and env vars
The following environment variables are specific to PHP and have no effect:
- [`COMPOSER_ALLOW_XDEBUG`](https://getcomposer.org/doc/03-cli.md#composer-allow-xdebug)
- [`COMPOSER_DISABLE_XDEBUG_WARN`](https://getcomposer.org/doc/03-cli.md#composer-disable-xdebug-warn)
- [`COMPOSER_MEMORY_LIMIT`](https://getcomposer.org/doc/03-cli.md#composer-memory-limit)
#### Audits
`audit.abandoned` is set to `"report"` in Composer 2.6 and below, with `"fail"` becoming the default as of version 2.7. Because of that, `"fail"` is considered the default for composer-rs.
#### No suggest
Because the `--no-suggest` flag has been considered deprecated since Composer 2.0 and will be removed in 3.0, this flag has not been implemented.