The Package manager creation is not too difficult, but a ton of documentation must be read before to even be able to make something work (I spent around one hour today to make one git based package work).
A wizard that would generate a package json file could be useful. Anything like that?
In our case we did this just once and created a package project template to build from whenever a new package is created in-house. The package also includes editor scripts for simplified package publishing and updating in our internal package registry.
This did, however, lead to issues with meta file collisions between packaged files added to the template project (mainly, assembly definition templates). Lesson learned, we simply don’t commit these and let them be regenerated and then committed when a new repository for a package is actually started from the template.
Generating these contents via a quickstart script/wizard would probably be the better solution and save us a bunch of hassle. Then again, distributing that wizard would probably be done via the package manager, which requires manual manifest editing to access our internal registry. These changes are premade in our package template, leading to a bit of a Catch-22 situation. Any thoughts on a better solution are definitely welcome.
Hi there,
We are working on a package that will enhance the Package Manager window to provide more options for package creation and development. It should be released relatively soon (within the next few weeks).
Thanks so much for your feedback!
Ethan
1 Like