chore: upgrading writr to 5.0.4

[jaredwray]

Please check if the PR fulfills these requirements

• Followed the Contributing and Code of Conduct guidelines.
• Tests for the changes have been added (for bug fixes/features) with 100% code coverage.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
chore: upgrading writr to 5.0.4

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a routine maintenance update by upgrading the writr dependency to its latest patch version, 5.0.4. This ensures the project benefits from the most recent bug fixes and minor improvements in writr and its underlying dependencies, as reflected in the updated pnpm-lock.yaml.

Highlights

• Dependency Upgrade: The writr package has been updated from version 5.0.3 to 5.0.4 in package.json.
• Lockfile Synchronization: The pnpm-lock.yaml file has been updated to reflect the new writr version and its transitive dependency changes, including acorn, hashery, html-dom-parser, html-react-parser, katex, and mdast-util-from-markdown.

Changelog

• package.json
  • Updated writr dependency to ^5.0.4.
• pnpm-lock.yaml
  • Updated writr dependency to 5.0.4.
  • Updated acorn from 8.15.0 to 8.16.0.
  • Removed hashery@1.4.0 and updated hashery to 1.5.0.
  • Updated html-dom-parser from 5.1.4 to 5.1.8.
  • Updated html-react-parser from 5.2.14 to 5.2.17.
  • Updated katex from 0.16.28 to 0.16.33.
  • Updated mdast-util-from-markdown from 2.0.2 to 2.0.3 across multiple entries.

Activity

• The pull request author, jaredwray, initiated this chore to upgrade the writr dependency.
• The author has confirmed adherence to contributing guidelines and code of conduct.
• Tests have been added and achieved 100% code coverage, as indicated by the PR description checkboxes.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (138e593) to head (41c60e6).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #336   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            9         9           
  Lines          417       417           
  Branches        97        97           
=========================================
  Hits           417       417           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gemini-code-assist]

Code Review

This pull request upgrades the writr dependency from version 5.0.3 to 5.0.4. The change is straightforward and correctly updates package.json and the corresponding pnpm-lock.yaml. I've noted an opportunity to improve dependency consistency by aligning the version of the hookified package, which is a direct dependency of this project and also a transitive dependency of writr.

[gemini-code-assist]

This upgrade to writr@5.0.4 brings in hookified@1.15.1 as a transitive dependency. The project's package.json currently specifies a direct dependency on hookified: ^1.15.0 (line 56), which resolves to 1.15.0. This leads to having two versions of hookified in the project.

To maintain consistency and avoid potential conflicts, it would be beneficial to update the direct dependency on hookified to ^1.15.1.