Fix plugin dependency checks and set npmPackage values on plugins

[antico5]

This PR addresses #6035

The original scope of the issue was to set the npmPackage property of our hardhat3 plugins, so when an import fails we can give detailed information if a given plugin package is missing, or some of its peer dependencies.

When running a test scenario, specifically using hardhat-viem and not having the viem peer dep installed, I noticed that even after setting the npmPackage property on our plugin, the error message wasn't helping. This lead me to debug the core plugins/detect-plugin-npm-dependency-problems.ts module.

I noticed that the require.resolve function was not working, and after thorough debugging I found out that the createRequire function doesn't work properly when passing an absolute path to a directory without a trailing forward slash. Adding the trailing forward slash to the directory path would make the require instance work.

After that, I started to get the error that package.json was not being exported by our modules, and we need to require() those to find the peer dependencies of packages. Then I added an export of package.json to all of our modules.

Closes #6035

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
hardhat	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 13, 2024 2:16pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 06f1e9a

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

[alcuadrado]

Approved as a temporary fix. We should make this work without exporting package.json. Luckily #6125 already does it for the resolver.