Boost your real estate sales with online auctions, powered by Enchères Immo's API 🚀
This repository contains all open-source packages developed by Enchères Immo :
| Package | Link | Description | README |
|---|---|---|---|
docs |
WIP | Coming soon | README |
packages/auction-widget |
 |
An auction widget for your website | README |
packages/widget-client |
 |
Build your own auction widget | README |
This repository is maintained by Enchères Immo, but we deeply appreciate any contribution from the community, no matter how small or big.
📖 Main repository, with all our public packages.
🐛 Report a bug, please read our contributing guidelines and code of conduct first.
🚨 Report a security vulnerability, and be sure to review our security policy.
💬 Join the discussion, if you have any questions, ideas, or suggestions.
We use pnpm as our package manager, since it's not only faster and safer than npm and yarn, but also because it has better support for monorepos. Global commands are :
| Command | Action |
|---|---|
pnpm install |
Installs dependencies for all packages |
pnpm changeset |
Generate a changeset for a pull request |
For package-specific commands and instructions, please refer to the README of the package, listed above.
We use GitHub Actions to automate our CI/CD pipeline. When a pull request is opened, the following checks are performed for all packages: linting (WIP), testing, and building. Learn more here.
Labels are also automatically added to indicate where the changes are located. Learn more here.
If your changes concern a published package (labels starting with pkg:), you will need to generate a changeset using the pnpm changeset command. This will create a new file in the .changeset directory. Once the pull request is merged, a release pull request will be created, consuming all changesets into changelogs and version bumps. Learn more here.
Merging the release pull request will automatically publish the new versions to npm and the CDN. Learn more here and here.