chore: add ava config and some basic tests

[yusefnapora]

This needs some cleanup, but I got ava + typescript to work after a bit of wrestling.

So far I've only added some simple tests to keyring-core that don't depend on the service, but I've also started on a mock access service so we can test registerSpace, etc.

I had to add "type": "module" to the keyring-core package.json to get the ava + typescript setup to work. That seems pretty safe, since we're only including the rollup bundle in the published package, so it shouldn't make a difference to users.

It seems like the mock services would be useful for all the packages, so maybe we should make a shared test-utils package?

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 75b9e3d:

Sandbox	Source
@w3ui/example-react-file-upload	Configuration
@w3ui/example-react-sign-up-in	Configuration
@w3ui/example-react-uploads-list	Configuration
@w3ui/example-solid-file-upload	Configuration
@w3ui/example-solid-sign-up-in	Configuration
@w3ui/example-solid-uploads-list	Configuration
@w3ui/example-vue-file-upload	Configuration
@w3ui/example-vue-sign-up-in	Configuration
@w3ui/example-vue-uploads-list	Configuration

[travis]

this is fantastic!! I left a couple comments but already pushed fixes for them - happy to back either of my changes out if you don't want them, but I was in the code testing the --experimental-specifier-resolution change and it was easy to knock them both out

[travis]

this is already strictly better than what we have now so I'd be happy if you merged as-is!

It seems like the mock services would be useful for all the packages, so maybe we should make a shared test-utils package?

I think it might be a little cleaner for

1. each package to export useful test utils for the functionality it provides and
2. to introduce a services package of some sort per proposal: add services-core and react-services packages to encapsulate upload/access service configuration #156 where we can implement service Providers and land these mock services -

I'm worried that a shared test-utils package will end up depending on all these packages, and that all the packages will end up dev-depending on test-utils leading to a gnarly knot of dependency resolution. Strictly speaking I think either will work, but the idea of a dependency knot like this puts a knot in my stomach...

[yusefnapora]

awesome, thanks for the fixes @travis :)

I think you're right that the services package is where it's at. Should we just pull the WIP mock service out of this PR, so it's not cluttering up the joint? It's not being used yet (except in the skipped test).

[travis]

Should we just pull the WIP mock service out of this PR

Yep that sounds great - probably time to create a new package (@w3ui/services?) where that can live. If you're up for creating it go for it, otherwise I'm happy to get that into a draft PR in the next day or so.

[travis]

oh also maybe just singular @w3ui/service since @gobengo unified the two services into one in storacha/w3up#325 (comment)

[yusefnapora]

sweet, this is passing on CI now that I bumped it up to node 18.

I'll go ahead and merge now that the mocks are gone. @w3ui/service sounds good to me for the new package. I can start on that tomorrow unless you feel like grabbing it sooner :)