Automate publishing to NPM

[jasongitmail]

I thought this might be helpful for you.

You'd just need to generate an NPM Token with the automation permission and add NPM_TOKEN as a secret on this Github repo.

Then any PR that is merged to main that bumps the version # in package.json will be automatically published to NPM.

There don't appear to be any tests in etherCorps/sveltekit-og currently, so I left a comment there; enabling this line will only publish to NPM only if tests pass successfully.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sveltekit-og	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 10, 2023 9:38am

[theetherGit]

@jasongitmail we have to build and add package dir to github, or you have to change config to make to build then change dir and then publish.

[theetherGit]

I think it looks good to go now.
We can test it as i'm going to push version for your patches.

[jasongitmail]

Updated. The package property is a path to a dir that contains the package.json of the package to be deployed, so this should work.

[theetherGit]

@jasongitmail please update publish file action node installation error.

[jasongitmail]

Oh shoot. I wanted to try lts because noticed it in the docs. I have used a number in the past; will switch to that.