copybara VS storybook

sure! it used a collection of tools, the main ones were

* copybara [https://github.com/google/copybara] to mirror between github and our internal repo and transform the source tree layout to our internal conventions

* mercurial patch queues [https://hgbook.red-bean.com/read/managing-change-with-mercur...] to apply internal changes

there are internal tools to automate the copybara configuration for python packages specifically, and to map between mercurial and google's version control system, but that's the main idea, and a specific review process for adding new packages.

the process is actually documented here though not all the referenced tools are available (or even applicable) externally: https://opensource.google/documentation/reference/thirdparty...

Step two of installing Copybara is to install Bazel [0], so that doesn't exactly contradict my claim that if you're not already using Bazel you probably won't use Starlark.

[0] https://github.com/google/copybara

> Also, they have a bunch of tooling to manage open source projects that mirror google3 projects. ... if I recall correctly the tool itself was open sourced too.

https://github.com/google/copybara

You can potentially use CopyBara https://github.com/google/copybara

We go much further than CopyBara by syncing CI / CD pipelines, syncing review comments and so on.

We are considering launching GitSlice as product on its own. If you are interested, email me and I can keep you updated when its ready to test (hamza [at] gitstart [dot] com)

I haven’t seen much info regarding their setup, aside from the bits about Pants and Bazel.

Are those actually the upstream repositories, though? And is it known how they interact with them?

Google has Copybara [1], which allows portions of a monorepo to live outside as an entirely separate repository without the need for things like Git submodules. It supports synchronization of histories, pull requests, path and file transformations, etc.

In that sense, something like Copybara would allow them to, relatively, easily open source those bits, receive outside commits, and then sync the changes back to the monorepo.

[1]: <https://github.com/google/copybara>

Take a look at https://github.com/Olivr/copybara-action and https://github.com/google/copybara

I use copybara to sync them, and once I go through and audit them making sure that they're not causing any breaking changes, will release it and then update the code that depends on it.

Another option is to use Copybara (https://github.com/google/copybara) to create a light-weight version of the repo from the local repo, and then push that. The problem is that it will be push-only. You won’t be able to pull. Again, a pain in the ass.

Also you may want to try developing in a monorepo. If you need to publish them you can use stuff like Copybara / Copybara action to push them to individual repos

As a development server, we can use an actual development server of our app, like Create React App (that we use for the examples) or Vite, or another tool like React Styleguidist or Storybook, to test isolated components.

Source: qcatch on Feb 22, 2024 https://github.com/storybookjs/storybook/discussions/25470

[Bug]: Configuration with TailwindCss Next.js using Tailwind with Storybook

Astro has no runtime. This means no unit tests. This also means no Storybook for your Astro components (although, they’re working on it!)

If you're into UI development, then you need to know about Storybook. It's a frontend workshop for building UI components and pages in isolation. The latest version brings some big improvements for testing and documentation with built-in visual testing. There's also React Server Component support, improved controls for React and Vue projects, as well as improved Vite architecture, Vitest testing, and Vite 5 support. Check out all the major changes in the Storybook changelog.

Storybook

We are continuing to make building fullstack websites and application with Analog and Angular as seamless as possible, and extending the Angular ecosystem through integrations with Astro, Nx, [Vitest]https://analogjs.org/docs/features/testing/vitest, Storybook, and more.

Storybook is the industry standard UI tool for building, testing, and documenting components and pages. It’s used by thousands of teams globally, integrates with all major JavaScript frameworks, and combines with most leading design and developer tools.

Expo has first-class support for building full-stack websites with React, so I can leverage that to add Cypress/Playwright for E2E testing and add the Storybook for UI components.

Storybook emerges as a pioneering solution among React debugging tools, offering an interactive environment for developers to create and test UI components. With its robust platform, teams can build, organize, and design UI components, and even entire screens, without the hurdles of business logic and plumbing.