chore: remove unused dependencies across the monorepo#1752
Conversation
|
@launchdarkly/js-sdk-common size report |
|
@launchdarkly/browser size report |
|
@launchdarkly/js-client-sdk size report |
|
@launchdarkly/js-client-sdk-common size report |
…ve ts-node requirement
| }, | ||
| "dependencies": { | ||
| "@launchdarkly/akamai-edgeworker-sdk-common": "^2.0.23", | ||
| "@launchdarkly/js-server-sdk-common": "^2.19.1" |
There was a problem hiding this comment.
this should be a transitive dep of @launchdarkly/akamai-edgeworker-sdk-common
| }, | ||
| "devDependencies": { | ||
| "@eslint/js": "^9.0.0", | ||
| "@rollup/plugin-commonjs": "^25.0.0", |
There was a problem hiding this comment.
this package uses tsc for build.
Note
Low Risk
Manifest-only cleanup with no SDK logic changes; main residual risk is CI failing if a removed package was still required indirectly.
Overview
This PR trims package manifests and one Jest config across many SDK, shared, store, and telemetry packages—no application source changes.
Dependency cleanup drops unused devDependencies (notably
launchdarkly-js-test-helpersfrom most packages that no longer import it), redundant type packages (@types/crypto-jswhere crypto isn’t used locally), and build-only tools that aren’t referenced (extra Rollup plugins,ts-node, Jest extras likejest-diff/@jest/globals). Runtime dependency changes include removing duplicate@launchdarkly/js-server-sdk-commonfrom akamai-base,@launchdarkly/js-sdk-commonfrom openfeature-node-server (left to the common package),crypto-jsfrom vercel (still available via sdk-server-edge), andesm-envfrom svelte.openfeature-server-common drops legacy ESLint/Prettier dev tooling and tightens the lint script to
npx eslint .. react-native’s Jest config is converted from ESMexport defaultto CommonJSmodule.exportsso Jest can load it withoutts-node.Reviewed by Cursor Bugbot for commit a49004a. Bugbot is set up for automated code reviews on this repo. Configure here.