Remove NODE_OPTIONS and regenerate package-lock.json

[chromium-52]

Summary by CodeRabbit

• Chores
  • Simplified the build script configuration by removing memory allocation constraints.
  • Updated ESLint configuration to consolidate ignore settings for specific directories.

[coderabbitai]

Walkthrough

The pull request involves a modification to the build script in the package.json file. The change removes the NODE_OPTIONS memory constraint setting that previously limited the maximum old space size to 4076 MB during the build process. The core build sequence remains unchanged, continuing to execute prebuild, build:css, and build:components scripts in order. Additionally, the eslint.config.js file has been updated to consolidate the ignore settings for specific directories, moving them to a top-level configuration object.

Changes

File	Change Summary
package.json	Removed NODE_OPTIONS='--max-old-space-size=4076' from build script, simplifying the build configuration.
eslint.config.js	Added ignores: ['assets/', 'dist/'] at the top level of the configuration, removing it from the main configuration object.

Possibly related PRs

• CI Step to run build scripts #561: The changes in the main PR regarding the build script in package.json are directly related to the CI step introduced in this PR, which executes the build command as part of the continuous integration process.

Suggested labels

automerge

Suggested reviewers

• kotAPI

Poem

🐰 A Build Script Hop and Skip
Memory limits no longer grip
Our code now builds with freedom's might
No constraints to dim its light
A rabbit's leap of pure delight! 🚀

---

📜 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 4ef30c4 and b21034d.

📒 Files selected for processing (1)

• eslint.config.js (1 hunks)

🔇 Additional comments (2)

eslint.config.js (2)

11-13: LGTM! Good structural improvement.

Moving the ignore patterns to a top-level configuration object follows ESLint flat config best practices and makes the configuration more maintainable.

---

11-13: Verify that the ignore patterns work as expected.

Let's ensure that the relocated ignore patterns still correctly exclude the intended files while not accidentally ignoring files that should be linted.

✅ Verification successful

ESLint ignore patterns are correctly configured ✅

The ignore patterns are working as expected:

• assets/ directory contains only images (no JS/TS files to lint)
• dist/ is correctly specified for build output
• No competing ESLint configurations found

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify ESLint ignore patterns work correctly

# Find all JavaScript/TypeScript files in assets/ and dist/ directories
echo "Files that should be ignored:"
fd -e js -e jsx -e ts -e tsx . -p assets/ dist/

# Run ESLint with debug output to verify ignore patterns
echo -e "\nVerifying ESLint ignore patterns:"
npx eslint --debug .

Length of output: 371

---

Script:

#!/bin/bash
# Check for assets directory and any potential files
echo "Checking assets directory:"
if [ -d "assets" ]; then
    echo "assets/ directory exists"
    fd . assets/
else
    echo "assets/ directory not found"
fi

# Look for any other ESLint config files that might conflict
echo -e "\nChecking for ESLint config files:"
fd -e js -e json -e yaml -e yml . | grep -i eslint

# Display the content of eslint.config.js to verify syntax
echo -e "\nVerifying eslint.config.js content:"
cat eslint.config.js

Length of output: 2235

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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.