Working NPX dev config and install.

[jerknose]

Summary

A summary of changes being made in this PR

Hey guys. I created a working prototype of a npx installer. Once published, we'll have a single command to configure everything.

"npx @xrengine/xrengine folder_name"

Then just run "cd folder_name & npm run dev"

Also, there's a GitHub action to auto publish to npm: https://github.com/marketplace/actions/npm-publish

References

closes #insert number here

Checklist

• If this PR is still a WIP, convert to a draft
• ensure all checks pass
• When this PR is ready, mark it as "Ready for review"
• Changes have been manually QA'd
• Changes reviewed by at least 2 approved reviewer

QA Steps

To test locally:
Run 'npm i -g'
Run 'npx xrengine folder_name'

[HexaField]

Nice!

[speigg]

We're in the process of moving everything over from xrengine -> etherealengine namespaces; let's do that here preemptively.

We have an @etherealengine org for npm, perhaps we should do npx @etherealengine/install for this?

[jerknose]

We're in the process of moving everything over from xrengine -> etherealengine namespaces; let's do that here preemptively.

We have an @etherealengine org for npm, perhaps we should do npx @etherealengine/install for this?

The default npx behavior is to use @org_name/repo_name. But I believe we can define multiple scripts in Package.json.

i.e. npx @org_name/repo_name script_name var_1

So, something like this (with the current repo name)

@etherealengine/xrengine install my_engine_folder

[speigg]

The default npx behavior is to use @org_name/repo_name

@jerknose Can you point me to some documentation about this?

[jerknose]

@speigg

NPX Tutorial: https://dev.to/9zemian5/basic-npx-command-line-tool-45k4
NPX Docs: https://docs.npmjs.com/cli/v9/commands/npx?v=true
NPM Publish Docs: https://docs.npmjs.com/cli/v9/commands/npm-publish?v=true
NPM Publish Action: https://github.com/marketplace/actions/npm-publish

[speigg]

Not seeing any reason we can't do npx @etherealengine/install for this; just waiting on npm support to get back to me about the @EtherealEngine npm org, which is being name-squatted right now...

[jerknose]

@speigg Can we merge this in as a working template? I think which org name, and repo name are a separate issue.