chore: bump node version to lts

[iiio2]

Summary by CodeRabbit

• Chores
  • Updated Node.js runtime versions for build and deployment environments to use LTS-supported versions.

[coderabbitai]

Walkthrough

Two Node.js version configurations updated: .node-version constraint changed from a specific version (22.14.0) to an LTS alias (lts/*), and the Netlify build environment NODE_VERSION incremented from 22 to 24.

Changes

Cohort / File(s)	Summary
Node.js version updates .node-version, netlify.toml	.node-version: Version constraint relaxed from fixed release (22.14.0) to LTS alias (lts/*). netlify.toml: Build environment NODE_VERSION bumped from 22 to 24.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Simple configuration updates with no logic or behavioral changes; purely version number adjustments across two files.

Poem

🐰 Hop, hop, the versions dance so free,
From fixed to LTS—flexibility!
And twenty-four now powers the build,
With modern Node, our needs are filled! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "chore: bump node version to lts" directly relates to the primary change in the .node-version file, where the version is being changed from a fixed version (22.14.0) to an LTS alias (lts/*). The title is concise, specific, and clearly communicates the semantic intent of the change. While the changeset also includes a version bump in netlify.toml (from 22 to 24), the title appropriately focuses on the more significant architectural change of adopting LTS versions, which aligns with the guidance that titles don't need to cover every detail of the changeset.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.}

[github-actions]

Size Report

Bundles

File	Size	Gzip	Brotli
runtime-dom.global.prod.js	102 kB	38.6 kB	34.8 kB
vue.global.prod.js	160 kB	58.7 kB	52.2 kB

Usages

Name	Size	Gzip	Brotli
createApp (CAPI only)	46.7 kB	18.3 kB	16.7 kB
createApp	54.7 kB	21.3 kB	19.5 kB
createSSRApp	58.9 kB	23 kB	21 kB
defineCustomElement	60 kB	23 kB	21 kB
overall	68.8 kB	26.5 kB	24.2 kB

[pkg-pr-new]

Open in StackBlitz

@vue/compiler-core

npm i https://pkg.pr.new/@vue/compiler-core@14026

@vue/compiler-dom

npm i https://pkg.pr.new/@vue/compiler-dom@14026

@vue/compiler-sfc

npm i https://pkg.pr.new/@vue/compiler-sfc@14026

@vue/compiler-ssr

npm i https://pkg.pr.new/@vue/compiler-ssr@14026

@vue/reactivity

npm i https://pkg.pr.new/@vue/reactivity@14026

@vue/runtime-core

npm i https://pkg.pr.new/@vue/runtime-core@14026

@vue/runtime-dom

npm i https://pkg.pr.new/@vue/runtime-dom@14026

@vue/server-renderer

npm i https://pkg.pr.new/@vue/server-renderer@14026

@vue/shared

npm i https://pkg.pr.new/@vue/shared@14026

vue

npm i https://pkg.pr.new/vue@14026

@vue/compat

npm i https://pkg.pr.new/@vue/compat@14026

commit: 526103e

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.node-version (1)

1-1: Consider pinning to a specific LTS version instead of using lts/*.

Changing from 22.14.0 to lts/* introduces automatic version drift:

• Different developers may end up with different Node.js versions over time
• The version will change when a new LTS is released, potentially causing unexpected behavior
• This conflicts with netlify.toml which pins to version 24

Consider using a specific LTS version (e.g., lts/iron for Node.js 20, lts/jod for Node.js 22, or the version number directly) to ensure consistent environments across the team and CI/CD.

Apply this diff to align with the Netlify configuration (assuming Node.js 24 is the intended version):

-lts/*
+24

Or use a specific LTS codename if available:

-lts/*
+lts/[codename]

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 45547e6 and 526103e.

📒 Files selected for processing (2)

• .node-version (1 hunks)
• netlify.toml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Redirect rules
• GitHub Check: test / e2e-test
• GitHub Check: Header rules
• GitHub Check: Pages changed

🔇 Additional comments (1)

netlify.toml (1)

2-2: No issues found. Node.js 24 is LTS and version is consistent.

Node.js 24 entered Active LTS on October 28, 2025, and lts/* resolves to Node.js 24 (24.x). The NODE_VERSION = "24" setting in netlify.toml is consistent with the lts/* reference in .node-version—both point to the same LTS release. The PR successfully achieves its stated intent to bump to LTS.