[FEATURE] Improve local development and package validation by using local verdaccio

[JeremyJonas]

Describe the feature

We need a way to verify published package content works as expected.

Use Case

Just realized that cdk-graph and cdk-graph-plugin-diagram packages were completely broken due to "bundledDependencies" not getting bundled, which was caused by yarn workspace hoisting. When testing those packages I created create several example workspaces outside of PDK repo and used "yarn link" successfully. The issue was that the "bundledDependencies" where available since yarn link is on the source which include them.

If we had an easy way to publish the PDK monorepo locally (verdaccio) during development, then we could more easily test usage outside the repo against actual published artifacts.

Proposed Solution

Implement tasks / helpers in the root to spawn verdaccio server and publish package to.

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

PDK version used

0

What languages will this feature affect?

No response

Environment details (OS name and version, etc.)

n/a

[cogwirrel]

As a related reference - the initial open-api-gateway package included some verdaccio integration tests but we deleted them because the build was really slow!

Since PDK has grown and the build has slowed (with my open-api-gateway package the clear offender!) it might not feel like as significant a slowdown as it did back then! :)

If we were to add verdaccio tests it'd be great to resurrect these since they're the only tests that can ensure the generated code compiles! :)

[github-actions[bot]]

This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. If you wish to exclude this issue from being marked as stale, add the "backlog" label.