Skip to content

WrapperGenerator: package generated modules as installable nupkgs (per-module nuspec) #3712

Description

@Joywambui-maina

Summary
Generated modules can be built and imported locally, but there's no way to hand one to another person. Emit a nuspec per generated module and pack it into a .nupkg, so testers can install modules from a feed and give feedback.

What's working now
Build-WrapperModule.ps1 builds any module into an importable PSD1 under artifacts/, and all 35 cmdlet-producing v1.0 modules build and import. The repo already has a packaging convention to follow: every shipped module has a nuspec next to its manifest, packed by PackModule.ps1 / NuspecHelper.ps1.

How can we make it better
Following the existing convention, the generator (or the packaging script) should emit a nuspec per module and pack a .nupkg, versioned as a prerelease. Two decisions to make along the way: what package IDs to use (the real Microsoft.Graph.* names collide with the published SDK on PSGallery, so previews need either a different ID or a separate feed), and where testers install from (GitHub Packages feed, release artifacts, or a private feed).

Metadata

Metadata

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions