feat: return generated manifest object

[EwanValentine]

🎉 Thanks for sending this pull request! 🎉

Please make sure the title is clear and descriptive.

If you are fixing a typo or documentation, please skip these instructions.

Otherwise please fill in the sections below.

• UPDATED: When the edge manifest is generated, this PR returns the generated manifest object, which means we don't have to load the manifest from the generated file in order to debug/inspect the output in other packages where needed.

Please add a x inside each checkbox:

• I have read the contribution guidelines.
• The status checks are successful (continuous integration). Those can be seen below.

A picture of a cute animal (not mandatory but encouraged)

[eduardoboucas]

• When the edge manifest is generated, this PR returns the generated manifest object, which means we don't have to load the manifest from the generated file in order to debug/inspect the output in other packages where needed.

I would argue that actually reading the file from its expected location at deploy time would be part of the diagnostic. Any reason you prefer to expose it programmatically and skip that step?

[EwanValentine]

Hmmm, I figured the contents of the manifest were the important part, rather than the loading of the manifest file itself. So figured it would be cleaner to just return it, rather than reload the contents from the file again. I wasn't 100% sure on that though, so happy to close this and just reload it in the builder

[eduardoboucas]

Hmmm, I figured the contents of the manifest were the important part, rather than the loading of the manifest file itself. So figured it would be cleaner to just return it, rather than reload the contents from the file again. I wasn't 100% sure on that though, so happy to close this and just reload it in the builder

No objections from me! I just wanted to offer an alternative option in case you hadn't considered it, as it could avoid making changes to Edge Bundler.

[eduardoboucas]

Nice! ✨