chore(deps): update pp-dev to 0.19.0

[sergak01]

Automated update of @metricinsights/pp-dev dependency.

• Previous: 0.18.3
• New: 0.19.0

[coderabbitai]

📝 Walkthrough

Walkthrough

The @metricinsights/pp-dev devDependency is bumped from ^0.18.3 to ^0.19.0 in five package.json files: the root package and all four template packages (template-nextjs, template-react, template-vanilla-ts, template-vanilla).

Changes

pp-dev Dependency Bump

Layer / File(s)	Summary
pp-dev bump across root and templates package.json, template-nextjs/package.json, template-react/package.json, template-vanilla-ts/package.json, template-vanilla/package.json	@metricinsights/pp-dev devDependency updated from ^0.18.3 to ^0.19.0 in all five package manifests.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• mi-examples/create-pp-dev#8: Same pattern — dependency-only bump of @metricinsights/pp-dev across all package.json files.
• mi-examples/create-pp-dev#174: Directly precedes this PR; bumped @metricinsights/pp-dev to ^0.18.3, which this PR supersedes with ^0.19.0.
• mi-examples/create-pp-dev#126: Identical change pattern, bumping @metricinsights/pp-dev across the same set of root and template package.json files.

Suggested reviewers

• MaksymovVolodymyr
• michailozdemir
• Sadilenko

Poem

🐇 Hop, hop, a version leap!
From .18.3 to .19.0 — not too steep.
Five files updated, all in a row,
The rabbit stamps each package with a bow.
A tiny change, but onwards we go! 🌟

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and accurately summarizes the main change: a dependency version update of @metricinsights/pp-dev to 0.19.0 across multiple package.json files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch deps/update-pp-dev

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 74: The `@metricinsights/pp-dev` dependency in package.json has been bumped
to ^0.19.0 but package-lock.json still resolves to version 0.18.3, causing a
manifest-lock mismatch. Regenerate package-lock.json by running npm install to
sync the lock file with the updated package.json dependency version, then commit
the updated package-lock.json file.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1bd97c3b-fe72-4330-9b8b-03f5e4099455

📥 Commits

Reviewing files that changed from the base of the PR and between 9a1ae57 and 74251e3.

📒 Files selected for processing (5)

• package.json
• template-nextjs/package.json
• template-react/package.json
• template-vanilla-ts/package.json
• template-vanilla/package.json

[coderabbitai]

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Lockfile is out of sync with the bumped dependency.

package.json now requests @metricinsights/pp-dev ^0.19.0, but package-lock.json still resolves 0.18.3 (see package-lock.json Line 1677+ in provided context). This can cause CI/install drift or npm ci failure due to manifest-lock mismatch. Please regenerate and commit package-lock.json with the new resolved version.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` at line 74, The `@metricinsights/pp-dev` dependency in
package.json has been bumped to ^0.19.0 but package-lock.json still resolves to
version 0.18.3, causing a manifest-lock mismatch. Regenerate package-lock.json
by running npm install to sync the lock file with the updated package.json
dependency version, then commit the updated package-lock.json file.