Limitations in Testing Local Packages with pnpm Due to Symlink and Dependency Resolution Issues

[brionmario]

Current Limitation

Testing local package changes in external projects is currently unreliable when using pnpm, due to known limitations:

• pnpm link does not work consistently with symlinks, leading to unexpected behavior when linking local packages
• The file: protocol fails in cases where dependencies use catalog: references
• workspace:* and catalog: dependencies are not resolvable outside the monorepo context
• These issues are tracked in pnpm:
  • Problem with peer dependencies when using pnpm link pnpm/pnpm#6804
  • pnpm link and pnpm unlink documentation page could be better? pnpm/pnpm#4640

As a result, developers face difficulties in validating local changes in external projects, especially when working with monorepo-based setups and modern dependency conventions.

Suggested Improvement

A more reliable and consistent approach is needed to enable testing of local packages in external projects without being affected by pnpm’s current limitations around symlinks and dependency resolution.

Please select the package issue is related to

@asgardeo/javascript, @asgardeo/browser, @asgardeo/express, @asgardeo/nextjs, @asgardeo/node, @asgardeo/nuxt, @asgardeo/react, @asgardeo/react-router, @asgardeo/vue, @asgardeo/i18n

Version

N/A

Reporter Checklist

• I have searched the existing issues and this is not a duplicate.
• I have provided all the necessary information.
• I have verified the improvement is not available in the latest version of the package.