refactor: migrate to fast-npm-meta

[9romise]

Close #14

[hyoban]

Regarding performance issues, I was thinking we could implement dependency-based caching. If the dependencies haven't changed (for example, if you only add whitespace characters), we shouldn't request them again.

We can also report issues as soon as possible instead of waiting until everything has been checked.

vscode-npmx/src/providers/diagnostics/index.ts

Lines 37 to 76 in a7111ff

	async function collectDiagnostics(document: TextDocument, extractor: Extractor) {
	diagnosticCollection.delete(document.uri)
	const root = extractor.parse(document)
	if (!root)
	return
	const dependencies = extractor.getDependenciesInfo(root)
	const diagnostics: Diagnostic[] = []
	await Promise.all(
	dependencies.map(async (dep) => {
	try {
	const pkg = await getPackageInfo(dep.name)
	if (!pkg)
	return
	for (const rule of enabledRules.value) {
	const diagnostic = await rule(dep, pkg)
	if (diagnostic) {
	diagnostics.push({
	source: displayName,
	message: diagnostic.message,
	severity: diagnostic.severity,
	code: diagnostic.code,
	range: extractor.getNodeRange(document, diagnostic.node),
	})
	}
	}
	} catch (err) {
	logger.warn(`Failed to check ${dep.name}: ${err}`)
	}
	}),
	)
	if (diagnostics.length > 0)
	logger.info(`${diagnostics.length} diagnostic collected in ${document.fileName}.`)
	diagnosticCollection.set(document.uri, diagnostics)
	}

[9romise]

Regarding performance issues, I was thinking we could implement dependency-based caching. If the dependencies haven't changed (for example, if you only add whitespace characters), we shouldn't request them again.

We do cache the result currently, see https://github.com/npmx-dev/vscode-npmx/blob/main/src/utils/memoize.ts#L18.

But I think we can add a pre-validation to ensure the package name is legal.

We can also report issues as soon as possible instead of waiting until everything has been checked.

I'll check it out. Thanks for your feedback!

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR migrates npm metadata fetching to fast-npm-meta and updates package.json and tsdown.config.ts. src/utils/api/package.ts now exposes a new PackageInfo (including a versionToTag Map) and getPackageInfo returns Promise<PackageInfo | null>. Call sites were adjusted to read version metadata from versionsMeta. Diagnostic rule types were updated to use PackageInfo. Hover provider link construction now uses new link helpers and the NPMJS_COM constant. The ModuleReplacement re-export was removed.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description check	✅ Passed	The PR description 'Close #14' is minimal but directly related to the changeset, which implements a migration to fast-npm-meta as evidenced by changes across multiple files.
Linked Issues check	✅ Passed	The PR successfully migrates the project to use fast-npm-meta by replacing npm package fetching logic with fast-npm-meta integration, updating all dependent code paths, and adjusting build configuration.
Out of Scope Changes check	✅ Passed	All changes are aligned with the migration objective. Updates to constants, links, diagnostics, providers, and configuration all support the fast-npm-meta migration without introducing unrelated modifications.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fast-npm-meta

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

[coderabbitai]

Actionable comments posted: 2

[coderabbitai]

Actionable comments posted: 1

[9romise]

Regarding performance issues, I was thinking we could implement dependency-based caching. If the dependencies haven't changed (for example, if you only add whitespace characters), we shouldn't request them again.

Oh, I see, do you mean caching Diagnostics based on the dependency name?