Release Node.js on the Microsoft Store?

[targos]

The new Microsoft Store now supports a lot of different kinds of apps. I don't know if it would be a good idea to distribute Node.js in it, but it seems worth having the discussion.

https://blogs.windows.com/windowsexperience/2021/06/24/building-a-new-open-microsoft-store-on-windows-11/ https://blogs.windows.com/windowsdeveloper/2021/09/28/microsoft-store-more-apps-more-open/ https://developer.microsoft.com/en-us/microsoft-store/

[richardlau]

Questions:

1. Is the process automatable?
2. Do we have enough volunteers to keep the process working?
3. Does it need to be via build? For example, we are not involved with the winget Node.js packages.

As a comparison we're not in (to my knowledge) the macOS store nor the old Windows app store. The only app store Build has involvement with at the moment is snapcraft and that was transferred over from NodeSource.

[targos]

Is the process automatable?

I don't know, but IMO that would be a requirement.

[targos]

Do we have enough volunteers to keep the process working?

We can look for volunteers if we agree on it.

[targos]

Does it need to be via build? For example, we are not involved with the winget Node.js packages.

Maybe not. I assumed that we would have to sign the app using an account owned by build.

[targos]

Maybe it's an issue that needs to be in nodejs/release first.

[richardlau]

Does it need to be via build? For example, we are not involved with the winget Node.js packages.

Maybe not. I assumed that we would have to sign the app using an account owned by build.

I guess the question there is whether we can reuse the msi we already build/sign or would need an additional signing step.

[nschonni]

I wasn't sure if https://github.com/nodejs/build/issues/1413 was a requirement for the old store, but might not be for the new one

[github-actions[bot]]

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.