Use the TroJS lint rules

[w3nl]

Summary by CodeRabbit

• Chores
  • Upgraded the Node.js version in build and deployment workflows.
  • Updated package dependencies and testing scripts for improved reporting.
• New Features
  • Introduced a new debugging configuration for Node.js applications in the development environment.
• Style
  • Applied consistent code formatting across tests and source files for enhanced readability.

[coderabbitai]

Walkthrough

The pull request updates several configuration files and code formatting without altering the underlying functionality. Node.js versions in GitHub workflows have been bumped from 20 to 22, and the ESLint configuration has been streamlined by leveraging a single linting package. The package metadata in package.json is updated with a new version, revised test scripts, and dependency changes. Additionally, the repository’s .gitignore has been modified to track Visual Studio Code files, and a new VS Code launch configuration for debugging Node.js tests has been added. Indentation adjustments improve the readability of both test and source files.

Changes

File(s)	Change Summary
.github/workflows/npmpublish.yml, .github/workflows/sonarcloud.yml	Updated Node.js version from 20(20.x) to 22(22.x) in workflow jobs and strategy matrix.
.gitignore	Removed the .vscode entry to allow VS Code configuration files to be tracked.
.vscode/launch.json	Added a new debug configuration for launching Node.js tests from VS Code.
eslint.config.js	Simplified configuration by importing plugins and rules from @trojs/lint and merging globals.
package.json	Bumped version (1.0.2 → 1.0.3), modified test scripts, updated jscpd, added @trojs/lint, and removed several ESLint-related dependencies.
src/(__tests__/*, default.js, string-helper.js)	Reformatted indentation and method signatures in both test and source files without changing functionality.

Poem

I’m a bunny with a coding flair,
Hopping through configs with extra care.
Node’s now twenty-two, and lint shines bright,
Debug and tests aligned just right.
With formatted hops, I cheer our flight!
🐰💻

---

📜 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 45600d6 and e4283db.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (10)

• .github/workflows/npmpublish.yml (2 hunks)
• .github/workflows/sonarcloud.yml (1 hunks)
• .gitignore (0 hunks)
• .vscode/launch.json (1 hunks)
• eslint.config.js (1 hunks)
• package.json (3 hunks)
• src/__tests__/default.unit.js (1 hunks)
• src/__tests__/string-helper.unit.js (1 hunks)
• src/default.js (1 hunks)
• src/string-helper.js (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.
• @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.

[w3nl]

@coderabbitai summary

[coderabbitai]

✅ Actions performed

Summary regeneration triggered.

PR Overview

This PR upgrades the Node.js version to 22 across GitHub workflow configurations and slightly adjusts test file formatting for consistency.

• Upgraded Node.js version in npmpublish and sonarcloud workflows.
• Adjusted whitespace in test files for improved formatting.

Reviewed Changes

File	Description
.github/workflows/npmpublish.yml	Updated Node.js version from 20 to 22
src/tests/string-helper.unit.js	Removed extraneous blank lines in test block
.github/workflows/sonarcloud.yml	Updated Node.js version from 20.x to 22.x

Copilot reviewed 12 out of 12 changed files in this pull request and generated no comments.