[Fix]: Dev Setup Issues (Extension resolution + Missing/deprecated dependencies + Build errors)

[deepak-terse]

Description

This PR addresses several issues encountered during the initial project setup.

1. Module Not Found on npm install

[webpack-cli] Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/Users/deepak.terse/Code/Personal/chatbox/.erb/configs/webpack.config.base' imported from /Users/deepak.terse/Code/Personal/chatbox/.erb/configs/webpack.config.renderer.dev.dll.ts

Root Cause:

Webpack config files are executed by Node.js. Since Node doesn’t natively resolve .ts files, a loader such as ts-node is required.

Fix:

Rather than explicitly adding .ts extensions to every import (which led to additional issues), I opted to run Webpack via ts-node, which only required a single update to package.json.

2. Unnecessary Dependencies Being Bundled

ERROR in ./node_modules/.pnpm/[email protected]/node_modules/node-pre-gyp/lib/info.js 14:14-32  
Module not found: Error: Can't resolve 'aws-sdk'

Root Cause:

Webpack attempted to bundle dependencies that are not required for the renderer (frontend) build.

Fix:

Excluded those dependencies in the Webpack configuration.

3. Missing / Deprecated Dependencies

ERROR in ./src/renderer/components/settings/mcp/utils.ts 5:0-20  
Module not found: Error: Can't resolve 'zod'

Module Warning (from sass-loader):  
Deprecation The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.

Root Cause:

Both these causing the app to crash with errors

• zod was missing entirely
• the installed sass-loader version uses the deprecated legacy API

Fix:

Installed zod and upgraded sass-loader to a non-deprecated version.

4. Dev Build Errors

Uncaught TypeError: sessions is not iterable

Root Cause:

sortSessions and related helpers received a Promise<Session[]>, but the async value was not awaited before use.

Fix:

Properly handled the promise when accessing sessions.

---

Additional Notes

• Steps to reproduce

  • Do a fresh clone on a machine running Node 24.1.0
  • Doing npm install will throw errors 1 and 2 mentioned above
  • Doing npm run dev will throw errors 3 and 4

• Tested with Node 24.1.0 on macOS 14.4.1 — npm run dev succeeds and the app launches successfully (see screenshot below).

• Fixes the following Open issues:

  • [BUG] Seeing "cannot find module '...webpack.config.base' #1802
  • [BUG]sessions is not iterable #1978

---

Screenshots

Successful launch on npm dev

Contributor Agreement

By submitting this Pull Request, I confirm that I have read and agree to the following terms:

• I agree to contribute all code submitted in this PR to the open-source community edition licensed under GPLv3 and the proprietary official edition without compensation.
• I grant the official edition development team the rights to freely use, modify, and distribute this code, including for commercial purposes.
• I confirm that this code is my original work, or I have obtained the appropriate authorization from the copyright holder to submit this code under these terms.
• I understand that the submitted code will be publicly released under the GPLv3 license, and may also be used in the proprietary official edition.

Please check the box below to confirm:

[X] I have read and agree with the above statement.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing Touches

🧪 Generate unit tests

• 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

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[themez]

Please use node 22+ and npm instead of pnpm

[deepak-terse]

Thanks for the clarification @themez

I verified the supported versions and confirmed that the project works as expected on Node 20–22 with npm.
To avoid recurring issues around this, I opened a follow-up PR that documents and enforces those requirements:

#2597

Let me know if that looks good.