[WIP] chore: Consolidate all dependencies
As the project is a monorepo, we should consolidate all dependencies:
Benefits of consolidating dependencies:
- Enforced single version: Ensures all projects use the same version of a dependency, preventing version conflicts and inconsistencies.
- Simplified dependency management: Centralizes dependency updates and maintenance.
Steps
1. Moved all dependencies to root package.json:
- Consolidated all dependencies and devDependencies from the three packages (api, app, common-utils) into the root package.json
- Resolved version conflicts by using the most recent versions
- Added missing peer dependencies to fix warnings
2. Cleaned up individual package.json files:
- Removed all dependencies and devDependencies from individual packages
- Kept only project-specific configurations like scripts, engines, nx configs, etc.
- Maintained package names, versions, and licensing information
3. Fixed ESLint configurations:
- Disabled
n/no-extraneous-importrule in individual packages since dependencies are now at root level - Updated lint scripts to use TypeScript from root (npx tsc instead of yarn tsc)
4. Updated TypeScript configurations:
- Fixed moduleResolution setting to match module: "Node16" in TypeScript configs
- Updated to TypeScript 5.9.2 to meet knip requirements
5. Added missing dependencies:
- Added peer dependencies like
@codemirror/view,@popperjs/core,@testing-library/dom,dayjs,webpack - Standardized Mantine versions to 7.11.2
- Added necessary build and development tools
⚠️ No Changeset found
Latest commit: 1de8bf2256cb8ac89a5b714bd1331b37c948d4c9
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
@candidosales is attempting to deploy a commit to the HyperDX Team on Vercel.
A member of the Team first needs to authorize it.