Chore: package manager migration from yarn to npm#785
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 fix for yarn-specific invocation (lint:fix) - Convert resolutions -> overrides (5 packages, simple flat rename, no version changes) - 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, cspell.config.json, eslint.config.mjs, docs/developer-guide.md, scripts/test.sh Note: docs/developer-guide.md and scripts/test.sh already referenced non-existent 'yarn watch' / 'yarn e2e:update' scripts pre-migration (no such scripts in package.json - likely stale docs/scripts from before a tooling change). Preserved as equally-broken npm equivalents rather than silently fixing unrelated, pre-existing issues out of scope for this PR.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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, script fix for a yarn-specific invocation (lint:fix)resolutions→overrides(5 packages, simple flat rename, no version changes).npmrc(fleet-standard template)package-lock.jsonvianpm install(no dependency versions changed, nolegacy-peer-depsneeded).gitignore,cspell.config.json,eslint.config.mjs,docs/developer-guide.md,scripts/test.shNote on pre-existing issues found (not fixed, out of scope)
docs/developer-guide.mdandscripts/test.shalready referenced non-existentyarn watch/yarn e2e:updatescripts before this PR (no such scripts exist inpackage.json— likely stale docs/scripts predating a tooling change). Preserved as equally-broken npm equivalents rather than silently fixing unrelated issues in this migration PR.Verification (local)
npm install— clean, no ERESOLVE errorsnpm run build— passesnpm run typecheck— passesnpm run lint— passesnpm run test:ci— passes (7/7 suites, 21/21 tests)Scope note
Part of a batched, wave-based migration. CI workflow files intentionally untouched.