This repository was archived by the owner on Jul 23, 2026. It is now read-only.
Chore: package manager migration from yarn to npm - #278
Draft
yesoreyeram wants to merge 1 commit into
Draft
Conversation
- Remove yarn.lock, .yarnrc.yml, .yarn/releases
- package.json: packageManager -> npm@11.18.0, script fixes for
yarn-specific invocations (dev, build)
- Convert resolutions -> overrides:
- immutable: simple flat rename, no version change
- protobufjs@^7.3.0 / protobufjs@^8.0.1 range-qualified entries
DROPPED - confirmed via 'npm ls protobufjs' that nothing in the
current dependency tree actually depends on protobufjs at all
(this was a defensive/proactive pin for a package with no
active consumer; npm's overrides require nesting under an
actual consumer, which doesn't exist here, so this can't be
faithfully replicated - flagging transparently rather than
guessing at a stand-in)
- Add 4 targeted overrides: eslint@10.3.0 is newer than several
plugins' declared peer ranges (same pattern across this
migration), and @testing-library/react-hooks@8.0.1's peers only
cover React 16/17. Uses $package override reference syntax.
- Add .npmrc (fleet-standard template)
- Regenerate package-lock.json via npm install (clean, no ERESOLVE,
no legacy-peer-deps needed)
- Remove now-dead yarn references in .gitignore
- Rewrite CONTRIBUTING.md local-linking instructions from yarn link/
version-branching to npm link (same fix as grafana-aws-sdk-react)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Migrates this repo's package manager from Yarn Berry (
yarn@4.17.1) to npm (npm@11.18.0), part of a fleet-wide yarn → npm migration across grafana-org datasource plugin repos.Changes
yarn.lock,.yarnrc.yml,.yarn/releases/package.json:packageManager→npm@11.18.0,engines.npmadded, script fixes for yarn-specific invocations (dev,build).npmrc(fleet-standard template)package-lock.jsonvianpm install.gitignoreCONTRIBUTING.md's local-linking instructions fromyarn link/version-branching tonpm link(same fix asgrafana-aws-sdk-react)resolutions→overridesimmutable: simple flat rename, no version change.protobufjs@^7.3.0/protobufjs@^8.0.1(the two range-qualified entries) were dropped — confirmed vianpm ls protobufjsthat nothing in the current dependency tree depends onprotobufjsat all. This looks like a defensive/proactive pin for a package with no active consumer right now. npm'soverridesrequire nesting under an actual consumer, which doesn't exist here, so this couldn't be faithfully replicated — flagging transparently rather than guessing at a stand-in. Happy to re-add if this comes back as an active transitive dependency later.Four targeted overrides added
Same peer-conflict patterns seen elsewhere in this migration, fixed with the
$packagereference syntax (nolegacy-peer-deps, no dependency versions bumped):eslint@10.3.0is newer thaneslint-plugin-react/eslint-plugin-react-hooks/eslint-plugin-jsdoc's declared peer ranges.@testing-library/react-hooks@8.0.1'sreact/react-dom/@types/reactpeers only cover React 16/17.Verification (local)
npm install— clean, no ERESOLVE errorsnpm run build(typecheck + rollup bundle) — passesnpm run lint— passesnpm run test:ci— passes (3/3 suites, 12/12 tests)Scope note
Part of a batched, wave-based migration. CI workflow files intentionally untouched.