feat: ContextProvider

[abdel-17]

TODO: add docs

[changeset-bot]

⚠️ No Changeset found

Latest commit: e7c4fc3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
runed	✅ Ready (View Log)	Visit Preview	e7c4fc3

[huntabyte]

I imagine we want to make this an entirely separate thing from Context for code-splitting/reducing unnecessary things on the instance?

Feels like this would be a pretty tight touch:

import { Context } from "runed";

export const MenuContext = new Context<{ open: boolean }>('Menu')

<script lang="ts">
	import { MenuContext } from "./context.js"
</script>

<!-- value is typed -->
<MenuContext.Provider value={{ open: true }}>
	<!-- things... -->
</MenuContext.Provider>

Edit now that I am thinking about it more:
We'd need a way to pass the context somehow into that component on the user's behalf to make this even worth anything 🤔