setup repo with yarn v4

[abeljohn]

renames packages from @stitches/* to @sigmacomputing/stitches-* for publishing, and updates supporting files to work with yarn v4 and node 20

[slequar]

Is there a description of what the larger changes were? Looks like there's a few big deletions (e: specifically of traces)

[peternandersson]

Why are we removing this packages/test/*?

[peternandersson]

Are we still using this branch?

[abeljohn]

we will not be using it actively, but since this is the branch our fork is based off of, we should keep it just in case we need to pull in changes from upstream

[peternandersson]

Do we need to change this? I figure we're not actually using this for CI?

[abeljohn]

yeah we can delete this since we aren't using codesandbox

[peternandersson]

Also just curious, why do we need a node version for this package?

[abeljohn]

this just ensures consistency across builds by ensuring all builds were generated using the same tooling

[abeljohn]

Is there a description of what the larger changes were? Looks like there's a few big deletions

I removed packages/test/traces/* from version control, as those traces contain filesystem paths from whoever ran the tests. Keeping them in version control would lead to large diffs anytime the tests are run locally. AFAICT these traces do not need to be committed, and are mostly for debugging locally

[rilescode]

Nice. Would it make sense to update the READMEs as well?

ie npm install @stitches/core -> npm install @sigmacomputing/stitches-core etc

[abeljohn]

Nice. Would it make sense to update the READMEs as well?

ie npm install @stitches/core -> npm install @sigmacomputing/stitches-core etc

let's do this when we start publishing the packages publicly