Go to file
Chris Wanstrath 6204f01912 helpers
2025-06-18 15:56:35 -07:00
.vscode 🆒 2025-06-16 09:27:35 -07:00
packages helpers 2025-06-18 15:56:35 -07:00
.bun-version this will make it better 2025-06-16 10:49:41 -07:00
.gitattributes 🆒 2025-06-16 09:27:35 -07:00
.gitignore 🆒 2025-06-16 09:27:35 -07:00
bun.lock Update bun.lock 2025-06-18 09:13:49 -07:00
main.ts new spike 2025-06-18 09:13:27 -07:00
package.json @the-rabbit-hole => @workshop 2025-06-16 22:16:00 -07:00
README.md new spike 2025-06-18 09:13:27 -07:00

Workshop Monorepo

We are making a bunch of smaller projects that occasionally rely on each other. So a monorepo makes a lot of sense! It lets us share code, and share dependencies with minimal fuss.

Ok, I want to add a new project.

  • bun init packages/WHATEVER_YOU_WANT
  • Edit the package.json and change the name to @workshop/WHATEVER_YOU_WANT

To add one of the existing packages as a dependency, edit the package.json and add it to the dependencies or devDependencies section. For example, if you want to add @workshop/WHATEVER_YOU_WANT, you would do:

{
  "dependencies": {
    "@workshop/WHATEVER_YOU_WANT": "workspace:*"
  }
}

Then run bun install and import it in your code like so:

import { something } from "@workshop/WHATEVER_YOU_WANT"

What does corey not love about this?

  • I put near-zero effort into naming things.
  • I'd prefer the namespace to be shorter, @workshop is a bit long.
  • There are lots things I don't love about nano-remix, but it works well enough for now.
  • The bun tailwind plugin doesn't work with nano-remix yet, but it looks like in a future bun release it will.

How do I run the tests?

😂