Packages

PlaidCloud Git includes a built-in package registry for distributable artifacts and Git Large File Storage (LFS) for large binary files inside your repositories.

About the Package Registry

The package registry is per-owner and supports a wide range of ecosystem formats — npm, PyPI, Maven, NuGet, RubyGems, container images, and more. Packages are private to your workspace and accessible only to authenticated members.

Each package type has its own endpoint under:

https://git.example.plaidcloud.com/api/packages/you/<type>

where <type> is the ecosystem identifier (for example, npm, pypi, or maven).

Authenticate to the Registry

Package manager operations use your PlaidCloud Git username and a personal access token as the password. See Repositories for how to create a token.

Publish a Package

The steps vary by ecosystem, but the pattern is the same: point your package manager at the registry URL and run its standard publish command.

For npm, add a .npmrc to your project to scope packages to the registry:

@you:registry=https://git.example.plaidcloud.com/api/packages/you/npm/
//git.example.plaidcloud.com/api/packages/you/npm/:_authToken=YOUR_TOKEN

Then publish as usual:

npm publish

For PyPI, Maven, NuGet, and other ecosystems, configure the tool’s repository or source setting to the matching registry URL and use that tool’s standard publish command (for example, twine upload, mvn deploy, or dotnet nuget push).

Install a Package

Point your package manager at the same registry URL and install as usual. With the .npmrc above in place:

npm install @you/my-package

For other ecosystems, add the registry as an additional source in your tool’s configuration and use its standard install command.

Large Files with Git LFS

Git LFS keeps your repository fast by replacing large or binary files in history with lightweight pointers and storing the file data separately. LFS is enabled for every PlaidCloud Git repository.

Install the LFS client once on your machine:
Terminal window
```
git lfs install
```
Tell LFS which file patterns to track, from inside your repository:
Terminal window
```
git lfs track "*.parquet"
```
This creates or updates .gitattributes. Commit that file:
Terminal window
```
git add .gitattributes
git commit -m "Track Parquet files with LFS"
```

Add and push as normal — matching files upload to LFS automatically:

git add data/large-dataset.parquet
git commit -m "Add dataset"
git push origin main