Aquesta és una versió anterior. La versió actual és la 2.8.3. aube 2.8.3 · Data de publicació:
Fitxers d’instal·lació 2.5.0
| Arquitectura | Tipus | Àmbit | Mida del fitxer | Baixa | SHA256 |
|---|---|---|---|---|---|
| 64 bits | ZIP → Portable | — | — | github.com | VirusTotal |
| ARM64 | ZIP → Portable | — | — | github.com | VirusTotal |
L’enllaç i l’SHA256 provenen del manifest comunitari del Gestor de paquets del Windows. Convé comparar el hash del fitxer baixat abans d’executar-lo.
Notes de la versió
aube update --interactive now lets you pick, for each package, whether to keep the current version, move to the newest version its range allows, or jump to latest. Repeated frozen installs and fresh installs without a lockfile are also faster, and a reinstall that failed after you deleted the cache and lockfile now works.
Added
- Per-package version choice in aube update --interactive (#1612 by @jdx): The picker used to be one checkbox per dependency, with the target set by flags. It is now a table, like Yarn Berry's upgrade-interactive. Each row shows the current version, the newest version the range allows, and the registry's latest. Use ↑/↓ to move between rows and ←/→ to choose a version. Rows left on Current are skipped, and / filters by name. Closes #1611.
$ aube update -i
Choose which dependencies to update
Current Range Latest
> chalk [•] ^4.1.2 [ ] ^6.0.0
is-number [•] ^6.0.0 [ ] ^7.0.0
ms [ ] 2.0.0 [•] 2.1.3
semver [ ] 7.5.0 [•] 7.8.5
↑/↓/k/j up/down • ←/→/h/l choose • / filter • enter confirm
- Rows start on Range, or on Latest with --latest. Pressing Enter right away does the same thing as the non-interactive command.
- Updates keep the manifest's range operator. Exact pins are now listed: each one is offered the newest release its caret range would allow, and it stays an exact pin after the update. -E still forces exact pins.
- --no-save hides Latest and pin bumps, because both would rewrite package.json.
- Latest is offered only when it is newer than the installed version, so the picker never offers a downgrade.
- With update -r -i, the version you choose for a shared catalog entry is used for later workspace packages without asking again.
- Rows no longer show the dependency section (dependencies / devDependencies).
Changed
- Faster repeated frozen installs (#1615 by @jdx): Standalone projects can now reuse the installed state when nothing has changed. This applies to projects with registry dependencies and no declared patches, installed with an explicit --frozen-lockfile and lifecycle scripts disabled (for example aube install --frozen-lockfile --offline --ignore-scripts). On the benchmark fixture, a no-op install went from about 82 ms to about 7 ms. The freshness check hashes the lockfile and manifest contents, so a change is caught even when file size and modification time stay the same. A missing dependency link also counts as a change. Workspaces, patches, local sources, enabled scripts, custom lockfile locations and active per-install advisory policies still go through full validation.
- Faster advisory checks on fresh installs (#1616 by @jdx): A fresh install without a lockfile used to query OSV for every resolved public-npm package. Under the default advisoryCheck: on, graphs with more than 10 distinct package/version pairs are now screened with the advisory Bloom filter first, and only probable hits are checked against the live API. On the benchmark fixtures this cut fresh install time by 36–67%.
- Full live checks are still used for smaller graphs, for explicit aube add / aube update, for transient aube dlx installs, and with advisoryCheck: required or advisoryCheckEveryInstall: true.
- If the filter can't be refreshed or validated, every package is checked live.
- The filter cache refreshes every 15 minutes, so a newly published advisory may take up to that long to be caught.
Fixed
- "missing package index" after deleting the cache and lockfile (#1613 by @jdx): A reinstall could fail with this error if you had deleted aube's cache/store and the root lockfile but kept node_modules. Now an existing package directory is reused only when its dependency subtree matches the previous install and the directory still exists. Anything else is looked up in the store again, or downloaded again, before linking.
💚 Sponsor aube
aube is built and maintained by @jdx, an open source developer at entire.io, the title sponsor of his open source work.
If aube saves your team install time or CI minutes, please consider becoming an individual or company sponsor. Your support funds ongoing development and helps keep aube fast, free, and independent.