Packages

@yarnpkg/esbuild-plugin-pnp

3.0.0-rc.15 · 24 Aug 2022BSD-2-Clause787.1k / weekRepositorynpmAtom feed

Your version

Where each line stands

Plan an upgrade

Latest releases

  1. 2.x · maintenance
  2. 2.0.1 – 2.0.33 releases without a noteShow each
  3. 2.0.0

    25 Oct 2021
    • Using yarn link will now properly resolve peer dependencies based on the package that requires the linked package rather than the dependencies installed in the linked project folder.

    • Packages will now only be built when one of their dependencies is changed in some way. Note that this includes both direct dependencies and transitive dependencies, which might trigger unintuitive rebuilds in some case (for example, since node-sass depends on lodash.assign, upgrading lodash.assign will trigger a rebuild). This will be improved in a later release by introducing a new runtime field for the dependenciesMeta object that will exclude the package from the build key computation (feel free to start setting this flag as of now, even if it won't have any effect until then).

    • Registry hostnames finally aren't part of the lockfile anymore. It means that you can switch the registry at any time by changing the npmRegistryServer settings. One unfortunate limitation is that this doesn't apply to registries that use non-standard paths for their archives (ie /@scope/name/-/name-version.tgz). One such example is NPM Enterprise, which will see the full path being stored in the lockfile.

  4. 1.x · maintenance
  5. 1.0.0

    26 Jul 2021

Dependency tracking

Know when your own dependencies move

This page watches @yarnpkg/esbuild-plugin-pnp. inlinr reads your package.json and keeps the same watch on every dependency you declare, then tells you only what needs you.

  • Advisories reach you

    An email when a critical or high advisory affects a project, before the next install.

  • Upgrades checked first

    Peer ranges, Node, ESM-only and types changes read before you bump.

  • Only what matters

    Majors and breaking notes stay; patches and sibling bumps fold into one line.

How dependency tracking works

Reading releases, release notes and advisories…

Registry facts last checked 20 Nov 2026. Releases and advisories last read 20 Nov 2026.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.