feat: update package json for npm publish

[huaweigu]

Motivation

It'd be helpful for devs to import this project (especially libraries) as a npm package.

Update - package is published here.

Solution

• Update package.json to be npm publish ready
• TODO - automate this in action in the future similar to this

  publish-npm:
   needs: build
   runs-on: ubuntu-latest
   steps:
     - uses: actions/checkout@v4
     - uses: actions/setup-node@v4
       with:
         node-version: 20.x
         registry-url: https://registry.npmjs.org/
     - run: npm ci
     - run: npm publish --access public
       env:
         NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
         NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
         token: ${{ secrets.NPM_TOKEN }}

  we just need to figure out where to host the secrets.

[huaweigu]

I tired the original name first, but got

npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access
npm ERR! code E404
npm ERR! 404 Not Found - PUT https://registry.npmjs.org/@erc6900%2freference-implementation - Not found
npm ERR! 404 
npm ERR! 404  '@erc6900/reference-implementation@0.8.0-rc.6' is not in this registry.
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

This solution or this doc requires the user to sign up with erc6900 scope, but it is already in use..

[jaypaik]

Hmm. I submitted a name dispute request. Would love to keep the org scope if possible...

[huaweigu]

yeah it'd be great if we can get erc6900 back. I tried user name and org name, both unavailable..

[jaypaik]

@huaweigu Mind bumping this to 0.8.1 and updating the package name/relevant bits now that we have the erc6900 org on npm?

[huaweigu]

Done 2bbfacc

I also published the package here

[huaweigu]

@jaypaik Let me know if we need to adjust any metadata, thanks!

[jaypaik]

lgtm!