chore: upgrade npm packages

[koladilip]

What are the changes introduced in this PR?

Upgrade to address security vulnerability

What is the related Linear task?

Please explain the objectives of your changes below

Put down any required details on the broader aspect of your changes. If there are any dependent changes, mandatorily mention them here

Any changes to existing capabilities/behaviour, mention the reason & what are the changes ?

N/A

Any new dependencies introduced with this change?

N/A

Any new generic utility introduced or modified. Please explain the changes.

N/A

Any technical or performance related pointers to consider with the change?

N/A

@coderabbitai review

---

Developer checklist

• My code follows the style guidelines of this project

• No breaking changes are being introduced.

• All related docs linked with the PR?

• All changes manually tested?

• Any documentation changes needed with this change?

• Is the PR limited to 10 file changes?

• Is the PR limited to one linear task?

• Are relevant unit and component test-cases added?

Reviewer checklist

• Is the type of change in the PR title appropriate as per the changes?

• Verified that there are no credentials or confidential data exposed with the changes.

Summary by CodeRabbit

• Chores
  • Updated ESLint configuration to ignore .properties files
  • Upgraded Vite development dependency to version 6.0.11

[coderabbitai]

Walkthrough

The pull request introduces two minor changes: an update to the .eslintignore file to exclude .properties files from ESLint linting, and an upgrade of the Vite development dependency from version 5.2.13 to 6.0.11 in the package.json file. These modifications appear to be focused on project configuration and dependency management.

Changes

File	Change Summary
.eslintignore	Added *.properties to ignore list for ESLint
package.json	Updated Vite dev dependency from ^5.2.13 to ^6.0.11

Poem

🐰 A Rabbit's Ode to Config Delight

Ignore those .properties with might,
Vite bumped up, a version so bright,
Linting clean, dependencies tight,
Configuration dancing just right!

🔧✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d819513 and ecabdcf.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• .eslintignore (1 hunks)
• package.json (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• .eslintignore

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Run Tests
• GitHub Check: Check for formatting & lint errors

🔇 Additional comments (3)

package.json (3)

Line range hint 1-77: Verify security vulnerability claims in PR description.

The PR description mentions addressing security vulnerabilities, but only updates Vite which is a development dependency. Could you please:

1. Specify which security vulnerability is being addressed
2. Confirm if there are other packages that need updating for security purposes

Let's check for any security advisories in the project:

---

Line range hint 54-55: Verify build script compatibility.

The build scripts use Vite commands. Ensure these commands remain compatible with Vite 6:

"build": "vite build && tsc",
"dev": "vite",

Let's check the build command changes between Vite 5 and 6:

✅ Verification successful

Build scripts are compatible with Vite 6 ✅

The current build scripts use basic Vite commands without any deprecated flags or syntax. Both vite build and vite commands maintain backward compatibility in Vite 6.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Compare Vite CLI commands between versions

echo "Checking Vite CLI documentation changes..."
curl -s https://api.github.com/repos/vitejs/vite/compare/v5.0.0...v6.0.0 | \
  jq -r '.files[] | select(.filename | contains("docs") and contains("cli.md")) | .patch'

Length of output: 2238

---

50-50: Verify Vite major version upgrade implications.

The upgrade from Vite 5.x.x to 6.0.11 is a major version bump that may introduce breaking changes. Please ensure:

1. Review the migration guide
2. Verify build script compatibility
3. Check for any known issues with 6.0.11

Let's verify the version and security implications:

✅ Verification successful

Vite 6.0.11 upgrade appears safe to proceed

The upgrade should be straightforward as:

• You're using the latest stable version
• Your basic build/dev setup isn't affected by breaking changes
• Vite 6 maintains compatibility for standard use cases

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check Vite versions, migration guide, and security advisories

# Get latest version from npm
echo "Latest Vite version:"
npm view vite version

# Check for security advisories
echo -e "\nSecurity advisories:"
npm audit [email protected]

# Fetch migration guide URL
echo -e "\nMigration guide:"
curl -s https://api.github.com/repos/vitejs/vite/releases/tags/v6.0.0 | jq -r '.body' | grep -A 5 "Migration"

Length of output: 668

---

Script:

#!/bin/bash
# Description: Check Vite usage and fetch migration guide

# Check build configuration and usage
echo "Vite configuration and usage:"
fd -e js -e ts -e json vite.config
fd -e js -e ts -e json -x cat {} \; | grep -B2 -A2 "vite"

# Fetch migration guide from docs
echo -e "\nMigration guide from docs:"
curl -s https://raw.githubusercontent.com/vitejs/vite/main/docs/guide/migration.md

# Check package-lock.json for previous version
echo -e "\nPrevious Vite version:"
if [ -f package-lock.json ]; then
    cat package-lock.json | grep -A 5 '"vite":'
fi

Length of output: 12958

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟢	Statements	93.24% (-6.65% 🔻)	4838/5189
🟢	Branches	92.75% (-7.18% 🔻)	1215/1310
🟢	Functions	100%	387/387
🟢	Lines	93.24% (-6.65% 🔻)	4838/5189

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	engine.ts	95.33% (-4.67% 🔻)	88.46% (-11.54% 🔻)	100%	95.33% (-4.67% 🔻)
🟢	lexer.ts	87.18% (-12.82% 🔻)	91.93% (-8.07% 🔻)	100%	87.18% (-12.82% 🔻)
🟢	parser.ts	88.56% (-11.44% 🔻)	89.78% (-10.22% 🔻)	100%	88.56% (-11.44% 🔻)
🟢	utils/common.ts	100%	88.89% (-11.11% 🔻)	100%	100%
🟢	utils/converter.ts	89.19% (-9.63% 🔻)	84.43% (-14.86% 🔻)	100%	89.19% (-9.63% 🔻)

Test suite run success

218 tests passing in 7 suites.

Report generated by 🧪jest coverage report action from ecabdcf

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.53%. Comparing base (97d95e8) to head (ecabdcf).
Report is 66 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##              main     #132      +/-   ##
===========================================
- Coverage   100.00%   91.53%   -8.47%     
===========================================
  Files           14       18       +4     
  Lines         4565     5189     +624     
  Branches      1082     1144      +62     
===========================================
+ Hits          4565     4750     +185     
- Misses           0      429     +429     
- Partials         0       10      +10     

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
90.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud