pesde
@pesde.dev
A package manager for the Luau programming language, supporting multiple runtimes including Roblox and Lune
Totally forgot to mention here, but pesde now supports an "engines" system.
Packages can choose what version of pesde and lune they want, and they'll automatically be managed by pesde. Similarly, `self-upgrade` now uses the same engines mechanism under the hood.
Also, check out this slick output!
Packages can choose what version of pesde and lune they want, and they'll automatically be managed by pesde. Similarly, `self-upgrade` now uses the same engines mechanism under the hood.
Also, check out this slick output!
February 8, 2025 at 7:26 AM
Totally forgot to mention here, but pesde now supports an "engines" system.
Packages can choose what version of pesde and lune they want, and they'll automatically be managed by pesde. Similarly, `self-upgrade` now uses the same engines mechanism under the hood.
Also, check out this slick output!
Packages can choose what version of pesde and lune they want, and they'll automatically be managed by pesde. Similarly, `self-upgrade` now uses the same engines mechanism under the hood.
Also, check out this slick output!
Similarly, deprecation allows you to disallow entire packages from being depend on, displaying a warning on the package's page.
February 7, 2025 at 9:02 AM
Similarly, deprecation allows you to disallow entire packages from being depend on, displaying a warning on the package's page.
It is now also possible to yank and deprecate. Yanking is a version specific operation which marks a specific version of your package as unresolvable, unless someone already explicitly depends on it in their lockfile. This is useful if you accidentally publish a broken version of your package.
February 7, 2025 at 9:02 AM
It is now also possible to yank and deprecate. Yanking is a version specific operation which marks a specific version of your package as unresolvable, unless someone already explicitly depends on it in their lockfile. This is useful if you accidentally publish a broken version of your package.
In order to make pesde's already disk-efficient caching even more convenient, pesde now has the ability to prune its CAS store from the CLI. Run `pesde cas prune` to remove unused packages from the CAS and claim back your disk space!
February 7, 2025 at 9:02 AM
In order to make pesde's already disk-efficient caching even more convenient, pesde now has the ability to prune its CAS store from the CLI. Run `pesde cas prune` to remove unused packages from the CAS and claim back your disk space!
We include some more useful utility commands for dependency management now -- namely, `list` to list all dependencies and `remove` to remove a dependency from the manifest.
February 7, 2025 at 9:02 AM
We include some more useful utility commands for dependency management now -- namely, `list` to list all dependencies and `remove` to remove a dependency from the manifest.
We have fully rewritten the installation experience, with improved and ✨pretty✨ outputs. But that's not all! Installs are incremental now, meaning pesde does not attempt to install all dependencies from scratch, and only installs those which have had changes.
February 7, 2025 at 9:02 AM
We have fully rewritten the installation experience, with improved and ✨pretty✨ outputs. But that's not all! Installs are incremental now, meaning pesde does not attempt to install all dependencies from scratch, and only installs those which have had changes.