set up pkg.pr.new to install unreleased versions from github

[RJWadley]

when working on #1639 I found it very difficult to test out versions of the plugin in real projects

solutions I explored:

• you could clone the repository and install via a link, but this only works locally and can't really be committed.
• pnpm will let you install from github, but it doesn't support rewriting the workspace protocol on the fly
• gitpkg also lets you install from github, but similarly don't support rewriting the workspace protocol
• in theory, you could add the entire vanilla extract repository as a submodule, but that's incredibly difficult to manage
• you can clone and build using gitpick but this can cause issues across different computers if you want to actually deploy anything with the prerelease version, and it's also not very stable for development. it also breaks resolving for packages that assume they are installed in the working directory.

https://pkg.pr.new/ solves all of these by building the package normally in github actions.

It generates links you can use to install any version that was previously built:

"pnpm": {
  "overrides": {
    "@vanilla-extract/compiler": "https://pkg.pr.new/RJWadley/vanilla-extract/@vanilla-extract/compiler@43e5044",
    "@vanilla-extract/css": "https://pkg.pr.new/RJWadley/vanilla-extract/@vanilla-extract/css@43e5044",
    "@vanilla-extract/integration": "https://pkg.pr.new/RJWadley/vanilla-extract/@vanilla-extract/integration@43e5044",
    "@vanilla-extract/next-plugin": "https://pkg.pr.new/RJWadley/vanilla-extract/@vanilla-extract/next-plugin@43e5044",
    "@vanilla-extract/turbopack-plugin": "https://pkg.pr.new/RJWadley/vanilla-extract/@vanilla-extract/turbopack-plugin@43e5044",
    "@vanilla-extract/webpack-plugin": "https://pkg.pr.new/RJWadley/vanilla-extract/@vanilla-extract/webpack-plugin@43e5044"
  },
}

Note

A maintainer will need to install the GitHub application on this repository

[changeset-bot]

⚠️ No Changeset found

Latest commit: a385bc3

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