Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: improve type safety and modernize image optimization code #243

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

GarmashAlex
Copy link

@GarmashAlex GarmashAlex commented Jan 8, 2025

  • Add proper TypeScript type annotations and return types
  • Use modern Node.js module imports with node: prefix
  • Make constants immutable with readonly type
  • Update TypeScript configuration for better type checking
  • Import only required functions from core modules
  • Fix ESLint/TypeScript compiler issues

Summary by CodeRabbit

  • Refactor

    • Updated TypeScript configuration to target ES2020
    • Refined import statements and type annotations in image optimization module
    • Improved function signatures for better type clarity
  • Chores

    • Added Node.js type definitions to TypeScript configuration

Copy link

coderabbitai bot commented Jan 8, 2025

Walkthrough

The pull request introduces refinements to the TypeScript configuration and image optimization module in the _api directory. The changes focus on improving type annotations, updating import statements, and enhancing the TypeScript compiler configuration. The modifications aim to clarify function signatures, specify ECMAScript target version, and streamline the code's type handling for Node.js environments.

Changes

File Change Summary
_api/src/optimizeImages.ts - Updated import statements to use specific functions from node:fs and node:path
- Refined function signatures with explicit return types
- Typed imageExtensions as a readonly string array
_api/tsconfig.json - Added target set to ES2020
- Included lib with ES2020
- Added types with ["node"]

Poem

🐰 Hop, hop, code so bright!
Imports trimmed, types take flight
ES2020 shines so clear
Optimization without fear
A rabbit's code, lean and tight! 🔧


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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🔭 Outside diff range comments (1)
_api/src/optimizeImages.ts (1)

Line range hint 61-76: Add cleanup for temporary files in error cases.

The temporary file might not be cleaned up if an error occurs during optimization.

async function optimizePng(filePath: string): Promise<void> {
  const tempFilePath = `${filePath}.${uuidv4()}.tmp`
+  try {
    const image = sharp(filePath)
    const metadata = await image.metadata()

    if (metadata.height && metadata.height > PNG_MAX_HEIGHT) {
      await image.resize({ height: PNG_MAX_HEIGHT }).toFile(tempFilePath)
    } else {
      const data = await image.toBuffer()
      await sharp(data).toFile(tempFilePath)
    }

    renameSync(tempFilePath, filePath)
+  } catch (error) {
+    try {
+      unlinkSync(tempFilePath)
+    } catch {} // Ignore cleanup errors
+    throw error
+  }
}
🧹 Nitpick comments (1)
_api/src/optimizeImages.ts (1)

Line range hint 18-27: Consider filtering files earlier for performance.

While the type annotation is good, we could optimize the directory traversal by filtering non-image files earlier.

export async function optimizeImages(dir: string): Promise<void> {
-  const files = getFilePathsInDirectory(dir)
+  const files = getFilePathsInDirectory(dir).filter(file => 
+    !isDirectory(file) && imageExtensions.includes(extname(file).toLowerCase())
+  )

  for (const file of files) {
    if (isDirectory(file)) {
      await optimizeImages(file)
      continue
    }

-    const ext = extname(file).toLowerCase()
-    if (!imageExtensions.includes(ext)) {
-      continue
-    }
+    const ext = extname(file).toLowerCase()
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2fe5577 and fd2e24b.

📒 Files selected for processing (2)
  • _api/src/optimizeImages.ts (5 hunks)
  • _api/tsconfig.json (1 hunks)
🔇 Additional comments (3)
_api/src/optimizeImages.ts (2)

1-2: LGTM! Modern Node.js imports.

The use of the node: prefix and destructured imports from core modules improves clarity and bundle optimization.


15-15: LGTM! Improved type safety with readonly.

The readonly type annotation prevents accidental modifications to the array.

_api/tsconfig.json (1)

3-9: LGTM! Modern TypeScript configuration.

The configuration is well-aligned with modern TypeScript practices:

  • ES2020 target is appropriate for Node.js
  • Bundler moduleResolution is future-proof
  • Explicit Node.js types improve type checking

Comment on lines +45 to +55
const relativePath = relative(dir, file)
console.log(`Optimized ${relativePath}: ${originalSize} bytes -> ${newSize} bytes`)

if (ext === ".svg" && newSize > SVG_SIZE_LIMIT) {
console.warn(chalk.yellow(`Deleting oversized SVG: ${relativePath}`))
fs.unlinkSync(file)
unlinkSync(file)
}

if (ext === ".png" && newSize > PNG_SIZE_LIMIT) {
console.warn(chalk.yellow(`Deleting oversized PNG: ${relativePath}`))
fs.unlinkSync(file)
unlinkSync(file)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Add error handling for file operations.

The synchronous file operations (unlinkSync) could throw errors if the file is locked or permissions are insufficient.

-      unlinkSync(file)
+      try {
+        unlinkSync(file)
+      } catch (error) {
+        console.error(chalk.red(`Failed to delete ${relativePath}: ${error.message}`))
+      }
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
const relativePath = relative(dir, file)
console.log(`Optimized ${relativePath}: ${originalSize} bytes -> ${newSize} bytes`)
if (ext === ".svg" && newSize > SVG_SIZE_LIMIT) {
console.warn(chalk.yellow(`Deleting oversized SVG: ${relativePath}`))
fs.unlinkSync(file)
unlinkSync(file)
}
if (ext === ".png" && newSize > PNG_SIZE_LIMIT) {
console.warn(chalk.yellow(`Deleting oversized PNG: ${relativePath}`))
fs.unlinkSync(file)
unlinkSync(file)
const relativePath = relative(dir, file)
console.log(`Optimized ${relativePath}: ${originalSize} bytes -> ${newSize} bytes`)
if (ext === ".svg" && newSize > SVG_SIZE_LIMIT) {
console.warn(chalk.yellow(`Deleting oversized SVG: ${relativePath}`))
try {
unlinkSync(file)
} catch (error) {
console.error(chalk.red(`Failed to delete ${relativePath}: ${error.message}`))
}
}
if (ext === ".png" && newSize > PNG_SIZE_LIMIT) {
console.warn(chalk.yellow(`Deleting oversized PNG: ${relativePath}`))
try {
unlinkSync(file)
} catch (error) {
console.error(chalk.red(`Failed to delete ${relativePath}: ${error.message}`))
}

Comment on lines +80 to +83
function optimizeSvg(filePath: string): void {
const data = readFileSync(filePath, "utf8")
const result = optimize(data, { path: filePath })
fs.writeFileSync(filePath, result.data)
writeFileSync(filePath, result.data)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Consider using async operations and add error handling.

The synchronous file operations could block the event loop. Consider using async alternatives and add error handling.

-function optimizeSvg(filePath: string): void {
-  const data = readFileSync(filePath, "utf8")
-  const result = optimize(data, { path: filePath })
-  writeFileSync(filePath, result.data)
+async function optimizeSvg(filePath: string): Promise<void> {
+  try {
+    const data = await promises.readFile(filePath, "utf8")
+    const result = optimize(data, { path: filePath })
+    await promises.writeFile(filePath, result.data)
+  } catch (error) {
+    console.error(chalk.red(`Failed to optimize SVG ${filePath}: ${error.message}`))
+    throw error
+  }
}

Don't forget to add the import:

-import { readFileSync, writeFileSync, unlinkSync, renameSync } from 'node:fs'
+import { readFileSync, writeFileSync, unlinkSync, renameSync, promises } from 'node:fs'

Committable suggestion skipped: line range outside the PR's diff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant