Tools for manipulating Sims 2 mod files on the web :computer:
First-time setup:
pnpmpnpm installpnpm buildRunning the app:
pnpm start to run dev server with all packages in watch modepnpm simpai preview to preview prod build (after running pnpm build)This repo enforces conventional commits to automate versioning and per-package changelog generation. This means commit messages must adhere to the following pattern:
type(scope): subject
optional body
where type is one of
featfixdocsstylerefactortestrevertscope is the name of a package in /packages, and subject is a normal commit message. If more context is needed, you can add a body after a newline. Example:
feat(dbpf-transform): add strange smells
they're pretty stinky
For breaking changes, add a ! after the scope:
feat(simpai)!: delete everything
For changes to the repo root, just omit the scope:
docs: add docs for conventional commits
Upon merging new code into main, release-please will create a pull request (PR) for each package that
has unreleased changes. Merging that PR will release those changes, which includes
CHANGELOG.md file to reflect any newly released changespackage.json according to the type of changes that were in the releaseFor versioning, fix indicates a SemVer patch bump, feat indicates a SemVer minor bump (or patch if < 1.0.0), and a trailing ! indicates
a SemVer major bump (or minor if < 1.0.0). All other types are not considered user-facing and do not indicate a bump of any kind.
packages/package.jsonrelease-please-config.json (see config options).release-please-manifest.json