fix: make "resolve" external, fixes pnp

[goloveychuk]

fixes #163

[goloveychuk]

@guybedford could you please check?

[styfle]

Thanks! Could you add a test to make sure this works as you expect?

[goloveychuk]

I would need to add new github check, create a dir with yarn3 project, ran yarn install. Is it ok?

[goloveychuk]

Also would need to pack plugin to tar file. And reference it from yarn3 package. Not straightforward.

[styfle]

I think it’s best to add a test. Otherwise how do we know it works? And how do we prevent regressions in the future? Imagine bumping the dependency version.

[goloveychuk]

@styfle added, please approve a run

[styfle]

Thanks! Looks like windows is failing CI

[goloveychuk]

I've made it run only on linux, please reapprove. Failing probably because of bash scripts

[styfle]

Probably because env vars work differently on Windows. Running on linux only is a fine workaround, thanks!

[github-actions]

🎉 This PR is included in version 1.7.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[styfle]

@goloveychuk I had to disable this test when upgrading dependencies here:

• feat!: bump node@18, webpack@5.76.0, ncc@0.38.1, codecov@3.8.4 #187