docs(recipes): update module deployment recipe

[infoxicator]

Updating documentation to use the new Vercel-cli and explain in more detail how the deployment of modules should work

Description

Motivation and Context

How Has This Been Tested?

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (adding or updating documentation)
• Dependency update

Checklist:

• My change requires a change to the documentation and I have updated the documentation accordingly.
• These changes should be applied to a maintenance branch.
• This change requires cross browser checks.
• Performance tests should be ran against the server prior to merging.
• This change impacts caching for client browsers.
• This change impacts HTTP headers.
• This change adds additional environment variable requirements for One App users.
• I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using One App?

[github-actions]

📊 Bundle Size Report

file name	size on disk	gzip
app.js	276.2KB	82.4KB
runtime.js	15KB	5.4KB
vendors.js	117.4KB	36.4KB
app~vendors.js	425.2KB	111KB
service-worker-client.js	17KB	5.2KB
legacy/app.js	291.4KB	85.6KB
legacy/runtime.js	15KB	5.4KB
legacy/vendors.js	172.9KB	47.1KB
legacy/app~vendors.js	439.9KB	114.1KB
legacy/service-worker-client.js	17.5KB	5.4KB

Generated by 🚫 dangerJS against 5423708

[JAdshead]

thoughts on calling this, publishing a module. and adding ad note "uploading to the CDN publishes/releases, similar to how you release a dependency. Updating a module map will tell one-app to consume that published/released module version."

[nellyk]

i agree on this, and create separate documentation on how to do this and a step by step on uploading to a cdn/using actions to achieve this

[infoxicator]

@JAdshead do you mean changing the name of the entire guide to be "Publising modules" or is this just for the "deployment overview" section?

[infoxicator]

Renamed to Publishing modules

[JAdshead]

should we also recommend uploading the contents of a build folder to a folder matching the name of the module:

/module-name/[contents-of-build-including-version]

| -module-name
   └ [version]
        ├ [locale]
        |    └ *.locales
        ├ module-name.browser.js
        ├ module-name.legacy.browser.js
        ├ module-name.node.js
        └ ..

[infoxicator]

I think I used to have that structure in my original script, but guess for Vercel was removed because it looks like you can't upload more than 1 module to the same project/url and you cannot select a folder, so every module will have it's own CDN instance / url which is a pain. With Amazon S3 you can keep all your modules under the same url/project so it the folder is required there

[infoxicator]

Added a note that vercel doesn't support multiple folders

[Francois-Esquire]

Suggested change

	* [Overview](overview)
	* [Overview](#overview)

[infoxicator]

added here 5423708