pixi-reels 0.3.0 → 0.3.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,17 @@
1
1
  # pixi-reels
2
2
 
3
+ ## 0.3.2
4
+
5
+ ### Patch Changes
6
+
7
+ - [`b86dad7`](https://github.com/schmooky/pixi-reels/commit/b86dad75fcdd4936170bb96a6084904bad419dd3) Thanks [@igaming-bulochka](https://github.com/igaming-bulochka)! - Fix: ship `CONTRIBUTING.md` in the npm tarball so the npmjs.com "Contributing" sidebar link resolves. npmjs builds that link from `repository.directory` (`packages/pixi-reels`) and a standard filename, but the file previously only existed at the monorepo root — the link 404'd. The build script now syncs `CONTRIBUTING.md` into the package alongside `README.md` and `LICENSE`, and the package's `files` array includes it.
8
+
9
+ ## 0.3.1
10
+
11
+ ### Patch Changes
12
+
13
+ - [`93aa66c`](https://github.com/schmooky/pixi-reels/commit/93aa66c103ef0f624345c76a92a22621fc3c676a) Thanks [@igaming-bulochka](https://github.com/igaming-bulochka)! - Update: package `homepage` now points at the canonical docs site, `https://pixi-reels.schmooky.dev`. No code or runtime change — npm metadata and the docs site URL only.
14
+
3
15
  ## 0.3.0
4
16
 
5
17
  ### Minor Changes
@@ -0,0 +1,85 @@
1
+ # Contributing
2
+
3
+ Thanks for your interest in pixi-reels. This file covers the mechanics of contributing. For the house style and load-bearing design constraints, read [`AGENTS.md`](./AGENTS.md) first — several of those rules are enforced by lint guards and pre-commit hooks, so they'll block a merge if you break them.
4
+
5
+ ## Quick start
6
+
7
+ ```bash
8
+ git clone https://github.com/schmooky/pixi-reels.git
9
+ cd pixi-reels
10
+ pnpm install
11
+ pnpm --filter pixi-reels test # vitest + typecheck
12
+ pnpm site:dev # docs site at http://localhost:4321
13
+ pnpm --filter classic-spin dev # classic 5×3 example
14
+ ```
15
+
16
+ Node 20+ is required. The repo uses pnpm workspaces.
17
+
18
+ ## Workflow
19
+
20
+ 1. **Branch from `main`.** Name it something human like `fix/stop-phase-slicing` or `feat/expanding-wilds`. Long-lived preview branches use `v*` (e.g. `v0.2`) and publish [snapshot releases](./README.md#snapshot-releases) automatically.
21
+
22
+ 2. **Make focused changes.** One logical change per PR. If you notice a second bug while fixing the first, open a second PR.
23
+
24
+ 3. **Run the test suite:** `pnpm test`. This runs the lint guards and all vitest suites. They must pass before review.
25
+
26
+ 4. **If your change ships user-visible behavior in a publishable package, add a changeset:**
27
+
28
+ ```bash
29
+ pnpm changeset
30
+ ```
31
+
32
+ Pick the affected packages and the bump kind (`patch` / `minor` / `major`) and commit the resulting `.changeset/*.md` file. Changes to private apps (`@pixi-reels/site`, any `examples/*`) don't need a changeset — those are deployed, not published.
33
+
34
+ 5. **Open a PR.** The template asks for a summary, a test plan, and confirmation that a changeset was added.
35
+
36
+ ## What "good" looks like in this repo
37
+
38
+ - **Small, readable diffs.** Don't sneak in refactors that weren't asked for. If a refactor is needed for a fix, do it in a separate commit in the same PR with a clear message.
39
+ - **Comments explain "why", not "what".** The code already says what it does; comments should capture the non-obvious reason a line exists.
40
+ - **No emoji in source, commit messages, changelog entries, or UI strings.** The fancy-Unicode lint guard enforces this. Use ASCII punctuation.
41
+ - **No default exports.** Always named. Tree-shaking and auto-imports both depend on this.
42
+ - **`.js` extensions in imports.** Even from `.ts` sources — this is required by Node ESM resolution of the published build.
43
+
44
+ ## GitHub Actions are pinned to SHAs
45
+
46
+ Every third-party action in `.github/workflows/` is pinned to a full commit SHA with the human version as a trailing comment, e.g.
47
+
48
+ ```yaml
49
+ uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
50
+ ```
51
+
52
+ This is a supply-chain hardening step: a moving tag like `@v4` could be repointed at a malicious commit by a compromised maintainer account, but a SHA cannot. Dependabot keeps the SHAs fresh. Approve those `chore(ci)` PRs like any other dependency bump.
53
+
54
+ If you are adding a new action, resolve its major-version tag to a SHA with `git ls-remote` and commit both the SHA and the version comment in the same `uses:` line.
55
+
56
+ ## Releases
57
+
58
+ Every published package is versioned and shipped by [changesets](https://github.com/changesets/changesets) on merge to `main`. The full flow (and the snapshot release workflow for `v*` branches) is documented in the [Releases section of the README](./README.md#releases).
59
+
60
+ TL;DR:
61
+
62
+ - Your PR should include a `.changeset/*.md` file if it ships user-visible changes in a publishable package.
63
+ - After merge, a `chore: version packages` PR opens automatically. Merging that PR publishes the affected packages to npm.
64
+ - Branch previews publish to npm under a per-branch dist-tag (e.g. `pixi-reels@v0-2`) so reviewers can install work-in-progress versions without waiting for a merge.
65
+
66
+ ## Reporting bugs and proposing features
67
+
68
+ Use the issue forms:
69
+
70
+ - [Bug report](./.github/ISSUE_TEMPLATE/bug_report.yml)
71
+ - [Feature request](./.github/ISSUE_TEMPLATE/feature_request.yml)
72
+
73
+ For security issues, follow [`SECURITY.md`](./SECURITY.md) and do not open a public issue.
74
+
75
+ ## Crediting contributors
76
+
77
+ This project follows the [all-contributors](https://allcontributors.org) spec. Anyone who helps — code, docs, design, reviews, bug reports, ideas — gets credited in the README.
78
+
79
+ To add someone (or yourself), comment on any issue or PR:
80
+
81
+ ```
82
+ @all-contributors please add @their-github-handle for code, doc
83
+ ```
84
+
85
+ The bot opens a PR updating `.all-contributorsrc` and the contributors block in the README.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pixi-reels",
3
- "version": "0.3.0",
3
+ "version": "0.3.2",
4
4
  "description": "A batteries-included slot machine reel engine for PixiJS v8 — fluent builder, typed events, spin phases, speed modes, win spotlight, and a headless testing harness.",
5
5
  "type": "module",
6
6
  "main": "./dist/index.cjs",
@@ -22,7 +22,8 @@
22
22
  "dist",
23
23
  "README.md",
24
24
  "LICENSE",
25
- "CHANGELOG.md"
25
+ "CHANGELOG.md",
26
+ "CONTRIBUTING.md"
26
27
  ],
27
28
  "sideEffects": false,
28
29
  "publishConfig": {
@@ -50,7 +51,7 @@
50
51
  },
51
52
  "license": "MIT",
52
53
  "author": "schmooky",
53
- "homepage": "https://pixi-reels.dev",
54
+ "homepage": "https://pixi-reels.schmooky.dev",
54
55
  "bugs": {
55
56
  "url": "https://github.com/schmooky/pixi-reels/issues"
56
57
  },