Skip to content

Conversation

camro
Copy link
Contributor

@camro camro commented Aug 18, 2025

Description

Type dependencies are only needed in the dev/build environment

How Has This Been Tested?

Backporting (check the box to trigger backport action)

  • This PR should be backported (make sure to check that the backport attempt succeeds)
  • [Optional] Override Linear Check

Summary by cubic

Moved all TypeScript @types packages to devDependencies so they aren’t installed in production, reducing install size and keeping runtime deps lean. Also bumped @types/js-cookie and @types/lodash to the latest patch versions.

  • Dependencies
    • Moved: @types/js-cookie, @types/lodash, @types/node, @types/prismjs, @types/react, @types/react-dom, @types/uuid to devDependencies.
    • Updated: @types/js-cookie to ^3.0.6, @types/lodash to ^4.17.20.

@camro camro requested a review from a team as a code owner August 18, 2025 00:24
Copy link

vercel bot commented Aug 18, 2025

@camro is attempting to deploy a commit to the Danswer Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

Greptile Summary

This PR moves TypeScript type definition packages from dependencies to devDependencies in the web application's package.json file. The following @types/* packages were relocated:

  • @types/js-cookie (updated from 3.0.3 to 3.0.6)
  • @types/lodash (updated from 4.17.0 to 4.17.20)
  • @types/node
  • @types/prismjs
  • @types/react
  • @types/react-dom
  • @types/uuid

This change follows JavaScript/TypeScript best practices, as type definition packages are only needed during development, TypeScript compilation, and build processes - they provide no runtime functionality. The relocation optimizes the production dependency tree by reducing the number of packages that need to be installed in production environments, while maintaining all necessary type safety during development.

The change aligns with the existing project structure where other development-only tools like ESLint, Jest, Prettier, and testing frameworks are already properly categorized in devDependencies. Two of the moved packages received minor version updates to their latest compatible versions as part of this refactoring.

Confidence score: 5/5

  • This PR is extremely safe to merge with no risk of production issues
  • Score reflects a straightforward dependency categorization following established best practices
  • No files require special attention as this is a simple package.json optimization

1 file reviewed, no comments

Edit Code Review Bot Settings | Greptile

@camro camro changed the title Move @types packages to devDependencies chore(packages): Move @types packages to devDependencies Aug 18, 2025
Copy link

vercel bot commented Aug 18, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
internal-search Ready Ready Preview Comment Aug 18, 2025 9:39pm

@wenxi-onyx wenxi-onyx merged commit 91c4d43 into onyx-dot-app:main Aug 18, 2025
3 of 6 checks passed
AnkitTukatek pushed a commit to TukaTek/onyx that referenced this pull request Sep 23, 2025
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.

3 participants